Hi, Mike. On Wed, Mar 28, 2012 at 12:24:14AM -0400, Mike Edenfield wrote: > > From: Alan Mackenzie [mailto:a...@muc.de]
> > Hi, Alan. > > On Tue, Mar 27, 2012 at 11:48:19PM +0200, Alan McKinnon wrote: > > > On Tue, 27 Mar 2012 21:24:22 +0000 > > > Alan Mackenzie <a...@muc.de> wrote: > > Why is nobody else on this thread willing to take up its main point, > > the exact equivalence between the known, ugly, initramfs solution and > > the as yet half-baked idea of putting the same binaries into /sbin? > Well, for one, the initramfs solution is not generally considered "ugly" > except by a select vocal few who object to it on vague, unarticulated > grounds. I'll articulate a few. (i) The initramfs involves having two copies of lots of software around. (ii) What's more, these two copies are often different, one being built with static libraries, the other with dynamic ones. (iii) This situation is not (as far as I know) yet handled by Portage, which means in building such software statically, you've got to save the dynamic version somewhere else whilst you're doing it. (iv) The initramfs requires a potentially long script to make it work. I think that qualifies the initramfs solution as ugly. > That notwithstanding: > The binaries on the initramfs are not always the same as the ones installed > in the system; frequently they are statically linked versions, or > stripped-down versions, or otherwise unsuitable for being used after the > full system is booted. (Dracut, for example, forces you to add > USE=static-libs to a lot of the packages it wants to put into your initramfs > image.) Putting those binaries into the execution path of the system is a > bad idea because you don't always them to run once the system has booted -- > I want the full set of udev rules, not the bare handful that my initramfs > has on it. My idea was for /sbin to vanish from $PATH just as soon as the boot had been completed; PATH gets set anyway on the initialisation of something or other, so this would happen automatically, just like the initramfs disappears when the switch_root is done. > [ more criticism, a lot of which I accept. ] I think I have the elegant solution: that would be for the kernel to be able to mount several partitions at system initialisation rather than just the root partition. With this, all the issues we've been discussing simply wouldn't arise. I accept that this solution will never happen. Sadly. > --Mike -- Alan Mackenzie (Nuremberg, Germany).
