hmpffff_ has quit [Read error: Connection reset by peer]
hmpffff has joined #nix-darwin
hmpffff_ has joined #nix-darwin
hmpffff has quit [Ping timeout: 240 seconds]
hmpffff has joined #nix-darwin
hmpffff_ has quit [Ping timeout: 258 seconds]
hmpffff_ has joined #nix-darwin
hmpffff has quit [Read error: Connection reset by peer]
hmpffff has joined #nix-darwin
hmpffff_ has quit [Read error: Connection reset by peer]
hmpffff has quit [Read error: Connection reset by peer]
hmpffff has joined #nix-darwin
hmpffff has quit [Read error: Connection reset by peer]
hmpffff has joined #nix-darwin
hmpffff has quit [Client Quit]
philr has quit [Ping timeout: 240 seconds]
gchristensen has joined #nix-darwin
<gchristensen>
LnL: do you know if NixOS installs cleanly on modern mac minis?
<LnL>
no idea
<gchristensen>
me neither :)
<clever>
gchristensen: the iohk mac mini's ran into problems due to the T2 based nvme
<clever>
gchristensen: linux doesnt support that nvme controller out of the box, so the disk drive just doesnt appear
<gchristensen>
interesting
__monty__ has quit [Quit: leaving]
<LnL>
oh right it has a T2 now
<clever>
gchristensen: basically, apple cant leave things alone, and rather then use a stock nvme controller, they made their own nvme controller, within the master encryption control chip
<clever>
gchristensen: which will also seamlessly decrypt everything, so the physical disk is encrypted, but the os doesnt even notice
<gchristensen>
wow
<clever>
and the key is likely tied to the motherboard
<clever>
if your motherboard dies, what happens to your data??
<clever>
LnL: i also told qemu to not report suspend support, but darwin still goes into a coma
pikajude has left #nix-darwin ["WeeChat 2.7.1"]
<dhess>
clever: any idea about NixOS on modern MacBook Pros? They're pretty similar to the Mac mini, I think, but then the Mac mini hasn't been updated in awhile, unlike the MBPs
<dhess>
ohhhh IOHK ci-ops GitHub repo. Yet another place I need to go dig around in IOHK's repos for great stuff :)
<clever>
dhess: the most i can say is to build an iso with the T2 patches, and then boot that
<dhess>
OK I'll try it out, thanks
<dhess>
clever: I see you've got some Hercules support in that ci-ops repo. What's your experience been with it so far?
<dhess>
I'm switching to haskell.nix for my Haskell projects and ohmylord the Hydra evaluations are killing me.
<dhess>
this one's been going for 2 hours now. No idea what it's up to.
<LnL>
I'm not sure how I feel about the evaluation magic of most of the recent generators
<gchristensen>
+1
<dhess>
LnL: you mean the IFD?
<LnL>
generating stuff is annoying and has it's own problems, but things are much more predictable after that
<LnL>
not necessarily, some of the generators parse everything without IFD
<dhess>
I'm not convinced myself so far. haskell.nix does support the "standard" way of creating packages a la cabal2nix/hackage2nix, but then you have to create one of those for each cross target, config flags, etc.
<clever>
dhess: ive not done much with hercules, just debugging basic problems like trying to run the linux build of hercules on a darwin box
<dhess>
regardless, I think it's important to decouple my Haskell package set from the rest of the Nixpkgs stuff.
<dhess>
Maybe flakes will make this all better
<dhess>
clever: why did you need to do that? Is it an issue with Hercules or just something about the way IOHK is using it?
<clever>
dhess: the way we pinned hercules, and then tried to eval it on linux via nix-darwin