Is anyone using the load_ramdisk= option in the kernel still?

[H. Peter Anvin]

Hi all,

I've come to the conclusion that in order to stay backwards
compatible while moving root-mounting stuff to userspace, in the
initial patch everything in prepare_namespace() and south needs to be
fully supported in userspace.  This looks perfectly doable, but is a
fair bit of work.

The one piece of ugliness I've encountered has to do with the
load_ramdisk= option; this causes a ramdisk to be loaded from an
external device, usually a floppy.  The ugliness has to do with the
fact that it requires the kernel itself to deduce the size of the
ramdisk, which is filesystem-specific.  Although this code is
currently run for initrds as well, it doesn't need to, since the
kernel knows the size of an initrd.

This code isn't complex by any means, but it's ugly and complex, and
I'm trying to make something a bit cleaner than just copying the
existing in-kernel code to userspace.

So, in short:

a) Does anyone use the load_ramdisk= option anymore, or is it
legitimate to drop?

b) If it is necessary to retain, does anyone care if this option would
only support gzip format in the future, i.e. NOT support uncompressed
filesystem images?  Since a gzip stream is self-terminating, this
takes care of the problem of finding the end, but adds a sizable chunk
of code to the kinit binary.

	-hpa

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/