On Sat, Nov 09, 2002 at 04:26:52PM +0100, Robert Millan wrote: > If a program hard-codes /sbin it means that it's being run as normal > user (without /sbin in PATH) but still needs that utility. so it's > just a workaround for the problem which is the lack of the utility > in users' PATH.
No, the reason to hard code is to make absolutely sure that you get this one executable, independent of the current PATH setting. This is usually quite reasonable for security reasons. Another way to solve this is to override PATH in the program to something secure. > I guess the debian-devel people wouldn't like to set symlinks either. I guess they wouldn't like moving them in the first place. Thanks, Marcus -- `Rhubarb is no Egyptian god.' GNU http://www.gnu.org [EMAIL PROTECTED] Marcus Brinkmann The Hurd http://www.gnu.org/software/hurd/ [EMAIL PROTECTED] http://www.marcus-brinkmann.de/
