On Sun, 27 Nov 2005, [EMAIL PROTECTED] whispered secretively: > Plus, for deep troubleshooting (mainly for kernels) init=/bin/sh is useful.
init=/bin/busybox/sh is also useful for those cases when you've futzed your libc. :) >> > No - the kernel doesn't allow storing the full set of infos which are >> > added by mount there. And frankly I don't want the kernel to do that. > >> Why not? It should. Only root can call mount(), so there's no real >> danger that some attacker will stick megabytes of stuff in there. > > Yep, but I don't like the kernel to become a configuration repository... it's > conceptually similar to the in-kernel Win32 registry (though it's smaller, > yep). Well, except that it's just storing, er, data about mount points. It *already* has to store that! -- `Y'know, London's nice at this time of year. If you like your cities freezing cold and full of surly gits.' --- David Damerell ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ User-mode-linux-devel mailing list User-mode-linux-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
