<clever>
ivanivan: pkgs.makeModulesClosure is used to merge all the modules together into 1 directory tree, and it runs the bash script i linked above, which does depmod
<clever>
ottidmes: i should look into that issue when i get a chance and finish my idea up
<clever>
then it kexec's your choice of OS
<clever>
ottidmes: and if you do connect, you get a boot menu (or shell) over ssh
<clever>
ottidmes: my idea, was to make a very thin "OS", that runs sshd, and if you dont connect within 30 seconds, it boots the default config via kexec
<clever>
ottidmes: because the grub generation list for emergency rollbacks, is 100% useless on a headless server
<clever>
ottidmes: i had an idea a few months ago, about making a kexec based bootloader, for servers
<clever>
ottidmes: hmm, yeah, you could, and that reminds me
<clever>
ottidmes: the problem, is that nixos has to modify the bootloader config every single time you `nixos-rebuild switch`, so it has to re-generate that, and re-flash the PBA
<clever>
ottidmes: at a glance, i think thats just making a /boot containing your kernel, initrd, and bootloader, formated with ext4, and gzip'd
<clever>
ottidmes: you generally put /boot on that unencrypted partition, and then it gets the kernel/initrd from that
<clever>
ottidmes: i think this option allows the legacy grub stub (between sector 1 and partition 1) to ask for a password and decrypt /boot/
<clever>
you also need to make sure the /boot partition is available at /boot inside the chroot
<clever>
ij: switch and test involve interacting with systemd and starting services up, which wont work under chroot
<clever>
ij: only "nixos-rebuild boot" and "nixos-rebuild build" would work in there
2018-02-03
<clever>
kini: yep
<clever>
kini: nix-prefetch-url just downloads it with curl, then calls nix-store, which needs $NIX_REMOTE set right
<clever>
kini: you have to tell nix that its in multi-user mode now, and how to contact something that does have write
<clever>
kini: this error is caused by not setting `export NIX_REMOTE=daemon`
<clever>
2018-02-02 22:35:32 < kini> and when I try to run THAT in the nix-shell, I get "error: Nix database directory ‘/nix/var/nix/db’ is not writable: Permission denied"
<clever>
freeman42x: oh, thats not even a fetchurl
<clever>
freeman42x: try sticking to fetchurl, and just add unzip to the buildInputs of the derivation using it
<clever>
freeman42x: that lets fetchurl and stdenv unpack it
<clever>
freeman42x: or, just add unzip to the buildInputs
<clever>
elvishjerricco: yeah
<clever>
elvishjerricco: and post a static check, like travis does
<clever>
elvishjerricco: it will then lookup the org/user owning that repo in github_authorization
<clever>
elvishjerricco: for github status, when a build passes, it will find the input of the given name (cardano in the case of line 80), and lookup where on github it came from, and what rev it was in the eval
<clever>
some CI tools do have caching, but they just upload the files to a place like S3
<clever>
eceuv: the queue times on hydra can be much shorter, even with the paid travis plan, ive found myself waiting hours for a job to even start
<clever>
eceuv: hydra can serve the resulting binaries to you and speed up your own local builds
<clever>
eceuv: hydra keeps a cache of all of your depdencies, so you dont haev to wait for travis to redownload them every time
<clever>
but if the input is another derivation, you already locked the hash of things in with a fixed-output derivation, so it doesnt really work there
<clever>
dhess: and most fo that filtering is to prevent the hash from changing
<clever>
dhess: cleanSource just uses filterSource behind the scenes, and filterSource is meant to filter things as they get copied from the mutable filesystem to the immutable nix store
<clever>
dhess: nix does it by operating on a secondary store within the tmpdir
<clever>
dhess: you may want to look at how nix's tests test filterSource, it runs nix inside nix
<clever>
i think it would be best to just have the input data not be in a tar
<clever>
ah
<clever>
dhess: why do you want to run cleanSource on it?
<clever>
dhess: if its a tar, clean it up in postUnpack
<clever>
dhess: generally, you shouldnt be using cleanSource on a tar, only on a working directory
<clever>
dhess: runtime dependencies
<clever>
dhess: the things imported by filterSource and cleanSource must have no dependencies
<clever>
dhess: cleanSource doesnt understand how to unpack things
<clever>
:D
<clever>
iqubic: yeah
<clever>
samueldr: it might be that the ld.so path is wrong, and the bash script assumes the error is due to noexec
2018-02-01
<clever>
on both cases, the config has to get into there somehow
<clever>
nix.buildMachines just configures /etc/nix/machines for you
<clever>
hakujin: yeah
<clever>
hakujin: is /etc/nix/machines configured?
<clever>
Shados: i generally use tab completion in nix-repl
<clever>
ij: thats likely giving you a shell suitable for building terraform, not using it
<clever>
joepie91: some quick math confirmed how big the framebuffer was, then i used MTD to convert a chunk of video ram into a block device, mkswap, double the ram!
<clever>
joepie91: the gpu also had 64mb of ram, and it was used as a server
<clever>
joepie91: i'm also reminded of a cheap trick i used, back when i had 64mb of ram
<clever>
joepie91: i cant remember who brought it up last time in #nixos, but they mentioned the switch
<clever>
joepie91: chromium is the only place i noticed that tooltip issue
<clever>
joepie91: i had to comment that out to even get graphics
<clever>
52 #"amdgpu.dpm=0"
<clever>
joepie91: and changing the power management options breaks the gpu entirely on my end
<clever>
but it still locks X up solid every now and then
<clever>
i have since switched to the amd-gpu driver, and most of those issues have gone away
<clever>
joepie91: i have even seen my windows wallpaper, slightly corrupted, upon logging into nixos!!
<clever>
so my tooltips always rendered as garbage on the first drawing
<clever>
joepie91: oh, that reminds me, for the longest time, ive found evidence of my GPU using tooltip textures before they where initialized
<clever>
unknown, i wasnt verifying the files often enough when they did become corrupt
<clever>
so bit-rot wont be an issue, but while moving, it may become corrupt
<clever>
viric: zfs would prevent the issues on-disk, but in my case, problems could still happen in ram and over the nfs layers
<clever>
ij: yeah
<clever>
viric: it was next to the other one in my bookmarks, lol
<clever>
ij: there is a post hook you can set, which can just rename whatever it wants
<clever>
yet nobody knows what the utility even does
<clever>
the talk at 58 minutes in, he starts diving into obscure utilities that are installed on every mac