Frederic Crozat writes:
this is a announcement regarding changes which have just landed in upstream systemd (not yet released nor pushed to Factory) regarding /media and /tmp: - /media will no longer mounted as tmpfs. This is because udisks2 will no longer use /media for mounting removables devices but /run/media/<user>
Out of curiosity, how does one deal with media mounts that should be available system-wide?
- /var/run and /var/lock are no longer bind-mounted to /run | /run/lock. We should replace those directories with symlink to /run | /run/lock (probably at initrd time, this is what is done on Fedora)
Just make sure that this time around the former contents of these directories does not vanish as it did the last time when they were changed to tmpfs (i.e. rename them first before installiung the symlinks or mount-overs).
- /tmp is mounted as tmpfs, to make the default setups as stateless as possible.
I don't think this is sensible as a general default.
As stated on https://fedoraproject.org/wiki/Features/tmp-on-tmpfs , we might need to fix some applications to use /var/tmp instead of /tmp when they need persistent storage.
I might agree on the "persistent storage" issue. But as has been said already, assert( "/tmp" != "/ramdisk" ) is built into many programs and it will be impossible to change all of them. We already have /var/tmp for "persistent" temporary storage. Applications that currently use /tmp for temporary files and directories that should ostensibly not be held in RAM, but should go away when the application for whatever reason doesn't delete them have no business to store their stuff in /var/tmp because nobody cleans up after them and if we start cleaning /var/tmp that would again break other legitimate uses. It would seem to make much more sense to introduce /run/tmp for "ephemeral" temporary storage in RAM and change those applications that don't need to commit to disk to use it than wholesale changing the semantics of /tmp. That doesn't preclude to change /tmp to tmpfs in situations where it is known to work correctly and where the benefits (power draw and SSD wear — really?) outweigh the potential problems. In other words, the "stateless system" that the proposal aims for is much more easily achieved by making the _system_ stop using /tmp and care only for /run/tmp (or maybe even /run/tmp/sys in a non-shared /run/tmp/<user> setup), which already is stateless.
Another big issue is educating users.
The big issue is third-party applications that would need to be changed, assuming that _all_ applications tat come with the distribution would be fixed already. What is the proposal for those, are you going to virtualize the file system like Win7 does? Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Waldorf MIDI Implementation & additional documentation: http://Synth.Stromeko.net/Downloads.html#WaldorfDocs -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org