systemd is a replacement for the sysvinit daemon used in GNU/Linux and Unix systems, originally authored by Lennart Poettering of Red Hat. It represents a monumental increase in complexity, an abhorrent and violent slap in the face to the Unix philosophy, and its inherent domineering and viral nature turns it into something akin to a"second kernel" that is spreading all across the Linux ecosystem.

This site aims to serve as a rundown and a wake-up call to take a stand against the widespread proliferation of systemd, to detail why it is harmful, and to persuade users to reject its use.

========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://boycottsystemd.org/"
linktext was:"http://boycottsystemd.org/"
====================================

I like this one:

systemd is viral by its very nature. Its scope in functionality and creeping in as a dependency to lots of packages means that distro maintainers will have to necessitate a conversion, or suffer a drift.

Sounds like a bug to me.

Sounds like a bug to me.

.....& a bloody big one at that!

There seems to be a lot of ex-Linux users turning up on the BSD forums lately, people are voting already.

I also worry about systemd. I don't like running things that I don't understand. If it gets to that I will likely switch to a slackware derivative. I tried gentoo, but couldn't even get it loaded due to the need to configure the kernel, and me not knowing what many parameters meant. The only one left once debian goes to systemd with jessie will be slackware, I think. Its quite a shame, IMO.

At least we should have a chance at being able to follow how something works.

If it gets to that I will likely switch to a slackware derivative.

Just something I am trying out on one of my many netbooks.


========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://forum.salixos.org/viewtopic.php?f=12&t=6131"
linktext was:"http://forum.salixos.org/viewtopic.php?f=12&t=6131"
====================================

I tried salix too but ended up moving on to another one called slackel. There was a puppy derivative I liked based on slackware, too but I forget which at the moment.

There was a puppy derivative I liked based on slackware, too but I forget which at the moment

Yeah. I sold one of my asus eeepcs with that on it. The 701SD I used to have.


========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://01micko.com/blog/blog/category/slacko/"
linktext was:"http://01micko.com/blog/blog/category/slacko/"
====================================


Ran good and was dumbed down enough for a Pecos,Tx Windows user. I had to include a Windows XP cd in the sale so I doubt he kept it on there. Even though I had skype and the kitchen sink thrown in.

We be pretty stone age backwards here, But I am not from here so I don't suffer from the local inbreeding.

Yeah, I've been there... done that.
Used to try out all lightweight Debian & Slack distros, but I keep coming back to deb based. __{{emoticon}}__
(Apart from SliTaz - it just intrigues me.)

It's not ready for production but
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://uselessd.darknedgy.net/"
linktext was:"uselessd"
====================================
may be a good solution in the long term:

uselessd (the useless daemon, or the daemon that uses less... depending on your viewpoint) is a project to reduce systemd to a base initd, process supervisor and transactional dependency system, while minimizing intrusiveness and isolationism. Basically, it’s systemd with the superfluous stuff cut out, a (relatively) coherent idea of what it wants to be, support for non-glibc platforms and an approach that aims to minimize complicated design.

uselessd is still in its early stages and it is not recommended for regular use or system integration, but nonetheless, below is what we have thus far.

I am not a fan of systemd or the devs it rode in on. Uselessd resolves my issues with systemd. It promises to be systemd done right. BSD support and support for the uClibc (a lightweight replacement for glibc) are big pluses.

IMO it could actually be an improvement over OpenRC (which I use and love).

========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"https://lists.debian.org/debian-ctte/2014/11/threads.html"
linktext was:"https://lists.debian.org/debian-ctte/20 ... reads.html"
====================================


========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"https://lists.debian.org/debian-devel-announce/2014/11/threads.html"
linktext was:"https://lists.debian.org/debian-devel-a ... reads.html"
====================================


keep the faith?

One of the debian technical committee members (Colin Watson) just announced his resignation
(er"intention to resign" in diplomacy-speak)

