Reading one of the HOWTO's out there, I gather that mkinitrd.xfs is only
required when xfs is being used as a module, but not if xfs is compiled
directly into the kernel. Is this correct? Will mkinitrd.xfs work on
non-xfs kernels as well (excluding the fact that it wouldn't do anything
useful)?
The same HOWTO indicates the lilo.conf line:
append="ramdisk_size=25000"
I gather that this should only be done under the circumstances that the
kernel will be using xfs as modules rather than built-in. There is also
an initial ramdisk size as an option during kernel compile, for default
size, which I recall was something like 4096. Will this work as a means
to avoid having to add the "ramdisk_size=25000" line in lilo.conf when
using xfs as a module?
Second, when compiling and getting the note about the image being too
large for a floppy, I'm wondering if compiling xfs as a module would
make any difference in this, since the ramdisk would itself need to be
part of the floppy as well? If a floppy is not possible, are most people
using the CDROM ISO image as backup instead? Just wondering what the
options are for having an alternate means of booting in case of failure.
D. Stimits, stimits@xxxxxxxxxx
|