<clever>
aminechikhaoui: it has to first download everything to the local machine, then have the remote machine download the same things from cache.nixos.org
<clever>
aminechikhaoui: but it will still want the entire closure on the nixops machine first
<clever>
sphalerite: but i have seen it soft-fail, one of the nodes has 65535 hardlinks, and cant accept anymore
<clever>
sphalerite: i believe its using the link syscall to overwrite the files, and i think thats atomic
<clever>
but if you unquote, then nix will copy it for you, and just work from any dir
<clever>
and it must be manually copied if your using nixops
<clever>
if its quoted, then it must work relative to whatever directory the script happens to run in (/ ?)
<clever>
thats the example
<clever>
{ name = "foodatabase"; schema = ./foodatabase.sql; }
<clever>
xok: next time you boot
<clever>
and was the service stopped when you did rm?
<clever>
ah
<clever>
you ran rm on the wrong dir i believe
<clever>
and the dataDir is either /var/lib/mysql or /var/mysql, depending on your stateVersion
<clever>
xok: the prestart scripts will import the initialDatabases if ${dataDir}/mysql doesnt exist
<clever>
Taneb: i woke up at 5am, and while debugging hydra issues, got an email about declarative jobsets in hydra, and responded within minutes
<clever>
Taneb: Tue Sep 11 11:01:13 ADT 2018
<clever>
i sometimes have to force myself to not answer questions
<clever>
joehh: i think part of my problem is that i am too eager to help people, even if it means loosing sleep or starving, lol
<clever>
joehh: by pure chance, somebody emailed me about hydra problems, while i was debugging a hydra problem, very similar to his, lol
<clever>
joehh: after booting it up, they asked for the root password, so they could fix the network config, then they noticed it was already working
<clever>
joehh: so, i just gave up on doing a remote install, did a local qemu install, and then converted it to a virtualbox disk image, and gave them the URL
<clever>
joehh: the 2nd machine turned out to be a virtualbox vm inside a windows host, lol
<clever>
joehh: i then used that first machine as an example for the 2nd machine, which happened to have different network config, just because the datacenter likes to make every machine its own special little butterfly :P
<clever>
joehh: the first machine had the raid array go south for some weird reason, and i had to debug it via ipmi, which required running 2 versions of windows in 2 types of vm's to deal with activex, lol
<clever>
my original goal for kexec, was to use it on remote baremetal machines, which has no undo :P
<clever>
but thats still recoverable with the ISO on a USB
<clever>
and then after finishing the entire install with legacy boot, he mentioned he was on an apple machine, which can only boot uefi
<clever>
a recent user in here had formatted the host hdd, before noticing that he lacked zfs unstable support in kexec
<clever>
but once you are in, you still need to be very careful
<clever>
joehh: so you can kexec that image on ubuntu for ex, and if you fail to get into it within an hour, it reboots, and nothing has been installed, so ubuntu just boots back up
<clever>
joehh: yeah
<clever>
joehh: i had made the above autoreboot.nix to handle kexec'ing into a nixos that lacks the proper network config
<clever>
that sounds like the network is working, but ssl isnt, due to a lack of /etc/
<clever>
and can you pastebin the full console output when the build fails?
<clever>
nix2 now rejects that
<clever>
kalbasit[m]: is the hash on line 53 valid?, there was a bug that allowed an empty string, and some people have abused that
<clever>
outputHashMode = "recursive"; allows $out to be a file, directory, or even symlink, and the hash is over the NAR of the output (nix-store --dump)
<clever>
outputHashMode = "flat"; means that $out is just a bare file, and the hash is over the file itself
<clever>
if the hash doesnt match, the build is considered to have failed
<clever>
kalbasit[m]: and nix will enforce that the hash of $out matches the declared outputHash
<clever>
kalbasit[m]: only a derivation that has all 3 of: outputHashMode, outputHashAlgo, and outputHash, can get network access during a build
<clever>
elvishjerricco: i have my hydra building the config for some of my machines
<clever>
the list of all emacs packages
<clever>
sphalerite: you beat me that time! :D
<clever>
but nix is not aware of the libs being in use, due to lack of gc roots
<clever>
nix-shell will provide all of the libs listed in the given shell.nix file
<clever>
then you want nix-shell
<clever>
write a nix file that will compile the files you want, and then use nix-build to run it
<clever>
(or nix-shell)
<clever>
semilattice: simple answer, use nix-build
<clever>
__monty__: would be simpler to just run a squid proxy on the remote end, and use the tox IP to connect to squid
<clever>
__monty__: that could be tricky, because you would need to change the default route, but not have toxvpn itself obey that
<clever>
but that example is missing the cabal file
<clever>
which has to also have cabal2nix and nix-build ran on it
<clever>
if you have a backup of the old /boot, you can restore it
<clever>
nixos likely wont boot, because the bootloader failed to install
<clever>
debian just ignores those files entirely, so you can just leave them
<clever>
yeah
<clever>
magnetop`: id say its best to just have a single block device at xvda, and then you can install a bootloader normally
<clever>
and nixos changes it more often then other distros, which can be a pain to deal with
<clever>
but you need to copy the kernel out of the guest any time it updates
<clever>
magnetop`: basically, you have the kernel and initrd on the host filesystem, and then you just point the VM at those
<clever>
magnetop`: ah, those are difficult to deal with with nixos
<clever>
magnetop`: what about lshw?
<clever>
magnetop`: can you pastebin the output of dmidecode ?
<clever>
magnetop`: what type of VM is this?
<clever>
so xvda, not xvda2
<clever>
magnetop`: boot.loader.grub.device must be set to the root of a disk, not a partition
<clever>
magnetop`: and can you pastebin your configuration.nix file?
<clever>
magnetop`: what command did you run when it gave that error?
<clever>
magnetop`: what is the error it gives?
<clever>
magnetop`: and ar they xvda1 and xvda2?
<clever>
magnetop`: what does lsblk report?
2018-09-07
<clever>
Henson: use buildPhase instead, and src = ./.; to get a copy of the current dir
<clever>
iclanzan: ive never used systemd-boot
<clever>
iclanzan: how old was it?
<clever>
iclanzan: definitely sounds like a /boot problem
<clever>
iclanzan: can you paste the result of `ls -l /run/current-system`, then reboot and paste the result of `ls -l /run/current-system` again, without a nixos-rebuild
<clever>
line 6 from efibootmgr matches the uuid on line 14 for sda1, so the correct boot partition is on /boot
<clever>
iclanzan: and the 3 cmds above?
<clever>
iclanzan: can you pastebin the output of `nix run nixpkgs.efibootmgr -c efibootmgr -v` and `blkid /dev/sda*` and `fdisk -l /dev/sda` ?
<clever>
iclanzan: ok, thats a bit odd, is this booting with uefi or legacy?
<clever>
iclanzan: check the output of `df -h` and confirm if it is mounted
<clever>
iclanzan: if you mis-configured it during install, then it wont mount automatically