Tiny Core Linux

Tiny Core Base => TCB Q&A Forum => Topic started by: robc on April 27, 2009, 06:51:04 PM

Title: root PATH on startup
Post by: robc on April 27, 2009, 06:51:04 PM

When I add the following line to bootlocal.sh

Code: [Select]

echo $PATH > /home/tc/path.txtthe results yield

Code: [Select]

/sbin:/usr/sbin:/bin:/usr/binBut when the echo command is used after JWM is up the local directories are added to the PATH.

Code: [Select]

/usr/local/bin:/usr/local/sbin:/usr/sbin:/usr/bin:/sbin:/bin
Is this done by design?

I ask this because it causes one to include the full path when running a command with bootlocal.

On another note I just found the time the other week to create a remaster of TC v1.3...but then the alpha for 2.0 just came out...you guys are working too fast!  ;)

Keep up the good work

Title: Re: root PATH on startup
Post by: mikshaw on April 28, 2009, 11:07:56 AM

I think it is done by design, since files in /usr/bin are typically not associated with the boot process, and /usr/local is empty in a default TC system.

Title: Re: root PATH on startup
Post by: robc on April 28, 2009, 02:39:44 PM

Quote

files in /usr/bin are typically not associated with the boot process, and /usr/local is empty in a default TC system

I understand this, but bootlocal.sh is ran after extensions are loaded, and many extensions need initial setup or daemons to run. i.e. setserial, lirc (not in the repository, yet), ftpd, etc.

I'm not saying this is a big deal, I just wanted others to know because it took me a few minutes to realize this.