<clever>
lucus216: simplest is to just not define the option, anything not in options= will be an error
<clever>
pie__: yeah
<clever>
pie__: ive read similar things about nuclear bomb computers, how they want to spread the data around the physical chip, so even if you recover a 1x1mm fragment of the silicon, it wont be of use in recovering keys, lol
<clever>
pie__: something i have noticed they do, is that the key slot material is striped, i think so that if any one block range is recovered, you cant actually make use of it
<clever>
sometimes, its simpler to just treat it like windows
<clever>
samueldr: time to reverse engineer hydra-in-a-bag!
<clever>
but somebody eventually fixed that bug, which broke synergy
<clever>
any user on the machine could connect to :0 and do anything
<clever>
originally, it "just worked" because somebody had accidentally disabled xauth cookies, since basically day 1 of nixos having xorg support, lol
<clever>
one thing i should look into, to see if its ever been fixed, is the synergy services
<clever>
ornx: you probably also want to use `nix-build` when testing, not nix-env
2019-08-11
<clever>
selfsymmetric-mu: you can also `nix-store --query --roots /nix/store/foo` to see what is rooting it, and `nix-store --delete /nix/store/foo` to just remove it
<clever>
exarkun: you imported nixpkgs without setting overlays= so it loads the overlays from $HOME
<clever>
exarkun: line 17 causes nixpkgs.overlays to never work
<clever>
exarkun: oh wait
<clever>
exarkun: it might be the bootstrap coreutils, which is at a different attrpath, not sure where
<clever>
exarkun: nix.package must be the result of building it, but fetchTarball returns a directory, in this case, of nixpkgs which isnt a even nix (the package manager)
<clever>
slabity: after a full power cycle, the card returned from beyond, and never did it again
<clever>
slabity: just once, the ethernet in my laptop failed hard, dmesg spewed errors, and after a soft reboot, lspci claimed the device didnt even exist
<clever>
slabity: double-check that the pci device is seated properly?
<clever>
slabity: what about lspci?
<clever>
exarkun: that might be a bug in the argv0 handling of the qemu stuff, i would just disable the tests
<clever>
petercommand: the main difference, is the lack of sandboxing, its not able to have conflicting versions co-exist, so rollbacks are missing, and no official binary cache, so you must build everything from source
<clever>
petercommand: similar, its just a giant heap of shell scripts that build everything, and define what the deps are
<clever>
prior to nixos, i ran gentoo
<clever>
sphalerite: reminds me of the old days when people joined christian channels, then made the bot quote a verse that had a curse word in it, causing the bot to get auto-banned :P
<clever>
DigitalKiwi: in my favor, it was an apt question, so it applied to either distro
<clever>
DigitalKiwi: i once got banned from #debian for asking ubuntu questions
<clever>
Athas: i think its so when 2 different builds get into the env, it can uniquely identify which is which
<clever>
Athas: ghc does, to give each build a unique id
<clever>
Athas: it shares the entropy with the host currently
<clever>
Athas: yeah, parallel builds have caused issues before, which is why parallelish is off by default
<clever>
Athas: some of the manual's in nixos used rng to generate links in the html, to make the links unique within the document
<clever>
Athas: its basically spinning up a dynamicly created container for every build
<clever>
simpson: the only time ive seen runtime detecting be a problem, was on an avr, where the cycle count of an `if` statement in an irq was too much, lol
<clever>
simpson: mplayer solves that by having runtime cpu detection, it just builds multiple variants of key functions, and selects the right one at runtime
<clever>
infinisil: as long as no funny cpuid stuff is going on
<clever>
dminuoso: ive not re-read them in a while
<clever>
dminuoso: probably
<clever>
dminuoso: yeah
<clever>
infinisil: nix's purity doesnt prove that the binary cache isnt malicious, bit-per-bit reproducible prooves that the binary cache hasnt done anything nasty
<clever>
nexgen: nix also has an option to repeat the same build N times, and fail if they didnt produce bit-identical results
<clever>
nexgen: https://r13y.com has been focusing on getting that for all nix packages
<clever>
imdoor: the rev is d567c486ca5 and tofu the sha256
<clever>
dminuoso: it might work better in systemPackages
<clever>
dminuoso: you probably want `nix-shell -p ncurses6
<clever>
dminuoso: files from .dev are usually ignored by nix-env
<clever>
nexgen: the source for electron, once you run gclient, is over 30gig, so iterating on a proper package takes hours per attempt
<clever>
nexgen: some things like electron are still blob based, even though they are open source
<clever>
nexgen: thats also just the binary blog being patched
<clever>
no need to compute a delta from the previous
<clever>
nexgen: so if a sub-step of the build has already been done before, it gets reused
<clever>
nexgen: basically, you just define how to build the final setup, and nix will use the hash of those directions to see if something is already built
<clever>
maralorn: `sudo -i` and `unset SSH_AUTH_SOCK`
<clever>
nexgen: yep
<clever>
maralorn: can you ssh into myhost as root?
<clever>
steam works just fine on nixos, and thats a giant mess of closed-source everything
<clever>
this video points out a number of "quirks" with JS
<clever>
moretea's fork is the one ive had experience with
<clever>
tokudan: have you tried yarn2nix?
2019-08-10
<clever>
at boot time, its binary
<clever>
device tree blob, an arm way of configuring things
<clever>
and all merging is done by nix before creating the main dtb, rather then using dt overlays
<clever>
you could even do something like having a services.foo.enable auto-config the DTB's for you
<clever>
Fahrradkette: if you can define all of that in device tree, then it should be possible to write a nixos module to configure it and enforce rules, then generate a DTB based on a config file
<clever>
that would explain how its aboe to restore certain elements of the state
<clever>
ahh, someone else linked crui to me recently
<clever>
pie_: thats a staticly linked c binary, using the namespace api's, to mount a nix store to /nix/
<clever>
pie_: have you seen nix-bundle and nix-user-chroot?
<clever>
> let foo = { a = 42; }; in foo.b or "not found"
<clever>
> let foo = { a = 42; }; in foo ? a
<clever>
> let foo = { a = 42; } in foo ? a
<clever>
> pkgs.hello.meta.position
<clever>
Orbstheorem: id say go ahead, its even used by things like
<clever>
Orbstheorem: ^^
<clever>
> builtins.unsafeGetAttrPos "hello" pkgs
2019-08-09
<clever>
pie_: pivot_root just changes what / is, it wont remap any existing open ahndles
<clever>
pie_: something something open handles pointing to the wrong fs and things still being written to :P
<clever>
pie_: when you literally swap the root out from under its feet and nothing is where it was
<clever>
pie_: systemd would get very upset, better to just reboot, lol
<clever>
pie_: a fuse app being ran in the initrd, to create the root-to-be
<clever>
pie_: thats how things like root on fuse function