5 ms·
Now? No, not really, just avoid GNOME. In the future? Yeah, probably. This wouldn't be an issue if the systemd people weren't notoriously hard to get along wi
by Karunamon 12y ago
Now? No, not really, just avoid GNOME.
In the future? Yeah, probably.
This wouldn't be an issue if the systemd people weren't notoriously hard to get along with. Really, I think all of the reasons why systemd attracts hate can be boiled down to this. Nobody wants a standard init system that's overtly hostile to bug reports and reasonable changes.
Say what you want about upstart and sysvinit, but I don't recall a point where the maintainers of it were told off for hijacking kernel flags...
- morganvachon 12y ago> This wouldn't be an issue if the systemd people weren't notoriously hard to get along with. This. It doesn't help this guy's case that he's basically calling anyone who doesn't want systemd a "troll". That's not the way to win people to your side of a disagreement.
- Aissen 12y ago> This. This. Backed by nothing, calling the systemd team "notoriously hard to get along with". I'd be interested in seeing proof of "this".
- Karunamon 12y agoThere are a couple of incidents mentioned on the LKML that go directly to their bug tracker - the ones I refer to is where Linus gives Kay Sievers an earful for hijacking the kernel flags (and subsequently writing off the perfectly reasonable complaint). I'd link you to them directly but I'm mobile now.
- Aissen 12y agoHere's the LWN story of this "incident": http://lwn.net/Articles/593676/ http://lwn.net/Articles/593676/ ; it has all the proper sources in links.
- morganvachon 12y agoA quote[1] by a systemd developer: "The only way to deal with journal corruptions, currently, is to ignore them: when a corruption is detected, journald will rename the file to <something>.journal~, and journalctl will try to do its best reading it. Actually fixing journal corruptions is a hard job, and it seems unlikely that it will be implemented in the near future." A major bug is reported, and their response is "it's too hard so we won't fix it" in a project that is soon to be at the core of every major GNU/Linux distro? No thanks. [1] https://bugs.freedesktop.org/show_bug.cgi?id=64116 https://bugs.freedesktop.org/show_bug.cgi?id=64116
- lttlrck 12y agoDoes that really illustrate 'hard to get along with'?
- scintill76 12y agoI guess not, but maybe it's even more damning that this core system component is so much more complex than the previous system, that it sometimes corrupts its data. I'm willing to believe that's not catastrophic, but can someone tell me why it's a good thing for an init system to have corruptible persistent state to begin with?
- morganvachon 12y agoI'd say telling a bug reporter that their report is useless because "we're too lazy and dumb to fix it" is being hard to get along with. Besides, that's far from the only example. A quick Google search brings up dozens of cases where systemd developers and evangelists deride even those who ask basic questions about it. It's a perfect example of "it's our playground, find your own" that is so juvenile and antisocial that it bothers the hell out of me. And that's not even the reason I don't want to use systemd; I simply prefer traditional init systems like sysvinit and Slackware's BSD-style init system.
- Alupis 12y agohave you actually used systemd before? it's quite good.
- vezzy-fnord 12y agoAs well as upower (though it still works with ConsoleKit as fallback, I think), udisks2, the Weston compositor and some other programs. Binary distros also have some pretty skewed dependency chains on systemd for packages where it's inessential. It'll only grow, though. Most certainly.
- e7620 12y ago> It'll only grow, though. Most certainly. Only up to a point. Systemd is getting too bloated, and software engineering tells us that the effort to maintain this will grow exponentially. So we have two options: if systemd improves and decides to follow UNIX principles, good. Otherwise it'll be replaced like consolekit et al. It's great that we have so many init systems to choose from. The only problem now is software that hard depends on systemd when a single line of code could avoid that.
- xfs 12y agoCore package bsdutils predepends on libsystemd0. Now it is impossible for any Debian jessie systems to be without systemd code. https://packages.debian.org/sid/bsdutils https://packages.debian.org/sid/bsdutils
- geofft 12y agoThat's moving the goalposts in a significant way. Debian has always been of the philosophy that binaries that have runtime-optional support for something link libsomething and have a dependency on it, but there cannot generally be a dependency from libsomething to the actual something package. For instance, openssh-client depends on libgssapi-krb5-2 and libselinux1, but neither of those packages have a dependency on the Kerberos 5 userspace clients or on SELinux being configured or enabled, respectively. If you happen to install Kerberos or enable SELinux, then openssh-client will work fine without a recompile (because Debian doesn't have USE flags). If you don't, the libraries will just do nothing. I think SELinux is a terrible and misguided idea that subverts the UNIX philosophy, adds needless complexity, and also doesn't work, but I have no objection to libselinux1 being installed. Same thing with bsdutils and libsystemd0. The discussion has never been about being "without systemd code" as if it were a noxious poison. (It's free software, I would _hope_ people incorporate good code from it into other packages.) It's about being without systemd, the init system, and if bsdutils did depend on a particular init system, it would be flagrantly in violation of the Technical Committee resolution.
- lomnakkus 12y ago> Now? No, not really, just avoid GNOME. You don't have to. Someone apparently implemented the logind interface(!) so that GNOME could function on non-systemd systems. Just use that. > This wouldn't be an issue if the systemd people weren't notoriously hard to get along with. [...] Are you kidding? I've been following along the mailing list for at least two years and I've never seen any of the unreasonableness you claim. (I'm not in any way connected or invested in the systemd project, just as a little disclaimer.) If you're going to pull this stunt please at least give us concrete references. > Say what you want about upstart and sysvinit, but I don't recall a point where the maintainers of it were told off for hijacking kernel flags... Ah, I see. You're just another troll recycling talking points. Oh, well. Oh, and btw: Complain all you want -- in F/OSS the people doing the work get to decide. Deal.
- JdeBP 12y agoNo-one has yet come forward publicly with a working second implementation of logind for Linux. The only person known to be working on a second implementation of logind is targetting OpenBSD. To use logind-API-client desktop environments with the well-known systemd-shim actually involves using the logind that is part of the systemd package, running on top of a daemon that implements only part of an internal systemd API. See http://homepage.ntlworld.com./jonathan.deboynepollard/FGA/debian-systemd-packaging-hoo-hah.html http://homepage.ntlworld.com./jonathan.deboynepollard/FGA/de...