Don't forget that initrd can also proceed to an NFS-mounted root. Putting
all the tools needed for this (ifconfig, route, perhaps some BOOTP/RARP
client, mount) onto an initrd is certainly a good idea, but you want to
take some time for careful testing of all cases before removing the old
procedure(s).
Also, with exec chroot /mnt ... , can you get rid of initrd afterwards ?
/ should be busy because of /mnt, so you're stuck without something like
the magic in change_root. This is particularly bad on systems with a big
initrd which always need it to boot (i.e. not just during installation).
I'm sure somebody out there must have a notebook with the hard disk on
PCMCIA or such ...
- Werner
-- _________________________________________________________________________ / Werner Almesberger, DI-ICA,EPFL,CH werner.almesberger@lrc.di.epfl.ch / /_IN_R_131__Tel_+41_21_693_6621__Fax_+41_21_693_6610_____________________/- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu