| 8 Dec 2024 |
 @jj:envs.net | generally also i have not been able to find documentation! for exactly what options disko.devices is expecting, and what all sorts of everything are doing. like zpool is a separate disk from the main disks for some reason, but i have no idea why this is, or what i would read to find out why this is. same goes for what datasets etc are doing. any pointers in this area would be appreciated. | 07:03:39 |
|  Austin Horstman joined the room. | 18:36:30 |
|  thecowboyai set a profile picture. | 19:36:37 |
| 9 Dec 2024 |
 spewdins | can I use disko at all on macos | 07:21:15 |
| spewdins | like with apfs volumes | 07:21:25 |
 lassulus | well I never tested it, but I'm pretty sure no | 09:52:07 |
| lassulus | In reply to @blimbus:matrix.org
was also wondering if I have to specify drive names when using disko-install or if I can make it just use the ones in my config afaik disko-install should use the disks specified if not overwritten with --disk? | 09:54:40 |
| 10 Dec 2024 |
|  Andy Hamon joined the room. | 05:43:08 |
 Mic92 | no. disko requires all disks to be specified explicitly | 06:48:40 |
| Mic92 | *disko-install | 06:48:50 |
| Mic92 | It's because it allows users to flash storage devices that from a different computer without overwriting their own disks. | 06:49:45 |
| Mic92 | This is some sort of safety feature. | 06:50:00 |
|  BeatLink joined the room. | 12:52:44 |
| BeatLink | Hey guys, So i have a somewhat unusual problem. My laptop contains 2 drives. A root drive that's running NixOS and a data drive thats intended to store my documents, videos, pictures, etc
I want to use disko to manage the mounting of both on the running system but NixOS Anywhere should only format the root drive while leaving the data drive alone. The data drive should only be formatted via a dedicated bash script called "format-data-drive.sh"
I recalled somewhere in the documentation you can generate a format script from disko that can then be consumed by the NixOS anywhere script as an argument but i cant seem to find the documentation | 12:56:08 |
| BeatLink | my plan was basically to generate 2 seperate disko scripts. One for the root drive and one for the data drive. The former would be consumed by nixos anywhere, the latter by the data drive format script | 12:57:11 |
| BeatLink | Am i on the right path? | 12:57:15 |
| Mic92 | BeatLink: disko will only format the disks that you have configured. However I would use not generic names such as nvme0 but instead longer ids that contain the nvme serial numbers. Because nvmes might be not stable and change after reboot: lsblk --output NAME,ID-LINK,FSTYPE,SIZE,MOUNTPOINT | 19:51:17 |
| Mic92 | Just include your main drive for nixos-anywhere in your nixos configuration. and for your data partition use the disko cli | 19:52:12 |
| BeatLink | thanks | 19:52:42 |
| BeatLink | I wanted to also use disko to handle mounting the drive in the installed system | 19:52:55 |
| Mic92 | You will need to add a fileSystems entry in your nixos configuration for your data drive. | 19:53:01 |
| BeatLink | right | 19:53:07 |
| BeatLink | I've already went ahead and coded in my script to comment out the data drive during installation and uncomment it once the installation is complete | 19:53:34 |
| Mic92 | I guess that also works. | 19:53:48 |
| BeatLink | yeah, that way its disko all the way down | 19:54:08 |
| BeatLink | a bit risky tho, since if the script fails to comment the line, there goes my cat pictures lol | 19:54:23 |
| BeatLink | i have an off site backup setup tho so im not tooo worried | 19:54:41 |
| Mic92 | Still time consuming | 19:54:52 |
| BeatLink | yep | 19:54:58 |
| BeatLink | it would be great if disko took an argument with a list of which devices to ignore | 19:55:27 |
