Dominique:
Le Mon, 13 Jan 2014 02:39:08 +1100 (EST),
"Patrick Shirkey" <pshirkey(a)boosthardware.com> a écrit :
> On Mon, January 13, 2014 2:28 am, Dominique Michel wrote:
> > Le Mon, 13 Jan 2014 00:22:40 +1100 (EST),
> > "Patrick Shirkey" <pshirkey(a)boosthardware.com> a écrit :
> >> On Sun, January 12, 2014 11:17 pm, Dominique Michel wrote:
> >> > Recently, I experimented with Debian sid, which use systemd.
> >> > Systemd idea is nice, but its implementation is a
> >> > catastrophe. It is more than one year I am using the kernel
> >> > cgroups on gentoo to get rt scheduling with JACK, that
> >> > without any trouble.
> >> >
> >> > On Debian, this is just impossible, because whatever I try,
> >> > systemd insist to put what it think is good to have into the
> >> > rt cgroup, which soon or later result in a complete system
> >> > freeze with even dead magic keys. After loosing my time a
> >> > few days with this, I removed Debian and installed gentoo
> >> > instead.
...
I can understand this when some developers seam
use their time to
break the kernel and other important functions. We get udev
breakage of firmware loading with some modules, the *kit story
which will hopefully end with its disappearance, and now systemd
which have a catastrophic implementation. And that's only the ones
I am aware of.
The sad part is that distributions and some programs have stopped to
respect the local administrator, by implementing more and more policy.
Regards,
/Karl Hammar
The usual answer that I get for criticism like that is: "Well, you can
change it.". The problem is that the effort to do so is often too large
to make this a practical option.
I'm not sure how it is in this case though, is it possible to change the
behavior of systemd without code change?
I do try to stay away from things that I don't need (polkit, systemd,
PA, *kit, ...) but it's not always possible. I can hardly maintain an
init system in parallel to the one my distribution uses.
Regards,
Philipp