Gilad Ben-Yossef wrote:
> This approach will allow in the future to throw out all the code in
> the kernel that has anything to do with finding the root file system,
> mounting NFS as root fs, kernel DHCP and IP setting (aka
> autoconfiguration) and replacing them will "early user space" - user
> space code compiled and linked against a mini-libc like library called
> klibc.
That much I have heard before. What I totally fail to understand is why
this is any different than initrd. Reasons I don't see any difference:
- The kernel did not have to find initrd either - it was loaded by the
boot loader
- Initrd contained the code to do all the above too. If there ever was
any such code inside the kernel (and I know that at least DHCP was
there), initrd could have made it redundant anyways.
- Iniramfs will save us the need to compile cramfs into the kernel
statically, but instead will require us to compile cpio and tmpfs
statically.
- The initramfs would still need to be generated after the kernel is
compiled, or else we go back to requiring an initrd IN ADDITION to the
initramfs, to store all the modules relevant for mounting root.
In short, I don't understand why a new technology was necessary.
Shachar
--
Shachar Shemesh
Lingnu Open Source Consulting ltd.
Have you backed up today's work? http://www.lingnu.com/backup.html
=================================================================
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]
