<clever>
dirkx__: check the module source, what does it to with extraModules?
<clever>
dirkx__: what does `nix-store --verify --check-contents` return?
<clever>
dirkx__: nope, its likely an issue with the config your giving it, what did you try changing?
<clever>
dirkx__: try `nixos-rebuild build` and then dig the httpd.conf out of the result symlink, perhaps with `nix-store -qR ./result | grep httpd.conf` ?
<clever>
doesnt need the quotes
<clever>
dirkx__: how is it getting included in?
<clever>
roxirc: can you pastebin the entire file?
<clever>
:)
<clever>
orloge: what about `nix-channel --list` ?
<clever>
orloge: what did nix-channel --update print out?
<clever>
orloge: nix-channel --update, as root
<clever>
orloge: you may need to update your channel
<clever>
or just move that remaining line (24) into installPhase
<clever>
mehlon: you can delete lines 21-23, and rename it to postBuildHook i believe
<clever>
mehlon: the default configurePhase will run cmake for you, and the default buildPhase runs make for you
<clever>
mehlon: is enableParallelBuilding set on the drv?
<clever>
mehlon: and `nproc` ?
<clever>
mehlon: what about `nix show-config | grep cores` ?
<clever>
then its not the nixbld group to blame
<clever>
mehlon: what does the `id` command output?
<clever>
bbl
<clever>
dirkx_: this lets you nix-env -iA foo.hello
<clever>
id say try rebooting and see what happens
<clever>
thenn it looks like boot0008 is the most recent one
<clever>
the_pumpkin_man[: what does `ls -lh` report for both?
<clever>
the_pumpkin_man[: what about the last-mod timestamp on both?
<clever>
juhe: is pkgs.flashplayer.src using fetchurl or fetchzip?
<clever>
the_pumpkin_man[: its loading boot0008 first
<clever>
the_pumpkin_man[: look closer, at the boor order
<clever>
the_pumpkin_man[: and has that file in /boot been updated?
<clever>
the_pumpkin_man[: grub can use efibootmgr without adding it to the global PATH
<clever>
the_pumpkin_man[: youll need to install it with nix-env, nix-shell or nix run
<clever>
the_pumpkin_man[: we will also want to inspect efibootmgr -v, before we reboot
<clever>
juhe: just let flash die? lol
<clever>
__monty__: yeah, the above is how to mount it from the livecd for repair work
<clever>
that might have been udev configured to activate lvm automatically
<clever>
then you need to luksOpen, then pvscan and vgchange -a y
<clever>
is the lvm inside the luks?
<clever>
why is it not possible?
<clever>
nixos-install is just a script that runs nixos-rebuild under a chroot
<clever>
the_pumpkin_man[: just boot the livecd, mount things at the "right" place, maybe tweak the config, and re-run nixos-install
<clever>
the_pumpkin_man[: you dont need to reinstall anything if you break it
<clever>
the_pumpkin_man[: can you try again, but before you reboot, pastebin the output of `lsblk ; blkid ; fdisk -l ; efibootmgr -v` ?
<clever>
the_pumpkin_man[: you might be better off just making /boot the ESP, and not having it encrypted
<clever>
i'm not sure how you would force grub to embed the keymap into its stage1 file
<clever>
the_pumpkin_man[: looks like you need to generate a keymap file, and then load it within grub, but that would normally load after it mounts /boot
<clever>
tbenst[m]: can you pastebin the entire nix expression?
<clever>
tbenst[m]: thats the name your matching against
<clever>
"cudatoolkit-10.1.243"
<clever>
nix-repl> cudatoolkit_10.name
<clever>
bots dead
<clever>
,
<clever>
> cudatoolkit_10.name
2019-12-22
<clever>
yeah, any program can now benefit from the modesetting
<clever>
prior to kms, the panic was printed to the text console, but xorg had a strangle-hold on the gpu, so you never saw the error, and the machine just "hangs" silently
<clever>
so you can actually see the panic msg
<clever>
another benefit of KMS (in theory) is that the kernel can switch back to text mode when it has a panic attack
<clever>
Fare: -I nixpkgs=/path/to/nixpkgs
<clever>
ah, correction, it runs the shell with -n, not shellcheck
<clever>
thomashoneyman: writeShellScriptBin will stick a #! at the top, and shellcheck it for you
<clever>
thomashoneyman: thats what you get from `ls $out`
<clever>
thats the temp dir that your cd'd into when the script starts
<clever>
yeah
<clever>
it never did a cd, so the ls is in $NIX_BUILD_TOP
<clever>
thomashoneyman: and the --query --binding?
<clever>
thomashoneyman: also, try running `nix-store --query --binding buildCommand /nix/store/foo.drv` on the drv that fails to build
<clever>
ah, that behaves a bit differently from the normal checkPhase, but it should run it
<clever>
thomashoneyman: can you paste your nix expr?
<clever>
thomashoneyman: i dont think writeTextFile runs checkPhase normally
2019-12-21
<clever>
Guest13048: what about file-roller?
<clever>
Guest13048: what happens if you just run unzip on the executable?
<clever>
Guest13048: can you pastebin it?
<clever>
> pythonPackages.binwalk
<clever>
Guest13048: try running binwalk on the installer, what does it find?
<clever>
Guest13048: check to see if it has a --extract flag, or if you can extract the files without running it?
<clever>
srhb: the quotes on the outside have the same effect
<clever>
srhb: that will copy the entire ./nix dir, then tack a file on the end
<clever>
srhb: i think `mySource = '${./nix}/some-specific-file.nix"; is much much simpler
<clever>
mehlon: if you want it in $PATH, use nix-env
<clever>
sphalerite: yeah, thats what i said earlier, the ratio of inodes to bytes of disk is set when you format
<clever>
sphalerite: but what about inode count?
<clever>
and once created, the ratio is fixed
<clever>
betaboon: i believe you can only change it when creating the fs
<clever>
Raito_Bezarius: just expand the EBS and reboot it, and your done
<clever>
Raito_Bezarius: the aws image will resize its own rootfs on bootup
<clever>
is the server in aws? nixops?
<clever>
assuming its ext2/3/4
<clever>
same as any other distro, expand the partition, then run resize2fs on it
<clever>
and it cant be changed
<clever>
Raito_Bezarius: when you format an ext filesystem, the ratio of disk space to inodes is set
<clever>
Raito_Bezarius: make the disk bigger
<clever>
nothing in /tmp at all?
<clever>
manually delete non-nix things first, to let it run
<clever>
that will delete as few things as possible
<clever>
try copying the resulting file back up to the server?
<clever>
Raito_Bezarius: can you run the same query that fails in the error?
<clever>
which filesystem?
<clever>
and if all went right, deletes the journal when its done
<clever>
it creates a journal when it begins a write, copies blocks to the journal before it overwrites them
<clever>
it has journal files to prevent such things from corrupting it
<clever>
the entire db engine is designed to be hardened against corruption
<clever>
Raito_Bezarius: how do people keep corrupting a sqlite db? lol
<clever>
Raito_Bezarius: how did the db get lost?
<clever>
Raito_Bezarius: not really, it would be simpler to just delete /nix and re-run nixos-install from the livecd
<clever>
so you have to manually dump things, and know your in such a state
<clever>
nixos partially supports it, but will just boot normal nixos in the event of a crash
<clever>
so it can then dump the ram of the dead kernel upon crashing
<clever>
the crash kernel is meant to kexec over to a pre-loaded kernel, and run within a pre-reserved area
<clever>
b: intentionally crash, so you run within the reserved region!
<clever>
which can be used to either a: exclude ram
<clever>
you can configure how much ram is reserved for it
<clever>
another hacky option is the crash kernel
<clever>
thats the one i was thinking of
<clever>
2373 mem=nn[KMG] [KNL,BOOT] Force usage of a specific amount of memory
<clever>
mb, but its not spelled right
<clever>
gchristensen: i think its maxmem=256 on the kernel cmdline
<clever>
jakobrs: but the cpu can run 32bit binaries just fine, so its simpler to use a 32bit->32bit compiler
<clever>
jakobrs: crossSystem is more for when you cant run the binaries your building
<clever>
jakobrs: when you run nix-build, you can just add `--argstr system x86_64-linux` or `--argstr system i686-linux` to force 64 or 32bit mode when building
<clever>
jakobrs: with nix, you just describe how to build it for any arch, and then nix can build a 32bit or 64bit version, as needed
<clever>
jakobrs: what part of the project needs multiple arches at once?
<clever>
jakobrs: my latest project involves 3 different cross-compilers, and mixing things up like that is trivial
<clever>
myme: might be an issue with 19.03 then, a reboot sounds good
<clever>
myme: and what does `nix-channel --list` return?
<clever>
myme: what config did you try last, and how did it fail exactly?
<clever>
elvishjerricco: yeah, youll have to check the bios options to try and convince it to netboot
<clever>
,unstable myme
<clever>
myme: boot.kernelPackages = pkgs.nixos-unstable.linuxPackages_5_3; for example, plus
<clever>
elvishjerricco: yeah, thats just general idle traffic
<clever>
elvishjerricco: and i dont see any trace of dhcp in that wireshark
<clever>
elvishjerricco: grub shouldnt be coming up if its network booting
<clever>
elvishjerricco: screenshot?
<clever>
yeah
<clever>
elvishjerricco: what does wireshark show in the dhcp packets?
<clever>
pie_: thats why modules have { ... }:, to ignore any extra things you add
<clever>
pie_: and that will ruin all error messages
<clever>
that problem, is why we used options instead
<clever>
pie_: which requires the if statement to be eval'd
<clever>
pie_: which requires knowing every key of config.
<clever>
pie_: but to read extra, you must read config._module.args.extra
<clever>
pie_: and imports gets moved up a level when it wraps
<clever>
pie_: if options and config are both missing, nixos will wrap it in a { config = ...; } for you, to fix things
<clever>
pie_: all modules contain options, imports, and config
<clever>
pie_: and extra itself may cause the same problem, try making isVM a let block
<clever>
pie_: try wrapping it as { config = if ... ; }
<clever>
elvishjerricco: only if you run justdoit, you can also just ignore that script and run anything else
<clever>
pie_: the problem, is that it must know if your set contains a .options, before it can compute the options
<clever>
pie_: `{ config = if condition then {} else {}; }` would fix it
<clever>
pie_: `if condition then {} else {}` may cause problems
<clever>
pie_: can you pastebin your example?
<clever>
fuzen: try creating a new user?
<clever>
fuzen: only other thng that could play a factor is your home folder
<clever>
elvishjerricco: you point wan towards the real router and internet, and lan towards a private ethernet card, that only has the client(s)
<clever>
elvishjerricco: yep
<clever>
elvishjerricco: which is why netboot_server.nix uses 2 cards, the ethernet port is isolated from the router and in full control
<clever>
elvishjerricco: or plug the client into a seperate network
<clever>
fuzen: that wouldnt help, the --verify already confirmed that all files nix can reinstall are already perfect
<clever>
elvishjerricco: yeah, its usually best to only have one dhcp server
<clever>
fuzen: it would have still made a generation for each upgrade
<clever>
have you tried older generations? you can test them without a rollback
<clever>
what changed?
<clever>
or maybe its already fixed in unstable?
<clever>
fuzen: you could try an older nixpkgs version
<clever>
fuzen: it might be a but with the chroot env stuff, not mounting /nix into the chroot
<clever>
fuzen: does that file exist?
<clever>
[pid 20090] execve("/nix/store/1vsf7dahgpwacy1ab3h0hx1w2ng9dqwx-lutris-init", ["/nix/store/1vsf7dahgpwacy1ab3h0h"..., "/home/aizuzu"], 0x7fff3186a578 /* 71 vars */) = -1 ENOENT (No such file or directory)
<clever>
elvishjerricco: start by opening up wireshark, and filter to dhcp and tftp packets, what is happening when it boots?
<clever>
elvishjerricco: the dhcp server should report a boot filename
<clever>
fuzen: can you pastebin `strace -f steam` ?
<clever>
and the stdenv will take care of the rest
<clever>
nativeBuildInputs = [ autoreconfHook ]; i believe
<clever>
gustavderdrache: there is also `autoreconfHook` which will give you the autoconf binaries, and automatically run them for you, to generate a new configure script
<clever>
anything you use at runtime goes into buildInputs (libraries, binaries ran at runtime)
<clever>
anything you use at build time (cmake, pkgconfig) goes into nativeBuildInputs