Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 06 Jun 2003 00:50:50 -0700
From:      Terry Lambert <tlambert2@mindspring.com>
To:        Peter Wemm <peter@wemm.org>
Cc:        "Matthew D. Fuller" <fullermd@over-yonder.net>
Subject:   Re: Making a dynamically-linked root
Message-ID:  <3EE047DA.850261F0@mindspring.com>
References:  <20030606063105.D3B442A8C1@canning.wemm.org>

next in thread | previous in thread | raw e-mail | index | archive | help
Peter Wemm wrote:
> "Matthew D. Fuller" wrote:
> > If a static /sbin/init gets hosed, you're screwed.
> > If a dynamic /sbin/init gets hosed, you're screwed.
> >
> > If /lib/libc gets hosed, your dynamic /sbin/init is screwed.  Your static
> > /sbin/init still moves along just fine.
> 
> Which is why /rescue/init is on the fallback init path, and can be explicitly
> entered at the loader prompt.  Right now it is:
> kern.init_path: /sbin/init:/sbin/oinit:/sbin/init.bak:/stand/sysinstall
> 
> And nothing would be stopping somebody from typing this at the loader:
> set kern.init_path=/rescue/init
> and at the shell path prompt, /rescue/sh

The /rescue, to my mind, is just a gratuitous renaming of /stand.

It also fails to make the dynamic linking argument strongly enough,
IMO.  That's why I'm trying to avoid invoking the "and then a
statically linked miracle happens"...  8-).

-- Terry



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3EE047DA.850261F0>