Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

no more tmp.mount systemd unit on my Debian Sid GNOME !

152 views
Skip to first unread message

antistress

unread,
Nov 23, 2015, 1:10:08 PM11/23/15
to
Hi,

About 2 weeks ago I couldn't start anymore my graphical Debian Sid GNOME
session. I don't know if it was related to the switch to non-root X
server. Some people on debian-fr forum helped me to get a graphical
session again.

But It seems that I have lost the ability mount tmp on a tmpfs by
running the command # systemctl enable tmp.mount (got "Failed to execute
operation: No such file or directory")

actually, I've checked and there is no tmp.mount in
/etc/systemd/system/local-fs.target.wants/ !

However Systemd (version 228-2) is running :

# ps -eaf | grep [s]ystemd
root 202 1 0 10:29 ? 00:00:00
/lib/systemd/systemd-journald
root 221 1 0 10:29 ? 00:00:00 /lib/systemd/systemd-udevd
systemd+ 547 1 0 10:29 ? 00:00:00
/lib/systemd/systemd-timesyncd
root 626 1 0 10:29 ? 00:00:00 /lib/systemd/systemd-logind
message+ 651 1 0 10:29 ? 00:00:00 /usr/bin/dbus-daemon
--system --address=systemd: --nofork --nopidfile --systemd-activation
Debian-+ 1003 1 0 10:29 ? 00:00:00 /lib/systemd/systemd --user
my_username 1163 1 0 10:29 ? 00:00:00
/lib/systemd/systemd --user

Maybe someone can help me to solve this ?

Thanks in advance,

antistress

Sven Hartge

unread,
Nov 23, 2015, 3:40:04 PM11/23/15
to
antistress <anti-...@laposte.net> wrote:

> About 2 weeks ago I couldn't start anymore my graphical Debian Sid GNOME
> session. I don't know if it was related to the switch to non-root X
> server. Some people on debian-fr forum helped me to get a graphical
> session again.

> But It seems that I have lost the ability mount tmp on a tmpfs by
> running the command # systemctl enable tmp.mount (got "Failed to execute
> operation: No such file or directory")

systemd (220-6) unstable; urgency=medium

* Stop installing tmp.mount by default; there are still situations where it
becomes active through dependencies from other units, which is surprising,
hides existing data in /tmp during runtime, and it isn't safe to have a
tmpfs /tmp on every install scenario. (Closes: #783509)
- d/rules: Ship tmp.mount in /usr/share/systemd/ instead of
/lib/systemd/systemd.
- systemd.postinst: When tmp.mount already was enabled, install tmp.mount
into /etc and keep it enabled.
- systemd.postinst: When enabling tmp.mount because of RAMTMP=yes, copy it
from /usr/share.
- Drop Don-t-mount-tmp-as-tmpfs-by-default.patch and
PrivateTmp-shouldn-t-require-tmpfs.patch, not necessary any more.



--
Sigmentation fault. Core dumped.

antistress

unread,
Nov 23, 2015, 6:20:06 PM11/23/15
to
Thank you Sven :)
0 new messages