<clever>
ah, nixos didnt have a .loopbackIPs option when i had setup my router
<clever>
also, this looks different from how i remember it a few months ago...
<clever>
and the 3rd will check all packets after routing has been computed, and will apply an SNAT
<clever>
the 2nd will i believe apply to all patches coming into the wan interface, before routing has been applied, and check that its targeting a loopback ip, port, and proto, then DNAT it again
<clever>
the first will match all outbound packets targeting the loopback ip, forwarded port/protocool, and use DNAT to redirect it to the destination of the forwarding
<clever>
for each combination, it will generate 3 iptables commands
<clever>
so for every combination of both of those options, it will run 58-78
<clever>
and line 57 looks over every loopbackIPs
<clever>
line 51 loops over every forwardPorts entry
<clever>
it sometimes helps to skip the description and go to the implementation
<clever>
tenten8401[m]: ive pulled up the first commit on nixpkgs, thats not nix ....
2018-07-23
<clever>
robstrr: it has been merged into nix 2.0
<clever>
__monty__: some names map to several attribute paths
<clever>
then sync the config.nix over and install it again
<clever>
RetardedOnion: create a config.nix with a buildEnv override, and install that
<clever>
RetardedOnion: ~/.nix-profile can only be modified with nix-env, so you cant rsync it to another machine
<clever>
bebarker: nix-env only ever adds packages to ~/.nix-profile/
2018-07-22
<clever>
it may need to be patched to allow it
<clever>
das_j: sounds like it would be better to disable the automatic recompile, and have it compiled once by nix
<clever>
das_j: all files must have a timestamp of 1 unix time
<clever>
das_j: its part of making everything pure and reproducable
<clever>
das_j: nope
<clever>
bed*
<clever>
without wiping the cache, it will take 30 days to correct itself
<clever>
angerman: if you delete soemthing from the binary cache, it will 404, but the positive cache says it exists, so nix will refuse to just build it locally
<clever>
angerman: there are also some bugs in nix to do with the positive caching
<clever>
nix will automatically recreate that if its missing, and then re-query every binary cache
<clever>
angerman: you can also just `rm -v /root/.cache/nix/binary-cache-v5.sqlite*`
<clever>
for the remote end, it has to be in nix.conf
<clever>
angerman: and then it can decide between uploading the local copy, or having the remote machine hit up a binary cache
<clever>
angerman: also of note, both tools must have the entire set of inputs locally, before they contect the build slave
<clever>
tertle||eltret: refer to lines 6 and 28 of my example
<clever>
tertle||eltret: you are missing the pkgs: { and } for packageOverrides
<clever>
angerman: the default for that flag may differ between the 2 tools
<clever>
angerman: there is a special flag, that will allow or dis-allow the remote machine to do the binary cache work on its own
<clever>
angerman: one difference that could exist, is the modes for nix copy closure
<clever>
they should use the same library behind the scenes, so that shouldnt be possible
<clever>
nix build is more silent by default
<clever>
angerman: nix-build prints all log output to stdout, which may eat some cpu, -Q will silence it
<clever>
yeah, they should be interchangable, once you know how to translate the args
<clever>
but once you know the quirks, you can translate between the 2 easily
<clever>
i find the nix-build api to be more predictable, but nix build is the only one with the better progress UI
<clever>
angerman: nix build uses the free argument as either an attrpath or an expression, based on some weird logic, but nix-build needs -E or -A for that
<clever>
angerman: nix-build treats the free argument as a filename, nix build needs a -f for the filename
<clever>
sophiag: the automatic GC wont touch generations, so you still have to manually delete those
<clever>
tertle||eltret: you need an entry in your config.nix packageOverrides, that does renoise = pkgs.renoise.override { releasePath = /path/to/something; };
<clever>
tertle||eltret: a: thats a "lovely" packaging idea, b: then how did i install it without a licenses? lol
<clever>
any time i reach 3gig of free space on /nix/store, it will start a gc, and it will stop when it gets to 6gig free
<clever>
sophiag: i was digging around in the nix source a month ago and discovered the min-free and max-free options
<clever>
sophiag: and then youll probably spend an extra 10-20mins re-downloading from the binary cache, depending on your modem speed
<clever>
samueldr: by default, a normal `nix-collect-garbage` will delete anything not currently in use, which may include build-time tools, and anything source like
<clever>
samueldr: you can also run "busybox strings foo" to run the strings sub-command
<clever>
tertle||eltret: the CI system for nix
<clever>
the default version in the busybox attribute could be changed, as long as the initrd uses an override to re-enable that
<clever>
half the command-not-found results tell you to try installing busybox, which just horribly breaks the machine
<clever>
samueldr: busybox probably should also be hidden from nix-index, lol
<clever>
hydra probably doesnt build it, so no index
<clever>
,locate renoise
<clever>
angerman: so once the process that was using the build slave quits, the lock should be auto-released by the kernel
<clever>
angerman: and the locks are opened with O_CLOEXEC
<clever>
angerman: ah, on closer inspection, nix uses fcntl(fd, F_SETLK on the lock files in /nix/var/nix/current-load
<clever>
tertle||eltret: you need to enable unfree packages in config.nix
<clever>
angerman: it looks like its no longer on a tmpfs, but deleting those files should reset its memory of in-use build slaves
<clever>
or windows is doing something seriously wrong, and can only use 10% of my cpu's power :P
<clever>
so either linux is doing something seriously wrong
<clever>
i started to suspect a linux problem, after i noticed windows at max load barely used 20 amps in the same monitoring util
<clever>
and just doing a rebuild was making it get dangerously close to overheating again
<clever>
in my case, the issue is a weird voltage control problem with the cpu, that leads to the motherboard dumping 80 amps into the poor cpu, which then overheats to the point of the machine cutting power
<clever>
sophiag: i did have to reduce my own rebuilds down to 1 core
<clever>
sophiag: sadly, 17.09 also shows signs of the same problem, so its either a long-standing issue in the linux kernel, or a config issue in configuration.nix itself
<clever>
sophiag: with only very minor changes to my configuration.nix, i was able to downgrade the whole machine to 17.09 effortlessly
<clever>
sophiag: the power of nixos config is amazing, i switched my desktop from nixos-unstable to 18.03, and then even 17.09 today, trying to narrow down a problem
<clever>
tertle||eltret: is it giving an error?
<clever>
the comments i read dont mention any cpu stalls, have you tried testing ssh?
<clever>
yeah, thats the comment i mentioned
<clever>
sophiag: that comment implies that its less to do with what grub did to the GPU, and more what grub isnt forwarding to the linux kernel
<clever>
looks like its still "linux"
<clever>
linux ($drive1)//kernels....
<clever>
[root@amd-nixos:~]# grep linux /boot/grub/grub.cfg
<clever>
sophiag: and for the comment a few down about linux vs linuxefi, just read the grub.conf file in /boot and see which one its using
<clever>
sophiag: from the first comment, it sounds like a race condition, the systemd unit just needs to wait a bit longer
<clever>
for legacy booting, i believe grub uses the same legacy bios calls dos would have used, and i has not messed with advanced stuff like pci passthru for me, so it should also not cause issues with wonky drivers
<clever>
sophiag: and if it did cause problems, i would expect every bootloader to have the same problems
<clever>
sophiag: for efi booting, there are dedicated functions provided by the firmware for drawing to the screen, i would expect that to not cause any gpu driver problems
<clever>
tertle||eltret: add yourself to the wheel group, example linked
<clever>
now you can undo the changes to configuration.nix to re-add yourself, nixos-rebuild switch, and possibly run `passwd username` to set the pw again
<clever>
tertle||eltret: try ctrl+alt+f1 and then login from text mode?
<clever>
tertle||eltret: using grub or systemd-boot?
<clever>
tertle||eltret: do you not have a root password?, have you tried booting an older generation from the bootloader?
<clever>
petersjt014[m]: looks pretty normal, i would expect that to boot
<clever>
petersjt014[m]: you can probably also just `fdisk /dev/sdX` and then run the print command within it (its probably just p)
<clever>
petersjt014[m]: list
<clever>
petersjt014[m]: if you put the sd card back into a reader and do `fdisk -l /dev/sdX` what does it list?
<clever>
turn off the power, remove the card, turn on the power
<clever>
petersjt014[m]: if you remove the SD card entirely, then reconnect power, does it blink the same way?
<clever>
2 flashes: The SD Card cannot be read.
<clever>
petersjt014[m]: how many blinks is it doing?
<clever>
petersjt014[m]: you can lookup what the blink pattern means online
2018-07-21
<clever>
dhess: ok, it doesnt appear to be a "recent" problem in nixos, even nixos-17.09 exibits the problem
<clever>
juhe1: sounds like a bug in nix then, it should have terminated that process automatically
<clever>
infinisil: then youll want a custom unpackPhase that will check $src, and decide if it should copy it directly, or run the original unpackPhase and filter it
<clever>
infinisil: what are you trying to actually do?
<clever>
infinisil: the default unpackPhase only works for tars, zips, and directories, it wont know what to do with a file
<clever>
infinisil: youll want to replace the default unpackPhase then, or just switch to runCommand
<clever>
juhe1: what is process 20938?
<clever>
infinisil: why is the src another nix file?
<clever>
juhe1: can you pastebin the output of `ps -eH x` after you ctrl+c the build?
<clever>
juhe1: strange, because it should be stopping
<clever>
infinisil: if only one thing provides a given directory, it links the directory, if 2 things provide a dir, it creates one, and links all of its contents
<clever>
infinisil: buildEnv links everything by default
<clever>
dhess: heh, during shutdown it rises to 1.3 volts on the cpu
<clever>
dhess: and you can remotely change the clock freqs
<clever>
infinisil: and buildEnv wont do?
<clever>
dhess: the motherboard has some monitoring software that runs over usb, and lets me monitor the cpu amps, many voltages, fan speeds, and temps
<clever>
hmmm, its only at 0.86 volts on windows...
<clever>
80 amps at 1v is very different from 80 amps at 120v
<clever>
dhess: remember, this is 80 amps at about ~1 volt
<clever>
dejanr_: its a 125 watt cpu, running at 0.8 volts right now
<clever>
so even with a linux host, your uptime is bounded by the stability of windows
<clever>
dejanr_: and even then, windows can only use the card once per boot, then the host has to do a full powercycle
<clever>
dejanr_: ive had a lot of trouble getting gpu passthru to work, i had to use a special linux param to entirely blacklist linux from touching the pci device, which meant you dont even get a text console to login at
<clever>
windows is pulling 10 amps at max load on all 8 cores...
<clever>
without a baseline, i just assumed that was normal, it matches up with the watt rating and the voltage in the same util
<clever>
i powered up the motherboard monitoring software, and found that the cpu is drawing over 80 amps
<clever>
lately, nixos has been having a lot of overheating problems, going into thermal shutdown repeatedly
<clever>
sphalerite: ok, something very fishy is going on with my desktop....