Sat Mar 26 14:02:08 EDT 2016
What worries me is that cups now depends on systemd (through dbus).
I don't see now how to work around that.
I think time has come to split all "office" tasks into a separate vm
or chroot that pretty much runs a standard debian or ubuntu
distribution. I require too many customizations in my "main" work and
use, but use "office" tasks only rarely.
And then set up the build machines to delegate to those.
For cups, it might already be enough to just do port forwarding to a
single machine, instead of running the daemon everywhere.
Nope.. Messes up auto-discovery..
- lean, modded dev system, duplicated
- desktop machine: standard install, as vm per workstation/laptop or
as application server per network
installing cups pulls in systemd, but removing systemd doesn't remove
cups. dependency problem?
root@zoe:~# apt-get remove systemd
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
colord libpam-systemd policykit-1 systemd
colord <- policykit-1 <- libpam-systemd <- systemd