<clever>
chisui: what happens when you run efibootmgr ?
<clever>
chisui: and "dmesg | grep EFI" finds something?
<clever>
yeah
<clever>
until result is deleted or pointed at something else
<clever>
chisui: try the other options in your bios when you pick booting from the cd
<clever>
chisui: how did you get the ISO onto the usb drive?
<clever>
CapsAdmin: nix builds them
<clever>
chisui: and also, how did you make the install media?, is it a cd? usb?
<clever>
chisui: you have to select it in the firmare, when booting the machine
<clever>
chisui: you need to make sure you boot the installer in efi mode
<clever>
chisui: that environment didnt boot via efi, so it cant configure efi booting
<clever>
chisui: you censored out the important bits
<clever>
chisui: what does "mount" output?
<clever>
symphorien: and it has sshd, so ssh back in, and you are free to reinstall the entire OS
<clever>
symphorien: and if your wondering what the expression i linked does, you just unpack the tar to /, and run /kexec_nixos, and you have nixos running from a ramdisk
<clever>
and yeah, nix is designed to not break things like apt does
<clever>
CapsAdmin: if you give a non-root user write access to an empty /nix directory, then you can install nix without root
<clever>
if unpacked to /
<clever>
symphorien: in this case, it creates a /kexec_nixos symlink and a /nix directory with the full closure
<clever>
just bios boot, which cant contain a filesystem
<clever>
jsgrant_: he currently doesnt have an efi partition
<clever>
and the output of mount isnt in there
<clever>
chisui: line 25, you dont have EFI enabled
<clever>
chisui: the bios boot partition is only to support legacy booting
<clever>
chisui: EFI cant install with only a bios boot partition
<clever>
i-am-the-slime: i use lastpass
<clever>
jsgrant_: yeah, it could overwrite the wrong MBR
<clever>
jsgrant_: the grub device has no default, and an assertion will fail if its unset
<clever>
thats only for legacy booting
<clever>
chisui: if you are booting with efi, you must set boot.loader.grub.device = "nodev";
<clever>
chisui: grub only embeds if your using legacy booting, it sounds like you configured it wrong
<clever>
chisui: what does "mount" say?, paste it into gist.github.com
<clever>
chisui: and what failed?
<clever>
chisui: you need a fat formated filesystem, with partition type EFI system, mounted to /mnt/boot/ and a rootfs of your choice mounted to /mnt/
<clever>
chisui: do you want to boot with efi or legacy?
<clever>
Myrl-saki: your derivation will install to $out/include/ and the stdenv will add the include dir of every input to the gcc search path via $NIX_CFLAGS_COMPILE
<clever>
dhess: the channel is mostly managed by external scripts, that wait until the tests pass on hydra, then publish the tarball hydra made in a certain job
<clever>
dhess: yes
<clever>
octe: then the editor has to be ran within the nix-shell
<clever>
octe: does flycheck have a daemon mode?
2018-01-06
<clever>
jekor: run "lsof -p <PID>" on the pid of nix-daemon, and check where stdout/stderr are directed
<clever>
jekor: i think that format will work, and the daemon runs as root, so it can read the key
<clever>
nikivi: if 2 programs use the exact same build, they will share that storepath, so there isnt a duplicate copy
<clever>
jekor: try putting the config into /etc/nix/machines
<clever>
jekor: nix-daemon doesnt get that variable
<clever>
jekor: and are the remote machines setup in /etc/nix/machines ?
<clever>
jekor: with that exact command?
<clever>
jekor: what happens if you run "ssh user@host nix-store --help" with the user/host of the darwin machine
<clever>
ertes: in general, i use super, self is to fix the loops
<clever>
yeah, that should work
<clever>
make a packageOverride that just overwrites haskellPackages with the 8.0 set
<clever>
so 6 months down the road, when you want to update, you dont need ot do as much work
<clever>
all the other stuf, is just to make it simpler to manage things
<clever>
for just installing it, all you need is nix-env -iA unstable.discord
<clever>
yeah
<clever>
all it knows is the names of the packages
<clever>
but `nix-env -u` wont always pick the right channel to read them from
<clever>
nix-env is then required to install the new versions
<clever>
nix-channel is required to update the expressions
<clever>
yeah
<clever>
fendor: nix-env -iA nixos.setname
<clever>
fendor: using a set in config.nix to define all of your programs
<clever>
fendor: and im not sure which channel `nix-env -u` will use
<clever>
that would only update things root installed with nix-env
<clever>
the user will automaticaly use the root channels
<clever>
no
<clever>
fendor: ah, then nixos will only update if root runs nix-channel --update
<clever>
fendor: is nixos listed on both users, or only one?
<clever>
jluttine[m]: manually create the missing directory
<clever>
so other things wont become unstable
<clever>
you can use the stable channel for most things, and then get just discord from unstable
<clever>
depends on if you want to keep using the stable channel or not
<clever>
nixos is 17.09, which is older, unstable is newer
<clever>
fendor: the version in unstable?
<clever>
fendor: try nix-env -iA unstable.discord
<clever>
fendor: what does nix-channel --list say?
<clever>
does it allow the old version to run?
<clever>
the update will either fail or break the program
<clever>
fendor: nothing installed with nix can update itself
<clever>
fendor: nix-env -iA nixos.discord
<clever>
jluttine[m]: nixos-install also works from any nixos install
<clever>
kim0: yes
<clever>
compare a normal release tarball with the github source, to see what they added
<clever>
nix removes the .git directory, so that wont help
<clever>
stuff that is never included in the github
<clever>
and the cmake files expect extra stuff to be added to the tarball when making a release
<clever>
kim0: the error is caused by nix not providing a git executable, and the .git directory being missing
<clever>
cmake/Version.cmake may explain it more
<clever>
it needs a version.cpp.in file to tell it what version it is
<clever>
kim0: line 20 and 21
<clever>
it helps stop the builds you do later from touching places it shouldnt
<clever>
those help ensure you dont break nix
<clever>
yes
<clever>
bobbypriambodo: you can use multi-user mode as a single user
<clever>
the stdin of the bash is connected to curl, so it cant read stdin from you
<clever>
ah, it must have been changed again
<clever>
bobbypriambodo: it will use stdin to ask that, when installing, how did you run it?
<clever>
Aleksejs: has that user relogged since the change?
<clever>
srhb: so i silently loose the ability to capture audio until i restart all of chrome
<clever>
srhb: oh, and if pulseaudio restarts, chromium can reconnect for playback, but not capture
<clever>
srhb: every 5 minutes
<clever>
srhb: and half my pulse clients are incapable of reconnecting, so i just silently lost audio in those applications
<clever>
srhb: the realtime watchdog assumed pulse was to blame, and -9'd pulseaudio with zero logs saying so
<clever>
srhb: pulse used realtime to prevent such issues, and other glitches in my system caused micro-hangs (locking up for ~2 seconds)
<clever>
srhb: ive had far worse problems with pulse and realtime scheduling
<clever>
macslayer: i also like doing nixpkgs.config.pulseaudio = true;, which means anything installed with systemPackages has pulse support enabled in it
<clever>
you need to ensure ~/.bashrc on the mac sources
<clever>
dhess: bash sources different files when ran interactively
<clever>
dhess: what if you run "ssh user@mac nix-store --help"
<clever>
longrin1: also, thats why i like gist, just nix-env -iA nixos.gist and then run "gist -p file1.nix file2.nix file3.nix" and all of them are published at once
<clever>
longrin1: anything that sets systemPackages
<clever>
dhess: restart the nscd service
<clever>
longrin1: can you also gist the entire nixos config?
<clever>
and murderizes the other 3
<clever>
then ghc or the glibcLocales tries to use 99% of the ram in a single job
<clever>
but if i instead limit it to 4 jobs, and make -j1, it runs fine 90% of the time
<clever>
if i limit it to 1 job and -j4 at the make level, it wastes cpu half the time, on single-threaded builds
<clever>
ive had the same issue on my arm
<clever>
and it is a hard thing to balance right
<clever>
dhess: while maxJobs is at the nix level, so it could potentially do x*y processes
<clever>
dhess: the buildCores option is passed to make, and not all packages use ot
<clever>
can you re-run the command with --show-trace and then gist the output?
<clever>
anelson-: once it has finished once, you can manually run make to do it incrementally
<clever>
anelson-: try just genericBuild
<clever>
anelson-: nix-shell '<nixpkgs>' -A nix
<clever>
iqubic: and there is a button in the top left, that says select an element
<clever>
iqubic: did you hit ctrl+shift+i ?
<clever>
iqubic: you just click on it with the inspector tool
<clever>
petersjt014[m]: dont even bother, dd will overwrite it all anyways
<clever>
petersjt014[m]: the directory entries are pointing into un-initialized data
<clever>
petersjt014[m]: lol
<clever>
iqubic: 2018-01-02 22:23:23 < MP2E> Not really sure how to workaround it other than pressing CTRL+Shift+I, isolating the element, and deleting it, but all that does is make the message go away
<clever>
petersjt014[m]: the default of 1 is incredibly hard on the cpu, try bs=512
<clever>
petersjt014[m]: did you set the block size?
<clever>
they had to be special :P
<clever>
iqubic: the binary is called Discord
<clever>
iqubic: how did you check to see if discord was installed?
<clever>
petersjt014[m]: sdb i believe, the image already contains partition tables
2018-01-02
<clever>
thats checking the binary cache
<clever>
dhess: is localhost in /etc/nix/machines?
<clever>
tilpner: i believe it does the same thing as nix-build -A or -E
<clever>
tilpner: but :b will build it
<clever>
tilpner: yeah, that prints the string without forcing its context to exist
<clever>
tilpner: :b buildFHSUserEnv { name = "foo"; }
<clever>
tilpner: :b
<clever>
tilpner: pass the derivation via -p instead
<clever>
lejonet: eval "${ceph}" and "${ceph.lib}" in nix-repl '<nixpkgs>'
<clever>
:D
<clever>
yep
<clever>
if you add it to an overlay, you can refer to it as pkgs.bitwig