Le 20.11.2013 12:48, Tom H a écrit :
On Wed, Nov 20, 2013 at 1:48 AM, Brad Alexander <[email protected]>
wrote:
On Tue, Nov 19, 2013 at 7:19 PM, Rob Owens <[email protected]> wrote:
I run a testing system that I depend on to get work done on a daily
basis. I noticed today that a dist-upgrade wanted to install
systemd.
I've never used systemd -- is there anything to fear? For those who
have installed it, does the system handle the switch from the old
init
scripts, or is there a lot of manual intervention and time
required?
That's interesting. I am on a sid system, and I haven't noticed
systemd on
my system. I have the support libraries:
$ dpkg -l | grep systemd
ii libsystemd-daemon0:amd64 204-5
amd64 systemd utility library
ii libsystemd-login0:amd64 204-5
amd64 systemd login utility library
I also checked a testing box, and it has the same libs.
I also, just out of curiosity, checked apticron on both boxes, but
neither
of them has systemd on the to be installed list. Maybe a dependency
on
something previously installed?
Please don't top-post.
systemd's pulled in by GNOME.
Wrong. Every program using dbus, and they are not only GNOME ones,
pulls in systemd-login0. For example, Konsole (KDE) depends on dbus. At
least on Debian Linux.
That fact that systemd is pulled by lot of components for things I do
not really needs is an argument against systemd that I accept. And a
good reason for me to try to avoid that switch (to be honest, I also
would like to reomove dbus, because I know that my softwares does not
*need* it: disabling the daemons removes no features).
But, it is not systemd's fault, if dbus depends on it. It's dbus'one.
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
Archive: http://lists.debian.org/[email protected]
