<samueldr>
gchristensen: not an issue (yet?) but I was wondering if there was anything I can do to help with disk-as-swap for the builder; I'm thinking the main issue being how to ensure the tmpfs is resized accordingly
<gchristensen>
great question, samueldr
<gchristensen>
here is what I think would be better
<gchristensen>
using the sda2 partition as the overlay and workdir for the /nix/store overlayfs which is created
<gchristensen>
we'd need to erase the partition each time (or mount it with a random encryption key? I think there are tricks here) so it is empty
<gchristensen>
is that something you can help with? I can build-and-deploy as needed
<samueldr>
maybe, though now I switched to doing something else on the machine
<samueldr>
though one slight worry, would the encryption cause slowdowns? I guess not really, but I don't know if it is CPU accelerated like in x86_64 land
<samueldr>
(though encrypting with randomized key is bound to be a good way to ensure cleanliness)
<gchristensen>
since "shove stuff in to the CPU" is a key selling point of ARM, I'dbe surprised if it didn't :)
<gchristensen>
if it didn't have acceleration*
<samueldr>
same
<THFKA4>
from my understanding, "neon" in your /proc/cpuinfo is analogous to "aesni"
<THFKA4>
and means that you have hardware crypto support
orivej has quit [Ping timeout: 244 seconds]
Acou_Bass has quit [Quit: byeeeeeeeeeeeeeee]
Acou_Bass has joined #nixos-aarch64
orivej has joined #nixos-aarch64
orivej has quit [Ping timeout: 250 seconds]
lopsided98 has quit [Ping timeout: 268 seconds]
lopsided98 has joined #nixos-aarch64
worldofpeace has quit [Remote host closed the connection]
vielmetti has joined #nixos-aarch64
worldofpeace has joined #nixos-aarch64
worldofpeace has quit [Quit: worldofpeace]
orivej has joined #nixos-aarch64
orivej has quit [Ping timeout: 240 seconds]
<samrose>
omg I finally got my machine to start building 4.20-rc5
<samrose>
needed the right contents in NIX_PATH (beyond just nixpkgs=/myrepo)
<samueldr>
yes and no, it's not different than any other nixos system, except that it's on ARM, so you should have a stateVersion, and keep it consistent as you would normally
<cyounkins>
Should I add `system.stateVersion = "18.09";` to the template in the wiki then?
<samueldr>
not sure if "18.09" is appropriate; imho the configuration there should probably be more obviously marked as partial
<samueldr>
and nixos-generate-config should be adapted to work appropriately (if it doesn't yet)
<cyounkins>
OK. I'm installing for the first time on ARM so I'm following the wiki instructions which say to use nixos-rebuild and keep the image partition layout. "if you know exactly what you're doing and how U-Boot on your board works, you can use nixos-install as usual"
orivej has joined #nixos-aarch64
flokli has quit [Ping timeout: 250 seconds]
flokli has joined #nixos-aarch64
cyounkins has quit [Remote host closed the connection]
worldofpeace has joined #nixos-aarch64
<gchristensen>
samueldr: might have a couple hours to hack on the root disk. are you using the machine this evening?
<samueldr>
yes, but it's all automated and I'd rather you do the thing than wait on that
<gchristensen>
but I'd rather wait on _you_! :')
<gchristensen>
<3
<samueldr>
especially considering I don't foresee a real lull in activity if everything goes well :)
<gchristensen>
can you review a diff before I try it?
<samueldr>
sure
<gchristensen>
ok
<gchristensen>
I'll write one :')
<gchristensen>
;)*
Thra11 has quit [Ping timeout: 244 seconds]
<samueldr>
meanwhile I'm "checkpointing" the thing I'm doing by copying it away temporarily
<gchristensen>
cool
<gchristensen>
time mkfs.ext4 -L scratch-space /dev/sda2 ...
<gchristensen>
real0m45.514s
<samueldr>
so compared to the current boot time, not that much added ;)
<samueldr>
(or mount it elsewhere for e.g. the raspberry pi so you can manipulate files in it)
<cyounkins>
Whoops, missed that in the wiki.
<samueldr>
huh?
<cyounkins>
I thought I needed to add it to the wiki but it's there (that you have to remove /boot from fileSystems)
<samueldr>
you're right that it's not documented there to remove it from the configuration if required
<samueldr>
uh!
<samueldr>
looks like I can't read either :)
<cyounkins>
haha it helps when there are numbered steps
<samueldr>
weird to me, to re-read what I edited :)
<samueldr>
gchristensen: by-partlabel if it's gpt?
<gchristensen>
I double checked that part: lrwxrwxrwx 1 root root 10 Dec 12 23:25 /dev/disk/by-label/scratch-space -> ../../sda2
<samueldr>
aw, dos
<samueldr>
nah, something else
<gchristensen>
I mean, its netboot, so ???
<gchristensen>
:)
<cyounkins>
I'd like to make a github issue to remove the use of /boot in the disk images unless someone knows that wouldn't fly.
<samueldr>
GPT has labels in the partition table, so you can do more fun stuff :)
<gchristensen>
oh cool
<samueldr>
and it also gets confusing when it won't or does match with the filesystem's label
<samueldr>
cyounkins: I *think* it would fly, since the author of the module for the sd images at one point said they think it would have been better not to use /boot for extlinux+kernels+initrd
<samueldr>
cyounkins: though the partition itself is required for the raspberry pi family
<cyounkins>
Can you elaborate on "the partition itself is required for the raspberry pi family" ?
<cyounkins>
lol sorry. You said "the partition itself is required for the raspberry pi family" and I wasn't quite sure what you meant. Like, the .img must be a full disk with partitions instead of a partition? /dev/sda instead of /dev/sda1?
<samueldr>
also
<samueldr>
but the raspberry will read the bootloader from a FAT-formatted partition
<samueldr>
so the image will always need to be made with a partition to hold the raspberry-pi specific files (as a convenience)
<samueldr>
though, since it will be only that, the size can be reduced
<cyounkins>
Right. I see. Thanks!
<samueldr>
(there's more to the magic than the partitions, it's also important to see that there's a gap between the MBR and the first partition, as most cheap SBCs will look at a predefined offset for a bootloader)
<samueldr>
cyounkins: on which device are you installing?
<cyounkins>
I'm using an RPI 3B
<samueldr>
ah, then threaded territories :)
<cyounkins>
threaded?
<samueldr>
hmm, I should check to see how I butchered the saying
<samueldr>
ah, well traveled road, or something along the way
cyounkins has quit [Remote host closed the connection]
<gchristensen>
speaking of which, if anyone wants a Ampere dev server, I have the hookup
<gchristensen>
$3,000-$6,000 depending on specs -- which I don't think I'm supposed to share publicly, but if you want a decent dev machine for $3-6k pm me :)