Bug 14700

To disable tmp.mount you can do
  ln -s /dev/null /etc/systemd/system/tmp.mount

but if systemctl disable doesn't work for tmp.mount that sounds like a bug.

CC: (none) => cjw

Putting a link to /dev/null into /etc/systemd is, I believe, masking, but I agree that not being able to disable it (ie, not being able to remove the link /etc/systemd/system/local-fs.target.wants/tmp.mount using 
systemctl disable tmp.mount) is a bug.

Fix: Put the following lines into /usr/lib/systemd/system/tmp.mount

[Install]
WantedBy=local-fs.target

would fix this bug. Then you could enable or disable tmp.mount and thus enable or disable the mounting of /tmp as a tmpfs.
While somethings you maybe do not want sysadmins disabling, because doing so would completely break the system, /tmp as a tmpfs is NOT one of them. There are probably other optional items that systemd makes mandatory for no good reason.
The sysadmin should be god-- ie, they should be able to configure their own system the way they want, not be forced to do it the way some developer thinks he should.

Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer 
maintained, which means that it will not receive any further security or bug 
fix updates.

Package Maintainer: If you wish for this bug to remain open because you plan to 
fix it in a currently maintained version, simply change the 'version' to a later 
Mageia version.

Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't 
able to fix it before Mageia 4's end of life. If you are able to reproduce it 
against a later version of Mageia, you are encouraged to click on "Version" and 
change it against that version of Mageia. If it's valid in several versions, 
select the highest and add MGAxTOO in whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.

Although we aim to fix as many bugs as possible during every release's lifetime, 
sometimes those efforts are overtaken by events. Often a more recent Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].

[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/

Still valid in MGA5. Probably also cauldron, but I have not checked.

Version: 4 => 5

Assigning to systemd maintainer Coling, but also adding the basesystem maintainer group in CC as well as the packagers looking after orphaned packages in CC, since we haven't heard from Colin recently.

CC: (none) => basesystem, pkg-bugs
Assignee: bugsquad => mageia

Hi w unruh,

Thank you for having taken the needed time to report this issue!

Did this bug get fixed? If so, please change its status to RESOLVED - FIXED

If it didn't, then we regret that we weren't able to fix it in Mageia 5. Mageia 5 has officially reached its End of Life on December 31st, 2017 https://blog.mageia.org/en/2017/11/07/mageia-5-eol-postponed/
It only continued to get important security updates since then, because we are waiting for a big Plasma5 update in Mageia 6, that'll fix many of the Mageia 5 => 6 upgrade issues.

If you haven't seen that this bug got fixed, then please check whether this bug still exists in Mageia 6. If it does, then please change the Version (near the top, at the left) to "6". If you know it exists in Cauldron, then change Version to Cauldron. If you see it in both Cauldron and Mageia 6, then please set Version to Cauldron and add MGA6TOO on the Whiteboard.

Thanks,
Marja

(In case this report needs to stay open for a supported release: Reassigning to the base system maintainers and CC'ing Neal.)

CC: (none) => mageia, marja11, ngompa13
Assignee: mageia => basesystem

No reply, so closing as OLD since Mageia 5 is no longer maintained.

Resolution: (none) => OLD
Status: NEW => RESOLVED