[Jeremy Jackson]
> try command 'man mkinitrd' under redhat for hints about initial
> ramdisk.
I have been puzzled about this for quite some time. Why exactly does
everyone always recommend using 'mkinitrd' on Red Hat systems? It
seems to me that if you are compiling a kernel for a specific server
anyway, it is a much more reliable proposition to just compile in
whatever drivers you need to boot.
initrd's are inherently clumsy and fragile, to my way of thinking.
I've always thought they should only be used to support diverse or
unknown hardware, or odd cases like crypto loopback root. Are there
other advantages to 'mkinitrd' in the case of a custom kernel for a
single machine?
Peter
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Wed Mar 07 2001 - 21:00:20 EST