Esentially, you only need initrd for modules that are required on your system for booting and mounting the root file system. All other modules can be modprobed in a normal script. regards Anders On Friday 23 November 2001 21:00, Michael Fischer wrote:
Hi.
I am curious if there are any caveats (particularly those specific to SuSE installations) about the use/non-use of initrd.
I have, on several machines, had success with hand-rolling kernels, generally compiling in whatever I want, and not using modules. With said kernels, I make a lilo.conf entry which does not include an initrd entry.
What I wonder is when initrd is truely required. Am I right in thinking this case is largely limited to the use of filesystems (e.g. Reiser) compiled as modules?
What other scenarios are likely candidates? initrd.txt does not suggest much to me besides the above, as well as scenarios which are not part of my workload (e.g., creating distribution cd's...), but perhaps I am overlooking something.
TIA
Michael