| 9 Sep 2024 |
 Tumble | In reply to @zerox:guix.uz
Tumble: in case if you don't need cache, you can remove it, otherwise you need another device for cache. I have a device for cache | 18:10:00 |
| Tumble | This works to make a zfs pool with a cache drive but I don't think it has any redundancy | 18:10:42 |
 zerox | Tumble: for redundancy, add mode= .... | 18:11:21 |
| Tumble | raidz1? | 18:12:06 |
| zerox | Tumble: yes, it can be raidz1. See: https://github.com/nix-community/disko/blob/master/lib/types/zpool.nix#L4 | 18:13:29 |
| Tumble | Does a disko options site exist? | 19:32:12 |
| Tumble | What's raidz? | 19:34:25 |
| Tumble | Without number | 19:34:33 |
| Tumble | Is z1 where I can loose one drive? | 19:34:46 |
| 10 Sep 2024 |
| Tumble | In reply to @zerox:guix.uz
Tumble: yes, it can be raidz1. See: https://github.com/nix-community/disko/blob/master/lib/types/zpool.nix#L4 Because I have zfs housing my /home and /var will I have to rebuild the whole install? | 00:30:39 |
| Tumble | I'm ok with that anyway because I've only just done that 10 hours ago | 00:31:09 |
 colemickens | Is it possible to specify a disko image partition whose contents are... a uboot build output, for example? | 02:56:44 |
| colemickens | weird. | 04:57:50 |
| colemickens | I'm trying to build diskoImagesScript on the aarch64 box for a hostPlatform.system = "aarch64-linux" machine and it's complaining that it wants an x86_64-linux builder for a qemu run-vm dep | 04:58:33 |
| colemickens | even weirder, it's a dep of an aarch64 output? | 05:00:54 |
| colemickens | /nix/store/giwwj37z3bv7zcd9np4h1475gv6v723x-h96maxv58-disko-images.drv
└───/nix/store/icdy400c78p77dmg953x9n0s9cd51x81-h96maxv58-disko-images.drv
└───/nix/store/mw0b87v5jir4lv9qk50h3dahqznqicmc-vm-run.drv
└───/nix/store/3sc1kz031fhjq0m6lk0dd96zb23c9jck-qemu-host-cpu-only-9.1.0.drv
└───/nix/store/wgyx5ghqdsy6zjr2f43bd1k53mbryiki-mesa-aarch64-unknown-linux-gnu-24.2.0.drv
└───/nix/store/wzab9w8ak2mafl1gxwi811lbc7pyjcgl-source.drv
| 05:00:57 |
| colemickens | error: a 'x86_64-linux' with features {} is required to build '/nix/store/wzab9w8ak2mafl1gxwi811lbc7pyjcgl-source.drv', but I am a 'aarch64-linux' with features {benchmark, big-parallel, gccarch-armv8-a, kvm, nixos-test}
| 05:01:13 |
| colemickens | odd, odd, odd. | 05:01:17 |
| colemickens | "aarch64-unknown-linux-gnu" looks like cross-comp but idk why | 05:02:10 |
| colemickens | I'm looking at how imageBuilderPkgs is defaulted/used and how host/buildPlatform are set for the system that includes this module and it seems like everything should be fine | 05:07:38 |
| colemickens | the next step would be vmTools, but also :/ I'm starting to doubt ? | 05:07:59 |
| colemickens | maybe this is vmTools use of buildPackages, and maybe I can just set customQemu and get around it | 05:14:34 |
| colemickens | well no that doesn't make sense, build and host is aarch64-linux. what the heck then. | 05:14:52 |
| colemickens | matthewcroughan: https://github.com/NixOS/nixpkgs/pull/325619 doesn't this kinda not work since ${qemu} is still used for making the empty disk image, etc? | 05:40:54 |
| colemickens | I'm so confused. If I build qemu_kvm or buildPackages.qemu_kvm it works, but if I build diskoImageScript it acts like it's crosscompiling from x86_64-linux. I've checked nixpkgs host/buildPlatform. :/ | 05:43:10 |
| colemickens | xargs cp :/ | 06:25:21 |
| colemickens | runs out of mem | 06:25:25 |
| colemickens | https://github.com/nix-community/disko/blob/e55f9a8678adc02024a4877c2a403e3f6daf24fe/lib/make-disk-image.nix#L200
💀 | 06:31:03 |
| colemickens | minus a couple small things, disko was great. got a gpt rk3588 uboot+roofs emmc image image, all automated with disko. | 07:47:18 |
| colemickens | truly much more pleasant that sdImage | 07:47:39 |
