Re: Jessie and Systemd integration
On Wed, 17 Sep 2014 17:16:57 -0500
"T.J. Duchene" <t.j.duchene@gmail.com> wrote:
> The decision has been made by the
> Debian TC. So be it.
Yeah, the nsa also made the decision to infect a max of computers
and phones among other things like spying on everybody… So be it?
(usual defense: "if you have nothing to hide, what the hell?"
my defense: "my private life, as its name says, is PRIVATE, and
the first who will try to put its long nose in it without my consent
will pay a higher price than he could imagine").
> a) If I will have to have systemd installed even if I do not want it.
From unstable (sid) perspective, not all systemd, but some of its libs
and "compatibility" pkgs.
> b) If completely purging Systemd and using an offered alternative
> break or otherwise hamper the packaging system.
Let me reformulate to see if I understand you well: you wanna get rid
of _all_ junkD pieces.
If it is that, I'm not even sure you would be able to login.
This is what happens if I wanna de-install junkD:
To be removed:
aptdaemon I can do w/o it
colord I can't do w/o it (color publications)
gnome-bluetooth I can do w/o it (but practical)
gnome-power-manager Don't care (tlp does it better)
gnome-settings-daemon Might cause problems w/ XFCE laptop keys
gnome-user-share Might cause PB w/ android
libpam-systemd ShitD plunges its claws in it :(
network-manager Quite useful for a nomade
network-manager-gnome "
packagekit ? (now part of apt)
packagekit-tools
policykit-1 Will almost certainly force me to input a P/W
policykit-1-gnome for each admin task
tlp-rdw Best I could find for laptop management
udisk2 Will force me to (u)mount manually
I'm not a specialist of every pkg, so I may be wrong on some of them
(or even all:)
This means eg: I can't get rid of junkD because of colord which is
important to me (and this is only the beginning of a terribly looong
list of dependencies to come).
In fact, it is the root of the rant of many of us: in a brief future,
we'll be _forced_ to use junkD because of all these dependencies.
Formerly, the Debian bureau did a very nice and responsible job, but it
seems that these days they've got shit for brain… (or sneaky goals, which
is even worse).
> If it is a case where systemd is required to be used, I might have to
> move some of my work off of Debian to Gentoo or FreeBSD.
_For now_, Gentoo seems to be able to completely avoid junkD to the
profit of openRC; will that be a lasting situation? Nothing's less sure:(
FreeBSD, seems to have some advantages (I didn't knew that it could
"execute most Linux binaries" as this page says; although, if these
binaries are rotten w/ junkD deps…):
https://www.freebsd.org/doc/en/articles/explaining-bsd/comparing-bsd-and-linux.html
Unfortunately, it doesn't seems to cope with desktops very well:
http://brioteam.com/linux-versus-freebsd-comprehensive-comparison
Some other links:
http://www.over-yonder.net/~fullermd/rants/bsd4linux/01
it also is less bloated than Linux (which has a bad tendency to
turn obese now):
http://nileshgr.com/2013/06/07/the-move-from-linux-to-freebsd
another brew:
http://www.dragonflybsd.org/docs/user/Comparison_with_Linux/
Reply to: