Bug#792307: closed by Brian Potkin <claremont...@gmail.com> (Re: Bug#863974: hplip should not require systemd)

2017-06-04 Thread Christian Mueller
Correct, sorry, I've been running without any systemd components for such a long time that I forgot the details. Either way, systemd components are currently pulled in and activated (logind-systemd). I don't have a good example for Linux off the top of my head because I've removed systemd a

Bug#792307: closed by Brian Potkin <claremont...@gmail.com> (Re: Bug#863974: hplip should not require systemd)

2017-06-04 Thread Simon McVittie
On Sat, 03 Jun 2017 at 22:50:58 +0200, Christian Mueller wrote: > (separate temp mount points for > each user) which, apart from the incredible clutter in the list of mounted > file systems, breaks my workflows (I need a single /tmp for all users). systemd-logind mounts a small tmpfs at

Bug#792307: closed by Brian Potkin <claremont...@gmail.com> (Re: Bug#863974: hplip should not require systemd)

2017-06-03 Thread Christian Mueller
Hi Brian, I just realized that my bug report, #792307, got merged with #863974 which may have the same underlying cause but a different interpretation of the results. Yes, just installing the systemd binary won't enable it as the active init system but another part of the dependency chain,