Thanks Matthias,
will try what you suggest.
Regards, Michael
"Becher Matthias"
Hello Michael, just try to reinstall the kernel-packages.... there you might get the loop.o. Otherwise compile the kernel again and just take loop-device support into the kernel.
hope good luck for you. PS: just try cat /proc/filesystems ... there the supported filesystems are listed
-----Ursprungliche Nachricht----- Von: Michael Ryan [mailto:ryanm3@eircom.net] Gesendet: Mittwoch, 11. Dezember 2002 16:01 An: suse-security@suse.com Betreff: [suse-security] OT because ...
... posted this query twice on suse-linux-e@suse.com with no joy :( so I'm hoping someone here might help ...
--- Original Message ---
Hi list,
I'm having a problem upgrading the kernel on an old SuSE 6.4 disto to kernel 2.2.19 using the SuSE supplied k_deflt_22-2.2.19-162.i386.rpm.
I have followed the SuSE kernel update instructions carefully but am having the following problem creating a new ram disk for my scsi and network device drivers:
****:/ # mk_initrd using "/dev/sda1" as root device (mounted on "/")
creating initrd "//boot/initrd" for kernel "//boot/vmlinuz" (2.2.19) mount: Could not find any loop device, and, according to /proc/devices, this kernel does not know about the loop device. (If so, then recompile or `insmod loop.o'.) failed to mount image ****:/ #
The file loop.o does not (or no longer) exists on my system :(
Any help VERY much appreciated.
Thanks - Michael
-- Check the headers for your unsubscription address For additional commands, e-mail: suse-security-help@suse.com Security-related bug reports go to security@suse.de, not here