4 ms·
FreeBSD should not adopt launchd (2015)
- bsder 6y agoCan we get a 2015 tag on this, please?
- dontbesquare 6y agoWhy? Please explain for those of us like me who don't understand.
- seniorivn 6y agothis article is a 5 year old argument in bsd dev community, it's impossible to know if it's relevant from an outside perspective
- CaliforniaKarl 6y agoWhen something is posted that was not published in $CURRENT_YEAR, it is convention to add the year of publication, in parenthesis, after the title. (Some leeway is provided during the first few months of $CURRENT_YEAR.)
- deleted 6y ago[deleted]
- jsiepkes 6y agoBesides this being a 2015 thing since Apple no longer provides the sources of launchd so I highly doubt this is still a thing.
- ksec 6y agoDo we known why Apple no longer provide the source?
- pjmlp 6y agoI guess MIT license freedom.
- jcfields 6y agoThey wrote it, so they could close its source regardless of the license (which was actually Apache 2 and APSL before that). It looks like 10.9 (released in 2016) was the last release on https://opensource.apple.com/ https://opensource.apple.com/ that included launchd. The original author left Apple in 2014, so maybe it had something to do with that (similar to why they abandoned MacRuby and CUPS), though one would think that they still update it internally.
- vlovich123 6y agoThey do. Launchd/Mach/xpc are still critical technology pieces that underlies every service and nearly every single framework (since most of them just delegate to a service). It’s gotten smarter over the years. Launchd now supports complex Jetsam configuration parameters which let you specify RAM and CPU thresholds when your daemon is active and not (to be robust against memory leaks)
- saagarjha 6y agoApple owns launchd, though, and it was available under APSL and Apache before going closed-source.
- dlivingston 6y agoHere’s an interesting lecture from the primary developer of launchd (which “launch’d”, pun intended, on Mac OS X Tiger) discussing its design goals and implementation: https://youtu.be/mLwn_TbBntI https://youtu.be/mLwn_TbBntI
- saagarjha 6y agoYeah, I never really understood why you'd want to adopt launchd anywhere but macOS. It's pretty clear that launchd was designed for Mac OS X first and foremost, so a number of its semantics just don't really make sense anywhere else. As a toy it would be interesting to have around, but I doubt anyone would want to ship it in an official distribution.
- arminiusreturns 6y ago> Yeah, I never really understood why you'd want to adopt launchd anywhere but macOS. Systemd took much of it's inspiration from launchd... at least I recall seeing this somewhere, but I could be wrong.
- moonchild 6y agoYes, and pulseaudio was also heavily inspired by apple's coreaudio.