News for hackers. Stuff that matters.
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?