| 21 Aug 2024 |
 matthewcroughan @fosdem | Redacted or Malformed Event | 16:56:45 |
|  egor changed their profile picture. | 17:43:11 |
| 22 Aug 2024 |
|  nyanbinary 🏳️⚧️ left the room. | 17:20:34 |
| 23 Aug 2024 |
|  @benjaminedwardwebb:envs.net left the room. | 18:57:13 |
| 25 Aug 2024 |
|  🎈 Always changed their display name from wieldable9080 to 🎈 Always hard to find my messages. | 05:22:12 |
| 🎈 Always set a profile picture. | 05:22:36 |
|  nbrr joined the room. | 10:34:14 |
| nbrr | Hi! Looking to use disko and I have a few questions:
- It seems guides on the disko repo are for new installs. Is there something about using disko for an existing install?
- Do I have to describe all existing disks with disko or can I just use disko for a single new drive I'm adding?
- I want to declare a disk with a couple of btrfs subvolumes. If I ever want to add more subvolumes, can I just add it to the disko declaration and have it perform the operation?
| 10:54:21 |
 lassulus | disko works for already installed systems, although writing a disko configuration is a bit more involved than declaring fileSystems.* so there wouldn't be much real gain. You can define many disks and btrfs subvolumes and you can rerun the creation step and it "should" just add the new subvolumes. although that is a new and untested feature, so use it with care (and backups) | 12:38:53 |
|  sylkos joined the room. | 14:58:41 |
 Raj | Is there any work ongoing to support multi-disk filesystems? | 15:06:30 |
| lassulus | We have support for some of those I think? Which one are you thinking of? | 15:20:04 |
