Back on July 24, 2015, I wrote:
I recently upgraded BusyBox from 1.18.1 to 1.23.2, and now I find I
cannot change the read-write mode on a loop mount. That is, if the
original mount is something like:
mount -o loop,ro /private/myopt.ext2 /opt
and I then remount this this:
mount -o remount,rw /opt
With 1.18.1 the filesystem is remounted as read-write as expected, but
in 1.23.2 the command has no effect and the filesystem remains read-only.
This was apparently a deliberate change, not a regression; the native
Linux mount command behaves the same way: if a loopback device is
initially mounted read-only, it cannot be remounted read-write.
There is a workaround using the blockdev --setrw option on the loop
device; that will probably be good enough for our purposes.
<csg>
_______________________________________________
busybox mailing list
[email protected]
http://lists.busybox.net/mailman/listinfo/busybox
