Re: 5.3: /stand/ versus /rescue/ ?

/stand is largely defunct.  It is, I believe,
still used to bootstrap the CD-ROM installation, but
has no particular purpose after that point.

Most of these do have counterparts in /rescue
(e.g. -sh is redundant with sh, minigzip is
redundant with gzip, cpio with pax/tar, etc.)

sysinstall is in /usr/sbin now.

The point of /rescue is to provide a reliable
environment from which a broken /bin and /sbin
can be repaired.  That seems to boil down to
basic tools for locating and copying files
from various sources (to replace a hosed
shared library, for instance).

If there are things that should be in /rescue that
would be needed in certain scenarios, feel free to
propose additions or changes to /rescue.  Be prepared
to nominate deletions as well; very many people
think that /rescue is already too large.

Tim

spam maps wrote:
> Hello,
> 
> On my cvs-updated 5.3 system I have /stand/ and
> /rescue/.
> 
> /rescue/ is updated according to cvsup/makeworld etc.,
> but /stand/ is not. Is /stand/ becoming redundant?
> Should these two directories be merged into a single
> /rescue/?
> 
> I notice following differences. Files and directories
> that are in /stand/, but not in /rescue/:
> 
>     /rescue/-sh
>     /rescue/arp
>     /rescue/boot_crunch
>     /rescue/cpio
>     /rescue/find
>     /rescue/minigzip
>     /rescue/ppp
>     /rescue/sed
>     /rescue/sysinstall
>     /rescue/usbd
>     /rescue/usbdevs
>     /rescue/etc/
>     /rescue/help/
> 
> Moreover, for those files that are in both, the
> /stand/
> ones are obviously older than the ones (from cvsup
> process) in /rescue/.
> 
> Regards,
> Rob.
> 
> 
> 		
> _______________________________
> Do you Yahoo!?
> Declare Yourself - Register online to vote today!
> http://vote.yahoo.com
> _______________________________________________
> freebsd-current_at_freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org"
> 
>