On Wed, 16.07.14 13:51, Jon Severinsson (j...@severinsson.net) wrote: > > > tmp.mount is part of our default expected setup and should behave like > > this by default without any presets or configuration. > > Which is why I made `make install` enable it, which wasn't in the original > patch for Debian. > > > It can be overridden by an entry in fstab just fine. Why is that needed? > > To my knowledge you can not create an fstab entry that would make /tmp not be > mounted at all but remain part of /. It can be done by masking the unit, but > enable/disable seems more appropriate than unmask/mask.
(Not that it matters, but actually you can. Just make it a bind mount on itself...) > Note that when Debian tried to change the default from /tmp being part of / > to > being a tmpfs several applications broke and the default was eventually > reverted. Most applications have probably been fixed since then, but even if > we are able to change the default we will need a supported way of disabling > it. I think for cases like this use "systemctl mask"... Note that Fedora has been shipping with tmpfs on /tmp for a while now. A few things broke, but they got fixed. Lennart -- Lennart Poettering, Red Hat _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
