<clever>
skdfjh: you must use runCommand to mutate the path before it goes into src
<clever>
skdfjh: i see the problem, src goes to one derivation, postUnpack goes to another, so you cant use postUnpack, and you cant even use unpackPhase
<clever>
stepcut: sounds like thats all right
<clever>
skdfjh: it will use your ssh agent to auth
<clever>
skdfjh: that would just make the code cleaner
<clever>
skdfjh: private git repo? you want builtins.fetchGit
<clever>
skdfjh: can you pastebin your current nix file?
<clever>
skdfjh: you need to be using the default unpackPhase for it to work
<clever>
postUnpack = "sourceRoot+=/socket-io; echo source root reset to $sourceRoot";
<clever>
skdfjh: you want to append to sourceRoot in postUnpack
<clever>
skdfjh: and also `nix show-derivation` on that same drv
<clever>
skdfjh: run `nix-store -r` on the .drv file that is failing to build
<clever>
now you dont know the paths until bash time, and the job is still done
<clever>
erasmas: then loop over every path in the closure
<clever>
for x in $(cat ${pkgs.closureInfo foo}/thing); do
<clever>
erasmas: create a derivation, that will use runCommand to do
<clever>
erasmas: why do you need it at eval time?
<clever>
erasmas: you cant really get that sanely at eval time, without IFD (which is messy)
<clever>
erasmas: buildEnv, or writeText
<clever>
i work exclusively in old-repl
<clever>
ive also not used the new-repl stuff at all
<clever>
which wont reload the libraries it depends on
<clever>
NemesisD: the quick flash is just it doing :r in ghci i believe
<clever>
NemesisD: i think you need to give it files
<clever>
NemesisD: `runhaskell Setup.hs repl` is identical to `cabal repl`, but saves you from having to install cabal-install
<clever>
then cabal will build the library, and then re-repl the tests
<clever>
NemesisD: any time the given path is modified, it will quit and re-run `runhaskell Setup.hs repl`
<clever>
--restart=PATH Restart the command when the given file or directory
<clever>
contents change (defaults to .ghci and any .cabal file)
<clever>
$ ghcid --help
<clever>
NemesisD: one min
<clever>
NemesisD: i just add the library srcs to the test and remove the dependency on the library, most of the time
<clever>
NemesisD: and yeah, that repl wont deal with the library changing under the tests
<clever>
it reads from 0-100, it just slams into the end, and reads 500
<clever>
ashkitten: the needle on the guage just pegs, lol
<clever>
ashkitten: every time i go to speedtest.net, damn
<clever>
also, its nixos, and the interfaces file doesnt do anything
<clever>
i was one step ahead of them :P
<clever>
then they realized, its already got the right ip....
<clever>
after they installed it, they asked for the root pw, so they could login and fix /etc/networking/interfaces to match my static ip
<clever>
so, i just whipped up a virtualbox disk image, with the fixes done, and sent them the whole disk image!
<clever>
when getting errors from them, i got back a screenshot of virtualbox running on windows, lol
<clever>
at the same datacenter, i had tried to install nixos in a vm, but the vm and baremetal machines had differing network setup, so bricked the guest
<clever>
without telling me anything, they also rebooted every machine in my account, thinking it was connectivity problems and they where doing me a favor :P
<clever>
however
<clever>
the answer, is that for privacy reasons, they cant tell me what the ip is connected to
<clever>
ashkitten: so i asked the via a support ticket
<clever>
ashkitten: i had the ip, but couldnt remember if it had been terminated, or was on a 2nd account
<clever>
ashkitten: that reminds me, a few years ago at another datacenter, i was looking for an old server
<clever>
ashkitten: tell them that its already installed and to shut up, lol
<clever>
ashkitten: lol
<clever>
adfaure: i would say the 2 terms are interchangable
<clever>
simpson: i think its more that we dont care about hiding what we download and ensuring the server is authentic, because we validate the result directly
<clever>
simpson: so if you are in the right place on the network, you can mitm fetchFromGitHub
<clever>
simpson: nix disables CA checking when fetching, because it assumes the hash of the output is enough
<clever>
Okinan: that same argument applies to curl itself and the entire ssl/tls layer
<clever>
Okinan: and if the hash is wrong, nix wont register the output as valid, so no other nix builds will ever make use of it
<clever>
Okinan: but this unpacking happens inside a nix sandbox, so it cant do much else
<clever>
Okinan: one problem i can see, is that you must unpack the zip, to check the hash, so you dont know if the hash is valid or not until after its unpacked
<clever>
ashkitten: getting late here, send the pastebin in a PM and i can look over it in ~9-10 hours
<clever>
ashkitten: just make sure to umount it before you kexec
<clever>
ashkitten: /boot is ext4, and the rescue system should support that
<clever>
ashkitten: if you pastebin configuration.nix and hardware-configuration.nix, i can also take a glance
<clever>
then adjust configuration.nix and nixos-install again
<clever>
ashkitten: if you did an install, but it fails to boot, you can just go back into kexec, and mount the FS's back at /mnt/
<clever>
ashkitten: and further nixos-install's will be faster, since it should be incremental, based on what you changed
<clever>
ashkitten: you can save time by mounting the existing fs, once your back in the kexec image
<clever>
but i dont think its following the dep tree, but rather, just doing every single thing under pkgs
<clever>
samueldr: its using nix-instantiate --json to dump the entire expr tree
<clever>
samueldr: that, plus the perl script it names, will find the url of nearly every fetchurl call, and then upload copies to tarballs.nixos.org
<clever>
Shados: i think slack keeps the scrollback history loaded, ive noticed in a free slack, that my desktop can see back going weeks, but my laptop cant even seen a single msg, due to the free msg cut-off
<clever>
and the most active slack, isnt even visible in the first page of the memory usage
<clever>
the weirdest part, is that the 2 slacks i use the least, where using the most ram
<clever>
46gig of swap now in use!
<clever>
and simply hitting refresh makes it drop off so much i cant find it now
<clever>
chrome also says that its using 2gig of JS memory!
<clever>
the pid managing a single instance of slack, is only using 156mb of ram, and 2gig of swap, but chrome claims its using 2.2gig of "memory"
<clever>
ashkitten: aha, the "memory footprint" according to chrome's task manager, is not the RSS usage!
<clever>
ashkitten: i have 64gig of swap on my desktop, and am currently using 49gig of it.....
<clever>
but ive not tested it much, and that relies on you already having systemd on the host
<clever>
adamantium: i believe you can also `systemctl kexec` to do a clean shutdown, and then execute at the end
<clever>
adamantium: ah, i mostly just use `kexec -e`, which triggers an improper shutdown of the current os
<clever>
adamantium: i mostly use kexec on systems that are about to be wiped, and then use zfs within the kexec image, as i format the disk
<clever>
Shados: `Consider setting dnodesize to auto if the dataset uses the xattr=sa property setting and the workload makes heavy use of extended attributes.`
<clever>
i always have a `sudo -i` open, and switch to that tab in screen if i get any permission errors
<clever>
Shados: the only xattr i believe i'm using is /var/empty
<clever>
adamantium: ah, i just assumed that was due to not setting systemd to let users own their own log files
<clever>
Shados: i dont really use acl's though
<clever>
Shados: oh, xattr=sa looks nice
<clever>
ashkitten: ashift is about the only one i ever set
<clever>
ashkitten: main one is to find the block or io size for your disk, fdisk -l /dev/sda should show it
<clever>
ashkitten: thats exactly what justdoit does, but its likely not configured for your disk layout
<clever>
ashkitten: you may also want to read `cat /run/current-system/sw/bin/justdoit`
<clever>
ashkitten: i do zfs on all of my machines
<clever>
ashkitten: but even if you do forget, its using a delayed shutdown, which alerts to every console, and you can `shutdown -c` to cancel it, 5 minute warning period
<clever>
ashkitten: which reminds me, once you do get in, systemctl stop autoreboot.timer
<clever>
ashkitten: so even if you lacked the console controls from OVH, you can still recover!
<clever>
ashkitten: it will reboot itself every hour, 5 minutes after the hour starts
<clever>
ashkitten: only the tar itself has to be copied, it contains everything it needs
<clever>
ashkitten: keeping the server out of america
<clever>
ashkitten: what about keeping it out of trumps reach? lol
<clever>
ashkitten: ive got a soyoustart machine, but ive yet to migrate it to nixos
<clever>
ashkitten: and it will then try the next device in your boot order
<clever>
ashkitten: i recently discovered, that you can `exit` when at the grub command prompt, and the bios will treat that as the drive being non-bootable
<clever>
ashkitten: it may be scanning the drive to see if its bootable
<clever>
ashkitten: after you clone my repo
<clever>
ashkitten: just run the exact nix-build command it shows, in the kexec directory, with the configuration.nix that is in that dir
<clever>
ashkitten: you need to use the configuration.nix in the kexec dir, when making the tarball
<clever>
ashkitten: ah, you only generate one after booting into the kexec image
<clever>
aoeu: ive never seen a cross-compiler that can target darwin
<clever>
ashkitten: did you include the correct configuration.nix in the -I flag?
<clever>
aoeu: but you need another mac to build it
<clever>
aoeu: this is an old hack i did to see how hard it could be, and it might work for you
<clever>
aoeu: as are most of the good solutions i was going to mention, lol
<clever>
aoeu: nix-user-chroot is linux only
<clever>
aoeu: are you on linux or mac?
<clever>
ivan: and just being able to skip creating a tar
<clever>
ivan: the main benefit over your tar idea, is that it can deal with a nix store already existing there, and do an incremental copy, and merge things in, if that happens to be needed
<clever>
ivan: basically, once you have nix installed in the rescue environment, you can use this to copy to /mnt/nix/store on a remote machine, over ssh
<clever>
manveru: use --to to make such a dir, and see what the file layout should be
<clever>
manveru: i think you could maybe put both the .nar.xz and the .narinfo into a directory, and then use `nix copy --from file:///path/to/dir /nix/store/path`
<clever>
but kill is send to the shell itself i think, so the whole terminal dies
<clever>
you have the option to send stop, cont, int hup, term, and kill!
<clever>
in xterm, you can hold control, and hold left-mouse, to get a menu
<clever>
i just ran `strace sh` and then whacked ctrl+\ to see what happened
<clever>
same
<clever>
zachk: sends SIGQUIT
<clever>
nix-env -iA nixos.htop will just go directly to htop
<clever>
`nix-env -i htop` will search every single package to see if the name patches htop