On Wed, Jul 16, 2014 at 2:57 PM, Zbigniew Jędrzejewski-Szmek <[email protected]> wrote: > On Wed, Jul 16, 2014 at 01:51:13PM +0200, Jon Severinsson 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. > Yeah, especially that this makes it possible for the distribution to nicely > use presets to override the default.
I don't think so. The common default of systemd should be /tmp on tmpfs, and it should be statically enabled. Tools should be fixed if needed to use /var/tmp for anything larger, and not systemd use preset stuff to setup core mount points. > I think that having /tmp on rootfs is legitimate, e.g. on memory > starved systems. The solution for such systems is called swap. :) Kay _______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
