| 12 Nov 2025 |
 lassulus | they are not getting formatted if you add disko, but they will get mounted according to it | 07:21:57 |
| lassulus | so if you add something that is not what you currently have, you could not boot it | 07:22:16 |
| lassulus | but rollback should still work in that case | 07:22:23 |
 Chris P Bacon | so besides not being able to boot (which I could solve with a live-usb and mounting manually), there are no dangers to my data when adopting disko? cool! | 07:23:59 |
| lassulus | well there is also rollback when booting, you can just boot an older generation without the usb | 07:27:56 |
| lassulus | but disko is not run automatically, only nixos-anywhere or disko-install is running disko | 07:28:17 |
| lassulus | or if you run it manually | 07:28:21 |
| Chris P Bacon | ooooooooooh, gotcha | 07:28:41 |
| Chris P Bacon | awesome, tnx! | 07:28:48 |
| lassulus | a downside of that model is: if you add new volumes, pools, mount or something in your disko config, it will not automatically apply without reinstalling | 07:29:33 |
| lassulus | in theory you can run the format script again, it has some checks to not delete data | 07:29:58 |
| lassulus | but that is not super tested, so better do it with backups | 07:30:10 |
| Chris P Bacon | Agreed. That is also not my goal. what I want to do is to migrate my current snowfall based config for my machines at home to a clan based one, and the only hurdle I saw was the adoption of disko. But knowing that disko is not really ran outside of install or manual invocations I can happily do my migration. If and when I ever do end up reconfiguring my disk I get it that the best course of action is to first to a backup, but then again, this would have been the flow if I'd done it all manually anyway! So again, thanks for dispelling my worries! | 07:35:57 |
|  Inayet changed their display name from inayet to Inayet. | 12:38:55 |
| 13 Nov 2025 |
|  @brian:bmcgee.ie left the room. | 09:40:01 |
|  debtquity joined the room. | 20:24:28 |
| 18 Nov 2025 |
|  jopejoe1 (4094@39c3) changed their display name from jopejoe1 to jopejoe1 (4094@39c3). | 20:18:55 |
|  dave :3 joined the room. | 22:59:07 |
| 19 Nov 2025 |
|  tioan joined the room. | 23:45:13 |
| 20 Nov 2025 |
|  redesign your logo changed their display name from seaweed salad to Juggalo Championship Wrestling. | 03:38:05 |
|  John joined the room. | 05:36:58 |
|  @rbtmcl:matrix.org joined the room. | 14:09:33 |
| @rbtmcl:matrix.org | Seems, I am running into the same issue. @brian:bmcgee.ie did you figure out some work around? | 14:16:29 |
| @rbtmcl:matrix.org removed their display name Robert Michael. | 14:17:38 |
|  luna joined the room. | 18:22:14 |
| luna | I'm looking into flake-parts and saw that disko has a module definition for it, but now I'm wondering what the benefit of that over the NixOS module is? will it even apply all the same NixOS config (filesystems etc) that the NixOS module does? | 18:25:10 |
| 21 Nov 2025 |
 blimbus | It allows you to output disko configs from your flake which can be useful for some. You still need the nixos module for the real functionality. | 02:14:49 |
| redesign your logo changed their display name from Juggalo Championship Wrestling to 9PM (Till I Come). | 05:51:13 |
| redesign your logo changed their display name from 9PM (Till I Come) to Juggalo Championship Wrestling. | 06:21:38 |
| luna | I see, so how would I apply a disko config from a flakes diskoConfigurations to my nixos config? | 17:33:51 |
