Am 17. Sep, 2001 schwätzte csj so: > I do know that. But what are the advantages of having an initrd? From the > number of posts bitching about it I was under the impression it's quite > important
There was a thread last week ( maybe the week before ) that covered pros and cons of using an initrd. For kernel-image packages it's pretty well required at this point, I think. The problem has been that prior to 2.4.x the kernel-image packages didn't use an initrd. With 2.4.x all the x86 kernel-image packages do[1]. Most of us didn't know that or how to deal with it. Unfortunately the install didn't communicate the problem. That has been fixed. I think it still requires some action by whoever's installing the package or the machine isn't bootable, so it still needs some work :(. Once I added 'initrd=/boot/initrd' and 'initrd=/boot/initrd.old' in the appropriate stanzas and rerun lilo everything works great. ciao, der.hans [1] Haven't moved to 2.4.x on any of my non-x86 boxen yet. Hopefully in two weeks. -- # [EMAIL PROTECTED] home.pages.de/~lufthans/ www.DevelopOnline.com # Magic is science unexplained. - der.hans
