Le mardi 27 mars 2012 à 20:39 +0200, Bruno Friedmann a écrit :
On Tuesday 27 March 2012 18.08:01 Frederic Crozat wrote:
Hi all,
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 okay so all work and effort to fix situation comparing 11.4 and 12.1 is lost (again :-()
There seems to be a general misunderstanding about /media : this particular directory was created to store mounts points created automatically by daemons like hal (in the early days) or udisks / udisks2 (these days), not to store "persistent" mounts points (/mnt is better suited for this). This is why /media was tmpfs-ified with systemd.
- /var/run and /var/lock are no longer bind-mounted to /run | /run/lock. First, I did a mistake in my mail: /var/lock and /var/run were not bind mounted to /run, they were mounted to separate tmpfs.
How much package will have to be fixed again just for that ?
None, if they were already fixed properly for 12.1, where those were already non persistent.
We should replace those directories with symlink to /run | /run/lock (probably at initrd time, this is what is done on Fedora) Could it be pushed before M3 please to have a better timeframe for feedback and tests?
We can't push it before the change is available in systemd (otherwise systemd would try to mount over a symlink, which is not possible)
- /tmp is mounted as tmpfs, to make the default setups as stateless as possible. 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. Another big issue is educating users. Just have a clear listing of all application that need to be fixed and all kind of usage verified, like split tar gimp inkscape (memory hungry things) etc and all kind of stuff that could use /tmp There's a bunch of application that use it to swap undo and kind of things using tmpfs could be pretty counter intuitive So test and bench need to be written for openQA
the whole /etc/sysconfig/cron has to be revisited completely
Well, it already need to be revisited and I'm willing to review patches against systemd-tmpfiles to have handling similar to what was in previous openSUSE release (bnc 721682) but so far, I got nothing..
And a point that need to be clear and have a hook permitting users to clean it up What happens with my old /tmp directory as soon as this feature is enabled?
On the next boot we'll simply mount the directory over with a tmpfs. and then you keep forever the 4GB iso you put it inside before the update/upgrade -> move previous /tmp to /tmp.old or rpmsave or whatever than joe and jane can cleanup
Lars suggested we could do a one time move for the data to a different
directory (and maybe even drop a README in the new tmpfs "where are my
data done").
--
Frederic Crozat