<clever>
Thra11: yeah, and you need the sandbox on to ensure it fails loudly
<clever>
Thra11: nix will make the PATH pure, but only the sandbox stops scripts from "fixing" $PATH
<clever>
its essentially a proxy
<clever>
johanot: the fact that i'm using an ipv6 tunnel is what breaks netflix
<clever>
johanot: if my ISP offered v6, then the geolocation would say canada, and everything would be fine
<clever>
and then its just 100% ignoring nix!
<clever>
or export PATH=/usr/bin/
<clever>
Thra11: it might simply be /usr/bin/g++
<clever>
Thra11: is this on nixos or another distro?
<clever>
johanot: in the past, i was successfully able to get the american lineup, using ipv6
<clever>
so i have a 2nd wifi that lacks ipv6, just for netflix use, lol
<clever>
netflix thinks i'm trying to get around region lockout, so it refuses to play anything!
<clever>
johanot: oh, and the tablet on my main wifi, has ipv6, which is a tunnel, so it exits in the wrong country
<clever>
johanot: i just use the tablet
<clever>
johanot: due to that, ive just given up on netflix in the laptop or desktop :P
<clever>
johanot: yeah, ive had to play netflix inside virtualbox, with windows 10, lol
<clever>
johanot: ive found that the android netflix app can remotely control the netflix app on a ps3 (and likely the chromecast), and skip the entire streaming layer
<clever>
> hello.drvPath
<clever>
aanderse-work: only if you have a derivation object
<clever>
Xyliton: $out/include/
<clever>
ocharles: can you rename the file in the gist to have a .nix extension?
<clever>
it already has a flag set there to support zfs
<clever>
adamantium: there is a chunk of nixos config in rescue_boot, just add normal nixos options to it
<clever>
patchShebangs .
<clever>
kenshinCH: sounds like you need to run patchshebangs over things
<clever>
so it would be a lot simpler to just use nixos-unstable for everything
<clever>
but your nixos modules are not aware of that change
<clever>
oh, and spl was merged into zfs
<clever>
ive not looked into that feature
<clever>
without that, it will obey /root/.config/nixpkgs/config.nix
<clever>
yeah, that will do it
<clever>
,unfree
2018-08-16
<clever>
adamantium: this is something i did back when i wasnt commited to nixos, and i was still using the gentoo grub to source the nixos grub.cfg
<clever>
adamantium: i had source inside a menuitem, so it only sources when i tell it to
<clever>
adamantium: they could even share a zpool, if they have different roots
<clever>
adamantium: you could potentially have 2 /boot partitions, for different OS's (even 2 nixos's!), and then have a menu option that sources the other one on-demand
<clever>
adamantium: in the past, i have used the source command in grub.cfg to source another grub.cfg file
<clever>
we need a way to add another linux based OS to the menu
<clever>
LnL: nixos just doesnt have enough options for systemd-boot
<clever>
~460mb cost
<clever>
LnL: this puts the entire nixos installer into /boot, along with a grub option to select it
<clever>
adamantium: yeah, as long as i have the config, and maybe the nixpkgs rev, i can repair almost any damage to /nix (except the nix-env profile list of packages)
<clever>
you have snapshots of /etc/nixos, so you can just rollback the config and nixos-rebuild
<clever>
it keeps daily and monthly snapshots
<clever>
and if / is on the same dataset, you are loosing backups of /
<clever>
and then you have to manually destroy snapshots to get your space back
<clever>
adamantium: the snapshot keeps a copy of everything you GC, and then you gain zero free space
<clever>
snapshots on /nix make it difficult to garbage collect
<clever>
then i have automatic snapshots on / but none on /nix
<clever>
i prefer having seperate datasets for / and /nix
<clever>
yeah
<clever>
adamantium: i dont really use the zfs rollbacks much, nixos generations handle that task fine
<clever>
Henson: which prevents bugs like moving things out of the store
<clever>
it makes the store read-only, so root cant modify files in the store
<clever>
adamantium: nixos always does that
<clever>
both of those are identical i believe
<clever>
and line 61 will be wrong on 32bit, you want --interpreter "$(cat $NIX_CC/nix-support/dynamic-linker)"
<clever>
line 63 is also not needed, the stdenv already defaults to the current system
<clever>
Henson: if you run ldd after patchelf, then you dont need LD_LIBRARY_PATH
<clever>
Henson: line 24, you can change the cp to: cp -a ${./69-basler-cameras.rules} .... and then delete line 8, and repeat for other similar things
<clever>
Henson: `set -e` is not needed, the stdenv does that for you
<clever>
Henson: can you gist what you have now and i can check it for anything minor?
<clever>
gchristensen: i easily missed the notice Sigyn sent when i started to flood a bit
<clever>
kalbasit[m]: to start with, try adding boot.kernelParams = [ "console=ttyS0" ]; and then nixos-rebuild boot and reboot
<clever>
kalbasit[m]: that effects the initrd as well, and handles the luks passwords
<clever>
kalbasit[m]: if you want linux on the serial and dont care about grub, you need to add console=ttyS0 to the kernel params
<clever>
Henson: its refering to line 9 of the old default.nix
<clever>
Henson: ${pylonArchive} is no longer a shell variable but a nix variable
<clever>
samueldr: give up and use grub? lol
<clever>
Henson: if you post the new nix file to gist, i can also check it for any other issues
<clever>
and then if you just swap that file out, you can test the same setup there
<clever>
a common reason to split them up like in your gist, is that you can create a sophos-vbox.nix, that sets deployment.targetEnv = "virtualbox"; instead
<clever>
in your gist, the only resource is an ec2 keypair
<clever>
and resources is the non-machine stuff defined in the nixops files
<clever>
nodes is a set of every other machine in the cluster, so you can do nodes.sophos.config,services.whatever to read the config of another machine
<clever>
nixops adds 2 extra arguments that nixos modules can accept, nodes, and resources