On Thu, December 2, 2004 19:00, Jari Ruusu said: > When loop was set up, it was set up in "hard" read-only mode, IOW, loop > driver would not permit any writes to reach underlying device. rw mount is oh, you're so right Jari. yes, i started to mount the partitions with "ro" in the first place. i.e. the system boots, "ro" is set in fstab, the loop device gets setup in "ro" mode and could only be changed when i unmount / then mount again in "rw" mode. *then* i can use -o remount,rw and -o remount,ro whenever i like. the inital losetup (done by mount, i guess) is to "blame" here. > worked like that for long time, years IIRC. OTOH, if VFS is now opening > about-to-rw-mount devices without FMODE_WRITE set, then something is > broken in VFS. i don't know if that's the case here. i know how to workaround the issue, but perhaps i should (wishlist)bug the util-linux people here? thanks for the (always) quick reply, Christian. -- make bzImage, not war - Linux-crypto: cryptography in and on the Linux system Archive: http://mail.nl.linux.org/linux-crypto/
