2017-05-23
01:24
<
clever >
this includes a custom fuse program, and a full nixos vm that has the program pre-installed
01:21
<
clever >
they can depend on eachother, as if they where in nixpkgs
01:21
<
clever >
so if i use the new callPackage to load my own default.nix files, and put them all into the self set
01:21
<
clever >
in this example, it will search self. first, then pkgs.
01:21
<
clever >
when you call newScope on an attrset, it returns a new instance of callPackage
01:20
<
clever >
stallion: you may want newScope more
2017-05-22
23:17
<
clever >
i had chosen to just hardcode the hd# and part#, which does fail every now and then (i have to edit it to hd2,msdos1)
23:16
<
clever >
SovereignBleak: you may need to load the right module for the filesystem and partition table your searching for
23:04
<
clever >
SovereignBleak: oh, your also missing a } inside the string, so the grub.cfg would become invalid and cease booting
23:03
<
clever >
SovereignBleak: and that option is of type string
23:03
<
clever >
SovereignBleak: attribute sets! must be in the form of key=value;
23:03
<
clever >
SovereignBleak: bare strings must be in the form of key=value;
23:02
<
clever >
SovereignBleak: you have a bare string inside an attribute set
07:23
<
clever >
that feels like a place a desktopmanager would look
07:22
<
clever >
bkchr: and if that is then put into systemPackages, it should appears in /run/current-system/sw/share/autostart/
07:22
<
clever >
bkchr: if you call it with the arguments listed on lines 5-11, it will copy the existing .desktop file from package to $out/share/autostart/
07:07
<
clever >
and the versions within that, only update when people make commits to nixpkgs
07:06
<
clever >
and a script will update that pointer when a set of jobs on hydra passes
07:06
<
clever >
the main nixos-unstable channel contains a snapshot of the nixpkgs git repo
07:05
<
clever >
not sure how to solve that, most of the framework in nix is designed to make things reproducable, so it doesnt just update to random versions without warning
07:02
<
clever >
ive never used that part of hydra
07:01
<
clever >
so adding it to the binary cache list wont help any
07:01
<
clever >
if things where working correctly, it would have complained that it didnt know how to build it
07:00
<
clever >
then it checks the binary caches for that path
07:00
<
clever >
and given that src hash, it will compute the path that the compiled ruma lands in
07:00
<
clever >
yeah, you need to put in a fixed-output derivation like fetchurl or fetchgit, and provide the hash of the src
06:57
<
clever >
thats exactly how nixpkgs and hydra.nixos.org work
06:57
<
clever >
Zer000: if you point the client at the exact same ruma expression, on the same nixpkgs, it will just use the hydra version
06:55
<
clever >
Zer000: try switching the import out to import the original nix expressions, not the hydra channel
06:55
<
clever >
its using fake derivations, with storepaths in them
06:54
<
clever >
yeah, theres the problem
06:53
<
clever >
can you gist the default.nix in that dir?
06:51
<
clever >
what does "nix-instantiate --find-file hydra_ruma" say?
06:51
<
clever >
is hydra_ruma in nix-channel?
06:50
<
clever >
Zer000: what is $NIX_PATH?
06:48
<
clever >
Zer000: strange
06:46
<
clever >
can you also gist the default.nix for hydra_ruma?, or is that another hydra input?
06:44
<
clever >
we need to see what <hydra_ruma> points to
06:44
<
clever >
Zer000: is this of type derivation, or string?
06:44
<
clever >
default = hydra_ruma.ruma;
06:44
<
clever >
what about just "ls -l /nix/store/h055a5gi0048fvm9lkmv51xs27zy126k-ruma"
06:43
<
clever >
Zer000: and what is in "ls /nix/store/h055a5gi0048fvm9lkmv51xs27zy126k-ruma/bin/" ?
06:42
<
clever >
what error is it having?
06:42
<
clever >
your using an absolute path, so it doesnt need to be "installed" to work
06:41
<
clever >
ExecStart = "${cfg.package}/bin/ruma run";
06:41
<
clever >
can you gist your nix expression?
06:39
<
clever >
put it in the .path of the service
06:38
<
clever >
Zer000: services dont use systemPackages
01:36
<
clever >
i also prefer chromium
01:35
<
clever >
17.03 is a stable snapshot
01:35
<
clever >
its probably only on nixos-unstable
01:34
<
clever >
nix-env -iA nixos.skypeforlinux
01:33
<
clever >
dont see it
01:28
<
clever >
this is also an option
01:28
<
clever >
nix-env -iA nixos.terminator
01:28
<
clever >
yeah, mate-terminal hasnt been added to 17.03 yet
01:26
<
clever >
sudo nix-channel --list
01:26
<
clever >
terminator is still a possibility
01:26
<
clever >
your channel might be too old for it then
01:25
<
clever >
it needs the A in -iA
01:24
<
clever >
i see it on this end, did you use -A?
01:22
<
clever >
nix-env -iA nixos.mate.mate-terminal
01:22
<
clever >
nix-envi -iA nixos.terminator
01:17
<
clever >
ive just been sticking to plain xfce+slim
01:15
<
clever >
you can also enable a desktopManager, and it will usualy install a terminal for you
01:14
<
clever >
but xserver hasnt been enabled, so there is no display-manager systemd unit
01:14
<
clever >
lightdm is trying to change the env vars for the display-manager systemd unit
01:14
<
clever >
you probably also need services.xserver.enable = true;
01:12
<
clever >
nixos-rebuild build 2>&1 | gist -p -
01:11
<
clever >
it also helps massively if you enable ssh, then remotely connect from another machine
01:10
<
clever >
Nobabs27: and what was the exact error?
01:06
<
clever >
Nobabs27: gist -p /etc/nixos/configuration.nix
01:03
<
clever >
Nobabs27: did you spell it correctly?
00:57
<
clever >
lukec1: it may also need other features, there is an open issue about it not saying why its blocked
00:56
<
clever >
lukec1: this is what i have on one of mine
00:56
<
clever >
supportedFeatures = [ "big-parallel" "kvm" "nixos-test" ];
00:56
<
clever >
lukec1: you have to list kvm as a supported feature on the buildMachine list
00:54
<
clever >
or 'man configuration.nix'
00:49
<
clever >
so the list remains in a text file i can archive with git
00:49
<
clever >
i prefer putting things into systemPackages or a buildEnv instead
00:49
<
clever >
maybe -iA each
00:48
<
clever >
i believe its nix-env -iA nixos.foo -A nixos.bar
00:45
<
clever >
which makes it much slower
00:45
<
clever >
-i searches the name attribute of every single package
00:45
<
clever >
Nobabs27: pretty much
00:43
<
clever >
Zer000: its been doing it for years
00:43
<
clever >
Zer000: because hydra always uses the buildMachines and will never try to build locally
00:42
<
clever >
--pure will stop that
00:42
<
clever >
by default, nix-shell lets the original $PATH leak in
00:40
<
clever >
you loose a lot of its feature when installing it, because gcc isnt supposed to be installed
00:40
<
clever >
because gcc must be in the env of the shell, not just installed
00:39
<
clever >
jackjackjack: what about nix-shell -p ncurses ncurses.dev gcc?
00:36
<
clever >
so that string needs to be corrected
00:36
<
clever >
Nobabs27: extraConfig is the right one, but the string inside isnt a valid sudoers config
00:35
<
clever >
Nobabs27: the extraConfig for sudoers isnt valid, check the man page or refer to your old sudoers on arch
00:34
<
clever >
Zer000: yeah, you can configure localhost as a build slave
00:34
<
clever >
Nobabs27: line 16 of the sudoers file, not line 16 of configuration.nix
00:34
<
clever >
Zer000: then it has no slaves to build on
00:33
<
clever >
Zer000: did you add a build slave in nix.buildMachines?
00:33
<
clever >
oops with 1 more - at the end
00:33
<
clever >
Nobabs27: can you gist more of the error?, nixos-rebuild build 2>&1 | gist -p
00:32
<
clever >
can you double-check the error msg?
00:32
<
clever >
16 looks normal to me
00:31
<
clever >
does it say where the syntax error is?
00:28
<
clever >
just | gist -p -
00:27
<
clever >
very first argument it lists
00:27
<
clever >
gist --help
00:26
<
clever >
can you gist the configuration.nix file?
00:26
<
clever >
Nobabs27: what exactly did the error say?
00:16
<
clever >
check the sudoers man page
00:16
<
clever >
security.sudo.extraConfig = "youruser = ALL=(ALL:ALL) NOPASSWD: ALL";
00:14
<
clever >
you need to put in the same like you would normally add to /etc/sudoers
00:13
<
clever >
sudo.nix is the internal file, that makes it an option
00:13
<
clever >
you are supposed to put that in /etc/nixos/configuration.nix
00:11
<
clever >
so you can undo the change by picking the older option
00:11
<
clever >
and every time you make any change, it creates a new entry in grub
00:08
<
clever >
can you pastebin the full output of "ls -l /nix/var/nix/profiles"
00:08
<
clever >
default is the current version of nix-env's profile
00:08
<
clever >
system is the current version of the system
00:07
<
clever >
system points to system-4-link
00:07
<
clever >
default is part of nix-env
00:07
<
clever >
and another nixos-rebuild boot should update grub.cfg to match
00:05
<
clever >
"nix-collect-garbage -d" needs root to delete system generations
00:05
<
clever >
Nobabs27: then you didnt delete the old versions
00:04
<
clever >
Nobabs27: and what does this say, "ls /nix/var/nix/profiles/"
00:03
<
clever >
and the attribute path is just a list of keys to follow
00:02
<
clever >
mellowmaroon: the nixpkgs package set is just a giant attribute set (key/value list) of packages
00:01
<
clever >
-i says to install, -A says to use an attribute path
00:01
<
clever >
but gist is in the gist package
00:00
<
clever >
Nobabs27: nix-env -iA nixos.git
2017-05-21
23:59
<
clever >
you can also "gist -p /boot/grub/grub.cfg" from the cli
23:59
<
clever >
can you throw /boot/grub/grub.cfg into a pastebin?
23:57
<
clever >
Nobabs27: does "mount" show /boot as being mounted?
23:56
<
clever >
Nobabs27: and is /boot correctly mounted when running nixos-rebuild?
23:55
<
clever >
Nobabs27: what are the names of them in grub.cfg?
23:54
<
clever >
what 4 do you have?
23:52
<
clever >
nix-collect-garbage -d
23:52
<
clever >
they dont take up that much disk space
23:52
<
clever >
yeah, thats normal, and you usualy want to keep all of the others
23:51
<
clever >
and nixos has its own profile, seperate from the default for nix-env
23:49
<
clever >
Nobabs27: grub isnt updated until you do another rebuild switch
23:23
<
clever >
maybe also: users.users.clever = { isNormalUser = true; extraGroups = [ "wheel" ]; };
23:23
<
clever >
Nobabs27: users.users.clever = { isNormalUser = true; };
23:22
<
clever >
any time you update configuration.nix, and rebuild, it updates the grub config to point to the latest
23:21
<
clever >
and it will install it for you, and configure everything
23:21
<
clever >
in configuration.nix, set networking.networkmanager.enable = true;
23:21
<
clever >
since it changes system wide config
23:21
<
clever >
network manager is something that has to be enabled, not installed
23:20
<
clever >
there is also 'man configuration.nix'
23:17
<
clever >
same for nox
23:17
<
clever >
nix-repl has to be installed first, nix-env -iA nixos.nix-repl
23:15
<
clever >
a tool that will index nixpkgs and allow searching
23:15
<
clever >
Nobabs27: i usualy use nox or nix-repl to search
23:14
<
clever >
nixos-install is basicaly just a script to run nixos-rebuild under chroot, and deal with getting nix inside the rootfs
23:14
<
clever >
if you remount an existing install and run nixos-install on it again, it will update it to match the configuration.nix
23:10
<
clever >
mellowmaroon: it still allows interactive logins over ssh, but you need a keypair to get it
23:10
<
clever >
Nobabs27: there is a "nixos-install --chroot" flag that does it all for you
23:09
<
clever >
only ssh keypairs, no other way in
23:09
<
clever >
mellowmaroon: i usualy set services.openssh = { enable = true; permitRootLogin = "yes"; passwordAuthentication = false; }; once the install is done
22:34
<
clever >
yeah, i think thats all you can do
22:30
<
clever >
Zer000: i'm guessing it has to do with the regex in parseTOML
22:24
<
clever >
Zer000: do you know if hydra is using a different version of nix?
22:24
<
clever >
yeah, thats not right
22:21
<
clever >
yeah, i would expect that to work
22:19
<
clever >
Zer000: anything in the hydra-evaulator journal?
22:19
<
clever >
Zer000: does it give any line numbers or other details?
07:44
<
clever >
drakonis: make sure /boot is in hardware-configuration.nix so it gets mounted on bootup
05:40
<
clever >
2017-05-21 02:03:48 < clever> about all i can think of right now is "dd if=/dev/zero of=/dev/sda5 bs=512"
05:26
<
clever >
the dd will return when its done
05:25
<
clever >
threshold: i believe its in here
05:25
<
clever >
[clever@amd-nixos:~]$ nix-build apps/nixpkgs/pkgs/top-level/release.nix -A manual
05:21
<
clever >
threshold: i havent found an attribute that has the pdf manual
05:21
<
clever >
i try to isolate windows to its own drive whenever possible
05:20
<
clever >
drakonis: if you are reinstalling, it will be easy to fix
05:08
<
clever >
yeah, it will take some time
05:08
<
clever >
and its probably safe to wipe sda2 as well
05:08
<
clever >
try running the dd i gave over sda5, and then see what mount says
05:08
<
clever >
and has to wipe and repartition to make it fit
05:08
<
clever >
legacy booting needs an bios boot partition, and everybody forgets it
05:07
<
clever >
i have seen a minor need for that with a lot of gpt installs
05:07
<
clever >
and if windows ever needs another misc partition, it can shrink the reserve
05:07
<
clever >
so it just reserves 16mb for later use down the road
05:05
<
clever >
i think its a backup thing windows uses
05:05
<
clever >
fdisk says sda2 is 'microsoft reserved'
05:04
<
clever >
i'm guessing wipefs didnt get the zfs header
05:03
<
clever >
to zero out all of sda5
05:03
<
clever >
about all i can think of right now is "dd if=/dev/zero of=/dev/sda5 bs=512"
05:02
<
clever >
even a usb stick would do
05:01
<
clever >
first, i would make a backup of the first 1mb, do you have another drive you can save files to?
05:00
<
clever >
so thats 0x600 bytes between the gpt and efisystem
05:00
<
clever >
efi system starts at 0x5000
04:59
<
clever >
and the EFI system starts at 40*512 i think, checking
04:58
<
clever >
0x4400 i think is where the GPT header ends
04:58
<
clever >
drakonis: this should put a hexdump of the start of the disk on gist
04:57
<
clever >
drakonis: "hexdump /dev/sda -C | head -n1500 | gist -p -"
04:56
<
clever >
hmm, wikipedia says its ~34 sectors
04:54
<
clever >
and gpt's header is of an unknown length, so its hard to safely clear the zfs header
04:53
<
clever >
thats the gparted problem, but mount should only be looking in sda5
04:53
<
clever >
and i would risk the data loss of trying to clear random areas
04:53
<
clever >
yeah, i cant think of anything else right now
04:52
<
clever >
drakonis: does mount -v /dev/sda5 /mnt say anything more?
04:49
<
clever >
we could try to strace mount, "strace -o logfile mount /dev/sda5 /mnt ; gist -p logfile"
04:47
<
clever >
and it still fails when you use the right type on -t?
04:46
<
clever >
you can probably run wipefs on sda5, and format it again
04:45
<
clever >
what about dmesg?
04:44
<
clever >
what error does mount give?
04:44
<
clever >
fdisk doesnt format things
04:43
<
clever >
did you format sda5?
04:42
<
clever >
can you do "fdisk -l /dev/sda | gist -p -" again?
04:41
<
clever >
because sda5 doesnt exist
04:39
<
clever >
the fdisk you gist'd only has sda1 thru sda4
04:39
<
clever >
yeah, fdisk says its gpt
04:38
<
clever >
fdisk says it only goes up to sda4
04:38
<
clever >
cant mount which partition?
04:37
<
clever >
can you just use fdisk instead?
04:37
<
clever >
kind of tricky, because gpt doesnt use just 1 sector
04:37
<
clever >
drakonis: i think the problem, is that zfs has a header near the start of the disk, so gparted assumes the whole thing is zfs
04:35
<
clever >
drakonis: can you hit 'view->device information' in gparted, and screenshot that?
04:34
<
clever >
drakonis: one min
04:33
<
clever >
disasm: id add logic to detect if the db is missing, and auto-configure it
04:30
<
clever >
drakonis: what about fdisk -l /dev/sda ?
04:30
<
clever >
disasm: but i think it only works the first time postgress is installed
04:30
<
clever >
drakonis: partitions, or zvols?
04:29
<
clever >
zfs will then divide it up internally
04:29
<
clever >
drakonis: having 1 big partition is normal for zfs
04:29
<
clever >
drakonis: ah
04:29
<
clever >
drakonis: ah, its not currently mounted, what about "zfs list" and "zpool status -v" ?
04:28
<
clever >
drakonis: there is a gist command in nixpkgs, nix-env -iA nixos.gist ; df -h | gist -p -
04:27
<
clever >
since it can handle multiple files and editing
04:27
<
clever >
drakonis: i prefer gist.github.com
04:27
<
clever >
disasm: which db engine is it on?
04:26
<
clever >
drakonis: what does df say you have?
04:24
<
clever >
the above will install the xfce version of the tool
04:23
<
clever >
drakonis: nix-env -iA nixos.xfce.xfce4-screenshooter or nvm, lol
04:21
<
clever >
does anything happen when you hit the printscreen key?
04:20
<
clever >
drakonis: can you screenshot it?
04:20
<
clever >
users.users.root.initialPassword = "root";
04:18
<
clever >
check the current dir to see it
04:18
<
clever >
and initial only works on the first boot, so youll need to delete the qcow
04:17
<
clever >
youll need .initialPassword = "hunter2";
04:17
<
clever >
no defaults
04:04
<
clever >
and if you dont give it root, it has zero chance of breaking things
04:02
<
clever >
disasm: i try to use "nixos-rebuild build-vm -I nixpkgs=/home/clever/nixpkgs -I nixos-config=./configuration.nix" for testing
03:32
<
clever >
threshold: for nix, this will make a result/manual.pdf
03:32
<
clever >
[clever@amd-nixos:~]$ nix-build nix/release.nix -A tarball -Q -j8
00:43
<
clever >
johnramsden: the activation scripts run much sooner in the bootup, and every time you rebuild-switch, so they wont have that issue
00:35
<
clever >
johnramsden: oh, and extraInit may also cause some issues, it will only run when you open a terminal, so running a program via the gui may skip creating the config
00:24
<
clever >
one of them must work
00:24
<
clever >
johnramsden: loginShellInit vs interactiveShellInit vs shellInit vs extraInit
00:17
<
clever >
the example i linked is what links /etc into the latest etc build in the store
00:16
<
clever >
and its free to mutate the system state
00:16
<
clever >
johnramsden: the activation script gets ran as root, on bootup, and when you nixos-rebuild-switch
00:16
<
clever >
activation scripts are a second option
00:14
<
clever >
johnramsden: i also remembered another way of doing it
00:14
<
clever >
johnramsden: try adding an echo before the if statement, and then open another shell
00:07
<
clever >
other then when a service reads pkgs.foo
00:07
<
clever >
and it will have no impact on services
00:07
<
clever >
i think overlays are only a way to give a list of packageOverrides
2017-05-20
23:46
<
clever >
ben: and nix tries to upload 2gig of closure to a remote build slave, because its "faster"
23:46
<
clever >
ben: another more anoying thing, buildEnv merely symlinks paths from all of the inputs 99% of the time
23:45
<
clever >
or /nix/store/hash-foo.service/foo.service, which confuses new users
23:45
<
clever >
but a lot of things like systemd use scripts in $out/bin/ when it doesnt have to
23:44
<
clever >
so writeTextFile could be modified, to call toFile if the arguments are simple
23:43
<
clever >
but can it put it in $out/bin/foo, and +x it?
23:43
<
clever >
rather then writing a string into the store, at a potentialy complex path, with +x