Comment # 19 on bug 1071224 from Thorsten Kukuk

(In reply to Franck Bui from comment #18)

> So the only safe way I can see would be to mask the unit by default during
> the installation if no entry for /tmp is created in fstab by the installer.

We have many installation ways and methods, and also upgrade has to work.
So, a solution based on special code in the installer violates with the
requirement and goal, to have an universal usable installer. And it does not
fix the problem for images (like build with kiwi), updates, rpm, SUSE Manager,
and a lot of other cases I'm pretty sure I forgot to mention.

The only good, reliable solution is one, which works if you install with rpm
-ihv into a chroot environment: the it will always work.

In my opinion, we should not ship tmp.mount in the default path, but as
'example' or documentation in /usr/share/doc/packages/systemd or so.
Yes, there is the risk to break very few installations, but I really doubt that
people outside there use it, since we remove it if not activated. So how should
an user ever activate it, if it is already removed at that point in time?
And if a user want's it, he can link the example to /etc/systemd/... or copy
it.