<clever>
double-check "ip addr" to see if you have a v6 addr or not
<clever>
i was using that to disable ipv6 in my tablet, but to disable it in a normal linux machine, just: echo 0 > /proc/sys/net/ipv6/conf/wlan0/accept_ra
<clever>
you can omit that part on if you can obtain a root shell normally
<clever>
and its only to remotely run it on an android device
<clever>
androidenv.platformTools
<clever>
so i use the above adb command to neuter ipv6 support in my tablet
<clever>
netflix thinks i'm trying to pirate content, and just shuts off entirely
<clever>
but geolocation my v6 says american
<clever>
in my case, i'm using an ipv6 tunnel, so geolocation my v4 says canadian
<clever>
and when linux gets one, it will automaticaly add the IP
<clever>
in most setups, the router is sending out route advertisement packets
<clever>
i typicaly use a command like this, and then cycle the network link
<clever>
adb shell su -c 'echo 0 > /proc/sys/net/ipv6/conf/wlan0/accept_ra'
<clever>
ah
<clever>
how did you disable ipv6?
<clever>
once you form the connection, its stuck on the protocol&ip it used, so ipv6 can turn back on without breaking it
<clever>
Dezgeg: found a potential solution, you must import <nixpkgs> { platform = platforms.raspberrypi2; }; (or change the default for v7 and break every other v7 platform)
<clever>
Sonarpulse: what error are you getting?
<clever>
gchristensen: the login attempt is on tty2 i think
<clever>
gchristensen: without more info on how exactly that host is messing up, it may be imposible to reproduce, but we can reasonably assume it was timing, and that vcs2 checks will solve it
<clever>
viric_: oh, and i see something related to your systemd issues too
<clever>
viric_, Dezgeg: got around to confirming it and bingo: ("kernelBaseConfig","multi_v7_defconfig")
<clever>
but if gtk2 ever gets deleted, it will silently build without gtk2, rather then failing
<clever>
so it currently only serves as a hint to people reading the source
<clever>
so you would need to use an override to force gtk2 to null
<clever>
but callPackage will always supply it
<clever>
sorta, it allows gtk2 to default to null if its not supplied
<clever>
glines: i got 4 or 5 rows from sparkfun in one of my last orders, and thats plenty for now
<clever>
glines: also, my soldering is so rusty, i got a cold joint on my raspberry pi, and managed to drip a huge glob of solder directly onto the decoupling caps under the cpu, the caps the size of a grain of sand :P
<clever>
glines: first thing i did was put some header pins on it, so i could use it without too much soldering
<clever>
:D
<clever>
and nix-shell needs the bash functions to convert buildInputs into $PATH
<clever>
unpackPhase and configurePhase are 2 i can see being usefull
<clever>
rardiol: but you can just manualy run zsh under nix-shell (and loose access to those functions)
<clever>
rardiol: it needs to source a large number of scripts that define bash functions, that wont like a different shell
<clever>
one path to rule them all!
<clever>
ah
<clever>
then nix could detect the rpath
<clever>
looks like jar 0uvf $out/${jar} ${file} would disable compression for that 1 entry
<clever>
it wont get that much until it asks for it
<clever>
so it can prevent the thing your worried about
<clever>
i believe the special driver in my mobo, was to detect when a device asks for more current, and cranks up the current limits in the hardware
<clever>
yeah
<clever>
the voltage regulation prevents such issues, when its not shorted
<clever>
amps dont work like that
<clever>
the above bluescreen, turns out to be a combination of the high power usb charging driver in my mobo, the teensy, and a hub between the pc and teensy
<clever>
glines: it scans the contents of $out when the build is finished, and the compression in the jar can mask the paths
<clever>
avn: jar's can be made with zero compression, that would let nix find things still, and some stuff like android requires it (it just mmap's the files without unpacking)
<clever>
glines: then furniture got moved, and it needed to be on a usb extension, so i plugged it into a 1 port hub (an extension with a hub in it), and bam, blue screen of death!!
<clever>
glines: so i just leave the teensy plugged in 24/7 and it works fine!
<clever>
glines: but, the teensy claims to be a mouse with a wheel!
<clever>
and goes nuts when it gets a wheel event
<clever>
the game detected, that no wheeled mouse is present at startup
<clever>
glines: and i discovered, certain games go nuts when i hit the mouse wheel
<clever>
glines: at one point, i was controlling said windows machine purely thru synergy (windows/keyboard sharing software), so it had no mouse/keyboard plugged in
<clever>
domenkozar: this would be a good PR to test the hydra stuff on, since its changing an artifact under nixos/release.nix, rather then nixpkgs, so travis likely wont know what to do
<clever>
gchristensen: and PR is open!
<clever>
gchristensen: and it now has nearly the identical unionfs that the ISO's have, PR incoming!
<clever>
the store on the host is read-only, so this fails hard
<clever>
gchristensen: has nix-store --check-validity always wanted to create /nix/store/.links?
<clever>
and in other netboot adventures, nixos is mounting a tmpfs over /mnt-root, and covering up the squashfs mount point
<clever>
there is a header on the rpi for a reset button, and with it network booting, i can fully generate every single file from nix-build
<clever>
arcade*
<clever>
Dezgeg: i have it fully network booting, so i can just run nix-build on the router, and punch a large arcane button to test it
<clever>
Dezgeg: i'm testing on an rpi3 at the moment
<clever>
Dezgeg: sounds likely
<clever>
Dezgeg: and when i checked the config nixpkgs was generating, it had some device-tree options wrong, and was compiled for any arm chip
<clever>
Dezgeg: ah, ive been unable to get any kernel from nixpkgs to boot
<clever>
Dezgeg: when is the last time you tried booting a rpi from nixos-unstable?
<clever>
and it looks like the netboot image i mentioned is criticaly broken, /nix/store is read-only, and nix-store --check-validity within nixos-install wants to create /nix/store/.links/
<clever>
oh
<clever>
and it will insert the mac of the 0th NIC
<clever>
Zvieratko: with ipxe, you can just insert ${net0/mac} into almost any command i believe
<clever>
Zvieratko: ah
<clever>
Zvieratko: and with 2gig of ram, it can boot
<clever>
Zvieratko: heh, 300mb initrd, with 256mb of ram, *doh*
<clever>
Zvieratko: aha, the vbox ipxe has an empty version string, my build has a version of 1.0.0+
<clever>
trying to minimize how much i change in the ipxe file provided by nixos
<clever>
so it doesnt make an infinite loop
<clever>
i already have ipxe on my tftp, i just need to chainload ipxe conditionaly
<clever>
heh
<clever>
Zvieratko: this should be fun...
<clever>
Zvieratko: dang, the ipxe embeded into virtualbox lacks bzImage support!
<clever>
Zvieratko: ah
<clever>
Zvieratko: the syntax reminds me a bit of asp, but its probably just some basic turing complete substitution
<clever>
Zvieratko: and i have a custom nixos module that can mount the rootfs over iscsi
<clever>
Zvieratko: and i'm using a mix of both on my laptop, ipxe hijacks the legacy bios hdd api, so grub thinks the iscsi device is a local drive
<clever>
Zvieratko: heh, i found ipxe simpler then grub on this end
<clever>
Zvieratko: ipxe and my bios havent had that issue
<clever>
Zvieratko: i also have a raspberry pi that claims to be PXE booting, but it ignores the next-server field in dhcp, and tries to tftp the dhcp host
<clever>
Zvieratko: ah, so it would probably spin up its own vm's on-demand
<clever>
Zvieratko: do you happen to know of any simple tools to simulate a datacenter, or should i just spin up a dozen virtualbox instances?
<clever>
so its just a matter of being able to configure it from software
<clever>
Zvieratko: in nix, its pretty simple to put an entire OS into the initrd
<clever>
but kexec would run from the initrd, so nothing is mounted
<clever>
nixos-in-place is limited to whatever partitions are existing
<clever>
so i could run that kexec thing on any cloud provider, and hijack the machine
<clever>
the kexec is more for when you have an existing OS you dont want, and lack control of the boot process
<clever>
ah, so id just make a nixos image that can netboot, and fetch config from foreman
<clever>
a kexec-able nixos installer image
<clever>
and that reminds me, another idea ive had
<clever>
yeah, it does sound like something i would want to add support for in nixos-installer
<clever>
much simpler, since its just a dummy to allow booting different images
<clever>
Zvieratko: nixos has something similar, one sec
<clever>
heh, didnt think they could get that small, but i am working on a ~40mb nixos installer image
<clever>
the /boot on my NAS is <64mb
<clever>
heh
<clever>
i was able to update it to nixos 32bit, and then with a few more tweaks, 64bit-ize it
<clever>
Zvieratko: in my case, all it had left was a nix-build copy from 2015 and a few shreds of init.d that could still boot
<clever>
the second time, i was on the road, and all i had was half a gentoo system (most of it had been mv'd out to the NAS, and i didnt have time to finish)
<clever>
Zvieratko: the first time i did it, was as an experiment, and because i cant put a cd drive into my netbook, lol
<clever>
i just ran the nix-build command above, and then forced it to update the MBR and keep using the same rootfs
<clever>
without booting install media or repartitioning
<clever>
on related subjects, i have also made nixos consume a gentoo install twice
<clever>
complete with grub in the MBR of the iSCSI device
<clever>
Zvieratko: i do have my laptop booting over iSCSI as we speak
<clever>
the above command would build a given configuration.nix file, so its already present in /nix/store for later use
<clever>
things go smoother if the host is also nixos, using another distro isnt officialy supported