On Monday 03 November 2008 00:26:30 Michael D. Setzer II wrote: > I have the g4l project that uses busybox plus a number of other programs. > A number of the additional programs I was building and installing manually > into directories in the path. As it turns out, some of the programs make > install puts the files in the /usr/local/bin or /usr/local/sbin. > > I then wrote a little script that will compare the files in my build > directory, to the systems to see if the files have been updated, and show > what is different. I then moved the files from there old locations to the > new /usr/local directories. I had found a web page saying the /usr/local > directories are part of the standard path. But a test of the new build > fail, and checking the path showed the /usr/local were not part of the path > with the boot. > > I added an export to command to the .bash_profile to fix the issue, but was > wondering if there is a better way, or if this is how things are suppose to > be. Not sure where the PATH value is set.
We usually inherit one in the environment from whatever program ran us. We used to use _PATH_STDPATH out of /usr/include/paths.h but now there's a hand-wired definition of bb_PATH_root_path[] in libbb/messages.h for some reason, and that's what ash sets its varinit_data[] to. If it's ever checking the environment it inherits to see if PATH is already set, I can't find where... Rob _______________________________________________ busybox mailing list [email protected] http://busybox.net/cgi-bin/mailman/listinfo/busybox
