> I just want to make sure we aren't considering losing the option of
> booting to single user mode.
>
You seem to not understand what single user mode is.
In System V, the only services missing in single user mode compared to
multi-user mode are login services, such as getty, gdm, sshd, etc. It's
not intended as a "recovery" mode.
A modern Linux system needs running services to function even at a basic
level. This, and the misuse of "single user mode", is where the current
friendly recovery design falls over and fails.
For example, the recovery menu is on /usr. If /usr is on a network
filesystem mount, you need a large number of services: udev, dbus, hal,
network-manager, portmap, rpc.statd, etc.
These will all be running off the root filesystem, and thus prevent it
from being checked.
Scott
--
Scott James Remnant
<email address hidden>
On Tue, 2009-10-20 at 08:40 +0000, ski wrote:
> I just want to make sure we aren't considering losing the option of
> booting to single user mode.
>
You seem to not understand what single user mode is.
In System V, the only services missing in single user mode compared to
multi-user mode are login services, such as getty, gdm, sshd, etc. It's
not intended as a "recovery" mode.
A modern Linux system needs running services to function even at a basic
level. This, and the misuse of "single user mode", is where the current
friendly recovery design falls over and fails.
For example, the recovery menu is on /usr. If /usr is on a network
filesystem mount, you need a large number of services: udev, dbus, hal,
network-manager, portmap, rpc.statd, etc.
These will all be running off the root filesystem, and thus prevent it
from being checked.
Scott
--
Scott James Remnant
<email address hidden>