<clever>
stepcut: you may also be able to adjust ssh-serve some....
<clever>
stepcut: ah, yeah, you would need to use firewall or vpn stuff to restrict access
<clever>
stepcut: you may also want to mix nix sign-paths in also
<clever>
stepcut: this is another option, it will just create a directory suitable for http:// cache operations, throw an http-server of your choice at it, and your up-and-running
<clever>
stepcut: aha, modify the systemd service to set `NIX_SSHOPTS = "-v"`
<clever>
stepcut: checking some source...
<clever>
stepcut: nix-daemon is running under systemd, so it likely wont find your agent, you could use /root/.ssh/ssh_config to force which key to use, or just have /root/.ssh/id_rsa lack a passphrase
<clever>
ambro718: your default.nix would need to specify which nixpkgs to use
<clever>
it will also make things build much faster for them
<clever>
ambro718: and there tmp dir wont be as loaded as heavily
<clever>
ambro718: if you get them to use a binary cache service (either your own, or cachix), then they can just download a pre-built copy
<clever>
ambro718: i went over to the console, to discover there was 20gig of garbage in /tmp, and the boot waits until its all cleaned up before continuing, lol
<clever>
ambro718: related, one of my old machines had a persistant /tmp, but it cleared it on bootup, and one day after an unplanned reboot, it didnt come up right away
<clever>
ambro718: libstore/build.cc looks like the best place, change the "" to point to the option, and if the option is "", the old behaviour returns
<clever>
ambro718: you may need a PR to nix, to add an option
<clever>
ambro718: and note, you want `unset`, not `export XDG_RUNTIME_DIR=`
<clever>
ambro718: clearing that too should force it back to /tmp/
<clever>
ambro718: it will then overwrite TMPDIR, TEMPDIR, TMP and TEMP, with the choice it made
<clever>
ambro718: if TMPDIR is not set, it will use XDG_RUNTIME_DIR, if that is also not set, it will use /tmp
<clever>
pbb: the stage-1-init.sh will treat that as having gotten the wrong pw, and try again, then i think it will notice its already open and keep going?
<clever>
pbb: i think you can just `killall cryptsetup`
<clever>
pbb: one minute
<clever>
ambro718: nix will obey TMP or TMPDIR i believe
<clever>
abbec: ive not used overlays outside of nixos
<clever>
abbec: i think so, or the overlays directory
<clever>
putting it all into an overlay forces you to keep a hard record of what the trick is, and you can just nix-env -iA nixos.tiny-vim any time you want to upgrade it
<clever>
`nix-env -iA nixos.vim_configurable.customize --argstr features tiny` may work, but then you have another downside, youll forget the magic incantation, and 6 months down the road, you wont remember how to get the new tiny vim when upgrading
<clever>
and unused args are silently ignored
<clever>
vim_configurable is not a function, so it wont try to call it with any arguments
<clever>
and then, for every attr in the -A foo.bar.baz, it will repeat that again
<clever>
abbec: when nix loads a given file, it will check if the top-level value was a function (the root nixpkgs function in this case), and call it with any args it can accept
<clever>
karetsu: systemd runs services with a different PATH
<clever>
karetsu: can you pastebin your home-manager config?
<clever>
karetsu: and your running that directly in a shell?, what does `type systemctl` say?
<clever>
elgoosy: nixos-rebuild always uses the channels on root, and you typically only need the user channels if you lack root or want to avoid sudo more
<clever>
karetsu: what command are you running, to cause the error message?
<clever>
elgoosy: compare `nix-channel --list` and `sudo nix-channel --list`
<clever>
elgoosy: did you run --add with or without sudo?
<clever>
elgoosy: looks like everything is working as it should
<clever>
elgoosy: sudo nix-channel --list
<clever>
tilpner: i think it just always obeys $TMPDIR, and users have a different value then services
2019-06-18
<clever>
or `with import ./common.nix; let stuff= things; in stuff`
<clever>
mac10688: in a let block, i would do `let stuff = import ./common.nix; things = stuff.things; in things` for ex
<clever>
andi-: if you can do it in c, you can also use IFD to cheat like i did
<clever>
andi-: i think its in there, if i did it at all
<clever>
2019-06-18 05:03:41 < clever> NYXT: you want to use disabledModules to remove the current plex module, and then use imports to add in the new one
<clever>
sudo cant fix a lack of +x
<clever>
but its not been +x'd so you lack permission to run it
<clever>
inquisitiv3: so your attempting to run base.lst
<clever>
inquisitiv3: you dont have a cat at the start
<clever>
inquisitiv3: what is it having permission errors on?
<clever>
capisce: ah, different from the problems i had
<clever>
karetsu: you can also do `chmod u+w` to only add write to user, and leave all other bits as-is
<clever>
capisce: anything 32bit or nfs at play?
<clever>
karetsu: that will find every directory, print them with \0 seperators, then grab chunks of them and pass it to chmod
<clever>
karetsu: nix-channel --list, nix-channel --add, nix-channel --remove, and every user has his own set of channels, you typically inherit from root's
<clever>
Synthetica: builtins.toFile "name?" (builtins.toJSON foo) or pkgs.writeText
<clever>
drakonis: nixpkgs-unstable did update, because it doesnt test grub, and then the nixpkgs on nixos guys broke grub
<clever>
samueldr: that would do it
<clever>
nixos-unstable refused to update, and protected most users
<clever>
a bug got in that corrupted grub.cfg
<clever>
about a year ago, there was a wave of people who ran nixpkgs-unstable on nixos (not master, but still lacked nixos tests)
<clever>
thats how you brick machines :P
<clever>
it takes a while for that to hit your channel
<clever>
it updated systemd from 241.something to 242
<clever>
drakonis: check the git history for the last file i pasted
<clever>
nixos/modules/system/activation/switch-to-configuration.pl:incompatible with the current configuration. The new configuration
<clever>
drakonis: major changes to systemd?
<clever>
Ankhers: just use normal attrs then, erlang = erlangR21;
<clever>
Ankhers: the difference, is that <nixpkgs>/.../foo.nix (or a variant of it), will search for <nixpkgs> in $NIX_PATH (even if its empty), while <nixpkgs/../foo.nix> will search for a version of nixpkgs that definitely has a foo.nix
<clever>
gchristensen: i was cleaning up a bucket with ~200gig of data in it last week, it took 3 days just to delete every item in the bucket
<clever>
yorick: on nix, ldconfig should just be ignored and never ran
<clever>
lol
<clever>
joepie91[m]: i think i heard it was at 80tb?
<clever>
,cache joepie91[m]
<clever>
hardware.enableAllFirmware and hardware.enableRedistributableFirmware will also install firmwareLinuxNonfree for you
<clever>
rndd[m]: any firmware you do install, must be put into the hardware.firmware option
<clever>
some serial port programs have a hotkey to send a break code over the serial port
<clever>
immae: and a break signal on a serial port, is i think 10 bits of low, when the normal pattern is 1 low for the start bit, 8 data bits, and 1 high for the stop bit
<clever>
immae: so <break>o will just cut power to the whole system
<clever>
immae: related, if you send a break signal over the serial port, you can follow it with one of those magic letters
<clever>
immae: ack!
<clever>
perhaps: ( echo l ; echo t ; echo w) > /proc/sysrq-trigger
<clever>
so you would need to issue multiple write() syscalls, one byte each
<clever>
it allocates a `char c`, and then reads that from userland
<clever>
immae: but also, line 1103, i think its only reading a single byte from the string being written
<clever>
immae: you must check dmesg to see the result of everything
<clever>
immae: this creates the sysrq-trigger file, and routes all writes to the function at the start
<clever>
pbb: ah, the machine is responding enough to run dmesg?
<clever>
so i can just turn the monitor on to see what blew up
<clever>
pbb: and because of that, any errors the kernel prints to the console, are visible, even after the kernel locks up solid
<clever>
pbb: this causes mingetty to print an ansii escape code on startup, which disables power-saving in the gpu, so the monitor output is never disabled
<clever>
li_matrix: and then people can take your stuff and setOfCrates.overrideScope' (self: super: { overlays })
<clever>
li_matrix: the next trick, is that you can mix makeScope and newScope together with your `self: { stuff }` to make a set that contains an .overrideScope'