<clever>
but i always turn snapshotting off there, because then garbage collect doesnt work
<clever>
ah, snapshots on /nix would preserve nix.db, and keep it in-sync with the rest of the store
<clever>
2nd worst would be a corrupt bootloader config
<clever>
the version of nix you build something with shouldnt impact its hash
<clever>
petersjt014[m]: what exactly do you want to do?
<clever>
also, it needs a different command if you want to view the configuration.nix of a different install
<clever>
nix-env -iA nixos.nix-repl
<clever>
petersjt014[m]: nix-repl '<nixpkgs/nixos>' and then try to eval config i believe
<clever>
but the nix sandbox fixes it
<clever>
turns out the new glibc doesnt agree with the nssswitch.conf of rasbbian
<clever>
i recently fixed my armv8 build slave
<clever>
dhess: have you seen the 96 core arm servers packet.net has?
<clever>
zero firewall
<clever>
so the wan port is essentialy just a 5th lan port, until the OS boots
<clever>
there is only one critical flaw with the one i got, the switch IC defaults into all ports linked mode
<clever>
i was planning on using it as a router
<clever>
i had gone with the bpi1 because it includes a 5 port gigabit switch
<clever>
samueldr: but my PSU strugles to keep it stable, and it has yet to get into a linux kernel
<clever>
samueldr: ive used the nixpkgs u-boot on the banana pi r1
2017-11-25
<clever>
i dont think so
<clever>
changing the permissions on $HOME with chmod so that updatedb can read it
<clever>
so it can only find files outside of home
<clever>
its also possible that permissions wont let updatedb read in /home
<clever>
jmc_fr: check "ps aux | grep update" and see if its still running
<clever>
jmc_fr: it takes time to build the db
<clever>
ah, its called update-locatedb.service
<clever>
it helps if update is spelled correctly
<clever>
yeah
<clever>
jmc_fr: you can also "systemctl start updatedb.service" to force it to run
<clever>
jmc_fr: the service will run update every day at 2:15 am i believe
<clever>
manveru: also, some types support merge (lines and such), and others dont (bool, int)
<clever>
manveru: id prefer to have full AST rather then just strings, because the user may have if statements in the configuration.nix
<clever>
benley: and XAUTHORITY is always in $HOME
<clever>
benley: nixos only supports one display at :0, so you can just assume its value is always :0
<clever>
infinisil: i think part of what lets it work in nix, is that the module system can know the keys, without knowing the values, and that lets it route the request to the right module
<clever>
havent looked into that function yet
<clever>
infinisil: i dont think you can give a function its own return value as an argument
<clever>
so they get their own return value as an argument
<clever>
infinisil: basically, nix will iterate over every module (reading the imports in each), and then merge the .config and .options of each, then pass that config and options as an argument to every module
<clever>
infinisil: lazy evaluation allows for some really wonky things that id never get in another language
<clever>
gchristensen: a bigger problem is if the imports value depends on other config
<clever>
gchristensen: pkgs doesnt depend on systemPackages, so it should be safe
<clever>
gchristensen: i dont think it will cause recursion in that case
<clever>
gchristensen: is it actually giving infinite recursion the way it is now?
<clever>
but it costs about 300mb on /boot
<clever>
that lets you get a rescue env from grub at any time, so you can repair any boot problems
<clever>
aminechikhaoui: it has no effect on all of the other nix tools
<clever>
aminechikhaoui: the nixpkgs.config option is only passed to the instance of nixpkgs used within nixos-rebuild
<clever>
aminechikhaoui: and thats over in ~/.config/nixpkgs/config.nix
<clever>
aminechikhaoui: the problem is that the option has to go into config.nix, not a shell.nix
<clever>
yeah, that will re-run the script inside a shell that has those tools in $PATH
<clever>
:q!
<clever>
aminechikhaoui: that only has an impact on nixos-rebuild, it doesnt affect nix-shell, nix-build, or nix-env
<clever>
ah, my only guess is to put allowUnfree into your config.nix like the error says
<clever>
asuryawanshi: which package does it complain about?
<clever>
das-g[m]: ah, just run the app like ./result/bin/appname
<clever>
das-g[m]: depends on what kind of string its inside, can you gist the entire file?
<clever>
steveeJ: that allows gaining access to a handle to /
<clever>
steveeJ: there is something special about having access to a filehandle of an FS outside the container
<clever>
if i ever have to duplicate the install, the boot stuff is going to change anyways, no need to preserve it
<clever>
Rovanion: so everything that isnt needed to boot, goes into a file in the nixcfg git repo
<clever>
Rovanion: i mostly put the boot related stuff into configuration.nix, then add ./nixcfg/hostname.nix to the imports list
<clever>
ive also played with a custom container type using systemd-nspawn and fuse
<clever>
steveeJ: at the kernel level, there isnt much difference
<clever>
steveeJ: it may have that option, but it would be more complex to setup, docker doesnt expect the sharing, and there are security issues with just jaming your own mounts into docker
<clever>
i havent played with lxc yet
<clever>
hiroshi: docker, is more about having pre-made images (or making them) that dont depend on the host in any way, and it cant share the /nix of the host
<clever>
hiroshi: ^^^
<clever>
hyper_ch: everything under the containers attribute is declarative containers, you give it a nixos module describing the container, and nixos-rebuild will build it and launch it for you
<clever>
Rovanion: ive used that before to spawn 100 containers, 10 per host, limited mainly by how much ram the target application required
<clever>
Rovanion: nixos hosts support containers, and will automaticaly build the container and spawn it with a shared copy of the host /nix/
<clever>
Rovanion: nixpkgs also contains routines for making docker images, they usually lack full nixos, and ive gotten them down to 69mb
<clever>
Rovanion: nixos containers share the /nix directory with the host, so the data isnt duplicated
<clever>
nixos-rebuild switch
<clever>
then it will never find the output, and do a rebuild
<clever>
i always change a digit of the hash to 0, or increment a digit
<clever>
yeah
<clever>
fixed-output rules bypass the normal automatic rebuild triggers
<clever>
so nix trusts you, and uses the previous value, because you claimed it has the same hash as before
<clever>
elvishjerricco: the issue, is that nix already has an output with that name + hash, and by definition, the output is fixed to always have that hash
<clever>
elvishjerricco: you have to make the hash invalid
<clever>
just add a preFetch string to the derivation, and have builder.sh eval it
<clever>
a preFetch script might do it
<clever>
elvishjerricco: it would probably be simpler to make your own fixed-output derivation that sets $HOME and does all of those git config flags, then git clones
<clever>
i dont see any simple way to do that
<clever>
ah, fun
<clever>
elvishjerricco: what config are you trying to modify?
<clever>
just point nix-channel at a server you can see access.log on, and you can see what its doing
<clever>
yeah
<clever>
forgetful: you can also package those expressions up into a nixexprs.tar.gz and then use nix-channel on that
<clever>
forgetful: then the user can just git clone, and run nix-env -f . -i or nix-shell
<clever>
forgetful: youll want to modify the nix expression to work without <nixpkgs> How_to_fetch_Nixpkgs_with_an_empty_NIX_PATH
<clever>
forgetful: if the user has the exact same nixpkgs as hydra used (pinning it in your expresison helps)
<clever>
forgetful: depends on what you want private, if the end-user is given the full nix expression for building it, along with the sha256's of the sources, nix will just grab the build from a binary cache
<clever>
forgetful: ive never seem them work
<clever>
forgetful: you need to just eval the same expressions hydra is evaling
<clever>
forgetful: i dont think that channel hydra serves works anymore
<clever>
forgetful: and hydra already provides the same API as nix-serve