6 ms·
You seem to be massively overcomplicating things. If you don't want to worry about the "distro drama", then don't. Just use one of the major distros (e.g. Debia
by hn_throwaway_99 6y ago
You seem to be massively overcomplicating things. If you don't want to worry about the "distro drama", then don't. Just use one of the major distros (e.g. Debian or Ubuntu) and move on.
- rualca 6y ago> If you don't want to worry about the "distro drama", then don't. Just use one of the major distros (e.g. Debian or Ubuntu) and move on. +1 on Debian. It's as drama-free as it gets. I mean, the distro is criticized for being too boring and too stable and too rock-solid and too unsurprising. Those descriptions are also used to describe power lines and sewer lines, i.e., reliable infrastructure.
- doublepg23 6y agoDid you miss the systemd drama? There was a new distro created out of it...
- deadbunny 6y agoAnd I'm sure the 3 people using it really like it.
- qz2 6y agoNo point in being popular and unhappy :)
- kbenson 6y agoSystemd in general makes me sad. It feels like the complete rewrite that happens only for the people doing to finally learn all the project needs at the end, and immediately need another rewrite, but nobody has the stomach for it now. Don't get me wrong, I think the authors are and we're probably the best authorities on what is and was needed in an init system, but the problem space was so poorly documented and understood because of all the crazy custom she'll init scripts people were using that they just kept having to tack on weird directives in piecemeal ways, until were left with what we have now. What the world needs is for the systemd authors to take all that knowledge an apply it to a new init system in a sane way, but nobody had the will to go through that again, most likely especially them.
- shawnz 6y agoWho is asking for a rewrite of systemd? From what I have seen, there are two camps: Either you believe systemd is fine, or you believe sysvinit never should have been replaced or should have been replaced with something totally different than systemd with a much smaller scope.
- michaelmrose 6y agoThere are 2 major problems cache invalidation, naming things and off by one errors.
- kbenson 6y ago> Who is asking for a rewrite of systemd? Me? > Either you believe systemd is fine I don't think anyone really believes that. They just believe the benefits it provides over sysvinit are real and generally worthwhile in most cases. Systemd has many warts. I'm not sure anyone refuses to believe that. > or you believe sysvinit never should have been replaced Yep, there's plenty of people that believe that. I've had discussions with them here. > or should have been replaced with something totally different than systemd with a much smaller scope. I'm sure there are people that believe this. Personally I think it's mostly due to being unaware of some facets of the situation. Systemd itself was much smaller in scope originally. The scope increased as they ran into things that it really made more sense to combine than leave separate. A different project may have chosen to leave those things out when encountered, but then it would have all the problems systemd tried to avoid. That actually aligns quite a bit with my argument. With time and foresight (which wasn't necessarily possible the first time, since this is the first time an init system has tried to accomplish these goals that wasn't already intended for a tightly coupled system like Windows or MacOS), they could plan: 1) A more sane unit file syntax that wasn't ambiguous and confusing because of accreted features (After vs Wants, etc). 2) A sane API for subsumed services so if someone doesn't want to use the reference version provided by systemd, it's straightforward to drop in something else as long as you an make it talk systemd (or provide an interop layer). E.g. DHCP client, login managers, etc. This may or may not be done to some acceptable level currently, I'm not sure (but I suspect it depends on the service). 3) Take advantage of even more new kernel features for additional benefits (it's eBPF all the way down). But here's the thing, while I think everyone would agree that something like systemd that's more modular in a well defined way and more sanely configured and documented would be preferable to systemd (I mean why not, it's basically "systemd but better" which is preferably even if you don't like systemd), I don't think anyone really wants to go through the process of either developing, integrating, or learning a new system at this point. We're all too exhausted. And that's a shame, because what we all have now is the mad scientist's awesome flying car. Sure, it does amazing things, and you can do things that would be near impossible in the past, but you control part of it with your thighs and elbows and there are two steering wheels, and the one on the ceiling is the one that steers it like a car.
- michaelmrose 6y agoIf you are a regular end user You can safely ignore it and just use systemd or not and not worry too much either way. Whats the worst case scenario? You find that you don't like the choice you made and spend 2 hours switching to the other option?
- rodgerd 6y agoMore like "oh hey encrypted LVM doesn't work and the package maintainer is refusing to allow fixes because he hates systemd and is indulging in maintainer terrorism to try and block it."
- michaelmrose 6y agoMaintainer terrorism? Can we keep this discussion rational.
- pessimizer 6y agoThe systemd drama is redhat drama. The pulseaudio drama was redhat drama. The glibc drama was redhat drama. This is redhat drama. It's not all redhat drama, sometimes it's Microsoft drama or Gnome drama, but it's funny: all of the sources have really good relationships with each other and commingle their drama until it's nearly indistinguishable. Get involved with one of them and you now have dependencies on all of them.
- Spivak 6y agoThe specific systemd drama the parent is referring to was really Debian drama and the requirements put on maintainers to support alternative init systems. If upstream drops support for non-systemd setups do the maintainers have patch in support? If upstream now has a hard dependency on systemd do maintainers have to patch it out? Red Hat wasn't involved in any of the drama outside of being the ones writing and funding OSS software for themselves.
- detaro 6y agoBut as a user I basically didn't have to care about the details and the "drama" aspects of that drama (I had the result to deal with of course)
- jasonjayr 6y agoRedhat was involved because they heavily maintain some of the upstream packages that put in a hard systemd/logind requirement (GNOME), thus forcing Debian into the uncomfortable position of taking on a large compatibility project, when upstream could have instead taken small patches to continue to maintain compatibility with non-systemd systems.
- cycloptic 6y agoWhich packages had a hard systemd/logind requirement upstream? As far as I understand it, GNOME still gets upstream patches from BSD developers and is still supported there. (Some Debian packages do have hard dependencies on systemd, but this is a downstream packaging issue)
- nix23 6y agoYeah true, the distro i had the longest time was arch and debian, then i changed to FreeBSD (because i can and i want), but on my laptop i need additionally a Linux...but installing arch when my main interests is *BSD..no, so i installed openSUSE tumble and that's it. The whole distro bs is just plain stupid, use what works and has a stable past...that's it.
- FlyMoreRockets 6y ago> The whole distro bs is just plain stupid... LFS for the win!
- nobody9999 6y ago> The whole distro bs is just plain stupid, use what works and has a stable past...that's it. That's absolutely a reasonable point of view -- for your use case. From the perspective of a variety of folks, including corporate IT, makers/vendors of drop-in appliances and other folks, the changes to the CentOS product will be disruptive. This is because production servers and appliances generally need to run, for extended periods (measured in years) the application set specifically designed and implemented for the particular set of software versions on a particular OS/distro. For many of the above folks, CentOS fit that bill nicely, as it reliably tracked (that is, was slightly behind) a commercial (i.e., you need to purchase a support contract to access updates and support from the vendor) Linux distro (Red Hat Enterprise Linux -- RHEL), but did not require any support contracts or fees above those for hardware, installation and administration. The problems for the above implementation/management/administration strategy comes out of changes to the CentOS long term support policy. CentOS (with versions 6 and 7) provide(d) a ten year support window for those versions and promised the same for CentOS 8 (released in 2019). Many of those who had chosen CentOS for it's free (as in gratis[0]) access to the commercial RHEL platform took CentOS (whose developers/maintainers were hired by RedHat[1] to continue that work in 2014) at its word that support for CentOS 8 would also be supported for that same ten year span, updated their environments and applications to the latest version. That promise of support has now been rescinded, as CentOS will now be the gamma/release candidate version of RHEL and will lead RHEL slightly rather than trail it. AIUI, there are many reasons for this change to CentOS development, the biggest being that Fedora (the community project that RHEL used as its Beta platform) is now so far ahead (via its rolling release schedule -- for example the RHEL/CentOS 8 kernel is v4.18 vs. Fedora 33 kernel v. 5.9 -- more than two years) that it's no longer providing that utility. I absolutely understand why some folks are upset, but claims that "CentOS is dead" and the like are rather hyperbolic in my estimation. Disclosure: I have no financial interest in IBM or Red Hat, nor am I a user of CentOS [0] https://en.wikipedia.org/wiki/Gratis_versus_libre https://en.wikipedia.org/wiki/Gratis_versus_libre [1] https://lists.centos.org/pipermail/centos-announce/2014-January/020100.html https://lists.centos.org/pipermail/centos-announce/2014-Janu...
- Macha 6y agoCentOS was certainly a major distro and now we're involved with drama for it.
- chefkoch 6y agoJust check back in three months and there will be a drop in replacement for CentOS. No need to follow the news now every day, it's not an election.
- deleted 6y ago[deleted]
- FlyMoreRockets 6y agoIf it is so easy to create a drop in replacement, why can't CentOS continue as usual?
- andyjpb 6y agoReading between the lines, I assume that it's because Red Hat / IBM own that trademark and they've decided to stop using it for that project. In principle, there's no reason why another-CentOS couldn't come about in the same way as CentOS came about originally. ...but now that CentOS has been professionally funded for so long, the bar is higher than it used to be.
- paulryanrogers 6y agoActually there is still Springdale Linux and soon to be Rocky Linux, from a CentOS founder.
- EwanToo 6y agoOracle already offers one, depending on your level of trust (or distrust) in future support from them https://linux.oracle.com/switch/centos/ https://linux.oracle.com/switch/centos/
- subhro 6y ago/me meekly says Gentoo anyone?
- biglost 6y agoGentoo user here! But to be honest i use flatpak and snap, not just portage. I dont care if it works
- gvurrdon 6y agoIt's great; I've used it for over a decade. These days it's only on my servers, though, due to lack of time. I'd very much like something along the lines of Sabayon with OpenRC for my laptop (currently using Fedora/KDE).