Quote:
Originally Posted by PeterT
Just wondering if you have tried the busybox version of test on any other platform?
|
Only on the SonyReader, which I bricked not too long ago. So I can't retest it now ; but I didn't notice the problem on that platform at the time.
I haven't tried the newest release of busybox to see if they have changed test to accurately reflect read only permissions on a mount-point. but I'm not surprised that busybox test on the Kobo returns true when the mount point is mounted read-only; because the linux kernel *is* reporting that the superuser has write permissions even though the device is mounted read only. I was more surprised that the normal gnu filesystem 'test' program can correctly determine that a device is read only, even when the permission bits on the mount point directory don't reflect reality.
I'm going to have to dig through the kernel source, and busybox, and the normal gnu filesystem utils to figure out why there is different behavior between the normal gnu utilities and busybox, and especially why the linux kernel doesn't change the permission bits to reflect that the mount point was mounted read only.