3 ms·
I do find it funny that people crap all over systemd, but don't seem to have a huge problem with launchd, despite the fact that systemd was almost a direct port
by tombert 7y ago
I do find it funny that people crap all over systemd, but don't seem to have a huge problem with launchd, despite the fact that systemd was almost a direct port of it.
Personally, while I do think that systemd's scope might have been a bit too ambitious, I do find it easier than something like Upstart
- telmich 7y agoI also think upstart was a bit nuts... but how do you think about openrc vs systemd?
- tombert 7y agoFreeBSD uses OpenRC right? I remember liking how easy it was to set up startup scripts in FreeBSD, so I think I like it? I'll admit I haven't used it as much as systemd or Upstart, so I can't give a strong opinion.
- snazz 7y agoIf you use a Mac, you don’t have much choice about your init system and probably don’t get into idealogical arguments about them as often as Linux users do. Plus, there’s always the BSDs, which don’t use systemd but still feel very clean and cohesive.
- JdeBP 7y agosystemd was not a port of launchd, direct or otherwise. The problem with launchd being difficult to port off MacOS is one of the reasons why launchd never came about for FreeBSD. * http://jdebp.uk./FGA/launchd-on-bsd.html http://jdebp.uk./FGA/launchd-on-bsd.html systemd was not a port of anything. And its immediate inspiration was Upstart, the system that Fedora was using at the time, and whose drawbacks provoked Lennart Poettering et al. to start working on systemd. (Interestingly, Upstart itself was inspired by the drawbacks of porting launchd.)
- tombert 7y agoAh, you may be right, that's what I get for trying to remember a talk without double-checking. I thought I remembered that systemd was a port of launchd here [1]. My mistake! [1] https://www.youtube.com/watch?v=o_AIw9bGogo&t=2178s https://www.youtube.com/watch?v=o_AIw9bGogo&t=2178s
- loeg 7y ago> systemd was not a port of anything. And its immediate inspiration was Upstart Its motivation was perhaps upstart's shortcomings, but systemd was definitely inspired by the design of launchd and that was repeatedly and explicitly mentioned in Lennart's very first blog post introducing it: > But first, let's clear a few things up: is this kind of logic new? No, it certainly is not. The most prominent system that works like this is Apple's launchd system ... > For socket activation we support full compatibility with the traditional inetd modes, as well as a very simple mode that tries to mimic launchd socket activation and is recommended for new services. > More importantly however, it is also our plan to experiment with systemd … to make it the ideal session manager… The problem set of a session manager and an init system are very similar… Using the same code for both uses hence suggests itself. Apple recognized that and does just that with launchd. And so should we… > Writing Daemons:: … The list above is very similar to what Apple recommends for daemons compatible with launchd. It should be easy to extend daemons that already support launchd activation to support systemd activation as well. http://0pointer.de/blog/projects/systemd.html http://0pointer.de/blog/projects/systemd.html
- JdeBP 7y ago
- clarry 7y ago> I do find it funny that people crap all over systemd, but don't seem to have a huge problem with launchd Because I've never been forced to use launchd. Well, you could say that I've never been forced to use systemd either but that's kinda how it feels when distros swap it out for you and things start depending on it. Guess what? I'd be furious if the distros I use forced me onto launchd all of a sudden.