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