<clever>
so you generally want to use self, except when it causes recursion
<clever>
super is the result of all overlays up to but not including the current, so you can modify foo without infinite recursion
<clever>
Akii: self in the last file, is the result of applying every overlay in the list of overlays, but also, foo = self.foo; causes infinite recursion
<clever>
try rerunning the command with --show-trace and post the backtrace
<clever>
where did you put the reference to this file?
<clever>
yeah, that should work
<clever>
you tried to put something into nixos imports that didnt fit
<clever>
Akii: i believe you want to store the fetchGit path in a variable, then callPackage "${thatvar}/utleague.nix" {}
2018-04-20
<clever>
and what arguments are given to it
<clever>
grep all-packages.nix to see where its loaded
<clever>
its probably making use of similar features
<clever>
Judson: and that function is ran on each kernel version, to generate a package set that compiles the same module against several kernels
<clever>
Judson: kernel packages have to be loaded by a special function in all-packages.nix
<clever>
tokudan[m]: page wont load, postgresql error, likely due to low disk space, lol
<clever>
check the cmakelists.txt source to see how its finding openmp
<clever>
and you searched all of /nix/store/?, maybe the cmake test for it is faulty
<clever>
and it wont be visible as installed from outside the build
<clever>
hodapp: nix will autoamtically fetch openmp and provide it to the build
<clever>
hodapp: nix doesnt care about what is "installed" currently
<clever>
infinisil: do ssh -v localhost
<clever>
bachp: id consider that a waste of resources, aws may also not wait for the machine to configure itself before trying to have it serve traffic
<clever>
bachp: line 34 is the key, it will need to be modified to embed your software and config into the image
<clever>
bachp: ive not used it yet, but my general theory is to use nix-build to create an AMI that has your software fully configured, and upload it to aws, then configure auto-scaling to spin up that AMI
<clever>
Myrl-saki: i saw what you reported earlier, and it should be fairly simple to implement, i can look into it in a bit
<clever>
ShalokShalom: attribute names
<clever>
nicl_l: and youve set networking.firewall.enable = false; ?
<clever>
cant think of why tracking would be enabled then
<clever>
nicl_l: is the firewall enabled?
2018-04-19
<clever>
t
<clever>
tilpner: nix-build creates such roots by defaul
<clever>
try stracing that next?
<clever>
that sounds entirely normal
<clever>
its opening it in read-only mode, so it wont be created
<clever>
that error also makes sense if the pid file doesnt exist yet
<clever>
Aleksejs: the 2nd argument should be a filename, and strace should have translated it to a string
<clever>
Aleksejs: re-run it under strace and see what the error is
2018-04-18
<clever>
and set the name to nixos, nixos-rebuild prefers that channel name
<clever>
WilliamHamilton: ahhh, yeah, you will need to patchelf the bootstrap program
<clever>
WilliamHamilton: its also likely to go a lot better if you use nix-build instead of nix-shell
<clever>
Akii_Work: yep
<clever>
Akii_Work: thats a recent bug i heard sphalerite mention an hour ago, it no longer shows the error
<clever>
WilliamHamilton: if you build it inside nix-shell, it should just find zlib when linking
<clever>
Akii_Work: `nix-env -iA nixos.slack` forces it to use the slack package in the nixos channel, and it will fail with an error explaining how to enable unfree packages
<clever>
Akii_Work: `nix-env -i slack` will search the .name of every package you can currently install, and unfree packages are hidden by default
<clever>
WilliamHamilton: what program is failing to find it?
<clever>
WilliamHamilton: the shell wont add it to the search path at runtime, only at build-time
<clever>
nick_l: when does gnome-backgrounds come into play, is nixos-rebuild downloading it?, is it already on-disk?
<clever>
kisik21: nix already sets a bash flag to hard-fail the whole thing if any step fails
<clever>
kisik21: you can also use ; or even multi-line strings, no need for &&
<clever>
kisik21: 2 different packages both had a share/xfce4/panel-plugins in their output, so it only used one of them
<clever>
nick_l: find the top-level .drv file that `nixos-rebuild dry-run` prints out, then do `nix-store -q --tree` on that, and trace the path to gnome-backgrounds
<clever>
tokudan[m]: its linked against nix 1.11, you need to either use `nix repl` or `NIX_REMOTE=daemon nix-repl`
<clever>
nick_l: there are configuration.nix flags to disable a lot of that
<clever>
kisik21: yeah, once you wrap it with ( and )
<clever>
nick_l: id start with a GC, and check for old profiles of nixos you can delete
<clever>
kisik21: and the whole runCommand function returns that string within nix, for use elsewhere
<clever>
kisik21: runCommand will have its own $out, that you can just use in the quotes
<clever>
nick_l: nix may have deleted a partially downloaded file, after running out of space
<clever>
kisik21: pkgs.runCommand may be more suited to your needs then mkDerivation
<clever>
Myrl-saki: all code in the process has to be in the same arch
<clever>
Myrl-saki: we need 2 types of import, for the host, and target, and limit TH to using host imports
<clever>
Myrl-saki: because the TH is importing libraries that have already been compiled for the target and the source for those is long lost
<clever>
then you wind up with x86 libraries in your arm initrd
<clever>
Myrl-saki: those magic env vars cause the dynamic qemu-user to spit out its own host deps!!
<clever>
Myrl-saki: ldd sets some magic env vars, that cause ld.so to spit out the dyn libs, rather then run things
<clever>
was too much of a mess to get a backtrace out of it
<clever>
and getting the right gdb to play nicely...
<clever>
Myrl-saki: and the coredump was mangled by the mix of arches
<clever>
Myrl-saki: i also once tried qemu-user-x86-64 to run teamspeak on an rpi, but it threw an assertion within pulseaudio
<clever>
Myrl-saki: :D
<clever>
angerman: qemu-user basically works the same as wine, but for different arches of linux
<clever>
angerman: it should be trivial to take a linux-arm TH runner, and throw it under qemu-user-arm
<clever>
Myrl-saki: yeah, its mostly a purity thing, you cant tell nix that compiler x and compiler y are identical and can be swapped out
<clever>
Myrl-saki: its mostly a limitation of nix
<clever>
Myrl-saki: and if you ever try to switch to native, nix will rebuild the world
<clever>
Myrl-saki: if you configure nixpkgs to cross-compile with a linux-x86 host, then nix-env will forever rely on you having a linux-x86 host to do your building
<clever>
Myrl-saki: one sticky area with nix, is that you cant really mix native and cross easily
<clever>
Myrl-saki: i think angerman already mentioned ghc can target ARM easily enough and generate a self-contained dynamic library that android can dlopen()
<clever>
Myrl-saki: there is also a language called c-- in the mix now i believe
<clever>
Myrl-saki: i'm guessing they started with a compiler written in c++
<clever>
Myrl-saki: what i want to see, is a nix derivation that spits out a binary ghc, that can be patchelf'd to work on any future nixpkgs
<clever>
Myrl-saki: but that pre-compiled one is from debian
<clever>
Myrl-saki: nixpkgs has a binary ghc package, that just patchelf's a pre-compiled one
<clever>
ryantrinkle: justdoit also has a range of config flags, to support virtio, sata, or nvme, with or without luks, and legacy or uefi
<clever>
ryantrinkle: but justdoit uses grub in removable efi mode, so the bios thinks the fresh install is on removable media, and boots it without efivars being configured
<clever>
ryantrinkle: only thing i havent gotten to work yet, is efi based pxe
<clever>
ryantrinkle: originally, i had used the netboot_server to spread nixos from my old laptop to my new laptop
<clever>
ryantrinkle: 42 makes an http dir with the kernel and initrd
<clever>
ryantrinkle: 36 makes a tftp root directory containing the bootloaders
<clever>
ryantrinkle: line 11 loads the netboot installer profile, which generates an initrd that contains the entire rootfs
<clever>
ryantrinkle: it also includes the justdoit script in the netboot image, so you literally type "justdoit" at the root shell, and it installs nixos
<clever>
ryantrinkle: this nixos module configures a complete router to act as an ipxe server
<clever>
the next 2 runs didnt, and the cursor hasnt changed
<clever>
sphalerite: in xfce terminal, the first run of that printf printed garbage
<clever>
though i just keep better track of the state, most of the time
<clever>
ah, i can see that being handy
<clever>
sphalerite: tmux also restores the original cursor on shutdown, so the terminal isnt "damaged"
<clever>
sphalerite: the line cursor just feels wrong in xterm lol
<clever>
Aleksejs: generally, you should have a central machine that you run nixops on, where the state file is kept, just left in the default directoryu
<clever>
you will have to patch hydra to change it
<clever>
srhb: its hard-coded to true, bypassing all config
<clever>
jtojnar: 2 or 3 people tried to make PR's for that, and they where rejected
<clever>
Dezgeg: those are either config files built locally, stuff --fallback built, or infested paths
<clever>
Dezgeg: which is why ive thought of an extra util to audit the store, double-check signatures against cache.nixos.org, and then just anything that was not signed by nixos
<clever>
Myrl-saki: in theory, malware that is aware of nix can just fudge the hashes in db.sqlite, to claim the backdoor'd binaries are not corrupt
<clever>
Myrl-saki: for the verify operation, nix keeps the "correct" hash in db.sqlite
<clever>
and the malware just worked, lol
<clever>
and popped the usb stick into his ubuntu machine
<clever>
the local IT guy wanted to help the pentester, not knowing he was an attacker :P
<clever>
Myrl-saki: i think i saw that during a pentesting defcon talk
<clever>
zybell: then its an issue with the nixpkgs rev?
<clever>
i mostly use it to force "fullscreen only" games to play in a window
<clever>
virtual desktop mode
<clever>
sphalerite: wine has a mode where it doesnt need a window manager
<clever>
at play*
<clever>
sphalerite: memory footprint is also at plat, a minimal nixos squashfs is about 300mb, but not-os is 40mb
<clever>
Myrl-saki: i think so
<clever>
Myrl-saki: an entire display manager, written in haskell
<clever>
sphalerite: need to set one of the search path flags, cant remember the right name
<clever>
and that is responsible for running X
<clever>
typically, the display manager is ran
<clever>
Myrl-saki: that could probably be done, just need to get X working under not-os
<clever>
Myrl-saki: you can either use not-os to get a heavily stripped down linux os, or you could just rewrite nixpkgs from scratch if your feeling insane :P