On Wed, 28 Mar 2012, Frederic Crozat wrote:
Le mardi 27 mars 2012 à 19:16 +0200, Matthias G. Eckermann a écrit :
On 2012-03-27 T 18:46 +0200 Frederic Crozat wrote:
Le mardi 27 mars 2012 à 12:35 -0400, Robert Schweikert a écrit:
We probably have to consider any potential ill side effects for users that have /tmp already setup as a tmpfs mount.
This will need to be tested but I think systemd will just "override" the default from /etc/fstab in that case (but I'm not 100% sure)
That would be rather inconvenient: think about people who might have special mount options to /tmp on tmpfs, such as size, ...
I've done some tests about this particular changes (forward porting the patch to see its effects) : * systemd ships its own tmp.mount file which is overriding any information which might be relevant in /etc/fstab regarding /tmp * however, this file is overridable in /etc/systemd/system (as it was explained in the url I gave regarding this feature on Fedora) : - if we want to disable mounting /tmp as tmpfs, ln -s /dev/null /etc/systemd/system/tmp.mount will be enough (the defaults won't be applied) - if other settings are needed than the one from /lib/systemd/system/tmp.mount, adding options in /etc/systemd/system/tmp.mount will work (and even something like mounting /tmp to a separate partition) - a radical solution could also be to remove file in /lib/systemd/system/tmp.mount and symlink in /lib/systemd/system/local-fs.target/tmp.mount to make sure systemd doesn't take care of /tmp.
This ignorance of systemd of standard configuration files gets annoying ... Richard. -- Richard Guenther <rguenther@suse.de> SUSE / SUSE Labs SUSE LINUX Products GmbH - Nuernberg - AG Nuernberg - HRB 16746 GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer