Re: itp: static bins / resolving static debian issues
Some of you may have missed the mounds of earlier discussion. The
point of "live recovery" is to recover the system WITHOUT requiring
a reboot, therefore any boot disk or LILO solution is not acceptable.
Suppose you screw something up, but your database and webserver are
still linked and loaded. Why bring them down?
You need to get a root shell WITHOUT a reboot. So you need roots
shell to be static, and you need a static su, and a static sulogin.
On Thu, Aug 19, 1999 at 09:37:24AM +0200, Ruud de Rooij wrote:
> Justin Wells <firstname.lastname@example.org> writes:
> > OK. Then ash should be installed and it should be static, and that
> > should be root's shell. If you are going to succeed in live recovery,
> > there *MUST* be a way to get yourself into a static shell as root.
> > If root's shell isn't static, then how do you do that? I think you
> > also need static su and sulogin.
> Type "linux init=/bin/sash" at the bootloader prompt.
> If you want to be able to log in as root while the system is up but
> has a broken libc, then you need a static init, getty, and login, as
> well. And inetd and telnetd or sshd if you want to do it remotely.
> And so on...
> - Ruud de Rooij.
> ruud de rooij | *@spam.ruud.org | http://ruud.org