←back to thread

InitWare, a portable systemd fork running on BSDs and Linux

(github.com)
167 points sunshine-o | 1 comments | 03 Apr 25 12:11 UTC | HN request time: 0.202s | source
Show context
donnachangstein ◴[03 Apr 25 16:40 UTC] No.43572244[source]▶
Writing software specifically for the BSDs then licensing it LGPL is like trying to sell them chilled, bottled poison from a roadside stand. What were they thinking?

That said, this sounds like what systemd should have been: a service control manager and nothing more, before they got a thirst for power and wanted to control any and every thing about the system.

But one of those already exists, it's called launchd, as long as you don't mind XML vs Windows INI syntax.

replies(4): >>43572334 #>>43572338 #>>43576429 #>>43597276 #
wpm ◴[03 Apr 25 22:52 UTC] No.43576429[source]▶
I'll take the well documented (man launchd.plist) XML property list (well, XML rendered, they're usually in binary) any day over some flat unstructured nonsense. I loathe INI syntax.
replies(1): >>43577618 #
1. squiggleblaz ◴[04 Apr 25 02:07 UTC] No.43577618[source]▶
In case someone gets the misapprehension that there is a contrast between systemd and launchd in terms of the "well documented" attribution, systemd configuration is also well documented e.g. man systemd.timer etc. I didn't know if launchd has an equivalent of timers, but it does and I've just read `man launchd.plist` "StartCalendarInterval" and compared it with `man systemd.timer` "OnCalendar". I would have said they're about equal. Launchd is more concise, but systemd talks a lot about the interactions with other settings and edge cases.

As for ini vs xml, I've generally found xml is a crueller syntax for humans than ini. At the time I started using systemd, it was a bit funny - the last time I'd been editing ini files was on Windows 3.11. But I think ini and toml are now once again reasonably common so I forgot about how out of place it felt at the time.