Typical embedded initrds do fairly disgusting tricks to "work around"
the limitations of themselves. These tricks are solved cleanly by
initramfs, but I'll guess that the reason embedded people will complain
is because it is different, and embedded people don't like to unlearn
old tricks.
Here's two things that initramfs does that there is no way in hell an
initrd can ever do:
- once you've finished with various stuff, you can remove it and
thereby free up the space that file was occupying for use by anything
without having to wait for the whole filesystem to become unused.
- there's no need to mount a ramfs filesystem, or a blockdev /dev/ram
ext2fs-formatted filesystem for /tmp, /etc or /var/run (etc) since
/ is already a ramfs filesystem, thereby removing:
+ extra symlinks for writable files in these directories
+ extra mount points (with associated kernel structures)
+ ext2fs
+ rd
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
-
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/