2018-02-23
19:33
<
clever >
LnL: the amd variant is handled by the kvm_amd kernel module
19:32
<
clever >
elvishjerricco: then its already using kvm, what about the ram within the guest, what does free -m report?
19:32
<
clever >
wervenyt[m]: /dev/kvm only exists if the modules are loaded and its enabled in the bios
19:31
<
clever >
elvishjerricco: while the VM is running, do "ps aux | grep qemu" on the host, and check its args, is kvm listed?
19:30
<
clever >
elvishjerricco: does /dev/kvm exist?
19:11
<
clever >
dottedmag: the closest thing i can think of is hnix, a haskell project
19:10
<
clever >
i prefer screen
18:39
<
clever >
ldlework: you want home.packages = [ (pkgs.python27Packages.python.WithPackages (ps: [ ps.jedi ]) ) ];
18:39
<
clever >
ldlework: also, nix lists are weird, that does not call withPackages, that makes a list containing a function and a list
18:39
<
clever >
ldlework: withPackages expects to be given a function, that is passed all the python packages
18:37
<
clever >
lejonet: oops, that was meant for ldlework
18:27
<
clever >
lejonet: you need to use python.withPackages
18:09
<
clever >
lejonet: youll also want to double-check that it still works on older nixpkgs
18:06
<
clever >
TweyII: same
18:02
<
clever >
some small bits like builtins.fetchTarball with a sha256 require both client&daemon to be updated
17:49
<
clever >
lejonet: sounds like a bug in nixops, not compatible with that nixpkgs version, maybe send nixops a PR?
02:38
<
clever >
the irc client doesnt always tab-complete in a predictable way
02:37
<
clever >
mrkgnao: thats systemd only
02:34
<
clever >
a small OS built with nix and using runit
00:38
<
clever >
taohansen: and nix-env -f '<nixpkgs>' -iA nix-info ?
00:33
<
clever >
taohansen: and nix-instantiate --eval '<nixpkgs>' -A lib.nixpkgsVersion
00:31
<
clever >
taohansen: what does sudo nix-channel --list say?
2018-02-22
23:43
<
clever >
sphalerite_: also, i managed to hard-lock pid 1 when the fuse process crashed
23:42
<
clever >
sphalerite_: oh, ive also got some systemd-nspawn scripts in my narfuse repo
23:32
<
clever >
gillmanash: you could maybe have a git repo of helper files for tasks like that
23:30
<
clever >
gillmanash: of you import <nixpkgs> { config = {}; overlays = []; } then all config.nix and overlays are ignored
23:25
<
clever >
gillmanash: and line 4 blocks the config.nix, but overlays didnt exist when i made that, so its not covered
23:24
<
clever >
gillmanash: for this project, the release.nix provides linux and darwin derivations for the nearby default.nix
23:23
<
clever >
gillmanash: yeah
23:21
<
clever >
gillmanash: i prefer having something like a release.nix, that loads nixpkgs and blocks all overlays/overrides, and provides its own
23:08
<
clever >
sphalerite_: i run nixos on my router, with static IP's via dhcp, and dns pointing to those IP's
22:57
<
clever >
when that was fixed, synergy broken, because it wasnt set to read /home/clever/.Xauthority
22:56
<
clever >
sphalerite_: the xorg was just allowing connections from any user
22:56
<
clever >
sphalerite_: when i first got into nixos, the synergy stuff was running as root, with $DISPLAY, and worked, due to an un-discovered security problem
22:31
<
clever >
shlevy: though both of them require uncompressed .nar files in a directory to operate
22:29
<
clever >
now it can lazily parse just enough of the nar to do what it needs
22:29
<
clever >
(one of the first big things i did in haskell)
22:28
<
clever >
but i found that c++ took too long to parse the files
22:28
<
clever >
shlevy: this is a c++ fuse layer, that takes a directory of nar files, and mounts them
22:28
<
clever >
shlevy: one min
22:02
<
clever >
ive found bluetooth to be a pain to work with
22:01
<
clever >
not sure then
21:59
<
clever >
jonge: in pavucontrol, on the configuration tab, what options do you have?
21:59
<
clever >
jonge: and you then need to connect with something like blueman
21:58
<
clever >
hardware.pulseaudio.package = pkgs.pulseaudioFull; has to be set to get bluetooth support
21:57
<
clever >
jonge: also, have you changed pulseaudio.package?
21:57
<
clever >
jonge: then something else running as the gdm user might be trying to use audio?
21:57
<
clever >
jonge: try killing it with the kill command?
21:49
<
clever >
BlessJah: i'm not sure whats the best way to deal with your ESP though
21:47
<
clever >
BlessJah: zfs supports its own raid'ing, so you dont need to put it ontop of mdadm or anything
21:41
<
clever >
lejonet: yeah
21:41
<
clever >
BlessJah: i believe the menu entries are programmed into the bios, with the efibootmgr program
21:39
<
clever >
BlessJah: EFI booting with grub just auto-detects whatever you mounted to /boot/
21:37
<
clever >
BlessJah: and i dont think the bios supports mdadm based raid, so if you did raid sda1&sdb1, it would have to be done without any headers prefixed onto them
21:37
<
clever >
BlessJah: that device field is only for legacy booting
21:37
<
clever >
BlessJah: if you are using EFI, then you dont need to set the device in grub
21:32
<
clever >
BlessJah: i'm not sure, ive found them to be a bit unpredictable
21:31
<
clever >
lejonet: put the configuration.nix stuff into a file, then nix-repl /path/to/nixpkgs/nixos -I nixos-config=/path/to/configuration.nix
21:31
<
clever >
BlessJah: yeah
21:30
<
clever >
BlessJah: so at least the rootfs and /nix have to be via legacy
21:29
<
clever >
BlessJah: the nixos boot scripts expect your rootfs to be mounted with the standard mount command
21:28
<
clever >
lejonet: and do you have a line like this?
21:27
<
clever >
lejonet: double-check against your version of nixos/modules/misc/version.nix
21:24
<
clever >
lejonet: it tries to read either your .git, or one of a few version files in the root dir of the nixpkgs
21:23
<
clever >
lejonet: let me see...
21:22
<
clever >
lejonet: sounds related
21:14
<
clever >
lejonet: not sure thats related
21:12
<
clever >
lejonet: the nixops state doesnt come that early into the nix eval
21:06
<
clever >
lejonet: i'm out of ideas then
21:05
<
clever >
lejonet: that can happen when your not on a version hydra has pre-built
21:01
<
clever >
does one nixpkgs fail, and the other nixpkgs work?
21:00
<
clever >
the values dont really matter, that build will never be booted
20:59
<
clever >
nix-build /path/to/nixos --arg configuration '{ ... }: { boot.loader.grub.devices = "/dev/sda"; }' -A system
20:59
<
clever >
you can set that config inside the {}
20:57
<
clever >
no, point it to /path/to/nixpkgs/nixos
20:56
<
clever >
lejonet: try both, and use the nixos sub-dir
20:55
<
clever >
nix-build /path/to/nixos --arg configuration '{ ... }: {}' -A system
20:55
<
clever >
lejonet: what about this command...
20:52
<
clever >
lejonet: but it sounds more like your nixpkgs is broken then nixops
20:52
<
clever >
lejonet: yeah, i'm not sure whats up with that
20:50
<
clever >
lejonet: /nix/var/nix/profiles/per-user/clever/channels/
20:49
<
clever >
lejonet: nixops deploy --build-only --show-trace -I nixpkgs=/path/to/something
20:48
<
clever >
lejonet: try pointing that at a normal channel temporarily, and see if `deploy --build-only` works
20:46
<
clever >
lejonet: where does <nixpkgs> point?, nix-instantiate --find-file nixpkgs
20:43
<
clever >
lejonet: everything looks just fine, try `nixops deploy --build-only --show-trace` and add it to the gist
20:41
<
clever >
lejonet: can you also add configuration.nix?
20:40
<
clever >
and it will update the gist (you will also want to gist --login)
20:40
<
clever >
lejonet: nix-env -iA nixos.gist, then "gist -u <gisturl> file1.nix file2.nix"
20:39
<
clever >
lejonet: and line 2 is missing a ;
20:39
<
clever >
lejonet: the ( on line 3 is missing the matching )
20:35
<
clever >
lejonet: can you add the 2 files on line 9 to the gist?
20:33
<
clever >
lejonet: can you gist that output?
20:32
<
clever >
lejonet: what does `nixops info` say?
20:32
<
clever >
lejonet: ?
20:31
<
clever >
lejonet: i think so
20:30
<
clever >
lejonet: and if the machine names match up, it will just upgrade them to match the new expressions
20:29
<
clever >
lejonet: i believe you can change the deployment file with nixops modify
20:21
<
clever >
manveru: have you seen not-os?
20:20
<
clever >
KABA: /exit
19:36
<
clever >
gchristensen: check the likn i linked above in nixos-install.sh
19:36
<
clever >
gchristensen: nixos-install basically resets NIX_PATH
19:35
<
clever >
nhill: sure
19:22
<
clever >
nhill: line 111 uses NIX_PATH to find <nixpkgs>, then it sets a new NIX_PATH, with only nixpkgs and nixos-config
19:21
<
clever >
nhill: maybe
19:19
<
clever >
nhill: nixos-install also messes with NIX_PATH
19:19
<
clever >
nhill: what command did you run to cause the rrror?
19:18
<
clever >
so all paths refering to the rootfs, are the host root
19:18
<
clever >
gchristensen: there is also a bug with the recent nixos-install, where it just does the nix-build in the host env, then copies the result over
18:57
<
clever >
so you can just makeFlags = [ "-Dsomeflag=foo" ];
18:56
<
clever >
TonyTheLion: the default buildPhase will obey makeFlags
18:56
<
clever >
TonyTheLion: ons min, oops
18:56
<
clever >
troydm: one min
18:49
<
clever >
troydm: and make sure its inside the linuxPackagesFor function, in all-packages.nix
18:47
<
clever >
nhill: also, setting programs.fish.enable adds it to systemPackages for you, so you can remove that bit
18:46
<
clever >
fish isnt a service that runs in the background
18:45
<
clever >
nhill: i think its programs.fish
18:40
<
clever >
boomshroom: you can also put that line into a shell-32bit.nix and then just point nix-shell at the file
18:40
<
clever >
boomshroom: nix-shell -E 'with import <nixpkgs> {}; pkgsi686Linux.stdenv.mkDerivation { name = "dummy"; buildInputs = []; }'
18:38
<
clever >
boomshroom: and if you use pkgsi686Linux.callPackage, everything you depend on will be 32bit
18:37
<
clever >
boomshroom: if you use pkgsi686Linux.stdenv.mkDerivation then it will use 32bit compiler/linkers
18:30
<
clever >
troydm: i havent done any kernel modules since getting into nix
18:11
<
clever >
troydm: grep the whole nixpkgs for the name of another directory in that region
18:11
<
clever >
troydm: you need to edit a file somewhere to reference the new rtl8192eu directory
14:45
<
clever >
guibou: it sounds like you need to add the library to the rpath of the program in question, with patchelf
02:58
<
clever >
but it will persist after a .overrideAttrs
02:58
<
clever >
so its the same as (mkDeriation ..) // { foo = bar; }
02:58
<
clever >
samueldr: so they have no effect on the hash of that derivation
02:58
<
clever >
samueldr: passthru adds attributes to the derivation, but does not actually exposed them as env vars within the derivation
02:57
<
clever >
samueldr: i would instead use passthru
02:54
<
clever >
samueldr: 1.11.15 also checks for that flag
02:53
<
clever >
samueldr: it will also obey the tarball-ttl field in nix.conf or --option
02:52
<
clever >
yeah, an hour sounds right
02:51
<
clever >
samueldr: you can also just make the url different when the contents change, thats another simpler way to deal with it
02:34
<
clever >
and then reuse caches, based on the hash of the tar
02:34
<
clever >
if you just nuke the entire directory, it will re-download the tar
02:33
<
clever >
the filename is a hash of the url its for
02:33
<
clever >
the second is a symlink to its location in the store
02:32
<
clever >
the first is the metadata about the url and a timestamp
02:32
<
clever >
lrwxrwxrwx 1 clever users 91 Feb 21 14:13 0d4h36hxmzd1dw4109idlxppb0ly013laj79b1bw1068mi0zgh2m-file -> /nix/store/d9q7wc59j6didr4m85hzwyxbqqgf7qaj-4fb198892d298452023ab176e7067da58d30772e.tar.gz
02:32
<
clever >
-rw-r--r-- 1 clever users 143 Feb 21 14:13 0d4h36hxmzd1dw4109idlxppb0ly013laj79b1bw1068mi0zgh2m.info
02:32
<
clever >
[clever@amd-nixos:~]$ ls -ltrh .cache/nix/tarballs/
02:32
<
clever >
and may reuse the output
02:32
<
clever >
and if you choose to have it unpacked, it will generate a derivation that unpacks, compute the output path, and check the store for that
02:31
<
clever >
then, based on the cache-control headers, it may discover it hasnt changed, and re-use the storepath again
02:31
<
clever >
and based on the TTL, either reuse the old store path, or re-query the webserver
02:31
<
clever >
samueldr: first, it will hash the url, and lookup a cache file in $HOME
02:30
<
clever >
samueldr: ive read the code involved in it
00:24
<
clever >
sphalerite_, triangles: -p doesnt accept channel names, only package attribute paths
2018-02-21
21:49
<
clever >
gchristensen: try logging `ps -eH x` from inside this program to see what its parent is?
21:11
<
clever >
dash: yeah, getting the npm built under nix is still a tricky part
21:09
<
clever >
dash: this downloads an electron based darwin app, extracts the javascript code, then generates a nix package that runs it under nixpkgs electron
21:06
<
clever >
dash: i have recently noticed that discord patchelf's the discord supplied electron, and now the file-browse dialog is significantly older and lacking of features
21:05
<
clever >
dash: i just run ${electron}/bin/electron against the dir with package.json
20:27
<
clever >
which may count as bloat
20:27
<
clever >
firefox linking against PA will pull it in as a dependency, even when the user isnt using it
20:25
<
clever >
i use pulseaudio on all of my desktop systems
20:25
<
clever >
2 laptops, 1 desktop, router, nas, and several servers
20:24
<
clever >
i use nixos on every machine i have installed since discovering nixos
20:14
<
clever >
nixpkgs.config.packageOverrides = pkgs: { openssl = pkgs.libressl.override { fetchurl = pkgs.fetchurlBoot; }; };
20:14
<
clever >
i copied some mistakes again, lol
20:13
<
clever >
toogley: this might fix it
20:13
<
clever >
nixpkgs.config.packageOverrides = super: config: { openssl = super.libressl.override { fetchurl = pkgs.fetchurlBoot; }; };
20:13
<
clever >
toogley: yep, openssl is given a special fetchurl to prevent the issue
20:13
<
clever >
10614 fetchurl = fetchurlBoot;
20:13
<
clever >
10613 inherit (callPackages ../development/libraries/openssl {
20:12
<
clever >
toogley: curl uses openssl, and nearly everything needs curl to download its src
20:12
<
clever >
toogley: oh, i think i know why
20:11
<
clever >
toogley: can you gist the files you have?
20:09
<
clever >
toogley: oops, my example gist carried over that mistake
20:09
<
clever >
toogley: packageOverrides is a function that expects only 1 argument
19:53
<
clever >
that content only works in configuration.nix or another nixos module
19:53
<
clever >
none of that belongs in config.nix, lol
19:53
<
clever >
and your being passed pkgs on line 3, so dont ask for any params at all
19:53
<
clever >
toogley: config.nix shouldnt be asking for params like that, its not a module
18:48
<
clever >
it will only effect foo
18:48
<
clever >
but if you do foo = pkgs.foo.override { openssl = pkgs;libressl; };
18:48
<
clever >
toogley: if you do openssl = pkgs.libressl;, it will affect every single package that uses openssl
18:45
<
clever >
toogley: you could do nixpkgs.config = import /home/clever/.config/nixpkgs/config.nix; to reload the same overrides in nixos
18:42
<
clever >
toogley: but the nixpkgs inside configuration.nix, obeys the nixpkgs.config attribute in your configuration.nix
18:42
<
clever >
toogley: nixpkgs on its own, will load ~/.config/nixpkgs/config.nix for overrides
18:41
<
clever >
toogley: the whole point of packageOverrides is that it lets you alter the inputs to some packages without having to clone nixpkgs
18:31
<
clever >
[clever@amd-nixos:~]$ nix-build '<nixpkgs/nixos>' --arg configuration '{ pkgs, ... }: { services.mysql.enable = true; services.mysql.package = pkgs.mysql; }' -A config.systemd.services.mysql.runner
18:30
<
clever >
gchristensen: one minute, typing up an example...
18:29
<
clever >
gchristensen: is that the perl wrapper around systemd?
18:29
<
clever >
a fetchFromFile would have solved that
18:29
<
clever >
and every single eval took an extra 30 seconds, to re-hash it
18:29
<
clever >
i was doing data manipulation with nix, and feeding it a 400mb file with src = ./foo.tar.gz;
18:29
<
clever >
and ive ran into similar issues before
18:29
<
clever >
i dont think so
18:27
<
clever >
Myrl-saki: depends on if root ever builds and runs that variant of pocl
18:26
<
clever >
Myrl-saki: and if configuration.nix obeys those overrides, it becomes the global sudo that actually has perms
18:26
<
clever >
Myrl-saki: the packages cant sudo, but the packageOverrides can define a new version of sudo
18:26
<
clever >
seequ: the only thing stateVersion does, is adjust what version of something like postgresql you get, to make sure you dont break the on-disk state
18:25
<
clever >
Myrl-saki: i could put in a malicious packageOverride to sudo or ping, both of which have setuid root
18:24
<
clever >
seequ: you always get the version in the channel, stateVersion doesnt control what version you get
18:24
<
clever >
Mic92: what Myrl-saki said, somebody could add an extra user with wheel perms in your config files in $HOME, and next time you nixos-rebuild, they get a free user with admin
18:24
<
clever >
seequ: switching from unstable to 17.07 will probably downgrade some things
18:21
<
clever >
seequ: just change the channel with the nix-channel command, and nixos-rebuild to update it
18:21
<
clever >
seequ: you dont have to clean install to get new features
18:20
<
clever >
Myrl-saki: which mutates the defaults in the stdenv
18:20
<
clever >
Myrl-saki: when you put cmake into the buildInputs, the stdenv will source this script
18:20
<
clever >
seequ: the stateVersion must always be set to the version you originally installed with
18:19
<
clever >
seequ: changing it defeats the entire point of having it
18:19
<
clever >
seequ: it must not be bumped
18:18
<
clever >
Myrl-saki: i always enable it
18:18
<
clever >
seequ: you could even just boot it normally, nix-channel --add the right url, and nixos-rebuild switch
18:16
<
clever >
Myrl-saki: darwin or nixos?
18:16
<
clever >
Myrl-saki: yeah
18:12
<
clever >
so you have to passwd and systemctl start sshd
18:12
<
clever >
seequ: the installer has an sshd, and i think root login is enabled, but auto-start is off
17:41
<
clever >
mt_caret_: add an echo to the script?
17:37
<
clever >
so just load it with pkgsi686Linux.callPackage and it should work
17:37
<
clever >
mt_caret_: pkgsi686Linux will give you 32bit versions of everything
17:31
<
clever >
mt_caret_: is the package doing a 32bit only build, or a mixed 32/64 build?
16:27
<
clever >
chreekat: you can also just add the nix-serve thing to the binary-caches config, and it will just always use the cache
16:26
<
clever >
chreekat: i dont think ssh-substituters has a trusted variant
16:21
<
clever >
chreekat: i think it has to be configured in /etc/nix/nix.conf for all users to benefit from it
15:49
<
clever >
sondr3: but you can set a uid = 1001; in the configuration.nix to prevent that
15:48
<
clever >
sondr3: it wont even try to fix the uid, so you may lack access to your own home directory
15:48
<
clever >
sondr3: yeah
15:46
<
clever >
sondr3: it wont delete anything from /home
15:16
<
clever >
ah, i probably need to update my channel
15:15
<
clever >
not actually a .lib output
15:15
<
clever >
"/nix/store/rimh7x5nn5dzzzfppp3m6nhv2a6z206j-clang-4.0.1"
15:15
<
clever >
nix-repl> "${clang.cc.lib}"
15:14
<
clever >
error: attribute ‘lib’ missing, at (string):1:1
15:14
<
clever >
nix-repl> clang.lib
15:13
<
clever >
dtz: i dont see a lib output
03:29
<
clever >
this would roll the socat stuff directly into nix, so you just pass a flag to nix-build and it works
03:28
<
clever >
so its just a matter of then passing the -I's to nixos-rebuild
03:27
<
clever >
taohansen: you could create a systemd service that manages starting the socat, and the file from the 2nd command should persist if your not wiping /tmp on shutdown
03:25
<
clever >
taohansen: but you can give it access to an ssh-agent, which keeps the secret a secret
03:24
<
clever >
taohansen: there is no real secure way to give nixbld access to the private key, without exposing it to every single build you do
03:24
<
clever >
taohansen: one min
02:07
<
clever >
Lisanna: can you gist the nix expressions?
02:06
<
clever >
unsafeDiscardStringContext should be identical to just typing it in directly
02:05
<
clever >
if you refer to it elsewhere, anywhere in the closure, it will be checked for
02:04
<
clever >
Lisanna: can you gist the nix expression?
00:20
<
clever >
nflores: ah, putting the -H and its param in the same string probably messed with things
2018-02-20
21:56
<
clever >
ive got no idea what the original problem was, lol
21:55
<
clever >
then the changes will be compiled in from the start
21:55
<
clever >
aminechikhaoui: you can also modify the nix expressions in nixpkgs that generated all of this, then just nixos-rebuild switch and reboot
21:53
<
clever >
aminechikhaoui: it might be contacting the existing instance, and reusing the script it was given
21:53
<
clever >
aminechikhaoui: ps aux | grep udhcpc
21:52
<
clever >
aminechikhaoui: what about just adding an echo $router or just plain 'set' or 'env' to the script?
21:51
<
clever >
aminechikhaoui: did you point udhcpc at the modified version of the script?
21:42
<
clever >
aminechikhaoui: preferably after a reboot so the state has been reset
21:42
<
clever >
aminechikhaoui: copy the script to the current directory, and edit it to add "set -x", then re-run it
21:37
<
clever >
aminechikhaoui: probably the reply it got from the dhcp server
21:37
<
clever >
vitiral-lap: yeah
21:37
<
clever >
vitiral-lap: sure
21:36
<
clever >
aminechikhaoui: that script is passed to the dhcp client, which will then set the vars and run it
21:36
<
clever >
udhcpc --quit --now --script ${udhcpcScript} && hasNetwork=1
21:31
<
clever >
nflores: try downloading it with a manual curl from a normal shell, and see what happens?
21:20
<
clever >
nflores: i also suspect that the token only applies to the first url, you want to switch to -u
21:18
<
clever >
nflores: there is a flag for curl to make it follow redirects, check its man page
21:16
<
clever >
nflores: that puts your token into the nix store, and it basically becomes public, depending on what you have configured
21:15
<
clever >
infinisil: so you can pre-test a dns, before making it active
21:15
<
clever >
infinisil: the first obeys /etc/resolv.conf, the second forces it to use a certain server
21:15
<
clever >
infinisil: `dig google.com` and `dig google.com @192.168.2.1`
21:14
<
clever >
infinisil: i prefer dig for testing
21:13
<
clever >
nflores: and i think you can put a user:pass for github or also a personal access token into that
21:13
<
clever >
nflores: if you set NIX_CURL_FLAGS prior to starting a build, those will be passed to curl when it tries to download things
21:12
<
clever >
nflores: ahh, i dont think the artifacts are available over ssh, one min
21:10
<
clever >
nflores: ive done it with ssh and ssh-agent
20:59
<
clever >
infinisil: possibly, but until we know what the "right" config is, its hard to know what commands to run
20:57
<
clever >
vitiral-lap: are you able to connect from another linux distro and have it work?, gather the same command outputs, and compare them
20:55
<
clever >
vitiral-lap: so its trying to access those servers via your main router/gateway
20:55
<
clever >
vitiral-lap: it also doesnt direct it over eth0, so those arent "local"
20:55
<
clever >
vitiral-lap: oh, the routing table doesnt direct that over tun0
20:53
<
clever >
vitiral-lap: but its likely what it inserted into /etc/resolv.conf
20:53
<
clever >
vitiral-lap: the logs dont clearly say what the dns server is
20:52
<
clever >
vitiral-lap: no
20:52
<
clever >
hask_bee_3: can you run nix-instantiate --find-file nixos-14.04, and then run ls -lh on that path?