Observations and suggestions for /etc/profile

codeguy · 05-25-2015, 07:40 AM

I'd like to see a small rc.6 change:

from:

Code:

echo "Sending all processes the SIGTERM signal."

to:

Code:

echo "All your processes are belong to SIGTERM!"

:-)

genss · 05-25-2015, 09:38 AM

Quote:

Originally Posted by XavierP

The thread has now returned to being a normal LQ thread Complete with thread jack to make it completely authentic.

to be a 100% proper LQ Thread™ it also has to age in the cold depths for at least a year then be resurrected by a novice necromancer

Richard Cranium · 05-25-2015, 08:09 PM

Quote:

Originally Posted by Alien Bob

I don't know how the original topic of dissecting the user profile configuration deranged into a discussion to change how the Slackware installer works?

I believe that people couldn't figure out why PATH contains directories with /mnt in them.

(I guess that I should have waited a year or two to post that.)

ttk · 05-25-2015, 08:34 PM

One of the first things I do when installing a new machine is fix the PATH for non-root users to include /sbin and /usr/sbin. It always takes me by surprise when I try to use ifconfig, ifstate, route, et al as a regular user and get a "command not found" error (or, in the case of bwtrack, which wraps ifconfig, wrong output).

Is there a compelling reason we can't simplify the PATH-setting logic to a single line?

Quote:

PATH="/usr/local/sbin:/usr/sbin:/sbin:/usr/local/bin:/usr/bin:/bin:/usr/games"

GazL · 05-26-2015, 04:49 AM

There are many things in {/usr,}/sbin that are simply not intended to be used by end users, so it makes sense not to have sbin in the users PATH. For the few exceptions that might be dual purpose, perhaps symlinking in the same manner as sendmail (/usr/bin/sendmail -> ../sbin/sendmail) is a better choice.

If you write a wrapper/shell-script then you really shouldn't assume anything about PATH. I'd suggest bwtrack is at fault for doing so in the example you gave.