On Sat, Sep 07, 2013 at 05:40:27PM -0700, Pwn Me wrote: > i have a question.. > > > > how can i edit the PATH="tools/bin:/bin:/usr/bin" to > PATH="tools/bin:/bin:/usr/bin:/tools/sbin:/sbin:/usr/sbin"? > > 'coz i tried to use "export" to edit this command and when i reboot the > system, the "PATH" thing goes back to the original syntax.. :/
After looking at the name you use for your email account, I have to ask "why don't you just run everything as root ? - it will make it much easier for people to own your system" ;-) I'm joking, but I start to wonder if you are trolling. For a safer system, limiting privileges is a good idea. To shut down a *desktop* box, I'm happy using a hack to let a user run 'shutdown' - but I'm the only user of those machines, and I can only run the user shutdown script from a tty (not an xterm, nor when using ssh to connect to a system). Some other people use 'sudo' and allow (some) normal users to shutdown, others run desktop environments where ConsoleKit gives permissions to whoever is at the physical machine. Every alternative method has its own advantages an disadvantages. Also, the /tools part of the PATH should be unnecessary after you have completed chapter 6 of LFS. If you need to go back in to chroot to edit some files, chroot /mnt/lfs should work fine - if it doesn't, you've got other problems. In any case, why would you prefer to run the programs from /tools/sbin in preference to /sbin or /usr/sbin ? - hint: a program will be run from the first directory which contains a program of that name. ĸen -- das eine Mal als Tragödie, dieses Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
