WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: root PATH on startup  (Read 2184 times)

Offline robc

  • Sr. Member
  • ****
  • Posts: 447
root PATH on startup
« 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
"Never give up! Never surrender!" - Commander Peter Quincy Taggart

"Make it so." - Captain Picard

Offline mikshaw

  • Sr. Member
  • ****
  • Posts: 368
Re: root PATH on startup
« Reply #1 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.

Offline robc

  • Sr. Member
  • ****
  • Posts: 447
Re: root PATH on startup
« Reply #2 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.
"Never give up! Never surrender!" - Commander Peter Quincy Taggart

"Make it so." - Captain Picard