Slashdot Mirror


Systemd-Free Devuan Linux Announces A Second Release Candidate (devuan.org)

An anonymous reader quotes The Register: Devuan Linux has released its second release candidate... A 1.0.0 release candidate emerged just under a fortnight ago and today the developers announced Devuan Jessie 1.0.0 RC2. New in this cut of the code is a systemd-free version of network-manager, new versions of reportbug, desktop-base and xfce4-panel. GNOME, KDE, and Cinnamon have been removed from tasksel, but can still be installed although they "are known to suffer from some glitches due to the lack of systemd."
The Devuan web site says this series of release candidates "marks an important milestone towards the sustainability and the continuation of Devuan as a universal base distribution." And their announcement describes Devuan as "the Debian that was and could have been. Our goal is to provide a viable and sustainable alternative...a new path, nurtured with your help and support."

69 of 122 comments (clear)

  1. systemd by Anonymous Coward · · Score: 2, Interesting

    Graybeards yelling at clouds

    Like... I understand not wanting all the cruft that comes with systemd, but as an init system it's absolutely fabulous! I know Debian tends to be the bastion of never change anything ever and I'm hardly surprised that "Debian makes decision to change something" was met with hostility. Regardless I think this whole thing is a bit ridiculous. Rather than forking ALL OF DEBIAN so you can keep sysvinit, why not fork systemd to use only the init? Hell, you could even have it use the horrible sysvinit script system if you like!

    1. Re:systemd by dreamchaser · · Score: 2, Insightful

      Sometimes people have valid reasons to not like change or anything different than their favorite [fill in the blank], and sometimes it's just akin to religious zealotry. Mac vs PC vs Linux is another good example. I find it all to be vaguely amusing.

    2. Re:systemd by Anonymous Coward · · Score: 5, Interesting

      I dunno, I think they might be on to something.

      https://linux.slashdot.org/story/16/10/01/2155209/multiple-linux-distributions-affected-by-crippling-bug-in-systemd

      SystemD ties in to everything. Init scripts were more compartmentalized last I read. Seems like tying so much in to one magic black box isn't as smart a move as people might think it is.

    3. Re:systemd by yeupou · · Score: 4, Insightful

      And sometimes people using GNU/Linux since 20 years and know what they want and are not up to some change that decreased their productivity for benefits that does not matter to deal.

      What is even a Mac vs PC vs Linux since all these are PC-based nowadays? I find bad choice of words vaguely amusing.

    4. Re:systemd by TWX · · Score: 2

      I have had to fix a couple of rackmount servers over the years with nothing more than my laptop, minicom, and a null modem cable to get into the TTY. I know I can manually edit init scripts and it's also very easy to back up or replace the init scripts, they're just scripts!

      --
      Do not look into laser with remaining eye.
    5. Re:systemd by TWX · · Score: 3, Insightful

      This is where I'm at, my first Slackware box would be old enough to drink at this point.

      On top of the issue of experience, I've got actual dead-tree books describing UNIX SystemV and BSD inits, which Linux's inits were derived from or outright copied from. In other words, documentation. I can actually RTFM if I need to, as I have the "FM" on my shelf.

      --
      Do not look into laser with remaining eye.
    6. Re: systemd by Entrope · · Score: 1

      Think of it as a Single Point Of Fixing.

    7. Re: systemd by Anonymous Coward · · Score: 1

      system =====D~~ ~

      bend over, here it comes again!

    8. Re:systemd by drinkypoo · · Score: 1

      This is where I'm at, my first Slackware box would be old enough to drink at this point.

      #metoo. Slackware 2.0 on a 386DX25 with 8MB/120MB. A, N, D, and most of the X set would fit with room left over for 8MB of swap. And it was plenty :) I just bumped my carputer up from 2GB to 8GB because 2GB was too little...

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    9. Re:systemd by TWX · · Score: 1

      Mine was a Cyrix clone, a 40MHz 486 with math coprocessor and 8MB RAM, a partition on a 420MB hard disk shared with DOS and Windows. The motherboard was unusual, it had sockets for both 386 pinout and 486 pinout processors; and if I'm remembering right the Cyrix processor went into the 386 socket and there was a placeholder chip in the 486 socket.

      For several years my normal process was to upgrade the Linux box with the old Windows box's hardware when I'd build a brand new Windows box. So the Linux box became a Pentium 133 when the Pentium 200 was built. The Pentium 200 became the Linux box when the AMD K6-2 350MHz was bought, etc.

      Now I mostly shop at the college surplus. Current desktop is a Dell Precision T7400 dual-quad Xeon box with 32GB RAM, and while older is rock-solid, and cost about $300 three years ago when I bought it.

      --
      Do not look into laser with remaining eye.
    10. Re:systemd by LVSlushdat · · Score: 1

      Those were the daze... I started with Slackware in 1994, on a 486DX2-66 with 8Mb of ram, Hercules mono video and an amber monitor. After I got the scads of floppies made and got the basic OS installed using the Herc mono video, I scrounged up a EGA monitor and if I remember correctly a Tseng Labs EGA card, and *tried* to get XFree86 configured correctly and get a GUI up and running.. What Fun!! I'll admit I managed to "release the magic smoke" on the first monitor trying to get the modelines set right.. After getting some info on irc, I managed to get X going and as I recall, fluxbox...

      --
      THANK YOU, Edward Snowden!! Americans owe you a debt of gratitude (whether they know it or not..)
    11. Re:systemd by LVSlushdat · · Score: 1

      Unfortuantly, its getting harder and harder to *find* a distro that isn't using systemd.. Obviously the BSD's don't (and never will --- thank goodness) and Slackware.. As I recall even the "build-you-own" distros, like Arch and Gentoo are sucking systemd's crank....

      --
      THANK YOU, Edward Snowden!! Americans owe you a debt of gratitude (whether they know it or not..)
    12. Re: systemd by Type44Q · · Score: 1

      This is where I'm at, my first Slackware box would be old enough to drink at this point

      Nicely aged perhaps but likely still rather undrinkable...

    13. Re:systemd by dreamchaser · · Score: 1

      You have a valid reason and aren't acting like a zealot. I've been using Slackware since the 90s as well, though I have a Macbook and . Windows gaming rig as well.

    14. Re:systemd by buchner.johannes · · Score: 1

      Gentoo has openrc by default, you can switch over to systemd if you want.

      BSDs are developing systemd-bsd for a dependency-tree based init system.

      --
      NB: The message above might reflect my opinion right now, but not necessarily tomorrow or next year.
    15. Re:systemd by Aighearach · · Score: 1

      I think it is pretty funny. I love systemd, but I really hate NetworkManager. If it is a laptop or something that is stuck on wifi then it is OK, but if I have a real network I can't imagine wanting that nonsense bouncing my connections.

      Even on Fedora you can run SysVinit if you want. People get their neckbeards all twisted up over the mere dependency that the packaging system has. I mean, they're so exclusive, they can't tolerate that the unused default software might have a few bits installed. As if any of it was really that exclusive and royal to begin with! And as if the default [everything else] isn't also installed?! It makes sense in a lot of cases to just install the default, and if you want to use something else, you also install that. It isn't always going to be a full replacement, because that's just extra packages to manage.

      Embedded systems are separate distros, so I know it isn't the 128k of disk space.

    16. Re: systemd by Aighearach · · Score: 1

      You haven't seen those new vacuum blenders, have you?

    17. Re:systemd by Aighearach · · Score: 1

      No it isn't.

      Just use Fedora, and choose sysvinit.

      Duh.

      It is like a holy war straight out of Monty Python. Everybody told them that they could choose which to run, but they just couldn't comprehend it. Were they supposed to say some sort of incantation afterwards? "You can use whichever you want, hontou ni hontou! Jingjing!"

    18. Re:systemd by SirCowMan · · Score: 2

      I'm not sure it's absolutely fabulous. All init systems basically work the same, when they work - when and how they fail is where they are measured. Sysv, openrc, I've had 0 problems with these over the last 20 years, something might not start up without a little intervention - but the system would, and it could be fixed. Systemd, on the other hand, currently running on maybe half my servers, generally works - but not all the time, and that's the big difference to my mind. For example, I had a netbook that I couldn't get a systemd distro on, as it go into a loop - start up bluetooth, bluetooth would fail for some obscure driver reason, I imagine it was some sort of dependency as systemd would try to start it again, over and over - leaving the system essentially hung. That's the sort of way systemd fails, and why my primary laptop runs gentoo without it.

      --
      !Equality through palindromes semordnilap hguorht ytilauqE!
    19. Re:systemd by Vlijmen+Fileer · · Score: 1

      Your comment is now valued at "Score:-1, Flamebait".
      I'd say that is indicative for the hysterical zeal with which systemd followers hammer down on anything and anybody who points out the fundamental and dangerous failures in it.

    20. Re:systemd by Tenebrousedge · · Score: 1

      I've written a small book about bash. Tell me what about it you think is an improvement on any other scripting language.

      Bash as a shell is mediocre. Bash as a programming language is shit. The language of Unix is C, and the Bash fanatics are the ones that cut their teeth on Unix in the mid-1990s and haven't learned anything since. There's a whole generation of programmers who didn't bother to learn anything about cgroups or why systemd exists in the first place.

      --
      Those who advocate genocide deserve every protection afforded by law, and none afforded by common human decency.
    21. Re:systemd by Barsteward · · Score: 1

      quite right too as its full of nonsense as usual. if there were "fundamental and dangerous failures in it" then i doubt redhat et al would be giving it to their customers - hence the flamebait indication.

      --
      "The hands that help are better far than lips that pray." - Robert Ingersoll (1833-1899)
    22. Re:systemd by gweihir · · Score: 1

      Indeed. The systemd idiots are waging an emotional campaign on a technological issue. That is about the most stupid thing possible. And they continue to demonstrate their utter cluelessness at any possible opportunity. At this time, the systemd proponents resemble a fanatical sect more than anything else.

      --
      Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
    23. Re:systemd by gweihir · · Score: 1

      "Appeal to authority" fallacy. Well, you have proven to be stupid before and you continue to do so. At least you are consistent.

      --
      Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
    24. Re: systemd by gweihir · · Score: 1

      While I expected I could stay away from all the systemd failure, I recently got hit as well. I have a netbook that is used for one purpose: Access to serial consoles via USB-serial adapter. Accidentally, it got downgraded to use systemd. And what does systemd break? Right, the serial adapter! The kernel detects it just fine, but then systemd and its tools mess with it and _remove_ it without good reason and without any useful diagnostic. That is _not_ the Linux I have come to know an love.

      Of course, removing systemd again fixed the issue, but one has to ask who such utter crap can make it into a supposedly stable release.

      --
      Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
    25. Re:systemd by Kazymyr · · Score: 1

      486DX50 (yes not DX2) on Octek Hippo DCA2 motherboard with 16MB RAM and a total of 5 HDDs (3 IDE and 2 SCSI) salvaged from older computers in a RAID0 configuration for a total of 1.3GB, with Slackware 3.6

      --
      I hadn't known there were so many idiots in the world until I started using the Internet -Stanislaw Lem
    26. Re:systemd by Tenebrousedge · · Score: 1

      Don't get me started! Ever thought that some might not even WANT cgroups support in their system?

      In an embedded system maybe. Otherwise I'm sure I'd be thrilled to hear a non-stupid reason for that.

      systemd mandating it is a PITA!

      Because you'd rather not run a recent kernel? Either you'll never know that cgroups are there or you've already recompiled both your kernel and systemd/OpenRC to disable them.

      Just like relying on journalctl program running on a working booted system to diagnose in log why same system didn't boot.

      The binary logs contain the normal text that any other log would have, plus a short checksum or somesuch that serves as an integrity check. They're legible with or without journalctl. However, journalctl is a rather nice way to dig into said logs.

      And suggesting to use gcc to adjust a system's boot behavior you must be kidding me .

      Outside of sysvinit pretty much all init systems are written in C. None require you to use anything but a text editor to change process behavior.

      ...veterans...have chosen shellscripting -- not bash! -- since it is the best tool for the job at hand.

      Again, I literally wrote a book on the subject, and I beg to differ. However, if you have some argument to support the notion that process management is best done with shell scripts, you'd do a lot better to actually make that argument instead. Relying solely on argument from authority is not going to get you very far. Generally, you seem to be ignorant of the many reasons and methods which have led to sysvinit's replacement, so I can't imagine you have much of an argument to make, but do knock yourself out.

      --
      Those who advocate genocide deserve every protection afforded by law, and none afforded by common human decency.
  2. Choice is good by mx+b · · Score: 5, Interesting

    I'm glad to see Devuan gearing up for a release. While Debian is not my favored flavor of linux, and I personally don't see any problems with systemd, I also recognize that this is exactly why different distros exist: we all have different needs.

    So cheers to the Devuan team on this upcoming release, and best wishes for many more.

    I hope this will help end the systemd "debate". I get a little tired seeing the constant re-treading of which one is better. If you like systemd or don't care, you have distro options. If you don't like systemd and DO care, you also have at least one distro to choose from. Use the tech that makes most sense for you.

    1. Re:Choice is good by LVSlushdat · · Score: 1

      Actually at least two, the other being Slackware.. From what I gather, Pat Volkering, Slackware's head-honcho hates systemd with a burning passion......

      --
      THANK YOU, Edward Snowden!! Americans owe you a debt of gratitude (whether they know it or not..)
  3. for how long will it be viable? by Anonymous Coward · · Score: 2, Insightful

    GNOME, KDE, and Cinnamon have been removed from tasksel, but can still be installed although they "are known to suffer from some glitches due to the lack of systemd

    Thing is, I consider KDE the only desktop GUI worth using anymore. (Notice I didn't say "only Linux GUI worth using". Haven't found a better one on another OS either). The way these things tend to unfold over time is the "glitches" become "bugs" and the "bugs" become "doesn't work at all without heavy merging work" and that becomes "impossible to keep working without people dedicated to the task".

    I wonder if this is going to be a viable thing to do over time as dependencies on systemd in upstream software become deeper.

    1. Re:for how long will it be viable? by yeupou · · Score: 1

      That is unfortunately a serious concern. A question I asked in 2015 here https://linux.slashdot.org/sto... and I am afraid situation is only worse now.

    2. Re:for how long will it be viable? by TWX · · Score: 1

      What's going-on in non-Linux? BSD and the like? Shouldn't their windowmanagers port over to a non-systemd Linux distro easily enough?

      --
      Do not look into laser with remaining eye.
    3. Re:for how long will it be viable? by HiThere · · Score: 1

      The interesting thing is, the last I heard both Gnome and KDE ran on BSDs. And the FreeBSD website currently lists both of them as choices.

      --

      I think we've pushed this "anyone can grow up to be president" thing too far.
    4. Re:for how long will it be viable? by TWX · · Score: 1

      Sounds to me like there's a pathway to make them both work without systemd then, even if it requires looking at what might be unique about the BSD port.

      --
      Do not look into laser with remaining eye.
    5. Re:for how long will it be viable? by nukenerd · · Score: 1

      Sounds to me like there's a pathway to make [Gnome and KDE] both work without systemd then, even if it requires looking at what might be unique about the BSD port.

      I am using KDE on Devuan beta and the only thing I have noticed that does not work in KDE (and does not even exist as an option) is a suspend mode. I can still suspend from a root command line though with pm-suspend

    6. Re:for how long will it be viable? by Aighearach · · Score: 1

      No coding or porting is needed, it is only a matter of package management.

      None of the systemd-haters who claim on the internet to be sysadmins are really sysadmins. There are lots of complainers who claim to have technical Special Needs that systemd doesn't meet, the problem is none of them are technical enough to manage a fancy zipfile that holds the configuration they want together. If only they had a Jr sysadmin or web programmer among their numbers, they could just maintain a PureGUIwithNOsystemdPackageDependency.rpm or whatever.

      But if they understood how to create what they want, and how easy it is, they'd also accidentally learn that they don't have to run systemd at all to use any of those window systems, all they have to do is let a small part of it get installed to meet the requirements of the package manager.

      Gnome and KDE don't want to have to know which init system you have installed, and they have to make sure various support files get installed for various use cases. That is why there are package dependencies. Because distro maintainers have experience with which dependencies need to be installed all the time so that features can be activated from config files, and which ones don't. Which ones create extra work if you want to leave them out, and which ones don't. For the same reasons, when I install GCC on x86-linux and I also install a cross-compiler for ARM, I end up with support for all sorts of CPUs in addition to the one I actually have. Maybe I'm only trying to target one ARM microcontroller from Texas Instruments, but I end up with SPARC support at the same time. It is not actually a problem. Things are grouped into packages for reasons.

    7. Re:for how long will it be viable? by Vlijmen+Fileer · · Score: 1

      "I consider KDE the only desktop GUI worth using anymore."

      That put a wry smile on my face. KDE is the desktop equivalent of the html blink tag, and Word's marching ants. Each new version I give it a try again, and each time its basic failing, of being far too intrusive, and having a UI design seemingly thought up by a drunkard on LSD, is still there.

    8. Re:for how long will it be viable? by ruir · · Score: 1

      If you are so smaart, maybe you should lunch your own linux distribution. And yeah, many of us are running Linux pretty well without system.
      However, it is no longer a question of package management. Several packages have already dropped support for other boot managers.
      You would better inform yourself better oh mighty one.

  4. how's the HW driver support? by Anonymous Coward · · Score: 1

    Do the NVidia hardware drivers work OK on this? I'm wondering if my games collection would be OK on it. The open source graphics drivers aren't suitable for modern games, so it's closed source or bust for that. One thing about Ubuntu is they make getting the gfx drivers and keeping them up to date effortless.

  5. Did try RC1, works fine as it is, glitch for KDE by what+about · · Score: 3, Interesting

    Comments on the RC1

    Install for the default version works well

    installing the kde version was not available as install option but needs
    # apt-get install task-kde-desktop

    wicd integration works, but NetworkManager does not
    some issues on handling permissions smb4k does not work as normal user but needs to be run using kdesudo

    I am really looking forward to use it on all my machines.

    systemd surely is a NSA work

    Going to test RC2....

  6. KDE and Cinnamon can run fine without systemd. by sombragris · · Score: 4, Interesting

    GNOME, KDE, and Cinnamon have been removed from tasksel, but can still be installed although they "are known to suffer from some glitches due to the lack of systemd."

    Cannot say anything on GNOME, but KDE (both KDE4 and Plasma 5) run fine in Slackware. As for Cinnamon, there's also an excellent distribution for Slackware, Cinnamon Slackbuilds . There are also implementations for Xfce, MATE, Lumina and LX-Qt, all up to date and fully functional. No glitches due to lack of systemd at all.

    I'm typing this on a Slackware64-current box, using the latest KDE Plasma with no trace of systemd.

    Since Slackware manages to avoid systemd like the plague even to this day, using modern desktop environments in a systemd-free environment should be no problem.

    --
    -- Look to the Rose that blows about us--"Lo, Laughing," she says, "into the World I blow..."
    1. Re:KDE and Cinnamon can run fine without systemd. by LVSlushdat · · Score: 1

      Didn't Pat Volkerung (sic) the Slackware "head-honcho" say systemd was evil and would NOT appear on Slackware as long as he controlled it??? Seems I heard something to that effect a while back...

      --
      THANK YOU, Edward Snowden!! Americans owe you a debt of gratitude (whether they know it or not..)
    2. Re:KDE and Cinnamon can run fine without systemd. by walterbyrd · · Score: 1

      Actually he said that systemd may be inevitable for Slackware.

  7. Re:Upgrade breaks shutdown by TWX · · Score: 1

    The only Devuan install I've done was a fresh install. I'm using it as a multimedia PC in my entertainment center and it's working fine.

    --
    Do not look into laser with remaining eye.
  8. MX Linux by supertall · · Score: 5, Informative

    For those interested in a polished out-of-the-box distro that does not use systemd, MXLinux is based on Debian Jessie and defaults to sysVinit. I'm a fan.

    1. Re:MX Linux by gomadtroll · · Score: 1

      +1, another satisfied user..like the lack of noise..
      greg

  9. Re:Upgrade breaks shutdown by drinkypoo · · Score: 1

    Yes, likewise. I have Devuan installed on a low-power Athlon X2 3800+ system with 8GB RAM and 8GB flash (it was lying around) and I'm molding it into a CarPC. Would have just used Debian if not for systemd. Kodi, Navit. Works a treat, except that I got corruption with the nvidia driver. That might just be me running into the limits of my PicoPSU, though. Nouveau works fine.

    --
    "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
  10. MATE by Anonymous Coward · · Score: 1

    MATE works just fine without systemd

  11. I'm on board by Bruce+Perens · · Score: 3, Interesting

    I installed Devuan on a laptop and will probably expand it to my other systems over time. I installed 1.0 and the absence of NetworkManager was a problem, so it's nice to see that this new version includes it.

  12. Are all pro-systemd folks anonymous cowards? by shoor · · Score: 2

    From my (admittedly casual) perusal of these followups that is what it seems like. Come on, who is willing to say:

    I'm pro-systemd and I'm proud!

    and sign with their slashdot monicker.

    In case anyone is curious, I would like to avoid systemd myself, and I resent that it's getting hard to do that. As for why I'm opposed, I don't have any facts I can cite as clinching arguments. I do see mysterious things happening on my latest Ubuntu and Mint distros that I don't know the cause of, but they don't happen on slackware. As an old time Unix guy (going back to BSD 4.2), the whole principle of systemd, not having init scripts that can be broken down and fixed with an editor, just seems wrong to me, and the claims I've seen about the advantages of systemd seem to have a suspicious amount of hand-waving, and a lot of "we know what we're doing you ignorant, backward luddite twerp!" to them. That's all.

    --
    In theory, theory and practice are the same; in practice they're different. (Yogi Berra & A. Einstein)
    1. Re:Are all pro-systemd folks anonymous cowards? by shoor · · Score: 1

      Mr Coward, I put the words "ignorant, backward, luddite, twerp" into the mouth of a hypothetical systemd advocate. Your post reminds me that systemd folks don't use such language.

      --
      In theory, theory and practice are the same; in practice they're different. (Yogi Berra & A. Einstein)
    2. Re:Are all pro-systemd folks anonymous cowards? by Spasmodeus · · Score: 1

      I'm mostly pro systemd, but I see no reason to be "proud" about init system preferences. I refuse to become partisan about it.

      I didn't like systemd at first, but I made the effort to start learning it, and I've come to like a lot of its features.

      I don't bother engaging in these "discussions" (more like Two Minutes Hate), because most of the anti-systemd commenters are so rabid and irrational that they are impervious to facts or reason. I expect I'll be called an NSA shill or Pottering's cock-holster just for this comment.

      I'm all for choice, though, so I'm glad that there are non-systemd distros available. I'd like to think it would mollify the anti-systemd folks, but I'm sure they'll still reflexively foam at the mouth every time systemd is mentioned.

    3. Re:Are all pro-systemd folks anonymous cowards? by Kabukiwookie · · Score: 3, Insightful

      I'm all for choice, though, so I'm glad that there are non-systemd distros available. I'd like to think it would mollify the anti-systemd folks, but I'm sure they'll still reflexively foam at the mouth every time systemd is mentioned.

      Well, one of the reasons, people who don't want system-D foam at the mouth is that initially this choice was taken away. Quite a lot of people had to put in a lot of work to make sure that there was a choice, something pro-system-D people didn't appear to actually give one shit about when they were pushing hard to move all distros to use system-D.

      It's funny that, people getting upset because they have to do (a lot of) extra work, just because some other group of people push their agenda and don't give a damn about the consequences for anyone else as long as they benefit themselves. Who could have imagined that would upset people.

      --
      The mountains of madness have many little plateaus of sanity - Terry Pratchett.
    4. Re:Are all pro-systemd folks anonymous cowards? by Aighearach · · Score: 1, Troll

      I'm pro systemd and proud!

      Activating services when a network connection comes, and without sucking at it, is a hugely good feature. And just a tiny example.

      People whine and cry, whine and cry about loving their SysV init scripts. Personally, I think they're disgusting. Almost everything about SysV is disgusting and that was always true. That was even true when it was the best option, which is simply no longer true.

      Systemd is modular and anybody who tells you differently is an idiot who didn't check, or can't comprehend how software is built and distributed. Yes, the different modules are in the same source code repository. No, that doesn't mean it is monolithic.

      And even funnier, I'm still using all the SysV init scripts that I was actually using before. All the major distros support using both systems together, and if I already have a customized init script, I'm still using it! But those scripts are disgusting, I'm unlikely to want to create new ones when I need custom behavior in the future.

    5. Re:Are all pro-systemd folks anonymous cowards? by jimbo · · Score: 2

      I'm the spawn of Satan; I'm happily using Ubuntu with KDE, systemd and whatever audio subsystem it uses.

      I really don't have strong opinions. I've created and set up daemons on systemd and it was easy and logical. I've done the same for decades before systemd was a thing. In both cases I first had to learn how it was done.

      I've also used numerous desktop environments and I always made things work without harming my precious productivity. These days I find most desktop environments are just fine for me, just like I've happily used several different init/system management systems.

      I wouldn't bring pride into, pride is often a bad thing but I enjoy using the systemd system management environment. It's no biggie either way though.

      I hope that there is a lot of people out there who are relaxed, open minded and for whom it works and for that reason simply don't have reason to get involved in these flame wars.

      Then I understand there's a minority with real problems with systemd in production environments and I'm happy they have other options.

      Live and let live.

    6. Re:Are all pro-systemd folks anonymous cowards? by mvdwege · · Score: 1

      I like systemd. It is the only viable alternative right now to the old mess of SysV, and my primary use case is resource control: systemd can control process resources from the equivalent of setting a nice(1) value up to complete containerisation. In fact, I think it takes less from Windows (as the haters maintain) as it takes from Big Iron systems in terms of process isolation and management capabilities.

      It has warts: it feels overengineered, and using dashes in unit file names to represent / was a dumb idea: I hate having to escape options with a double dash just in case I have to manage a root unit.

      --
      "I know I will be modded down for this": where's the option '-1, Asking for it'?
    7. Re:Are all pro-systemd folks anonymous cowards? by thegarbz · · Score: 1

      No we're not.

    8. Re:Are all pro-systemd folks anonymous cowards? by Aighearach · · Score: 1

      If you can't find a module's makefile, try in its folder!

  13. That's the problem with systemd, not just an init by raymorris · · Score: 2

    > Rather than forking ALL OF DEBIAN so you can keep sysvinit, why not fork systemd to use only the init?

    That's the entire problem with systemd - it forgot it was supposed to be an init. Systemd has consumed more and more of the OS, and in ways that require *applications* to have dependencies on systemd.

    If it were just a bad init system, people would complain, but most would deal with it. Some would use a different init. Systemd doesn't work that way. Like a particularly nasty rootkit, you have to replace half the system to get rid of systemd.

  14. Re:Not RedHat by nukenerd · · Score: 1

    Only RedHat derived distributions or Ubuntu are worth using for any serious work.

    Idiot

  15. Re:Why does systemd have to be so obnoxious? by nukenerd · · Score: 1

    Speaking as someone who has no real skin in the game either way I just don't understand the point of systemd or what benefit it gives me as a user who has a Linux server to run some basic services...

    They say it boots quicker. So when you or I have to reboot (as I do about once every 3 months) we won't have time to arrange our chair nicely while it boots. That's it, I think.

  16. Launchd by cadeon · · Score: 1

    Is anyone using launchd on Linux? If I recall correctly it's modern like systemd, but primarily in it focused like it should be.

    1. Re:Launchd by Barsteward · · Score: 1

      how many things are actually coupled to "init" PID1? or are you confused between systemd the init program and systemd the project - easy mistake to make when you don't research anything

      --
      "The hands that help are better far than lips that pray." - Robert Ingersoll (1833-1899)
  17. IMO: Radical changes are for radical improvements by walterbyrd · · Score: 2

    Systemd is certainly a radical change. It takes over everything. It completely throws away POSIX, and the UNIX philosophy. Systemd changes everything that made Linux, Linux.

    And for what? I see no substantial improvements. Just the opposite. I see a less stable system, more difficult to use, everything is hidden from the users.

    Systemd may benefit Red Hat, but it does not benefit anybody else.

    JMHO, of course.

  18. If you like systemd, u will love ms-windows by walterbyrd · · Score: 1

    Everything that is great about systemd, is even better in ms-windows.

    Want an OS that is controlled by a single for-profit corporation? A corporation that cares more about it's shareholders, than end users.

    Want everything hidden from the users? Everything in binary.

    Want an OS that has all kinds of mystery crap going on in the background?

    Want a less stable OS, and mysterious changes forced on you all the time?

    Want an OS designed by people who hate the UNIX philosophy, and have deep contempt for UNIX grey beards?

    MS-Windows has better drivers, better graphics, way more apps - especially games. MS-Windows apps are way more standard.

  19. Re:You are an idiot, STFU, GTFO! by Vlijmen+Fileer · · Score: 1

    "Debian violated it's charter when it made the systemd move. No if's, and's, or butt'$; at this point in time, Debian is mimicking RHat ..."

    Precisely!
    All knowledgeable people dumped RedHat like the pile of stinking poo it had become very long ago already for changing to be commercialised, non-compatible, and dumping Unix philosophy.
    Debian essentially did the same with their accepting systemd.

  20. Re:Did try RC1, works fine as it is, glitch for KD by Barsteward · · Score: 1

    they didn't land on the moon either... it s big conspiracy

    --
    "The hands that help are better far than lips that pray." - Robert Ingersoll (1833-1899)
  21. Followup to my own post:Are all pro-systemd by shoor · · Score: 1

    I was thinking about the James Brown song "Say It Loud! I'm Black and I'm Proud!" when I put in the "I'm pro-systemd and I'm proud" remark. Maybe I should have included the "Say It Loud!" line. Then again, how many of y'all are old enough to remember that song.

    For myself, I wanted to show honestly my position that I'm wary of systemd but not an expert and not trying to present myself as somebody who 'knows'. But one of the things that makes me wary is that while a lot of people who make anti-systemd posts do so as themselves (or at least not as ACs), the ones who were pro-systemd were ACs, and that seemed kinda fishy to me.

    Anybody who takes a position one way or the other is going to catch some flames, and I can see how, in a forum where most people are against systemd (like slashdot) maybe pro-systemd folks figure it's not worth all the flaming to say what they think. But some did post in response to my call and I appreciate that.

    --
    In theory, theory and practice are the same; in practice they're different. (Yogi Berra & A. Einstein)
  22. Re:Why does systemd have to be so obnoxious? by ashkante · · Score: 1

    So you're basically saying that systemd is the "Lotus Notes" of init?