Using Initrd Dynamic a person can boot with a ramdisk as their primary
root, populating it with tar.gz archive(s). Making 'image' changes works
very well and in a modular way. (IE root.tgz, etc.tgz)
With this release you can now forgo an internal mkfs on /dev/ram0 before
archive extraction and go straight to a truly dynamic tmpfs VFS as the root
without the minix FS limitations.
Now, could you please explain to me how the hell you boot to a tmpfs
root from userland!?!? This feature *creates* your userland.
Maybe you're just confused what this feature does. Maybe you've never
worked with systems that run a volatile root. Maybe you've just never made
a boot disk.
Maybe you even think it's sane to compile userland into the kernel? <snicker
snicker> I just looked at your initramfs. From what I see it's the same
scheme I used to use In the Linux Router Project before I wrote
initrd-archive. Except I did it *entirely* in userland back in 1997. It
sucked. Badly.
> _Please_, let's stop
> adding complexity to already ridiculously bloated late boot stages.
It's funny you've refered to my patch as bloated. What you've wrote (which is
a limited solution) weighs in at ~122k. Initrd Dynamic is ~35K complete and
that includes ~7K of mkfs_minix, which can be removed when use Linux 2.4 with
tmpfs (and ~2K of Configure.help : > ). Compiled up it add only ~3K to the
kernel size, and as for boot complexity, I agree lets reduce it. Leave it
up to the bootloader to populate initrd memory space, or let a specific
driver tie the initrd file handle to a device to load from. Initrd Dynamic
is made to work this way and is (should be) entirely platform independant
code.
One day I hope someone finally implements loading kernel modules from
'initrd' type memory space, again leaving the job of getting them their to
the boot loader. (Actually it's called the multi boot standard and GRUB boot
loader has supported it for 3(?) years.)
> David, no offence, but let's do it the right way.
It is done right. Infact, I'm proud that this release finally has implemented
it to perfection for the purposes it was designed. It took 3 years
to get to this point of a completly dynamic, modular, ram based root.
It never fails, post a patch to kernel and they come out of the wood work
with delusional bitching. This is one reason I sat on releases for 9 months.
BTW Offence intended...
Dave
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/