========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"https://lists.debian.org/debian-ctte/2014/11/msg00052.html"
linktext was:"https://lists.debian.org/debian-ctte/20 ... 00052.html"
====================================


Also, Ian Jackson has called for a vote, intended to clarify / reaffirm (or not) that, for jessie release, packages should _NOT_ depend on a specific init.
The ballot (voting underway Nov5--Nov18, open to the 1000 or so"debian develpers") also intends to clarify / stipulate
that an upgrade of an existing debian system should _NOT_ hijack (convert to systemd) the existing init

edit:
another resignation: Joey Hess (a DD with 18yrs tenure) (and a systemd proponent)

========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"https://lists.debian.org/debian-devel/2014/11/msg00174.html"
linktext was:"https://lists.debian.org/debian-devel/2 ... 00174.html"
====================================

========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"https://lists.debian.org/debian-devel/2014/11/msg00234.html"
linktext was:"https://lists.debian.org/debian-devel/2 ... 00234.html"
====================================

No, the fire is not systemd, it is the politicization of the project
via ctte and GR rather than patient evolution of the best technical
solution.

My two cents is that it's naive to dream of technology devoid of politics, culture, etc...

rokytnji wrote:

If it gets to that I will likely switch to a slackware derivative.

Just something I am trying out on one of my many netbooks.


========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://forum.salixos.org/viewtopic.php?f=12&t=6131"
linktext was:"http://forum.salixos.org/viewtopic.php?f=12&t=6131"
====================================

Looked at your thread. Very interesting, like Arte Johnson would say from Rowan & Martin's Laugh In. (Smoking cigarette and all.)

See, even scooter trash needs help sometimes. Loved it though.

thriftee wrote:I also worry about systemd. I don't like running things that I don't understand. If it gets to that I will likely switch to a slackware derivative. I tried gentoo, but couldn't even get it loaded due to the need to configure the kernel, and me not knowing what many parameters meant. The only one left once debian goes to systemd with jessie will be slackware, I think. Its quite a shame, IMO.

At least we should have a chance at being able to follow how something works.

I don't completely understand Linux, but I still run it. Do you completely understand everything that Linux does?

Slackware may not be able to avoid systemd either based on a reply I read on the Salix forums recently.

I'm not a fan of systemd because I think it's too encompassing. To its credit, it does boot and shut down much quicker. I have resigned myself to stick with Debian and see what happens. If things get too bad regarding systemd, I'm hoping that the Debian leaders will make necessary changes.

By the way, I thought this forum was for the discussion of non-Linux subjects.

KrunchTime wrote: I don't completely understand Linux, but I still run it. Do you completely understand everything that Linux does?

Slackware may not be able to avoid systemd either based on a reply I read on the Salix forums recently.

I'm not a fan of systemd because I think it's too encompassing. To its credit, it does boot and shut down much quicker. I have resigned myself to stick with Debian and see what happens. If things get too bad regarding systemd, I'm hoping that the Debian leaders will make necessary changes.

By the way, I thought this forum was for the discussion of non-Linux subjects.

Nope, but trying to learn, but what I do know is that it takes away some of what ability I do have. I have tried to kill it, but that doesn't work. I don't see parameters to tweak, either. To be honest, I don't understand how I can control it other than to use it to turn things off or on. And the net bottom line is that it eats memory, and on my old machines that are maxxed out, that's very not good. And no, it doesn't speed up ANYTHING that I have noticed, and on a P IIIm you can bet I would notice.

I am testing a Manjaro distro that uses OpenRC to replace systemd the moment, and have been successful trimming memory requirements, better than with the systemd version, which I was stumped on, and more memory available in turn improves performance. As soon as I go into swap, it gets so slow I might as well reboot, so if I can't keep the memory requirements down, i just can't run it on the older machines.

systemd seems to be more of a"religious" subject if you ask me. You either believe in the Gods or you don't.