5.3: /stand/ versus /rescue/ ?
kientzle at freebsd.org
Sun Oct 3 13:08:14 PDT 2004
/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.
spam maps wrote:
> On my cvs-updated 5.3 system I have /stand/ and
> /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
> I notice following differences. Files and directories
> that are in /stand/, but not in /rescue/:
> Moreover, for those files that are in both, the
> ones are obviously older than the ones (from cvsup
> process) in /rescue/.
> Do you Yahoo!?
> Declare Yourself - Register online to vote today!
> freebsd-current at freebsd.org mailing list
> To unsubscribe, send any mail to "freebsd-current-unsubscribe at freebsd.org"
More information about the freebsd-current