Bug#1072290: I should add that the bug is due to bogus listchange wording
Control: tags -1 -moreinfo Control: close -1 On Fri, 31 May 2024 16:55:44 +0200 Eric Valette wrote: > The way I read the message below is as this: > > /tmp will unconditionnaly mounted as a tmpfs file system (which I do not > want). Uncondionnally does not mean "even if /tmp is explictly mounted > in /etc/fstab". > > So this encourage user to do the command mentionned below. The previous > setup is rather unclear. > > I tried to let the /tmp entry in /etc/fstab and do not do the mask > command and then it boot but So if you do *nothing* then everything works as expected, but things break when you misunderstand the NEWS entry and apply a change that you shouldn't apply? Then there's no bug, it's just a misunderstanding, closing -- Kind regards, Luca Boccassi signature.asc Description: This is a digitally signed message part
Bug#1072290: I should add that the bug is due to bogus listchange wording
The way I read the message below is as this: /tmp will unconditionnaly mounted as a tmpfs file system (which I do not want). Uncondionnally does not mean "even if /tmp is explictly mounted in /etc/fstab". So this encourage user to do the command mentionned below. The previous setup is rather unclear. I tried to let the /tmp entry in /etc/fstab and do not do the mask command and then it boot but "/tmp is not by default a tmpfs" or by default should read unless otherwyse explicitly mounted via entry in /etc/fstab. - found in list-change systemd (256~rc3-3) unstable; urgency=medium - /tmp/ is now by default a tmpfs, via the tmp.mount unit provided upstream. The previous setup can be retained simply by masking the unit locally with: systemctl mask tmp.mount or: touch /etc/systemd/system/tmp.mount -- Eric Valette
