Subject: Re: RFC: migration to a fully dynamically linked system
To: Luke Mewburn <email@example.com>
From: Manuel Bouyer <firstname.lastname@example.org>
Date: 08/22/2002 20:05:15
On Thu, Aug 22, 2002 at 01:56:37PM +1000, Luke Mewburn wrote:
> Sure, but now we're starting to drag strawman cases out of the wood-work.
> In the past, it was very easy to screw a system so you couldn't recover
> without falling back to separate boot media/mechanisms:
> - Missing /dev/console
> This is now fixed with the mfs-/dev workaround, assuming your
> box has enough memory to cope, which 99.9% of NetBSD machines
> do. (8MB I think)
> - Missing or corrupt /sbin/init, /sbin/init.bak, /sbin/oinit.
> Oops :) (No easy solution yet)
> I have just committed a bunch of stuff to enable the building and
> installation of /rescue, which contains all of the stuff from /bin
> and /sbin (as well as gzip, bzip, ldd, ktrace, kdump, ...)
> If something goes wrong with the applications in /bin or /sbin, you
> can prepend /rescue to your PATH and resolve your problem.
> The change to a dynamic /bin and /sbin (with /sbin/init static),
As long as /sbin/init is static, and we have static tools available
with the base install I'm happy :)
Manuel Bouyer <email@example.com>