<clever>
eyJhb: do you have any weird things in your fileSystems. config?
<clever>
eyJhb: yeah, they should perform identially
<clever>
i'm runnign nixos-unstable
<clever>
and if you logout from everything, it will destroy it
<clever>
eyJhb: that unit is responsible for creating this tmpfs, if you login via any method (graphical, or ssh)
<clever>
tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=3284088k,mode=700,uid=1000,gid=100)
<clever>
eyJhb: yep
<clever>
user-runtime-dir@1000.service loaded active exited /run/user/1000 mount wrapper
<clever>
eyJhb: i use slim, and havent had any problems, despite slim being "deprecated"
<clever>
ah, its user-runtime-dir, thats why i didnt see user-dir on my box
<clever>
eyJhb: i dont see a user-dir service on my box
<clever>
eyJhb: then you likely just need to set the right restart conditions on the service
<clever>
eyJhb: does systemd register it as failed in `systemctl status`? you could change the restart conditions to have systemd itself restart on failure
<clever>
so if you use 1 passphrase on both the zfs and swap, it just unlocks both at once
<clever>
but nixos has recently gained the ability to temporarily save your passphrase to an env var, and use it on all disks
<clever>
and i didnt like that, so my zfs is on lvm (for swap), and lvm is on luks
<clever>
previously, nixos required some fairly ugly hacks (luks key for swap+root on a 3rd partition, that is luks'd with a passphrase)
<clever>
lol
<clever>
i try to match the pool name and hostname up
<clever>
only in example commands :P
<clever>
just `zpool add tank cache /dev/nvme1n0p1` and your done
<clever>
but under linux, its just a plain old nvme device
<clever>
ar1a: yep
<clever>
the drivers just refuse to work in such a situation
<clever>
so you cant harm performance, and then claim optane modules make your system slower
<clever>
basically, it will only work, if you can afford the overhead of a cache
<clever>
but, that special sauce, is also locked to certain intel CPU's
<clever>
due to a lack of zfs and cache-device support in windows, they have custom stuff that will add a caching layer to ntfs
<clever>
the optane drivers on windows, are just plain whack though
<clever>
the nas, has an optane module, which uses the nvme protocol, but is supposed to be even faster
<clever>
nvme0n1 259:0 0 13.4G 0 disk
<clever>
and the desktop
<clever>
nvme0n1 259:0 0 477G 0 disk
<clever>
ar1a: that would be my main laptop storage
<clever>
nvme0n1 259:0 0 465.8G 0 disk
<clever>
i was surprised how easily skyrim just worked
<clever>
and for many, it wont even start
<clever>
and then for others, its almost unplayable
<clever>
proton works great for some games, practically seamless
<clever>
ajs124: there is also an flock bug when dealing with nfs
<clever>
lol
<clever>
i have so much free space, that steam overflows an int, and thinks i have 0 bytes free!
<clever>
ZFS, ~8tb total size
<clever>
dont trust the avail, i had to set a quota due to steam bugs
<clever>
nas:/nas 3.6T 3.6T 84G 98% /nas
<clever>
Filesystem Size Used Avail Use% Mounted on
<clever>
i havent subscribed to pass either
<clever>
i suspect it may be due to them using things like libmpv for playback
<clever>
and ping is trying to load the libnss_mdns library, to add .local support to itself
<clever>
openat(AT_FDCWD, "/run/opengl-driver/lib/libnss_mdns.so.2", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
<clever>
ar1a: hmmm, if i stop nscd, then ping fails much faster...
<clever>
it doesnt show any .local's, but it can see the laptop
<clever>
+ enp3s0 IPv4 system76 [a0:af:bd:82:39:0d] _workstation._tcp local
<clever>
+ enp3s0 IPv4 system76 _ssh._tcp local
<clever>
ar1a: `avahi-browse -at` can find system76, so avahi itself is working
<clever>
ar1a: given what youve said, i'm not sure any of my machines have working .local, since i rarely reboot and have switched on nearly all of them, let me see if i can fix it locally....
<clever>
nimblepoultry: <nixpkgs/nixos/modules/profiles/hardened.nix> or (pkgs.path + "/nixos/modules/profiles/hardened.nix")
<clever>
ar1a: looks like mine is also broken, done many switch's
<clever>
ping: system76.local: System error
<clever>
ar1a: what about nscd.service?
<clever>
ar1a: does it recover if you manually restart avahi.service in systemd?
<clever>
ar1a: the major difference, is that nixos-unstable wont update, if things like grub are broken, so it is far less likely to brick the entire machine
<clever>
ar1a: its not really a downgrade, nixpkgs-unstable and nixos-unstable both follow master, and there is only a 2 hour difference between the versions
<clever>
ar1a: just re-run nix-channel --add, with the name set to nixos
<clever>
ar1a: if you want the nixos unstable channel, then you must use nixos-unstable
<clever>
ar1a: it is not safe to run nixos from the nixpkgs channels, and can potentially brick the machine
<clever>
ar1a: what does `sudo nix-channel --list` report?
<clever>
slack1256: if you nix-channel --update all the machines at the same time, then they will usually match up, you could also use things like nixops to manage things more centrally
<clever>
slack1256: nix-serve just shares whatever is currently in /nix/store/, and doesnt really care about nixpkgs versions
<clever>
may need to update the package to use ncurses
<clever>
:S
<clever>
,locate libcurses.so
<clever>
DanC: ahh
<clever>
DanC: opam using the ld from $PATH or its own ld?
<clever>
DanC: did you `-p ncurses` ?
<clever>
-rw-r--r-- 1 root root 50 Mar 17 2017 /etc/nix/signing.pub
<clever>
-rw------- 1 root root 94 Mar 17 2017 /etc/nix/signing.sec
<clever>
slack1256: i just stick the keys into /etc/nix/
<clever>
mek42_laptop: at lower levels, some FS's can corrupt some storepaths, leaving random (recently edited) files truncated, `nix-store --verify --check-contents` will find that
<clever>
mek42_laptop: at the top-level, none of the changes will happen, the entire nix-env operation is atomic
<clever>
DigitalKiwi: another package appears to be doing a --replace, to just delete that dependency
<clever>
infinisil: the whole point of the uid-map, is that it keeps them static for you, so you dont have to set things in configuration.nix
<clever>
infinisil: if you had assigned that from the first deployment, it would always have that uid, and the problem wouldnt exist
<clever>
infinisil: update-users-groups.pl would need to be updated, to support forcing the uid change
<clever>
infinisil: which means recursively searching every mounted FS
<clever>
infinisil: the problem, is that you must find every file owned by that user, and fix the uid
<clever>
and its only a one-time thing, for when the uid defined in the nixos module is changed
<clever>
infinisil: the uid-map file sovles that, by remembering the uid even if you delete a user
<clever>
infinisil: in the past, nixos would forget the uid when you delete a user from the cfg, and it may wind up with a different uid when you re-enable, causing similar breakage
<clever>
infinisil: i would just do the standard linux solution, manually edit /etc/passwd to sync it over, manually chown the home dir, and then add a nixos twist on the end, fix /var/lib/nixos/uid-map
<clever>
infinisil: thats to prevent the horid mess that happens when the uid changes, and the files arent chown'd over
<clever>
yokyolu: i think hackage2nix turns a hackage snapshot into a haskellPackages, but callHackage lets you just directly load a given version of a given package
<clever>
DigitalKiwi: looks like python is trying to download dependencies at build-time, you may need to supply it with more buildInputs
<clever>
DigitalKiwi: what error did it fail with?
<clever>
DigitalKiwi: nothing at a glance, does it build and run?
<clever>
slack1256: if you just want to see if it builds, use nix-build
<clever>
slack1256: why are you using nix-env to test it?
<clever>
slack1256: what are you trying to do exactly?
<clever>
slack1256: so you need to drop the nixos. prefix
<clever>
slack1256: but when using -f default.nix, it has no channels loaded
<clever>
slack1256: the nixos. in -iA, refers to a channel called nixos
<clever>
DigitalKiwi: 90% of the time, it can just go into buildInputs, propagated is mainly only used in python and some other special setups
<clever>
ah, then youll need to add that to package.json
<clever>
bsima: did you set a name when calling it?
<clever>
bsima: gulp is a build-tool that expects node_modules to already be setup, so you need npm (or yarn) to create node_modules
<clever>
that step needs network, but you can then add yarn.lock to the git repo
<clever>
bsima: if you run `yarn` without any args, it will create a yarn.lock
<clever>
thomasd: ah, then youll want something more like `env | grep --color julia`
<clever>
thomasd: yeah, you can `nix-shell default.nix -A parallel-julia.env` and then `ghc-pkg list`
<clever>
thomasd: your original msg says 1.0.3 is the worng one, so which derivation is using itt?
<clever>
thomasd: yeah, or its name, from the .drv it started building
<clever>
thomasd: which derivation is getting a 1.0.3 of julia?
<clever>
thomasd: can you pastebin your current nix?
2019-02-20
<clever>
srk: i started from the wrong end, i learned the c code within the ghc rts, before learning the language, lol
<clever>
reallymemorable: so i had to deal with files getting corrupt, and restarting over&over for days
<clever>
reallymemorable: the crazy thing i did, that really hammered LFS in, was trying to install it on a laptop with a failing harddrive
<clever>
reallymemorable: ive been using linux since ~2005, and i learned the most when i installed http://www.linuxfromscratch.org/
<clever>
and the ssh-agent also has to remain running
<clever>
the socat is required for the nixbld users to talk to ssh-agent
<clever>
yeah
<clever>
only time ive passed thru NYC was for connecting flights
<clever>
:D
<clever>
UserKnownHostsFile /dev/null
<clever>
StrictHostKeyChecking=no
<clever>
reallymemorable: add these 2 lines to the /tmp/ssh-config
<clever>
reallymemorable: yeah
<clever>
reallymemorable: try switching back to ssh-config-file=/tmp/ssh-config, and also add nix.sandboxPaths = [ "/tmp/ssh-config" ]; to the configuration.nix, and do another nixos-rebuild
<clever>
,libraries cthachuk
<clever>
nope
<clever>
reallymemorable: try setting nix.useSandbox = false; in the host configuration.nix, and nixos-rebuild switch to apply it
<clever>
reallymemorable: what path is it showing in the error?
<clever>
so its not using the new path
<clever>
reallymemorable: you have ssh-config-file= in there twice
<clever>
reallymemorable: with the new path?
<clever>
yeah
<clever>
yeah, make that ssh-config-file=/nix/store/something
<clever>
and edit it before you run that cmd
<clever>
reallymemorable: echo the current value, then just copy/paste it to a new `export NIX_PATH=....`
<clever>
the agent handles that
<clever>
they shouldnt have access to the keys
<clever>
reallymemorable: try `nix-store --add-fixed sha256 /tmp/ssh-config`, and then replace the /tmp/ssh-config in $NIX_PATH with the path it returned
<clever>
reallymemorable: that looks like a different error, its not complaining about ssh-auth-sock
<clever>
reallymemorable: can you pastebin the whole output on that terminal, including the error msg?