[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#36151: Clearing out old policy proposals

On 21-Jun-01, 17:33 (CDT), Julian Gilbey <J.D.Gilbey@qmw.ac.uk> wrote: 
> Scripts which use programs in a directory other than /usr/bin and
> /bin (and /usr/bin/X11?) should append that directory to the PATH

I'd really like to see the list expanded to include /sbin and /usr/sbin
as well. My rationale is that init.d scripts are intended (and mostly
only useful) for the root user, and the the whole point of /sbin
and /usr/sbin is to contain scripts useful for the root user. It is
completely reasonable to assume that those directories are in the path,
and my opinion is that if they aren't, the admin needs to fix their

(Yes, this is the same argument from debian-devel when we had this
discussion originally. The counter-argument is to "protect the admin
from making a dumb mistake." The counter-counter-argument is that an
admin who can't manage to keep a sane path in the root account needs to
be running MacOS, not Linux. Please proceed from here.)

As a particular point, note that if they are not considered "standard",
most init.d scripts will have to be modified add them to the path, as
start-stop-daemon is in /sbin.


Steve Greenland <stevegr@debian.org>

Reply to: