Re: Rescue mode

[John Kodis <kodis@jagunet.com>]

On Sun, Mar 07, 1999 at 06:24:28PM +0300, Alexander Maryanchick wrote:

> Mustdie(TM) uses another method.  In rescue mode it ignores
> non-critical conf. files (autoexec) at boot and at run time and
> non-critical drivers (recognized by flags in header).  This way is
> also a kernel issue.

I think that what you're asking for is there already.  My box has two
kernels -- 2.0.xx, as supplied by Redhat, and 2.2.x, which boots by
default -- and lilo stanzas for each.  No matter how broken a new
kernel may be, I can always boot the original 2.0 kernel (LILO:
linux-2.0).  No matter how broken my configuration is, I can always
boot the 2.0 kernel in single-user mode (LILO: linux-2.0 single) and
fix things.

Most of the things beyond this that you are asking for are user-space
issues.  It sounds like you're mistaken about which of the boot-time
activities are kernel issues and which are user-space concerns.  Watch
a typical boot sequence: everything after the line that says something
like "INIT: v1.2.3 starting..." is a user-space issue.

-- John Kodis.

BTW, what does Mustdie(TM) refer to?  I'd guess it's one of the MS
O/S's, but it's not clear which one or ones you mean.
-
Linux-future: thinking about the future of the Linux kernel
Archive:      http://humbolt.nl.linux.org/lists/
Wish list:    http://users.ox.ac.uk/~mert0236/linux-future.html