<nschoe>
I've just booted the SD card, it went mostly okay. But /etc/nixos/ is an empty dir on the rPi, is this normal?
<nschoe>
So I'm just coming to check if this is normal not to find _anything_ under /etc/nixos/
<nschoe>
I know I am supposed to write my first configuration.nix and nixos-rebuild switch to finish the installation per-see, but I was still expecting an empty or template configuration.nix.
<bennofs[m]>
nschoe: yes that is normal. You should be able to use nixos-generate-config link on normal install to make a template
<bennofs[m]>
s/link/like
<nschoe>
bennofs[m]: thanks for your answer! So I must call nixos-generate-config first? I was about to write the template from the link above.
<nschoe>
Okay, will do that then
<nschoe>
Ahhh yes indeed, it generated th ehardware-configuration.nix and configuration.nix, thanks for that. I was in for troubles.
<bennofs[m]>
nschoe: you should check though if the generated ones make sense
<nschoe>
Yes sure, I'm doing this. But it provides a nice head start rather thant going from scratch
<nschoe>
On the rpi, should I set boot.tmpOnTmpfs and boot.cleanTmpDir to true like on my laptop?
<bennofs[m]>
It won't have much space then since RAM is limited on RPi. But if you can live with that little tmp space I guess it would make sense to reduce SD wear
<bennofs[m]>
Keep in mind though that nix-build performs builds in /tmp by default, and with tmpfs there may be not enough free space for some builds
<bennofs[m]>
And RAM usage is a problem for me often even without extra usage by tmpfs
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<nschoe>
bennofs[m]: ah, thanks.
<nschoe>
I knew I should ask.
<nschoe>
So no tmpFs then
<nschoe>
Should I still enable cleanTmpOnBoot?
<bennofs[m]>
I would say cleanTmpOnBoot makes sense. I don't know if there is anything specific to this on rpis
nschoe has quit [Quit: No Ping reply in 180 seconds.]
nschoe has joined #nixos-aarch64
<nschoe>
bennofs[m]: okay, I enabled it. Will see.
DigitalKiwi has quit [Quit: quite.]
DigitalKiwi has joined #nixos-aarch64
<nschoe>
I had a bad experience with this option not being enabled recently: I actually reached max number of inodes on my /tmp at 920k temp files :)
ashkitten has quit [Ping timeout: 272 seconds]
ashkitten has joined #nixos-aarch64
<nschoe>
Oh god, thanks to whomever make cache.nixos.org wok on the rPi. It's a life saver.
orivej has joined #nixos-aarch64
zupo has joined #nixos-aarch64
<srk>
:))
* srk
just rolled znc image for pi2 and it connects \o/ can't access the ssh tho so one more round :D
<nschoe>
:)
<nschoe>
Meanwhile I just launched a crosscompiation wiht pkgsCross.aarch64-multiplatform on a simple "Hello world" package from Haskell....
<nschoe>
I think it's rebuilding the entire world :D
<nschoe>
Just to make sure I'm not missing something: I don't have anything to do to specify a binary cache when building for aarch64-multiplatform, right?
<nschoe>
I think I remember reading that cache.nixos.org also buils aarch64-multipalteform.
<nschoe>
Am I correct or have lauched a command that will take months for nothing? ^^
<clever>
nschoe: if you build with --dry-run, youll see what it will build and what it can dl
<nschoe>
clever: yes, unfortunately I have already launched the command, and it's running.
<nschoe>
Which worries mebecause I see both gcc and ghc.
<clever>
is that from a channel?
<nschoe>
clever: my default.nix contains this: "hel = pkgs.pkgsCross.aarch64-multiplatform.haskellPackages.callPackage ./hello.nix {};" (the hello.nix is not GNU hello, its just my haskell hello world)
<clever>
nschoe: that will cross-compile, rather then native-compile
<nschoe>
so not sure about teh channel. I build with 'nix-build -A hel'
<clever>
nschoe: and cache.nixos.org only has native builds
<srk>
iirc there was some progress regarding aarch64 ghc but I'm not sure what's the state of it
<nschoe>
clever: yes: my goal is to cross compile the package fro mthe laptop to my rapsberry pi
<clever>
nschoe: the cache wont help with that then
<nschoe>
clever: ouch okay, thank sfor the clarification :)
<nschoe>
clever: so does it mean it will acually be quciker to compile directly on the rpi?
<nschoe>
Which woud have binary cache?
<clever>
nschoe: change the `import <nixpkgs> {}` to `import <nixpkgs> { system = "aarch64-linux"; }` and use plain `pkgs.haskellPackages.callPackage`, then try another --dry-run, and youll see what the pi would have to build, even if your on an x86 machine