xcmw has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
rb2k has quit [Ping timeout: 260 seconds]
philr has joined #nix-darwin
philr_ has quit [Ping timeout: 268 seconds]
LnL has quit [Ping timeout: 265 seconds]
LnL has joined #nix-darwin
kalbasit has joined #nix-darwin
xcmw has joined #nix-darwin
LnL has quit [Quit: exit 1]
LnL has joined #nix-darwin
rb2k has joined #nix-darwin
kalbasit has quit [Remote host closed the connection]
LnL has quit [Quit: exit 1]
LnL has joined #nix-darwin
LnL has quit [Quit: exit 1]
LnL has joined #nix-darwin
rb2k_ has joined #nix-darwin
rb2k has quit [Read error: Connection reset by peer]
rb2k_ has quit [Ping timeout: 260 seconds]
rb2k has joined #nix-darwin
rb2k has quit [Ping timeout: 268 seconds]
rb2k has joined #nix-darwin
hedgie_ has joined #nix-darwin
hedgie has quit [Ping timeout: 260 seconds]
rb2k has quit [Ping timeout: 260 seconds]
supersandro2000 has quit [Disconnected by services]
supersandro2000 has joined #nix-darwin
xcmw has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<stephank>
Oh, just noticed that WWDC video has a transcript. That's interesting. I guess, either these parts are still in-process, or it can't connect to the daemon from within the chroot?
<stephank>
It's not a Unix socket as far as I can tell. Maybe it's using Mach ports.
<stephank>
fwiw, at least /usr/lib/dyld itself needs to be available still, or the process is killed right away. But at least dyld itself only a couple of MB.
philr has quit [Ping timeout: 240 seconds]
__monty__ has joined #nix-darwin
<LnL>
I'm guessing it's dyld that's doing the xpc with it's daemon parts in that case
<LnL>
based on the explanation, that sends the binary data to be parsed along with stuff like DYLD_* to resolve it
<LnL>
but I'm not sure how that would know where it's chrooted