Alex Holden wrote:
> The initial RAM disk tftp support is effectively a complete kernel-space
> TFTP client implementation, configured to load the initial RAM disk with a
> file (currently specified at compile time) obtained from a TFTP server.
Funny, this is precisely the kind of hacks initrd was designed to
obsolete ;-)
If all you want is another RAM disk, you could just put all the tools
you need to download it on an initrd, then construct the RAM disk, and
then mount that one as root. Unless you're really badly limited for
space, this (i.e. a stripped-down user space tftp) should be a lot more
convenient to maintain.
Now, if you need yet another level of indirection, e.g. "static" initrd
-> "variable" initrd -> real root, then you exceed the current design.
I find it somewhat difficult to imaging a case where you absolutely
need to have a full root FS in the middle step, though. (As opposed to
copying some scripts, etc.)
- Werner
-- _________________________________________________________________________ / Werner Almesberger, ICA, EPFL, CH werner.almesberger@ica.epfl.ch / /_IN_N_032__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 Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Jan 15 2000 - 21:00:12 EST