[lkml]   [1998]   [Apr]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: initrd vs. chroot
Hi Werner.

===8<=== On the subject of initial ramdisk ===>8===

> 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 ...

Perhaps somebody could turn that into a ROMFS option?

Best wishes from Riley.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to

 \ /
  Last update: 2005-03-22 13:42    [W:0.041 / U:1.484 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site