Loop device appears as readonly to updated RH 6.2 kernels I have a 'partitionless' installation of RedHat 6.2, created some time ago with the intention of exploring Linux without repartitioning or otherwise putting at risk data held by WindowsME on the same disk.
The Linux system lives in a 2GB Windows fat32 file and is accessed as ext2fs through the loopback device. It boots from a floppy bootdisk. The RHN up2date process has worked quite happily but I have not been able to complete booting of either of the updated kernels (both i586) that it has offered and installed. After both /sbin/mkbootdisk -v 2.2.22-6.2.3 and /sbin/mkbootdisk -v 2.2.19-6.2.12 booting gets as far as attempting to remount the root fs in read/write mode, but then reports that it is read-only and does nothing more that is useful. Bootdisks created like this using the original kernel, 2.2.14-5.0, still work. I have made several attempts to modify the booting/reporting sequence by editing /etc/rc.d/rc.sysinit, but only got the report:- 'block device /dev/loop0 is write-protected but explicit -w flag given.' I haven't been able to find any reference to this particular problem, but I have seen that some 2.4 series kernels had problems with failure to return from calls to the loopback device. Is the loop device broken, or perhaps intentionally readonly, in the later 2.2 kernels, or can anyone suggest a fix? TIA JohnP -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
