Date: Wed, 19 Nov 2003 09:25:33 -0800 From: Marcel Moolenaar <marcel@xcllnt.net> To: Ken Smith <kensmith@cse.Buffalo.EDU> Cc: freebsd-current@freebsd.org Subject: Re: Unfortunate dynamic linking for everything Message-ID: <20031119172533.GB9066@dhcp01.pn.xcllnt.net> In-Reply-To: <20031119142535.GA27610@electra.cse.Buffalo.EDU> References: <200311182307.hAIN7Wpm000717@dyson.jdyson.com> <20031118164905.R35009@pooker.samsco.home> <20031119141059.GA14308@madman.celabo.org> <20031119141950.GA95734@ussenterprise.ufp.org> <20031119142535.GA27610@electra.cse.Buffalo.EDU>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Nov 19, 2003 at 09:25:35AM -0500, Ken Smith wrote: > On Wed, Nov 19, 2003 at 09:19:50AM -0500, Leo Bicknell wrote: > > > To boot a machine into single user mode you need a kernel, init, > > and /bin/sh (minimally). > > Roughly the same thing was bothering me last night. You get a chance > to specify the shell when init is in the last phase of getting you to > single-user mode so you can say /rescue/sh at that point. init is > another story and I asked someone about that, they said it either is > or will shortly be a loader option so you can override that to be > /rescue/init that way. set init_path=/rescue/init It's rather non-intuitive. It works, but having a static /sbin/init avoids having to muck around in the loader in order to get to the rescue bits. If you need the rescue bits, you pretty much always need to use /rescue/init anyway. A dynamicly linked /sbin/init just makes it harder to get to the rescue bits, so it makes sense to link init(8) staticly. Especially since there's no advantage to dynamic linking init(8) that compensates for the inconvience. -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031119172533.GB9066>