<clever>
you need to delete and remake the partitions with a better offset
<clever>
which just ruins performance
<clever>
c0c0: then every 4kb write, involves reading 8kb, modifying a 4kb substring, then writing 8kb back out
<clever>
c0c0: if a filesystem is using 4kb blocks, and your physical drive is also using 4kb blocks, but your partition starts at an offset line 5kb in
<clever>
,-A c0c0
2019-09-22
<clever>
jD91mZM2: you can probably `nix-build` the manual, though i'm not sure of the attr path
<clever>
jD91mZM2: security is also another reason, since it can isolate `ps aux` output and such, but the `/nix` is still shared between host and guest, so be careful with secrest in derivations
<clever>
in one recent case, even if the service (buildkite-agent) supports multiple instances, the scripts that run within it expect exclusive access to /build
<clever>
jD91mZM2: one option is to be able to run services like mysql, that currently dont support multiple instances (in the nixos module as it is now), and to spawn several of them
<clever>
emily: from what ive heard, zfs can be configured to scrub at regular intervals (read all data, and check checksums), and then email you if it detects corruption
<clever>
thats why i never had that specific problem
<clever>
cinimod``: i can also confirm, the systemd service i used cuda in, always runs as root
<clever>
no example to compare against
<clever>
which is why i still havent gotten opencl to work on amd
<clever>
it helps to have access to a nixos machine that already has cuda working
<clever>
yep
<clever>
reboot, save the output of lsmod, run it as root, save the output of lsmod again
<clever>
does the output differ?
<clever>
without root, try to strace python, and see what fails with EPERM
<clever>
sounds like permission issues
<clever>
`sudo -i` gets a shell
<clever>
so you want to sudo before you nix-shell
<clever>
cinimod``: sudo may undo key env vars like LD_LIBRARY_PATH
<clever>
yep, that part works
<clever>
cinimod``: what happens if you run the tensorflow stuff as root?
<clever>
cinimod``: what happens if you run `nvidia-smi` ?
<clever>
2019-09-22 08:53:07.507573: I tensorflow/stream_executor/platform/default/dso_loader.cc:53] Could not dlopen library 'libcuda.so.1'; dlerror: libcuda.so.1: cannot open shared object file: No such file or directory
<clever>
cinimod``: it must be set like this, for things to find the gl/cuda libs
<clever>
Huw: i would start by adding `noauto` to the options, and then see what happens if you try to manually `mount -v /mnt/d/`
<clever>
Huw: i would start by adding `noauto` to the options, and then see what happens if you try to manually `mount -v /mnt/d/`
<clever>
cinimod``: the nix needs to be on the host to see kvm, and you need permission to access kvm, in your case, to be in the kvm group
<clever>
cinimod``: a vm usually wont have kvm working
<clever>
justsomeguy: if your on nixos, its best to use documentation.man.enable = true;
<clever>
cinimod``: intel or amd cpu?
<clever>
cinimod``: does /dev/kvm exist?
<clever>
werner291: `ps aux | grep X`, find the config file its using, and read that, is the config you set present?
2019-09-20
<clever>
__red__: channels are also global and per-user, and you can add multiple channels if you want to use things from another channel
<clever>
__red__: overlays can be either system wide or per-user
<clever>
__red__: nixpkgs also supports overlays, which can change and add packages
<clever>
`nix-env -q` will list its contents
<clever>
any time you run `nix-env -i` or `nix-env -e`, it will modify ~/.nix-profile/manifest.nix and update the profile
<clever>
__red__: manifest.nix and systemPackages basically have the same role as world
<clever>
__red__: at one time, nixos.com was nsfw, but the domain has since expired
<clever>
__monty__: i'm guessing it was made as small as possible, and its supposed to resize itself on first boot, but maybe it was just a little bit too small
<clever>
cinimod`: this will load azure-mkimage.nix and pass it a nixpgs and rev, you could add a diskSize there, or just modify the default
<clever>
toString behave very differently from treating it as a string
<clever>
> "${./.}"
<clever>
> toString ./.
<clever>
mishac: is the dns server configured in /etc/resolv.conf ?
2019-09-19
<clever>
Ariakenom_: its more about the difference, between the old and new config
<clever>
Ariakenom_: if mutableUsers = false; i think you just use password/passwordHash instead, not entirely sure, i just always leave it mutable
<clever>
Ariakenom_: if mutableUsers = true; then the initial password only applies when first creating the user, and wont have any future effect
<clever>
and find out what you did wrong to reset the pw to default
<clever>
if you had to use hunter2 to login, change it asap, and review the ssh logs
<clever>
and make a note to fix it asap :P
<clever>
and for more automated things, where ssh isnt public (or is secure initially), you can also use users.extraUsers.clever.initialPassword = "hunter2";
<clever>
symphorien: yeah, but these are all single-user machines
<clever>
hyperfekt: thats why its in a passwords.nix file, that is never put into git
<clever>
Zer0xp: does /dev/kvm exist now? what about `lsmod | grep kvm` ?
<clever>
Zer0xp: what does `sudo modprobe -v kvm_intel` say?
<clever>
Zer0xp: intel or amd cpu?
<clever>
Zer0xp: kvm should just work out of the box, does /dev/kvm exist?
<clever>
Ariakenom: the main things you want to pay attention to, is to get the bootloader, fileSystems., and network config right, then you can incrementally finish everything else
<clever>
Ariakenom: and you can still nixos-rebuild --rollback to undo it
<clever>
Ariakenom: it will just replace the currently running os, but it wont touch configuration.nix
<clever>
nixos cant touch the version in nix-env, so that version is lagging behind and causing problems
<clever>
you need to do `nix-env -e nix`
<clever>
you have 2 copies of nix installed, on your user, and on nixos
<clever>
contrun[m]: what does `type nix` return?
<clever>
it looks like it detects failure to make a namespace (due to debian sillyness) and then turns off the sandbox
<clever>
peti: but that --argstr would be passed to nixos/default.nix, not configuration.nix
<clever>
peti: i checked the source in the above, and it looks like there is no way for you to access that, and the vars that do contain the value arent exported
<clever>
sb0: the official hydra.nixos.org has also disabled that perl code, since it now uploads everything to S3 and is configured to not act as a cache
<clever>
sb0: somebody forgot to update the perl code
<clever>
sb0: but store-uri is used by the c++ code, when the queue-runner is copying artifacts into whatever the store-uri is
<clever>
sb0: ive also looked into the source, binary_cache_secret_key_file is used by the perl code, when hydra itself as acting as a binary cache (over http)