initrd and noinitramfs.c -- the saga continues

["Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>]

  just perusing the simple code in init/noinitramfs.c, which is
what's invoked if you choose not to build in initrd support:

static int __init default_rootfs(void)
{
        int err;

        err = sys_mkdir("/dev", 0755);
        if (err < 0)
                goto out;

        err = sys_mknod((const char __user *) "/dev/console",
                        S_IFCHR | S_IRUSR | S_IWUSR,
                        new_encode_dev(MKDEV(5, 1)));
        if (err < 0)
                goto out;

        err = sys_mkdir("/root", 0700);
        if (err < 0)
                goto out;

        return 0;
	...

so, if you choose not to select initrd support, then the above trivial
initial root filesystem better be everything you need to completely
finish the boot process, right?  i just want to make sure i'm not
overlooking anything subtle.

rday

========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA

http://crashcourse.ca
========================================================================

--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx
Please read the FAQ at http://kernelnewbies.org/FAQ