Explainer: XPC
https://fed.brid.gy/r/https://eclecticlight.co/2026/02/07/explainer-xpc/
http://jdebp.info/FGA/launchd-on-bsd.html
It went dormant some time in 2015, to my knowledge. I had genuinely been joking about an #XML parser in process 1 until someone went and did that.
With a shell, of course, it's the same sort of thing, with a full language parser, an interactive user interface, curses, terminfo/termcap, an editing library, command completion add-ins, and so forth, in the program for process 1.
Almost all proper process 1 programs do far less.
@CursedSilicon @gettie mostly because #systemD (and it's competitiors) took all the right lessions:
And basically everyone (#OpenRC, #Upstart, etc. Even #LaunchD [the #init for #macOS that is literally the SystemD but before SystemD and by Apple] and #SMF [#Sun's SystemD for #Solaris] did that to allow for boot times in secinds, not minutes…
@fabiscafe @okapi OFC @chesheer 's criticism is understandable on #FreeBSD given that #SystemD is inherenty focussed and intertwined with #Linux (just as it's Inspiration, #LaunchD, is intertwined with #macOS's Darwin/NeXTstep kernel).
And sadly there's nothing they (or anyone else) could've done unless they had multiplied suddenly and being able to keepcthe old tech stack maintainable.
OFC I wish for more diversity in solutions, but #Linux being #streamlined is what makes #portability across distros easier and boosted adoption as well as providing massive gains in solutions like #DXVK, #Proton and #Wine in general.
@fabiscafe @okapi espechally in the form of an interactive desktop...
I could see it valid for multiple shell sessions, but #tmux & #screen cover that pretty well.
If one has to login into different machines then chances are #aithentification is centralized anyway.
Needless to say #modernizations like #SystemD don't happen because people like #Poettering are "hobbyless", but because the preexisting status-quo (#SysVinit) was slow, inflexible and error-prone by strict linearity and non-parallelization.
/etc/init file one can literally get a system to hang due to a mistake (i.e. certain call doesn't get invoked correctly), whereas on #SystemD (and competing solutions like #LaunchD on #macOS and #SMF on #Solaris) your desktop / laptop will continue to noot even if it doesn't have a network connection. Not to mention as Benno Rice explained: 'Shit just gotmore dynamic!': We don't have that one big ass maingrame and serial terminals, instead we have laptops that may he carried around a campus or traveled with all day and that constantly switch between wireless and wired networks and have VPN tunnels open and whatnot...
🐌 Wow, someone found a way to make their #localhost #setup even more convoluted! Now, instead of just typing "localhost:4333", you can go through the joyous process of configuring #launchd daemons, editing /etc/hosts, and wrangling #Caddy for that sweet appname.localhost experience. 🧙♂️ Truly the pinnacle of #productivity for when you have too much time and not enough friends. 🤦♂️
https://inclouds.space/localhost-domains #devlife #HackerNews #ngated
Learn from the voice of experience when saying such things. (-:
I used to joke about someone putting an XML parser into the code for process #1, as an example of something outlandish that no-one would do.
Then one of the people who tried to port launchd to FreeBSD did exactly that.
Upstart both rose and fell in the time that it has taken even to get launchd ports to the BSDs attempted, let alone to Linux-based operating systems.
launchd leans heavily on MacOSisms.
@freya @BrodieOnLinux makes sense, ofc.
/etc/init file for space reasons alone.Tho in fairness I'm shure #SMF did inspire #Apple to do #LaunchD which in turn was copied with #SystemD, abeit all 3 are very much centric about the Kernel and Userland they target.
@rust_discussions in contrast to what the article claims, socket activation wasn't pioneered by Apple's #launchd, but much earlier in 1986 by #inetd as part of BSD 4.3.
@shupfel There were quite many #BSD developers interested in #launchd. The drama around system seems to be really a Linux thing.
https://www.youtube.com/watch?v=o_AIw9bGogo
@BestGirlGrace yes, and they'll basically refuse to accept the #InconvenientTruth that #systemd is at worst a "#NecessaryEvil" because what came before it was way worse, competing solutions failed to get adopted and even mainline #Unix like #Solaris (#SMF) and #macOS (#LaunchD clearly is the inspiration for SystemD!) did the same...
@nuintari @pid_eins @OS1337 Again: I disagree as both #SMF and #LaunchD do more than just #init amd like #systemd are a whole collection of utilities and not a single massive binary.
In fact, #journalctl is an evidently better way to debug issues and fix problems with #services / #daemons than having to parse #Syslog through dozens of filters or spechalized tools.
Similarly, if #gstreamer & #ALSA / #OSS / #PulseAudio weren't shitshows, we'd not see the need for #PipeWire!
@nuintari I disagree.
#SystemD is a "necessary evil" because what existed previously was bad for anything that isn't a "build once never change" server that never gets changed much...
https://www.youtube.com/watch?v=o_AIw9bGogo
The only reason I "cut" systemd from @OS1337 as of now is because I can't make it - or the #GNUtils that preceded it - fit within the few hundred kB on a 1.440 kB FDD I can spare.
Noone wants to go back to #SysVinit when even the fastest systems took longer to boot that most peoole need to make a shitty coffee or dump ass on the toilet.
Periodic Backup of a Mac Folder on a Synology NAS
https://en.ileif.de/wp-content/uploads/2024/06/image2-150x150.webp
This article describes how to use rsync in a shell script to create backups of your Obsidian Vault. It then guides you through setting up this script for a 1‑click backup solution using Apple Shortcuts and automating periodic backups using launchd on macOS.
#automation #launchd #macos #obsidian #shortcuts
https://en.ileif.de/2024/06/15/periodic-backup-of-a-mac-folder-on-a-synology-nas/
Regelmäßige Backups von Mac-Ordnern mit rsync und launchd auf ein Synology NAS
https://ileif.de/wp-content/uploads/2024/06/rsync-launchd-150x150.webp
In diesem Artikel wird gezeigt, wie man regelmäßige Backups von Mac-Ordnern auf ein Synology NAS mithilfe von rsync und launchd einrichtet. Die Anleitung umfasst die Konfiguration des Backup-Skripts, das Einrichten der Automatisierung mit launchd und den Umgang mit möglichen Problemen.
#automation #launchd #Mac #obsidian
https://ileif.de/2024/06/11/regelmaessige-backups-von-mac-ordnern-mit-rsync-und-launchd-auf-ein-synology-nas/