help-hurd
[Top][All Lists]
Advanced

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

Re: Hurd FS hierarchy (was Re: LD_LIBRARY_PATH troubles)


From: kreuter
Subject: Re: Hurd FS hierarchy (was Re: LD_LIBRARY_PATH troubles)
Date: Tue, 19 Mar 2002 21:58:55 -0500
User-agent: Mutt/1.3.27i

On Tue, Mar 19, 2002 at 02:52:50PM -0800, Thomas Bushnell, BSG wrote:
> Richard Kreuter <kreuter@ausar.rutgers.edu> prompted a little:
> > On Tue, Mar 19, 2002 at 12:20:15AM -0800, Thomas Bushnell, BSG wrote:
> > > Andreas Voegele <voegelas@users.sourceforge.net> writes:
> > > > But programs should not be left in /sbin for historical reasons.
> > > 
> > > Well, some scripts *do* refer to things by absolute path, so if they
> > > are moved, then a symlink does not to be retained.
> 
> s/does not/does need/
> and they refers to the programs being moved from sbin to bin or vice
> versa.

  So for compatibility, we should populate /sbin with a symlink for
lots of binaries.  It's ugly, but it does accomodate the goals:

1) /bin contains binaries that a normal user will want to run,

2) /sbin contains binaries for the superuser.


  Related: some of the residents of Debian GNU/Linux's /sbin might or
do qualify for /libexec; getty is already there.  Presumably, any
candidates for /libexec should also be moved and linked, for
compatibility?  


Thanks,
Richard





reply via email to

[Prev in Thread] Current Thread [Next in Thread]