Grover, Andrew wrote:
[...]
> I'm arguing that no matter
> how whizzy
> initrd is, it's still an unnecessary step, and it's one that
> other OSs (e.g.
> FreeBSD) omit in favor of the approach I'm advocating.
Well, I'm a linux user more than a developer but I disagree.
It isn't hard to make an initrd, and initrd will always be
neccessary for some things. Since we can't get rid of it
and don't want to (*), I like the approach of making it better.
* I network boot (via pxelinux boot loader) a linux kernel and
initrd.gz, total size <2 MB, which then proceeds to:
1 - load network drivers, do dhcp
2 - partition and format the hard disk
3 - mount the new filesystems
4 - download (with retry/resume), unpack, cryptographically
verify, and install a complete (~100 mb) embedded linux
system.
5 - while it does all the above, it shows pretty graphics and
"please wait while we setup your system" messages on the
attached television set via framebuffer support.
You may be able to get grub to do the first step but the next
four would be... challenging. I agree that grub is cool, though.
Torrey Hoffman
-
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/
This archive was generated by hypermail 2b29 : Sun Dec 23 2001 - 21:00:17 EST