On Mon, Feb 25, 2002 at 10:18:38AM -0500, [EMAIL PROTECTED] wrote: > Tapio Riikonen wrote: > > > > > i tried to install beta3 from harddisk hd.img , but it failed. > > > It said pretty early in the installation, I think just after > > > selection of keyboard that I missed a file: > > > /lib/modules.cz-2.4.17-mdk10BOOT and it just closed down. > > > > > > Keld > > > > It is still broken (I don't know what is so difficult to fix it). > > > > hd.img 022402 gives this error message: > > Can't access kernel modules corresponding to your kernel (file > > /lib/modules.cz-2.4.17-20mdkBOOT is missing) > > > > and hd.img 022302 > > nothing found while parsing /mnt/var/lib/urpmi/hdlist.Installation CD > > (disk1).cz > > > > Tapio > > Well, see what happened: > /lib/modules.cz-2.4.17-10mdkBOOT > /lib/modules.cz-2.4.17-20mdkBOOT <== > > You need to use "hd.img" from the distro that you try to install! > It happened to me when I did use floppy with older version hd.img than > the one in the 8.2 beta3. > It was unable to find the proper version of module to install (which is > need).
Why does it need these specific modules? I think it would be nice if the boot.img could be one that you could use from distribution to distribution. Basically one version should be able to perform with the same hardware from time to time. If you want the new modules then that is fine and you should be able to run then with that image. I see these images as self-contained systems that just have to execute until they have established the real kernel and its operating environment, end let the control pass to the real kernel. So this kind of bootstrap should be independet of the linux kernel and its modules. Maybe I am wrong. Keld
