<clever>
infinisil: id expect it to only use 2 or 3 times the storepath size
<clever>
kreetx: i think each top-level directory in /nix/store is copied as a single unit, and the whole thing has to fit in ram
<clever>
dhess: yeah, that flag would still be of use there i believe
<clever>
dhess: the default in nixpkgs has recently changed, all binaries are now static by default
<clever>
leo60228: git clone my repo, then add the path to the qemu.nix to your imports list
<clever>
leo60228: so you just set qemu-user.aarch64 = true;, nixos-rebuild switch, and it can magically run aarch64 binaries, and nix can even run an "aarch64 only" compiler
<clever>
let me double-check what ive done locally...
<clever>
other then all the machines sharing a mac, an outside observer has no way to tell if you have 10 physical computers, or 10 containers
<clever>
and at that point, each container will be available to the local LAN, and it will act like normal machines on the lan
<clever>
arianvp2: then youll want to put the host eth0 into the bridge, and move any ip config from eth0 to br0, if you have any
<clever>
arianvp2: if you dont connect it to any interface, the containers will have zero internet access, and can only ever talk to eachother
<clever>
you should be able to configure port-forwarding to allow it
<clever>
elvishjerricco: weird
<clever>
Myrl-saki: the daemon will first try to get a lock file on A, and block
<clever>
elvishjerricco: also of note, the stdenv will pass both -j and -l to make, to keep the loadavg under the target core count
<clever>
elvishjerricco: ive been told that the interface file parsing makes that worse
<clever>
i would have expected ld to say that it was out of disk
<clever>
~1h 10mins total
<clever>
more
<clever>
once i gave it more space, it finishes within half an hour
<clever>
the weird ld error at 30 mins in, was out of disk space, lol
<clever>
i also figured out most of my build failures
<clever>
interface files take a while to parse, and --make shares that cache within the process
<clever>
but can share caches between the units
<clever>
it acts like make -j8
<clever>
i think ghc --make will build one module per thread
<clever>
try turning on thread mode, its H in regular top
<clever>
is that top or ps?
<clever>
how many cores?
<clever>
boomshroom: #nixos-aarch64 may also be of interest to you then
<clever>
boomshroom: is it a 32bit or 64bit arm cpu?
<clever>
boomshroom: but its also a lot smaller then full nixos, and could be usefull to get a kernel+rootfs working before you switch to something bigger
<clever>
boomshroom: it has zero gui, and doesnt even run a login prompt on the main tty, but the rootfs stuff can be modified easily
<clever>
boomshroom: the initrd downloads the rootfs over tftp, and then boots into not-os, which has sshd and nix-daemon
<clever>
boomshroom: this generates a directory in my tftp server, that serves rpi firmware, a kernel, an initrd, and the root.squashfs (40mb)
<clever>
kreetx: for more static things like the public_html of a website, you can build and manage it with nix, but a gallery is a bit too dynamic to bother with in nix
<clever>
kreetx: yeah
<clever>
kreetx: id just manually scp the images up once the system is deployed
<clever>
kreetx: and should tbe folder be read-only, writable, and if writable, what happens to the changes at next boot?
<clever>
kreetx: where would you want the folder to turn up?
<clever>
lol
<clever>
ah
<clever>
aristid: what does `nix-store --query --roots /nix/store/wahtever` say, when ran against the mono path?
<clever>
bbsl: if your working in a fork of nixpkgs, edit all-packages.nix to add your package, and use the default.nix in the root of the whole nixpkgs tree
<clever>
bbsl: you have to load that default.nix with callPackage
<clever>
s
<clever>
but i dont like how its tab-completion work
<clever>
that one just works
<clever>
daveo: the replacement is now `nix repl` without a -
<clever>
daveo: but nix 2 now auto-detects that, and nixos 18.03 leaves NIX_REMOTE unset
<clever>
daveo: the issue is that nix-repl uses nix 1 libraries, and expects NIX_REMOTE to be set
<clever>
its a bug between nix1 and nix2
<clever>
daveo: export NIX_REMOTE=daemon
<clever>
daveo: i started with the command inside the $( to confirm it worked, then just used copy/paste to build the outer cmd
<clever>
env is in /usr/bin, not /bin
<clever>
daveo: it looks like i added qemu-user-arm to my os in generation 401
<clever>
daveo: /bin/sh and /usr/bin/env are the only 2 executables that are at "standard" paths
<clever>
daveo: for the #! line, #!/usr/bin/env bash, for everything else, just do "bash" and let $PATH do its job
<clever>
justan0theruser: also, all of those options lack a type, which means it will get very buggy if 2 modules try to set the same option
<clever>
justan0theruser: which itself gets the default value from line 41
<clever>
justan0theruser: line 11
<clever>
daveo: some are installed with environment.systemPackages and others with nix-env
<clever>
daveo: yep
<clever>
daveo: nixos is always in an environment with nix available, you can just skip 3.1
<clever>
daveo: link?
<clever>
daveo: thats only needed if you are not on nixos
<clever>
daveo: which one?
<clever>
pirateking: you can probably change the init= in grub to init=/bin/sh to get a very basic single-user shell and attempt repairs, but it would probably be simpler to boot into the original installer ISO and repair it from there
<clever>
pirateking: where does it fail when booting nixos?
<clever>
xorg and gparted could be included in that "rescue" blob, and then you have gparted and the ability to shrink windows filesystems
<clever>
and nuke windows from orbit with wipefs!
<clever>
which means i could take ~4 files from the rescue_boot system, stick them in c:\, modify boot.ini, and then f8 my way to the nixos installer
<clever>
PolarIntersect: and i believe grub can be configured to support an ntfs "/boot" partition
<clever>
PolarIntersect: something i have been wanting to do, is to modify boot.ini to be able to chainload grub
<clever>
and /mnt/boot was mounted during that install?
<clever>
PolarIntersect: your firmware could be buggy
<clever>
PolarIntersect: and see what happens then
<clever>
PolarIntersect: id recomend you set boot.loader.grub.efiInstallAsRemovable = true; and then re-run nixos-install
<clever>
PolarIntersect: that appears to be your windows drive
<clever>
ghostyy: because the installer itself is a program that has to exist in /nix/store/
<clever>
ghostyy: the iso includes an MBR partition header, so you have to use the losetup flag for obeying partition tables, installing from a squashfs is also tricky
<clever>
PolarIntersect: can you add the `fdisk -l /dev/sdb` to the output?
<clever>
which one is it?
<clever>
it looks like the efi vars are not updated correctly, so the firmware doesnt know about the new install
<clever>
PolarIntersect: if you do `blkid /dev/sd??` do you see the uuid from Boot0001?
<clever>
PolarIntersect: Boot0001 doesnt look right, and why do i see a microsoft thing in Boot0000?
<clever>
PolarIntersect: everything looks fine, what does efibootmgr -v say?
<clever>
so you actually set it to [ 22 22 ];
<clever>
it concats the value of that option from every module
<clever>
yeah
<clever>
you cant lock yourself out easily
<clever>
PolarIntersect: also line 28, the ssh service automatically allows port 22 in the firewall
<clever>
PolarIntersect: hardware.nix is also of interest
<clever>
PolarIntersect: and what is the contents of your configuration.nix file? youll need to open the luks and mount the fs within
<clever>
PolarIntersect: its the bash wildcard for 1 character
<clever>
PolarIntersect: the ? is missing from the command
<clever>
PolarIntersect: blkid /dev/sdc?
<clever>
PolarIntersect: fdisk -l /dev/sdc
<clever>
then ssh in from a machine with a working mouse and irc client
<clever>
passwd ; systemctl start sshd
<clever>
PolarIntersect: do you have a 2nd machine with ssh client?
<clever>
PolarIntersect: if possible, can you just throw it all into a pastebin?
<clever>
PolarIntersect: what does lsblk say when booted into the installer?
<clever>
PolarIntersect: i think systemd-boot and grub should warn you
<clever>
leo60228: i'm out of ideas
<clever>
PolarIntersect: yeah, efi firmware can only boot in efi mode from a gpt disk
<clever>
wilornel: ive had zero problems resizing things while the machine was running
<clever>
no
<clever>
correct
<clever>
so it has never been partitioned
<clever>
nvme1n1 doesnt even have a disk label type
<clever>
yeah
<clever>
wilornel: fdisk doesnt show any partitions on the 80gig one
<clever>
its entirely unused
<clever>
the 80gig drive has no partitions on it
<clever>
you cant grow the nixos, because the drive its on is already full
<clever>
and the 80gig drive is unused
<clever>
nixos is installed to the 40gig drive
<clever>
wilornel: you didnt resize it, you added another disk, you have 3 hard-drives, with sizes of 40gig, 80gig, and 8gig
<clever>
wilornel: oh, i think i see whats going on
<clever>
wilornel: your hard-drives
<clever>
wilornel: ah, i dont think nixos supports resizing the nvme drives currently, those are pretty new
<clever>
wilornel: what about fdisk -l /dev/vda, or whatever it happens to be called?
<clever>
wilornel: i didnt even shutdown mine
<clever>
wilornel: nixos will automatically growpart and resize for you on bootup, just reboot the machine after growing the ELB
<clever>
leo60228: try turning docker back on by uncommenting the old config, and nixos-rebuild switch
<clever>
leo60228: and since you did a channel update, what does `systemctl status docker` say now?
<clever>
yep, exactly what i would expect
<clever>
leo60228: try turning on services.openssh.enable and then pastebin the output of nixos-rebuild switch
2018-04-27
<clever>
leo60228: thats also fairly good, it will basically force nixos to rebuild everything, so anything that might have somehow gone corrupt and un-detected is going to be rebuilt
<clever>
leo60228: something changed that caused a mass-rebuild
<clever>
leo60228: as an experiment, try turning on services.openssh.enable and then pastebin the output of nixos-rebuild switch
<clever>
looks standard, nothing that would break things
<clever>
leo60228: what is in /etc/nixos/hardware-configuration.nix ?
<clever>
leo60228: can you screenshot the whole terminal?, it shouldnt be that small
<clever>
leo60228: if you remove docker from systemPackages and comment out the 2 virtualisation.docker lines, what does `nixos-rebuild switch` print?
<clever>
leo60228: and /etc/nixos/configuration.nix is what you included in a previous pastebin?
<clever>
yeah
<clever>
leo60228: ?
<clever>
leo60228: what does `echo $NIX_PATH` say?
<clever>
leo60228: what is the output of: nix show-derivation /nix/store/9y0gqcdg6228qgrjvz4qax7m2iw4z0gq-system-units.drv
<clever>
leo60228: and then pastebin the output of `nix-store -qR /nix/store/vzsfy8hy86zw4qdmb022wniww4src6rf-nixos-system-leonix-18.03.132083.06c576b0525.drv`
<clever>
leo60228: what does `sudo nix-channel --list` say?
<clever>
leo60228: what is the output of `nix-store -q --deriver /run/current-system` ?
<clever>
has the --verify finished?
<clever>
once those 2 are ran, that "corrupt" path will be gone
<clever>
sphalerite: you got time to debug an arm linker problem ive run into?
<clever>
wilornel: the zip format decided to have a new epoch i think
<clever>
the regex -e uses to match names can sometimes get confuse
<clever>
ldlework: run `nix-env -e /nix/store/hash-name` to uninstall it
<clever>
M-bbigras: nix deletes the build directory after the build has finnished, but you can view the log with `nix-store -l /nix/stor/epath` or maybe `nix log`
<clever>
AGTT: its not currently maintained by hydra, so you would have to compile it, and binutils currently fails to build on arm, so that wont work with current nixpkgs
<clever>
AGTT: you would need an arm build of nix to start with
<clever>
AGTT: depends on the target, one machine ive wanted to convert has a 1tb / and a 20gig /home
<clever>
AGTT: yeah, both the fs and partition layout
<clever>
AGTT: i also have a kexec trick that lets you do similar and change the partitioning however you like
<clever>
AGTT: i have done that manually before, and i nixos-in-place automates it, but you are still limited to the existing partition layout