<gchristensen> I've been building a bootstrap perl for hours
<DigitalKiwi> Can it build on the server?
<clever> 2019-07-13 23:20:24 < geist> and though its not this case MMC cards and chips have a 'boot mode' that's kinda neat
<clever> 2019-07-13 23:20:43 < geist> basically you can just start applying a clock to them after power on and they'll start clocking out the first N bytes of a boot sector
<clever> 2019-07-13 23:20:58 < geist> the intention is to use it precisely as some sort of early boot device for something that's brain dead
<clever> 2019-07-13 23:21:13 < geist> spi flash is good for that too for similar reasons
<clever> gchristensen: neat, but i dont think the rpi uses this at all
orivej has quit [Ping timeout: 244 seconds]
orivej has joined #nixos-aarch64
FRidh has joined #nixos-aarch64
Thra11 has quit [Ping timeout: 272 seconds]
Thra11 has joined #nixos-aarch64
orivej has quit [Ping timeout: 244 seconds]
orivej has joined #nixos-aarch64
ToxicFrog has quit [Ping timeout: 244 seconds]
orivej has quit [Ping timeout: 245 seconds]
orivej has joined #nixos-aarch64
ToxicFrog has joined #nixos-aarch64
samrose has joined #nixos-aarch64
t184256 has left #nixos-aarch64 [#nixos-aarch64]
t184256 has joined #nixos-aarch64
jackdk has quit [Quit: Connection closed for inactivity]
<gchristensen> binutils fails to build: out of space :/
<gchristensen> did a fresh GC and trying again ...
<clever> gchristensen: of note, if you run `nix-shell /nix/store/foo.drv` it will give you a shell suitable for building a given thing
<clever> gchristensen: which also roots the inputs, so it cant GC those
<gchristensen> oh that would have been good :P
ris has joined #nixos-aarch64
<ris> so i'm guessing people have been discussing the possibility for the rpi4 as a build machine...
<gchristensen> hmm possibly
<gchristensen> it does suddenly start to look like a reasonable computer, doesn't it
<gchristensen> ris: although, check the topic :)
<ris> buildbox schmildbox
<ris> it's no fun if it doesn't keep me awake with its overnight whirring
<gchristensen> haha
<gchristensen> if you want to build *and trust what you built* the rpi might be a good choice
t184256 has left #nixos-aarch64 ["Error from remote client"]
t184256 has joined #nixos-aarch64
<DigitalKiwi> trust? don't install any node packages
<DigitalKiwi> https://twitter.com/purescript/status/1150201027553058817 the latest fun i know of
FRidh has quit [Quit: Konversation terminated!]
<gchristensen> I mean specifically that the community builder is not trustworthy
<DigitalKiwi> i know
<DigitalKiwi> trusting what you built isn't all that good when what you're trusting is malicious code to start with
<DigitalKiwi> community builder needs a modern welchia for node packages ;p
<DigitalKiwi> OOH clippy reinvented! "it seems you're attempting to install a node package, are you sure you want to install untrusted malicious crypto miners/wallet stealers?"
<gchristensen> eh, nodejs isn't unique in this way
<gchristensen> it is just popular
<gchristensen> a fun thing about the purescript thing is it didn't even do anything
jackdk has joined #nixos-aarch64
<DigitalKiwi> luckily
<ToxicFrog> Node is not unique in kind here, but I do think it's unique in degree, for two reasons: a culture of making tiny packages and depending on lots of them, which means that it's very easy for your dependency closure to be massive, and tooling that defaults to "just grab the latest version" rather than defaulting to the version the project was originally written for.