<clever>
hmmm, partition table looks a little strange, but if its already the one in the iso, its probably good
<clever>
yep, looks just fine, try booting that now
<clever>
and fdisk?
<clever>
once the dd is done, double-check it with fdisk -l /dev/sdc
<clever>
yeah, that is a disk
<clever>
oh, and also, what does "ls -l /dev/sdc" say?
<clever>
and try running sync
<clever>
that might be the write cache cheating, check the activity light
<clever>
what exactly did it output when ran?
<clever>
fresheyeball: are you sure its the right sdX?
<clever>
fresheyeball: no, that generaly means that no card is in the card reader
<clever>
sure
<clever>
and the ticket says that the label on the disk image must be set to NIXOS_ISO, which the iso already has
<clever>
the iso is already a valid usb disk image, it doesnt need any special tools
<clever>
try using just dd
<clever>
fresheyeball: how did you make the usb stick?, you should be able to just dd the iso to sdf
2017-04-01
<clever>
Svarog: i dont think it records it anywhere, but for a given nix expression, it will always give the same result
<clever>
Svarog: for systemPackages, i think its whichever came first, for nix-env, its a fatal error and you must set a priority
<clever>
Svarog: you would need to run it on the derivation that /run/current-system/sw points to, to get the collisions for the current environment.systemPackages
<clever>
Svarog: that will show the build log for foo, and if it was something like system-path, the collisions within
<clever>
Svarog: run nix-store -l /nix/store/foo
<clever>
ndowens08: yeah
<clever>
ndowens08: nix-shell -p nixUnstable
<clever>
try running file on it, and check uname -a
<clever>
cant think of anything else to check right now
<clever>
neeasade: so this directory exists?
<clever>
[clever@amd-nixos:~]$ ls /run/opengl-driver-32
<clever>
alphor: and preStart just automaticaly gets written to a bash script, whose path is put into ExecStartPre
<clever>
alphor: i believe ExecStartPre must start with an absolute path, and can only contain a single command
<clever>
Drakonis: and for that, clangStdenv.mkDerivation
2017-03-31
<clever>
exarkun: as long as the db.sqlite can downgrade cleanly
<clever>
exarkun: you could just change the channel afterwards and nix-env -iA nixpkgs.nix to install the older nix
<clever>
pmahoney: simply adding cmake to the buildInputs causes this script to get sourced, which will mutate how the stdenv behaves, causing it to run cmake instead of ./configure
<clever>
pmahoney: about the only way to improve it, is to modify librsvg to store the path in a variable within $out/nix-support/setup-hook.sh, which will get sourced by anything with librsvg in buildInputs
<clever>
pmahoney: and thats relatively expensive, and forces thing to build in a weird order
<clever>
pmahoney: i suspect thats also doing import from derivation, so it has to download (or build) librsvg before it can finish the nix eval
<clever>
This is caused by assignments to the top-level attributes `config' or `options'."
<clever>
alphor: remove the word config.
<clever>
can you throw it in a gist along with the error?
<clever>
can you gist the module that is causing the fault?
<clever>
all modules must have one of those attributes, and nothing else
<clever>
i think in the context of the linked line, that is just part of the api of modules
<clever>
dtzWill: then you can repartition it
<clever>
dtzWill: you need to "vgchange -a n" to close all LVM devices
<clever>
ericnoan: that allows unpatched games to run
<clever>
ericnoan: steam uses a FHS chroot to simulate a system with /usr/lib
<clever>
pi3r: in other setups, where S3 isnt enabled, that UI does work
<clever>
pi3r: all data is now stored on the binary cache
<clever>
dtzWill: ah :)
<clever>
Dezgeg: but part of the goal of kexec is to be able to umount /
<clever>
Dezgeg: most pid1's already have the ability to re-execute /bin/init or similiar, for upgrading
<clever>
dtzWill: i have also been considering making the above a nixos option, so you can basicaly boot the installer from grub if you ever break the system
<clever>
dtzWill: then just reboot and pick it from grub
<clever>
dtzWill: you can also copy the kernel+initrd to /boot and add a grub.conf entry for it
<clever>
dtzWill: i recently helped somebody else in a very similiar situation, and the only issue was that kexec doesnt work within a xen dom0
<clever>
disasm: ah yeah, all of the service@foo things in systemd lack auto-restart
<clever>
dtzWill: so it will restore control to the previous os
<clever>
dtzWill: correct, and the auto-reboot timer will cause it to self-reboot at the end of the hour
<clever>
dtzWill: just remember to put an ssh key in the right spot and to stop the autoreboot timer in systemd
<clever>
disasm: i am able to ssh into the guest from the host
<clever>
disasm: yeah
<clever>
dtzWill: i believe that is how nixops handles all of the pre-generated stuff on cloud machines
<clever>
dtzWill: using LABEL=root for things can simplify that last part
<clever>
dtzWill: and keep in mind, you need to correctly specify all of the fileSystem. stuff on the central box, so the builds it pushes out are still able to boot
<clever>
dtzWill: i have seen somebody recently run nixos-rebuild by mistake, and it reverted the entire machine back to a fresh install
<clever>
dtzWill: and one tip i would give is to delete the configuration.nix once nixops takes over
<clever>
dtzWill: oops, wrong d name
<clever>
disasm: should be, ive heard that if you set the targetEnv = "none"; it will just nix-copy-closure and activate it
<clever>
erictapen: activation scripts are ran any time a nixos build is activated (on boot, and after rebuild switch), and they are also responsible for creating users
<clever>
erictapen: system.activationScripts = ''mkdir and chmod it'';
<clever>
erictapen: you will need an activation script that changes that
<clever>
eacameron: the entire users option tree goes into a json file that goes at ${spec}, and the perl script manages mutating /etc/passwd correctly
<clever>
eacameron: this line of bash will get ran on bootup, and after a nixos-rebuild switch (and when nixops does a deploy)
<clever>
eacameron: the 2nd option would probably be better for users, no visible change in how things work, and the problem goes away
<clever>
eacameron: my own fix has just been to always set a uid, but modifying the code to have more state (a history of name+uid pairs) would also solve things without forcing users to pick a uid
<clever>
just serving https is trivial with nginx and acme
<clever>
eacameron: in my case, i'm doing ssl requests within the php login code, to query other remote servers
<clever>
eacameron: i think i had to add this to php.ini to get ssl to work
<clever>
eacameron: but as far as i know, the module paths have to be configured in php.ini, and i have to customize php.ini for other things to work, and now nix needs a way to merge those customizations
<clever>
then you can swap the entire phpPackages out, and it wont mix up the versions
<clever>
mojjo: no, buildCommand handles the stdenv for you
<clever>
mojjo: when buildCommand is used, the build will fail if any command returns non-zero, but you loose that feature if you use builder
<clever>
mojjo: try switching it from builder to buildCommand and see if it does something different
<clever>
mojjo: you also need to copy or symlink html files into the $out directory
<clever>
unlmtd[m]: nix-env -iA nixos.my_nvim
<clever>
unlmtd[m]: you want -iA
<clever>
mojjo: is this on nixos or another distro?
<clever>
mojjo: i think the problem is that its pointing to a different <nixpkgs> so some defaults changed
<clever>
mojjo: you probably just want to switch it to pkgs.runCommand "my" { jars = ... ... } ''bash script here''
<clever>
mojjo: also, the version on line 16 does absolutely nothing
<clever>
mojjo: you should almost always use buildCommand, rather then just builder
<clever>
filyforasec: nix-env -e program
<clever>
mojjo: can you gist my.nix?
<clever>
mojjo: sounds like the script inside my.nix didnt mkdir $out, so you need to look further up in the log
<clever>
mojjo: and what error does it fail with?
<clever>
mojjo: can you gist the file your putting that into?
<clever>
LnL: and nixos also mounts /nix/store read-only, so it cant even be written to by root!
2017-03-27
<clever>
disasm: and of course, the rootfs for the container must be mounted to the right spot
<clever>
RequiresMountsFor=/var/lib/containers/%i
<clever>
disasm: ahh, and systemd is told to use the .conf to initialize env variables, before it runs any (pre)start/stop scripts
<clever>
EnvironmentFile=-/etc/containers/%i.conf
<clever>
the script in ExecStart just runs systemd-nspawn with a bunch of special arguments
<clever>
disasm: if /nix is mounted correctly, it might work to just symlink the configs and .service file, but that would need experimentation to confirm
<clever>
disasm: this bash script(and a few other in its .service) then deal with starting/stopping the container as a systemd unit