I am afraid that I do not understand exactly what you mean. Initrd is not for newbies wanting an out-of-the-box working installation and it needs to be rebuilt for every new kernel image cause of the modules included into initrd (although the slack kernel does not change so much often...). So initrd sucks mainly.lmello wrote:Aren't those messages gone when you make an initrd and boot the generic kernel instead?
(I have some experiences with lvm support that needs such an initrd.)I do not have the test environment for the described behaviour any more, so I've closed the thread to "done". For me, the problem is solved.
