Re: Rescue mode

["Alexander Maryanchick" <Sasha@GDev.msk.ru>]

>> -  to show rescue menu only in two cases:
>>     - The previous boot failed.
> Define "failed".
Two (or more) variants (analogs for "FS was not cleanly unmounted"):
- Crashed. (Flag "ShutdownSuccessful" is not set)
- Flag "BootSuccessful" is not set. (For example, login, xdm,... not crashed
in 5 second)
A kernel issue!

>> - to have always ready to use system image (kernel, startup scripts,
etc.).
> A distribution issue.
Nope. See below.
>> - updated automaticaly after every successful configuration change.
A kernel issue. It requires reliable "BootSuccessful" flag.

> Define "successful configuration change".
1. Critical files was changed (not the same in root and rescue image)
2. At least one boot was not failed (the definition was given ealier)

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.

> Given a definition, I am sure you can easily implement a method to copy
> whatever you consider to be the necessary configuration information to
> wherever LILO knows to look for it.
Yes, I can implement an ugly hack, but I can not implement
even 100% of windows rescue mode functionality. Am I wrong?
IMHO, if feature is worse then in mustdie - then the feature is absent.


                Thank you.
                Best regards.

                                Alexander.

-
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