Arch Linux Is Switching To Systemd

[n3wu53r]

I stopped using my installation of Arch when upgrading offered NO OPTION but to install systemd.

My experience with other distros using systemd is: If it works you don't even know its there.
If it doesn't work YOU, the user have little control, or knowledge, of how to fix it.

My view is that systemd is a complicated solution looking for a problem to fix.
I had NO PROBLEMS with booting, that I could not fix, until systemd came along.

If you just use the basic install a distro gives you, likely you won't care about systemd.
Assuming the distro developers can learn how to setup and use systemd.

If you are a tweaker, and like to change things, systemd has a LONG way to go before it is usable.
Perhaps in the future 3rd party developers will produce an interface for humans to control systemd.
Until that time I still have other options. Debian and slackware to name a couple.

NO option but to install systemd? You must be mistaken.
https://www.archlinux.org/news/syste...replaces-udev/

Switching to systemd is the topic of this article.

[ninez]

Wow, so much FUD in this thread, just like all the threads in the arch-general mailing list.

A. You can still use rc.conf, some of the Arch devs have worked hard to make their systemd be able to read the DAEMONS array so no changes necessary, though they are recommended to match upstreadm.

B. The main selling point of systemd is not speed, though it is much faster. The reason the devs are all so eager to switch is because systemd service files are MUCH easier to write than initscripts. Not only are they much faster to write but they're portable so the hope is upstream will eventually be able to maintain their own service files and the devs jobs will be much easier. People do things that make their lives easier - surprise!

C. They didn't force you to install systemd, systemd-tools is a collection of small binaries which are useful to any init system - Arch's initscripts make heavy use of them. AFAIK they're still not forcing you, but it will be default and they probably will force you eventually.

+1 ...and very well said. I had also been following the threads on the list and was a little surprised by some of the comments.

I wasn't sure if i was going to like systemd, at first. but after switching over and familiarizing myself with it - i quite like it. My system boots faster (small benefit, no big deal) but the service files are easy to work with and fairly straight-forward.

I think it is a good move for Archlinux to switch now rather than somewhere down the line. I haven't switched my other Arch machine yet, but i think i will do that sometime over the next few days.

[RealNC]

Good thing he didn't begin his computing with CP/M. He would still be using it because the boot system of MS-DOS was a bit different.

[Delgarde]

I stopped using my installation of Arch when upgrading offered NO OPTION but to install systemd.

My experience with other distros using systemd is: If it works you don't even know its there.
If it doesn't work YOU, the user have little control, or knowledge, of how to fix it.

Learn how to use it. It's not like you knew how to maintain the traditional bootscripts before you learned how they worked...

[RealNC]

Another thing about systemd is that it uses the Linux kernel more. Other init systems usually only make use of POSIX calls. Linux-exclusive features are not used at all.

[TheCycoONE]

Wow, so much FUD in this thread, just like all the threads in the arch-general mailing list.

A. You can still use rc.conf, some of the Arch devs have worked hard to make their systemd be able to read the DAEMONS array so no changes necessary, though they are recommended to match upstreadm.

B. The main selling point of systemd is not speed, though it is much faster. The reason the devs are all so eager to switch is because systemd service files are MUCH easier to write than initscripts. Not only are they much faster to write but they're portable so the hope is upstream will eventually be able to maintain their own service files and the devs jobs will be much easier. People do things that make their lives easier - surprise!

C. They didn't force you to install systemd, systemd-tools is a collection of small binaries which are useful to any init system - Arch's initscripts make heavy use of them. AFAIK they're still not forcing you, but it will be default and they probably will force you eventually.

[RollMeAway]

Users loosing control?

I stopped using my installation of Arch when upgrading offered NO OPTION but to install systemd.

My experience with other distros using systemd is: If it works you don't even know its there.
If it doesn't work YOU, the user have little control, or knowledge, of how to fix it.

My view is that systemd is a complicated solution looking for a problem to fix.
I had NO PROBLEMS with booting, that I could not fix, until systemd came along.

If you just use the basic install a distro gives you, likely you won't care about systemd.
Assuming the distro developers can learn how to setup and use systemd.

If you are a tweaker, and like to change things, systemd has a LONG way to go before it is usable.
Perhaps in the future 3rd party developers will produce an interface for humans to control systemd.
Until that time I still have other options. Debian and slackware to name a couple.

[ulenrich]

The next step of computation technology will be to aid in some real ai way. For this to achieve there might be needed some thousands of different services waiting to get in action. Alike to get stoped in an interdependend way. I don't think this can be done via a simple rc file ...

[RealNC]

Next step: registry?

Gnome has already switched to a registry for a while now and they run a background process dedicated to it.

[energyman]

Luddites tend to be hairy, but don't confuse them with neckbeards.

Change is cool and technology is cool. Systemd kicks ass, but only if it is setup correctly. Just like Pulseaudio kicks ass, but only if it is setup corrrectly.

Most distros, in terms of number of distros, don't set it up correctly.

you kknow what kicks ass? Not using a superfluos sound daemon in the first place.