Quoth Douglas A. Tutty: > On Wed, Jan 16, 2008 at 01:39:51PM +0100, ???????????????????? ??. > ???????????????? wrote: > > No, the Kernel doesn't depend on those libraries. Evenything you need to > > boot a > > machine is in /boot and /lib/modules/`uname -r`. From then on, any > > init-process > > may get called, which will most likely depend on _a lot_ of libs, but that's > > fine. > > > There's and advantage to having some kind of static-linked shell (at > least). There used to be busybox static and now there's sash. You > would start it (and bypass the standard lib-dependant init scripts with > a kernel command line that contains: > > init=/bin/sash
That's absolutely right. Combined with GRUB's ass-kicking ability to edit the kernel command (actually, the whole freaking _boot-sequence_) on the fly, this has saved my life a couple of times on all sorts of machines (I had this fuck-up in Gentoo once where glibc was FUBAR'ed and this came in really handy.) Typically, though, you won't need that on a Debian system as a normal user. Most people wouldn't be able to get their environment working in busybox (never tried sash, thanks for the tip) - you have to mount proc and dev you have to load modules, probably set the terminal keymap, get networking to run, etc. Not that it's particularly hard, but it's not what you would do every day, so you have to really konw your way around the system (and probably be able to use Google). It shouldn't be needed, too, except you did something very kinky with your libs - in which case most users would probably go for a reinstall instead of trying to figure out what's broken and how to fix it. Aleks
signature.asc
Description: Digital signature
