<clever>
hyper_ch2: as long as i dont drop the dhcp lease, and dont go offline for over an hour, it doesnt expire, so i could keep it for years
<clever>
anyways, its getting pretty "late" here, i should get to bed before i pass out
<clever>
LnL: ah, ive had problems in the past where zfs would deadlock, every core stuck in a spinlock waiting for more ram, and no cores able to release ram
<clever>
thats over a year worth of upgrades being applied to an active machine, without it going offline or loosing its public ip
<clever>
and i was able to upgrade the router from nixos to nixops, without loosing my internet, then upgrade it from 16.03 to 17.09, without going offline
<clever>
hyper_ch2: i have 5 machines in my house that run 24/7
<clever>
the panic output is rather unreadable if the machine is frozen and cant wake up the gpu
<clever>
hyper_ch2: some are very special purpose, this line for example disables dpms on a headless machine, so if it ever has a kernel panic and locks up, the gpu remains on and can render the panic
<clever>
zfs.zfs_arc_max=1234 on the kernel cmd line to set it at bootup
<clever>
echo any number to adjust it
<clever>
hyper_ch2: this file is the max number of bytes the arc can use
<clever>
/sys/module/zfs/parameters/zfs_arc_max
<clever>
mfiano: i dont see 20 listed in any of the configs
<clever>
hyper_ch2: though i also have 64gig of swap and i havent played with my overcommit settings, so the kernel is more willing to give me ram i dont yet have
<clever>
hyper_ch2: i think the issue, is that qemu tries to allocate a huge amount all at once, more then what the kernel has free normally
<clever>
hyper_ch2: there is a min-free thing somewhere in /proc
<clever>
hyper_ch2: btrfs just didnt perform that well, and it falsely read-only'd the machine after a write timeout because of how bad the perf was
<clever>
mfiano: are you using mkForce in either file?
<clever>
gchristensen: lol
<clever>
yeah
<clever>
nixer101: though they also block old versions from working, so it doenst really help much
<clever>
nixer101: yeah, thats also anoying, and they should stop doing that
<clever>
nixer101: but i think it had a redesign since then, it looked different when i was fixing the nix package once
<clever>
nixer101: in the past, i remember looking at how teamviewer worked, and it was just an exe file with wine bundled along-side it, and a special wine library to give linux screen-capture support to an exe file inside wine
<clever>
dont remember the details
<clever>
all with btrfs
<clever>
mfiano: and the machine falsely detected write failures, and went into a panic mode, remounting the rootfs read-only
<clever>
mfiano: then it took another hour just to GC those .drv files
<clever>
mfiano: a hydra based job took over an hour to generate just the .drv files
<clever>
mfiano: i think i just set the +C flag it says to set, but i dont use btrfs anymore
<clever>
nixer101: you need to use callPackage if you want to mix things together
<clever>
nixer101: it figures it all out, within the nixpkgs the package came from
<clever>
nixer101: how is nix going to know which programs to use from the 2nd set, and which library to not use from the 2nd set?
<clever>
nixer101: use callPackage to load the package you want
<clever>
mfiano: nix-store --version
<clever>
mfiano: it can also happen if you just unset NIX_REMOTE somehow
<clever>
those directories are owned by the user they are named after
<clever>
drwxr-xr-x 3 clever users 18 Mar 1 10:07 /nix/var/nix/profiles/per-user/clever
<clever>
drwxr-xr-x 2 clever users 2 Oct 11 2015 /nix/var/nix/gcroots/per-user/clever
<clever>
pareidolia: /nix/var/nix/gcroots/per-user/foo and /nix/var/nix/profiles/per-user/foo is the only parts that are not owned by root
<clever>
pareidolia: and you can just chown -R the whole thing over for the most part
<clever>
risci: nix doesnt really deal with things changing on their own, you have to either manualy update the file with `git pull`, or update the rev and sha256 of the result and use fetchFromGitHub
<clever>
the man page may also help correct any typos i made
<clever>
mpickering: you can double-check the pkg-config invocation if you run nix-shell against the failing .drv file
<clever>
mpickering: in the preBuild for the problem package, set CFLAGS="$CFLAGS $(pkg-config --cflags libspatialindex)" i think
<clever>
also, most of my machines are in the house, so you already have physical access by that point
<clever>
youll have better luck just finding my house and breaking in
<clever>
good luck guessing my 2048bit key :P
<clever>
mfiano: it has to be enabled for nixops to work, i prefer just turning password login off
<clever>
when cross-compiling, nativeBuildInputs will be built for the host arch, and buildInputs for the target arch
<clever>
nativeBuildInputs is best for build-only tools
<clever>
its trying to solve the same problem nix solves, but it breaks all nix builds in the process :P
<clever>
ive also been anoyed at how all of the gnome/glib stuff puts its headers in include/glib-1.0 and such
<clever>
mpickering: how are you building it when it fails?
<clever>
mpickering: check to see what happeks if you just put pkgconfig into the buildInputs of your thing
<clever>
mpickering: pkg-config should spit out the right -I flag you need to add to CFLAGS, and the build system for your package may automatically use that if you add pkgconfig to the buildInputs
<clever>
mpickering: yeah
<clever>
mpickering: does the package have a pkg-config file?
<clever>
or it could builtins.fetchurl a revision from github
<clever>
it could return an entirely custom set of packages via: with import <nixpkgs> {}; { foo = callPackage ./foo.nix; }
<clever>
how it gets nixpkgs, and if its even using nixpkgs, is up to you
<clever>
in the example .nix-defexpr/test/foo/default.nix above, and any custom ones you make, you just need to ensure the default.nix returns a set of packages
<clever>
and ~/.nix-channels is just a text file, that contains the URL's nix-channel will download
<clever>
and ~/.nix-defexpr/channels/ is just a symlink to that profile
<clever>
nix-channel treats each channel as a seperate package that can be installed within that profile
<clever>
and this one lists all "packages" installed in the current generation
<clever>
the laptop also has a totally unmarked hotkey, fn+1 just maxes out the cpu fan
<clever>
gammarray: i tried both synaptics and libinput, neither could disable tap to click
<clever>
and its hard to simply scroll down, because 2 finger drag is a 2-axis mouse "wheel"
<clever>
i let go of control too fast,because the dumb firmware is checking for a double-tap
<clever>
single click has a decent amount of latency, so it always messes up if i try to control+tap
<clever>
you cant tripple click, because the touchpad firmware thinks your trying to so a single click&drag
<clever>
tapping with 2 fingers is right click
<clever>
gammarray: on my laptop (not a macbook), nothing ive done has been able to disable tap to click, and every now and then i find a new un-documented feature
<clever>
Acou_Bass: ive got zfs with daily snapshots and mirroring, so i would expect things to be recoverable
<clever>
mpickering: lib.optional returns a list in either case
<clever>
mpickering: id also recomend just putting the override into config.nix, so you dont forget it
<clever>
Sonarpulse: then it should have restarted itself
<clever>
Sonarpulse: how did you install 2.0?
<clever>
Sonarpulse: is the daemon also 2.0?
<clever>
elvishjerricco: nix-store --dump <path> prints a nar to stdout, and nix-store --restore <path> reads a nar from stdin
<clever>
Acou_Bass: not sure then, i also had problems on the last update, but X refused to even start, amdgpu cant find the card, and simple rollbacks dont help, have to boot the older kernel
<clever>
mpickering: nix-env -i -E 'with import <nixpkgs> {}; foo.override { bar = true; }' i believe
<clever>
elvishjerricco: do you want it to land in /nix/store or just unpack it anywhere and peek inside?
<clever>
Acou_Bass: ah, journalctl -u display-manager, any errors near the end?
<clever>
elvishjerricco: it has to eval every single attribute in pkgs. and check the .name of each
<clever>
Acou_Bass: then check if X is running
<clever>
Acou_Bass: if you do ctrl+alt+f1 can you get a text console?
<clever>
:'(
<clever>
wow
<clever>
catern: -i has to eval all of nixpkgs, -iA hello only has to eval hello
<clever>
!-A
<clever>
catern: nix-env -iA nixos.hello
<clever>
srhb: i remember that one, what was it...
<clever>
but you now have the option to disable
<clever>
it defaults to checking signatures, even when you have absolute control over the store (+w)
<clever>
that even explains the weird problems ive had with `nix copy`
<clever>
and is also an improvement
<clever>
that would explain things
<clever>
while on 1.11, a trusted client just never has checking, i think
<clever>
tnks: so a trusted client, has to choose to enable/disable signature checking
<clever>
untrusted are forced to false
<clever>
ultimate is also something the client provided
<clever>
if you are untrusted, it forces it back to false
<clever>
ah, and the dontCheckSigs line 689 is checking, is what the client set
<clever>
and ultimate may have other effects afterwards
<clever>
tnks: ah, so the new way, it sets the ultimate flag, rather then dontCheckSigs