Once upon a time, Avi Kivity <avi(a)argo.co.il> said:
We require /. We require initrd.
initrd is not currently required. It is for out-of-the-box setups, but
you can:
a) not use LVM for root
b) not use ext3 for root or rebuild kernel with ext3 included
c) use hardware that doesn't require modules for root device or rebuild
kernel with drivers included
I'm sure we can arrange initrd to look at the command line. For
example:
mount=/=server1:/path/to/root,/usr=server2:/path/to/usr
IP can already be configured this way.
That's a pretty ugly hack just to get python support for startup. Also,
that is limited; the kernel command line has a limit that isn't all that
big. You also then need to handle fsck and such in initrd for
non-network filesystems.
--
Chris Adams <cmadams(a)hiwaay.net>
Systems and Network Administrator - HiWAAY Internet Services
I don't speak for anybody but myself - that's enough trouble.