<kloenk>
Hi, I'm trying to get my own arg into the eval process. but while doing so, nix doesn't like me, talking of infinit recursion
<kloenk>
I also would like to give more then one module into the process, but I only see the coniguration attribute, and no modules attribute
kalbasit has joined #nix-darwin
hedgie has joined #nix-darwin
kalbasit has quit [Ping timeout: 256 seconds]
eraserhd2 has joined #nix-darwin
eraserhd has quit [Ping timeout: 240 seconds]
eraserhd3 has joined #nix-darwin
eraserhd2 has quit [Ping timeout: 240 seconds]
<abathur>
has anyone successfully used anything that depends on osxfuse? I've tried several and they all end up causing a "fuse: failed to exec mount program: No such file or directory" error
<abathur>
not sure if the package builds but doesn't work, or if I'm holding it wrong
philr has quit [Ping timeout: 264 seconds]
<LnL->
abathur: you till need to install the kerneel modul through the regular pkg installere
<abathur>
aha; is this described or documented anywhere on the nixpkgs end?
<abathur>
I guess this also means it'll stop working when apple shuts off kexts without a macOS app of some sort?
<LnL->
well, I would guess that installer would also include an app then :)
<LnL->
but not sure, the osxfuse expression is basically just the headers so stuff compiles AFIAK
<abathur>
wish it had one of those requirement warnings that alerts users when it's missing something; blew several hours trying to debug; alas
<abathur>
not sure, having not directly fiddled, how the extension would work for osxfuse. I guess I can assume Apple wouldn't break something like that irrevocably, but I watched the wwdc presentation this weekend for an unrelated reason and they spent some time talking about how projects like generic drivers would need to specify a "resuable" entitlement that would enable it to be built into another
<abathur>
"Apple has not announced an alternative API. Kernel extensions are the only way to develop full-featured file systems on macOS."
<abathur>
maybe I'm tilting at the wrong windmill anyways; I'm curious what you think about the viability of (and best path to?) making a cross-platform sandbox that: 1.) is safe enough to fuzz a shell script in without destroying stuff, and 2.) has any file-serving layer that can log/report paths the script tries to read/write
<LnL->
I've never worked with fuse directly, but definitively would be the first think to look at I think
<LnL->
in combination with a small platform specific part that restricts access
<abathur>
drat; was hoping you'd tell me I'm overthinking it :)
<abathur>
sadly, it's fairly simple to track executions in straight bash, but I'm trying to get a sense of whether it's feasible and how much more work it is to make the jump to wrapping the execution in something that'll notice read attempts triggered by an external program
<eraserhd3>
osxfuse is one of the few homebrew casks I still install for this reason.
<eraserhd>
(I have yet to make it pin to a homebrew repository commit hashes, which seems to be doable, and required for reproducibility)
__monty__ has quit [Quit: leaving]
<abathur>
I'm a fan of folding homebrew stuff in when I can (and have only casks installed that way), but I've avoided jumping through hoops to do it since a lot of it likes to auto-update anyways
<abathur>
I don't see much sense pinning something like spotify that'll throw a fit if it's too old when I open it anyways; I might change my tune around an actual break, but meh