h0m1 has quit [Ping timeout: 252 seconds]
h0m1 has joined #nixos-aarch64
<gchristensen> [root@nixos:~]# pgrep rosetta | wc -l
<gchristensen> 44
<samueldr> ?
vika_nezrimaya has joined #nixos-aarch64
vika_nezrimaya[m has joined #nixos-aarch64
dongcarl has quit [Read error: Connection reset by peer]
samrose has quit [Ping timeout: 240 seconds]
FRidh has joined #nixos-aarch64
orivej has joined #nixos-aarch64
zupo has joined #nixos-aarch64
FRidh2 has joined #nixos-aarch64
FRidh has quit [Ping timeout: 256 seconds]
FRidh2 is now known as FRidh
FRidh has quit [Quit: Konversation terminated!]
FRidh has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zupo has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<Acou_Bass> hey everyone, just a quickie, when i run nix on my pi 3 it seems like it takes forever to do anything and causes processes running to die (when i do nix-env or nixos-rebuild etc.) just wondering, would a better/faster SD card or ist
<Acou_Bass> is the pi3 just a bit slow? XD
<srk> o/ how much ram does it have?
<srk> it's not very fast, I've update my rpis via nixos-rebuild --target-host from a bit more powerful ARM machine with SS
<srk> SSD
<srk> I think you could achieve the same with cross compiling
<Acou_Bass> pi 3 is... 1gb ram but im only using about 200-300 of that from normal usage
<srk> hmm, need to try that cross thing
zupo has joined #nixos-aarch64
<Acou_Bass> and i dont think nixos updates compile much if anything, its even if i run like nix-channel update
<srk> the problem is the evaluation which takes quite a lot of ram
<Acou_Bass> ahhh
<srk> does it get to building?
<Acou_Bass> yeah it does eventually do its thing
<Acou_Bass> just takes a while to do it
<srk> cool, that's expected I would say :)
<srk> could be worse with pi1/2 :)
<Acou_Bass> fair
<Acou_Bass> XD
<srk> or - there's another option - bake the image with all the required stuff, insert sd card and forget about it :D
<Acou_Bass> means rebuilding an image on another PC when i wanna update it though
<srk> not necessarily, you can still update it via nixos-rebuild directly on it if you have a config there or update it remotely with nixos-rebuild --target-host
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
Darkmatter66 has quit [Ping timeout: 265 seconds]
Darkmatter66 has joined #nixos-aarch64
FRidh has quit [Ping timeout: 265 seconds]
FRidh has joined #nixos-aarch64
FRidh has quit [Ping timeout: 256 seconds]
FRidh has joined #nixos-aarch64
FRidh has quit [Ping timeout: 240 seconds]
FRidh has joined #nixos-aarch64
zupo has joined #nixos-aarch64
<gchristensen> huh
<gchristensen> buildFHSUserEnv seems awfully x86-only
<makefu> and i686!
Acou_Bass has quit [Ping timeout: 264 seconds]
Acou_Bass has joined #nixos-aarch64
<Acou_Bass> srk: yeah but doing nixos rebuilds on it directly causes the same thing hehe
<Acou_Bass> hmm
<Acou_Bass> i dont have another nixos pc to run it remotely... hmmmm
<Acou_Bass> i mean its not a huge issue, and if its just a Pi limitation then meh - just figured maybe theres something i can do to improve it XD
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zupo has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
Acou_Bass has quit [Ping timeout: 256 seconds]
Acou_Bass has joined #nixos-aarch64
Acou_Bass has quit [Quit: ZNC 1.7.4 - https://znc.in]
Acou_Bass has joined #nixos-aarch64
arianvp has quit [Quit: WeeChat 2.6]
vika_nezrimaya has quit [Quit: ERC (IRC client for Emacs 26.3)]
zupo has joined #nixos-aarch64
Darkmatter66_ has joined #nixos-aarch64
Darkmatter66 has quit [Ping timeout: 250 seconds]
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zupo_ has joined #nixos-aarch64
FRidh has quit [Quit: Konversation terminated!]
zupo_ has quit [Ping timeout: 265 seconds]
Darkmatter66_ has quit [Ping timeout: 264 seconds]
zupo has joined #nixos-aarch64
Darkmatter66 has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<samueldr> I really need to setup a hard drive on my local aarch64 builder
<samueldr> it's quick enough to handle builds in a passable amount of time (rk3399)
<samueldr> but it's slowed down heavily by an SD card
zupo has joined #nixos-aarch64
<hexa-> really? an sd card? :p
<hexa-> someone smart told me adding a real disk increases reliability of such a device
<samueldr> things you do when you settle for "good enough"
<samueldr> though I did try setting it up to boot on hard disk
<samueldr> but u-boot wouldn't
<samueldr> and I didn't spend more time at the time since it was good enough for my needs :)
<samueldr> it's good enough as I can start a build for a system before going to sleep, and the next day it's done
<samueldr> but it's horrible for doing it live!
<matthewbauer> you can get better performance/liftime by setting "commit=600" on the ext filesystem. you would lose up to 10 minutes of data on power failure, but limit the number of writes a ton (120x). probably a good idea if you have a UPS .
<samueldr> yeah, just saw that commit
{`-`} has joined #nixos-aarch64
dongcarl has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]