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
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
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,
Control: reopen -1
Control: reassign -1 policykit-1
Control: forcemerge 792307 -1
On Fri, Jun 02, 2017 at 05:20:51PM +0200, Julian Andres Klode wrote:
> On Fri, Jun 02, 2017 at 10:10:57AM -0400, Mark Murawski wrote:
> > Package: hplip
> > Version: 3.16.11+repack0-3
> > Severity: important
> >
>
Package: hplip
Version: 3.16.11+repack0-3
Severity: important
* What led up to the situation?
# apt-get install hplip
Outcome:
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
hplip-data libhpmud0 libpam-systemd libsane-hpaio
5 matches
Mail list logo
