The syslinux.cfg file on the Bering disk I used as a starting point (the latest release version 1.2) sets init=/linuxrc, which seems sort of pointless, since /linuxrc is automatically run when using an initial ramdisk, and the linuxrc script currently directly calls /sbin/init.
I'm also wondering why /linuxrc doesn't simply exit and allow the kernel to launch init from the (now fully created) ramdisk filesystem.
This would remove the need to specify init= on the kernel command line (saving a few characters), and allow standard linux tricks (like setting init=/bin/sh).
If there are no objections, I'll set linuxrc up to work this way (which I don't think will require anything more than echoing 256 to /proc/sys/kernel/real-root-dev and exiting linuxrc rather than executing /sbin/init, along with removing the init= kernel command line setting).
-- Charles Steinkuehler [EMAIL PROTECTED]
------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
