remount

These are still applied if you remount it rw, which means that in the future users will have to modify SELinux policy to write while the OS is running.

And each time you remount the part you have to be able to tell the machine exactly how the part is mounted so that everything lines up.

In a few years, when the ink fades, he can print it again and remount on the same surface.

You could mount /etc and /usr as read-only, and have the upgrade process briefly remount it read-write.

Plus you need to remount the moment you want to actually do write actions to protected areas of the phone.

You can remount those dirs without noexec when you need to do a legitimate install.

If you want to preserve the raw data, you can remount (move the mount point).

If you want to do something less tricky and low level than dd just remount the drive in question read-only and use tar.

I don't want to have to unmount and remount my Truecrypt container once an hour or whatever to sync changes.

Also, you don't get working apt-get unless you remount the root filesystem read-write, in which case you lose image-based updates (the only supported update mechanism).

Get root, create a ramdisk, copy /usr/bin/* into it, and remount it under /usr/bin/*, and now you can do as you please.

If you wish to have higher disk speeds, but not use backups, we recommend for you to remount your disk with journaling.

You can still write by just doing "mount -o remount, rw /" beforehand.

Probably step 1 should be "remount the partition read-only".

At the very least windows itself could/should "clean slate" (aka unmount remount I guess) the thumb every once in a while if there has been activity followed by no activity and no opened descriptors for a few minutes since that would cover a majority of the cases.