News for hackers. Stuff that matters.
Re:Portable systemd services by m3rc on Thursday November 17, 2016 @01:00AM (#12974769)
I used to spend time arguing with people on the internet about how systemd was an actually very useful tool but I never changed any minds and didn't help myself any. Now I just wait and watch for new helpful things it does to show up and I live a much happier life.
Re:Portable systemd services by badsock on Thursday November 17, 2016 @02:06AM (#12975076)
I almost think there should be a divorce. Call it systemdOS and be done with it. At that point every service it subsumes will be seen as a step closer to the obvious end-goal rather than a point of contention. And the other OS can be something like the Gnome2 fork MATE.

It's not a technical thing, it's cultural. The two sides are playing tug-of-war with the same OS, and systemd's winning, but maybe it would be better to have a positive culture around the changes they're making instead of always having people dragging on the rope. Some forks have been good in the past - EGCS/GCC for example.

Re:Portable systemd services by SwellJoe on Thursday November 17, 2016 @02:12AM (#12975111)
> Call it systemdOS and be done with it.

Every major Linux distro has chosen systemd as their future. I think that means whoever wants something different needs to change their name, rather than every major Linux distro changing theirs. Just as the Gnome 2 fans chose a new name for their future based on that lineage.

Re:Portable systemd services by yedpodtrzitko on Thursday November 17, 2016 @05:05AM (#12976063)
If you would tell me "this will just fix & improve init system" then that would a no-brainer. However I feel like the scope of the project has massively changed over time, so people (distros) who agreed with something a year or two ago could have a different opinion nowadays.
Re:Portable systemd services by SwellJoe on Thursday November 17, 2016 @03:58PM (#12981492)
> so people (distros) who agreed with something a year or two ago could have a different opinion nowadays.

Do you have an example of a distro that feels that way?

I only follow Fedora and RHEL/CentOS close enough to know, and they're still quite pro-systemd on all fronts, though there's still some hybrid stuff sticking around for backward compatibility and user comfort (so, a lot of stuff people were used to doing in the past still works the same on systemd-based systems).

Re:Portable systemd services by kasabali on Tuesday November 29, 2016 @03:58PM (#13066233)
> Do you have an example of a distro that feels that way?

Void Linux switched from systemd to runit.

Re:Portable systemd services by mfukar on Thursday November 17, 2016 @03:39AM (#12975576)
> as their future

..and here I was thinking they chose it as an init system.

Re:Portable systemd services by fapjacks on Thursday November 17, 2016 @03:38PM (#12981274)
Well, hopefully now you see that it never was just an init system. It is literally the future of Linux in the eyes of its proponents, as it gobbles up more and more crap. And people wonder why there is opposition to systemd!
Re:Portable systemd services by snaky on Thursday November 17, 2016 @04:35AM (#12975895)
> Every major Linux distro has chosen systemd as their future

Gentoo is a major Linux distro too.

Re:Portable systemd services by SwellJoe on Thursday November 17, 2016 @05:03AM (#12976054)
I don't really stay on top of popularity of distros, but I'd be surprised if Gentoo is in the top 10, in terms of usage. But, when I say "major Linux distros", I mean, specifically: RHEL/CentOS, Ubuntu and Debian, as those are clear market leaders on the server (I mostly pay attention to the server space). Fedora, Mint, and maybe Arch comes into the picture for desktop, I guess? SuSE seems to be on the rise again. All of those are systemd, I think.

I guess one can argue about what level of popularity makes something a "major Linux distro". I, personally, wouldn't put Gentoo into that category, unless I saw some evidence of dramatic increase in its usage.

Re:Portable systemd services by belorn on Thursday November 17, 2016 @05:00AM (#12976033)
Correct me if I am wrong here, but I thought Gentoo user had to make active choices when it came to make, compile and configure an installation, and that Gentoo as a distribution had a hands-off approach when it came to make decisions for the user. Is there a "default" init system, where if the user make no decision they end up with a specific one?
Re:Portable systemd services by pdkl95 on Thursday November 17, 2016 @05:30AM (#12976167)
https://wiki.gentoo.org/wiki/Comparison_of_init_systems

Gentoo officially uses OpenRC (and eudev), which is what you get if you follow the installation handbook. However, Gentoo also encourages choice and allows many options for init, daemon management, etc, which includes systemd. Other options ( are also available, too, at least unofficially.

> if the user makes no decision

While OpenRC is the official default, the "compile and setup everything yourself" nature of Gentoo makes this kind of statement somewhat irrelevant. One of the major reasons to use Gentoo is the ability to pick the components you want in your OS so it meets your specific needs. So yes, while there is a default, the concept of having a "default" is less important when you are installing everything manually.

Re:Portable systemd services by badsock on Thursday November 17, 2016 @02:25AM (#12975173)
Fair enough. It just seems like it might be useful to have a symbolic split of some kind, where people choose a camp instead of trying to pull in both directions. Naming can do that.
Re:Portable systemd services by SwellJoe on Thursday November 17, 2016 @02:39AM (#12975249)
Devuan is, apparently, a fork of Debian without systemd, so there are seemingly reasonable options for going that path. I, personally, won't miss initscripts, but one of our customers has been begging for a Devuan port of our products, so I guess some folks are excited about it.
Re:Portable systemd services by emmelaich on Thursday November 17, 2016 @02:53AM (#12975323)
Only systemd opponents think it is cultural.

Systemd is just fixing things that have been broken for a very long time.

Re:Portable systemd services by 2bluesc on Thursday November 17, 2016 @03:20AM (#12975486)
> Systemd is just fixing things that have been broken for a very long time.

This. I for one don't miss the mess of shell scripts for network management, init, bootloader, cron, etc. I personally think systemd already does 10x better at each of these tasks then the broken scripts have ever done.

Re:Portable systemd services by mfukar on Thursday November 17, 2016 @03:42AM (#12975589)
Changing the syntax of scripts managing devices and services is hardly an improvement by itself. Yes there are some ideas which have resulted in more useful tools for administrators (systemd-analyze and friends), along with more predictable behaviour which again helps administrators a lot, but apart from those systemd is just "fixing" things which were never an issue for the desktop user.
Re:Portable systemd services by SwellJoe on Thursday November 17, 2016 @04:38AM (#12975908)
"Changing the syntax of scripts managing devices and services is hardly an improvement by itself."

That's not what has been done.

systemd unit files are not "scripts". They are declarative configuration files, usually orders of magnitude smaller than the initscripts, network scripts, etc. that they replace. The Apache unit file on RHEL7 is ~17 lines long, and it replaced an initscript that was a couple hundred lines long.

It is a difference of both degree and kind.

Re:Portable systemd services by mfukar on Thursday November 17, 2016 @04:55AM (#12976013)
There's script & executable invocations inside systemd service files as well. They're simply handled differently. Some setups use dedicated units to just do `modprobe X`, and have "easy" dependency management. Some are replacing udev rulesets with systemd units, none of which are "orders of magnitude smaller".

Just saying, the de facto ways of using systemd are starting to diverge a lot from the intended behaviour. And of course, the de facto usage is what we'll judge each piece of software's merits on...eventually.

Re:Portable systemd services by untoreh on Thursday November 17, 2016 @12:05PM (#12979196)
I wouldn't call that diverting, but adapting already available scripts to systemd, and eventually they'll get rewritten
Re:Portable systemd services by mfukar on Thursday November 17, 2016 @02:44PM (#12980753)
Presenting the need to rewrite service scripts as an inevitability is not convincing anybody - and I hate shell scripts more than most.
Re:Portable systemd services by untoreh on Friday November 18, 2016 @04:50AM (#12985578)
I never said that they are going to be forcefully rewritten, I meant that whoever maintains initscripts might eventually rewrite them using systemd units more tightly because they are going be simpler and easier to maintain (in general, not because systemd is making anything any harder). You will still run something with systemd, this something can be the plain executable or an initscript, it is not like systemd checks and makes sure it likes whatever it is running...
Re:Portable systemd services by SwellJoe on Thursday November 17, 2016 @04:00PM (#12981504)
systemd has an initscript compatibility layer; it works with initscripts, and there is no expiration date on that functionality, to my knowledge. What more do you want?
Re:Portable systemd services by makomk on Thursday November 17, 2016 @05:02AM (#12976045)
Except that the more complex unit files still rely on shell scripts - they're just split off into separate files in another directory. systemd simplified init scripts by spraying their content over half a dozen or more different files and then only advertising the size of one them.
Re:Portable systemd services by jononor on Thursday November 17, 2016 @06:56AM (#12976617)
Got any examples?
Re:Portable systemd services by GFK_of_xmaspast on Thursday November 17, 2016 @07:58AM (#12977026)
If you're only a desktop user, where do you interact with systemd at all? I am, and I certainly don't.
Re:Portable systemd services by mfukar on Thursday November 17, 2016 @08:29AM (#12977216)
Precisely. No desktop user ever interacts with the init system.

On the other hand, Linux has a history of _forcing_ desktop users to mess with device management for the simplest of tasks, e.g. making their audio devices work.

Re:Portable systemd services by alphapapa on Thursday November 17, 2016 @03:10PM (#12981005)
> No desktop user ever interacts with the init system.

So you've never restarted a service on your desktop system?

Re:Portable systemd services by mfukar on Friday November 18, 2016 @03:06AM (#12985144)
On both Windows & macOS, I've created & managed services, and never had to restart them after they were deployed.

I don't use a Linux desktop (I often retry) because that is unattainable.

Re:Portable systemd services by beojan on Sunday November 20, 2016 @06:19PM (#13001843)
You've never changed the configuration of a service?
Re:Portable systemd services by yarrel on Thursday November 17, 2016 @03:27AM (#12975522)
The claim that systemd doesn't just fix init scripts packs two lies into a very small amount of space.
Re:Portable systemd services by wmf on Thursday November 17, 2016 @06:45PM (#12982936)
I don't know about that. I like systemd but I think it has a very different culture from classic Unix. (I never liked Unix culture.) It is probably possible to fix many of Linux's problems while keeping the old culture but no one can be bothered to do it.
Re:Portable systemd services by alphapapa on Thursday November 17, 2016 @03:08PM (#12980987)
The parallels between the systemd/anti-systemd "war" and the recent U.S. election are striking. I wonder if a "trumpid1" systemd competitor is in the future...haha...ha...
Re:Portable systemd services by upofadown on Thursday November 17, 2016 @03:27AM (#12975528)
> Call it systemdOS and be done with it.

I think of systemd as one component in an attempt to create a good desktop environment based on the Linux kernel. Sort of like how Android is an attempt to create a good phone environment based on the Linux kernel.

Based on that, I think it makes more sense to come up with a separate name for something like a Gnome/Wayland/Weston/systemd/Linux combination. While we are at it we could come up with a separate name for a Linux based system configured primarily by writing scripts. We should stop pretending that there is some sort of generic combination of things called "Linux".

Re:Portable systemd services by fnord123 on Thursday November 17, 2016 @04:58AM (#12976022)
>I think of systemd as one component in an attempt to create a good desktop environment based on the Linux kernel.

systemd works on systems as small as embedded systems up to huge hpc systems. It's not just a desktop thing.

Re:Portable systemd services by dozzie on Thursday November 17, 2016 @05:24AM (#12976129)
...for some value of "works".
Re:Portable systemd services by jononor on Thursday November 17, 2016 @07:07AM (#12976686)
...works better than sysvinit, and upstart.
Re:Portable systemd services by dozzie on Thursday November 17, 2016 @07:35AM (#12976868)
Except when it doesn't or when it's pain in the ass (embedded systems, or so I hear).
Re:Portable systemd services by mfukar on Thursday November 17, 2016 @08:57AM (#12977434)
You heard right.
Re:Portable systemd services by dasyatidprime on Thursday November 17, 2016 @03:56AM (#12975665)
I've been tentatively calling the former FDO/Linux or XDG/Linux, FWIW.
Re:Portable systemd services by mfukar on Thursday November 17, 2016 @03:40AM (#12975579)
Android is hardly a component. It's a fork. Systemd should also be a fork, that was the GP's opinion too, wasn't it?