<clever>
then it will be in the grub config by default
<clever>
you can also add boot.shell_on_fail to boot.kernelParams
<clever>
it seems stable during stage-1
<clever>
boothead: i do find it strange that the problem only manifests after you proceed to stage-2
<clever>
boothead: and you should be able to check lsmod after you get an initrd shell to confirm
<clever>
boothead: you wouldnt even be able to mount /nix if dm_mod was missing
<clever>
boothead: nixos already has those by default
<clever>
Myrl-saki: the remote nix.conf controls the core count
<clever>
Myrl-saki: it doesnt control the core count, only the total number of nix jobs you try to send to the machine
<clever>
boothead: the cmdline in grub should show the version, as would uname -a in the initrd
<clever>
google the error and see what others have done
<clever>
boothead: yeah
<clever>
boothead: id try an older generation of a channel, but its all gone now
<clever>
boothead: due to the deterministic nature of nix, it is likely to recreate the same problem if installed from the same nixpkgs
<clever>
boothead: try exit and see if it can continue to boot
<clever>
or its ext4?
<clever>
boothead: ahh, so your iso formatted /nix with new features, and the kernel you installed cant mount it
<clever>
then we can review your configuration.nix
<clever>
and then exit out of that shell to resume the boot
<clever>
then you should be able to just mount each LV to the right sub-dir of /mnt-root/
<clever>
boothead: and is the status available?
<clever>
boothead: does it say the access is read/write?
<clever>
boothead: you may need to use "lvm pvdisplay"
<clever>
boothead: lvm should be available
<clever>
boothead: thats basically partitioning your partitions
<clever>
boothead: generally, the dm-0 device shouldnt be partitioned
<clever>
boothead: what does tabtab show as being available?
<clever>
boothead: you can now open a shell, and check what lvdisplay, pvdisplay, and vgdisplay say
<clever>
boothead: then you can get a shell when it fails to mount the root
<clever>
boothead: boot.shell_on_fail
<clever>
boothead: do you know how to edit the cmdline in grub with e?
<clever>
Myrl-saki: the user importing the build from the builder has to be trusted
<clever>
sphalerite: use relative paths in the config?
<clever>
if you dont specify a user when you ssh into a machine, it defaults to the same user you are locally
<clever>
remote builds are not initiated from the nixbld group
<clever>
Myrl-saki: ssh keys?
<clever>
it shoved 4 NAR's worth of data into the socket before getting a reply back
<clever>
and ive seen it claim to be copying 4 things, then fail because the 1st was unsigned
<clever>
ive seen only a single `nix-store --write` on the remote end
<clever>
i think it does 1 thing at a time over 1 ssh, but it doesnt wait for confirmation that things are working
<clever>
Myrl-saki: oh, and i have also noticed similar lag spikes, my laptop is a build slave and is on 802.11g, and synery lags noticably when its transfering things
<clever>
not sure
<clever>
scp does things one file at a time, and waits for the remote end to sync
<clever>
ive seen users in here before trying to diagnose why X dies whenever they try to build something
<clever>
nix will kill the chosen user, so any nix build command is asking nix-daemon to kill your entire session :P
<clever>
do not add yourself to the group, its literally suicide
<clever>
oh yeah, you also need a nixbld group with write to the store, and build users in the group
<clever>
Myrl-saki: yeah
<clever>
Myrl-saki: i think nix tries to auto-create it with the users name, the one in the user may also have to be updated to not be default anymore
<clever>
Myrl-saki: this symlink may also have to be manually created
<clever>
Myrl-saki: the default and user profile should be in $PATH, something in $NIX_PATH, the user should own his own profile dir
<clever>
Myrl-saki: then i run nix-daemon as root, and fix the errors as i see them
<clever>
Myrl-saki: i tend to mutate single into multi, i start by chowning /nix/store to root:root, and i tend to drop nix.sh entirely and set things up myself
<clever>
ah, i see
<clever>
Myrl-saki: there is an option in nix to have the remote end use a binary cache when possible
<clever>
nikivi: use "sudo -i" then "nix-channel --list"
<clever>
nikivi: sudo sets the wrong $HOME
<clever>
nikivi: are you on darwin?
<clever>
nick_l: can you pastebin the full output when its failing (and ran with -v) and also the info output?
<clever>
then nix-build only has to be ran once to update the script
<clever>
jD91mZM2: it would be better to have nix wrap or modify that script in an automated way, to insert the paths it needs
<clever>
nick_l: every line of code that nixops can potentially reference
<clever>
nick_l: this will search the entire closure of nixops for "foo" or "undefined variable"
<clever>
wolftune: git wont be available until you install git
<clever>
wolftune: how did you install git and docker?
<clever>
iqubic: let me gist my setup...
<clever>
iqubic: is it listed in `mount` ?
<clever>
UNIcodeX_: it would still waste cpu cycles on write, then find it made it worse and save uncompressed
<clever>
i find zfs better then btrfs
<clever>
after fixing /boot and the config that refered to it
<clever>
boot nixos form usb, mount the rootfs, run nixos-enter, nixos-rebuild boot
<clever>
maurer: i dont even bother with backups for /boot, it can be recreated in minutes with the right recovery media
<clever>
grub already has trouble traversing /nix/store/
<clever>
UNIcodeX_: i wouldnt trust any bootloader with zfs, since its so bleeding edge
<clever>
UNIcodeX_: i also dont trust grub with zfs, so id still use a diff boot
<clever>
`Native encryption is not production ready, keep backups.`
<clever>
i think the topic in the channel also says so
<clever>
a 32bit-only and a 64bit-only wine?
2018-05-01
<clever>
gleber_: build-time would likely use exec, runtime would use nixops key management
<clever>
gleber_: runtime or buildtime secrets?
<clever>
and its safe in a multi-user context, since it runs as your own user, the nix it spits out is evaluated, and then its pure and the daemon doesnt care or know
<clever>
it always runs as the user doing the nix eval, never the daemon
<clever>
gleber_: updated the gist, you can see it ran as my user
<clever>
gleber_: but if you instead only do impureEnvVars = ["FOO"]; on a fixed-output derivation, and set FOO at build time, it should get in
<clever>
gleber_: builtins.getEnv also saves the auth details into /nix/store as world-readable files
<clever>
gleber_: the value it gets is put into the .drv file, and when the value changes, it triggers a rebuild
<clever>
gleber_: builtins.getEnv is still "pure"
<clever>
dmj`: pkgs.gcc contains g++
<clever>
dmj`: did you try gcc?
<clever>
stdenv.cc.cc
<clever>
nschoe: ah, then nixpkgs may not have enabled opus
<clever>
nschoe: but it can find opusparse ?
<clever>
nschoe: its part of the nix-index package
<clever>
nschoe: [clever@amd-nixos:~]$ nix-locate opus | grep gstream
<clever>
nschoe: it appears to be in plugins-bad
<clever>
gst_all_1.gst-plugins-bad.out 23,088 x /nix/store/43szlakcix305r4rwr45v0sxpfb939a9-gst-plugins-bad-1.10.4/lib/gstreamer-1.0/libgstopusparse.so
<clever>
yep
<clever>
lejonet: what about this?, after you fix the references
<clever>
Myrl-saki: you need to create a new derivation with mkDerivation or runCommand, which depends on gcc (mkDerivation already does by default), and add things to its buildInputs
<clever>
Myrl-saki: thats just a dumb list of derivations and will fail the same way
<clever>
Myrl-saki: also, -A gives you a shell suitable for building gcc, not running gcc
<clever>
Myrl-saki: it has no clue how to merge 2 of them
<clever>
Myrl-saki: it creates a shell that has all of the env vars of the named derivation
<clever>
[Leary]: what about its log output?
<clever>
Dezgeg: if there is only one dvb-core.ko at the time depmod is ran, it wont see the kernel version
<clever>
Dezgeg: i'm guessing meta.priority so the nix buildEnv of modules overwrites correctly before the depmod runs?
<clever>
[Leary]: what does `systemctl status wpa_supplicant` say?