Hello, I have a use case where a file system partition gets mounted read-only and a daemon is started from that partition. At some times it is necessary to have that partition read-writeable to update some files on it.
Under BusyBox 1.2.2 one could simply change the file systems flags to 'rw' by issuing 'mount -o remount -o rw /mnt/myMountPoint' Since I upgraded to Busybox release 1.11.3 the same scenario fails with 'Device or resource busy', as if it was tried to unmount and mount the partition again, which is not possible as the mentioned daemon is still running. Is this a desired change in the behavior or a regression? Regards, Christian _______________________________________________ busybox mailing list [email protected] http://busybox.net/cgi-bin/mailman/listinfo/busybox
