| 24 Feb 2025 |
 Arian | we already have that. image.repart.definitions includes toplevel but systemd.repart.definitions does not | 22:12:55 |
| Arian | it’s a bit hacky but can make it work ? | 22:13:00 |
 @elvishjerricco:matrix.org | oh, ok | 22:13:09 |
| @elvishjerricco:matrix.org | well I'm definitely interested in this | 22:13:17 |
|  Saturn changed their profile picture. | 22:36:11 |
| 25 Feb 2025 |
 @marie:marie.cologne | could someone here have a look at this?
https://github.com/NixOS/nixpkgs/pull/372979
would be nice to have this working in the next release, and we should make sure this doesn't lock anyone out with the ssh changes | 10:16:18 |
| 26 Feb 2025 |
 @srestegosaurio:tchncs.de | In reply to @arianvp:matrix.org
so we can use systemd.repart.partitions as a full replacement for fileSystems What advantages could it have? Or is this related to a specific usecae? | 06:03:55 |
| Arian | The main complaint about nixos that I hear from people is that it's too much like arch Linux and gentoo. The fact that our manual spends the first whole chapter telling you to type manual partitioning commands into a cli is terrible sales pitch | 08:21:49 |
| Arian | What if we have a partition scheme that just is nix code and then takes care of both partitioning your disk and mounting your disks once installed. Suddenly you can replace the entire first chapter with 4 lines of nix | 08:22:29 |
| Arian | That's the usecase | 08:22:42 |
 K900 | Isn't that just disko | 08:22:46 |
| K900 | And also like | 08:22:48 |
| K900 | We have a GUI installer? | 08:22:50 |
| K900 | Maybe we should advertise that more | 08:23:07 |
| Arian | Yes disko does the same. But it's not upstreamed yet. But I'm a bit more fan of repart's model | 08:23:52 |
| Arian | As it also runs during runtime. So can extend partitions etc. Add new ones | 08:24:28 |
| Arian | The repart stuff is in nixos. Disko is not. | 08:25:09 |
| Arian | Also Disko is not part of nixos-install | 08:25:18 |
| Arian | Nothing against the creators of Disko. But I want less shell code running during activation time not more. We've been on a slow but steady quest to replace all of activation scripts with systemd-native alternatives to support shipping nixos images that have no interpreters shipped whatsoever | 08:27:33 |
| Arian | So to me repart would be the natural first choice | 08:27:51 |
| Arian | But sleeping on it for a night the fstab generation is not that exciting lol. As we don't generate fstab at activation time. We generate it at build time already.
Still think we should have a nice way of defining partitions and fileSystems in a single DSL though | 08:29:32 |
| Arian | * But sleeping on it for a night the fstab generation is not that exciting lol. As we don't generate fstab at activation time. We generate it at build time already. So we could just generate it from the repart nix options
Still think we should have a nice way of defining partitions and fileSystems in a single DSL though | 08:29:55 |
|  raf joined the room. | 13:53:50 |
| raf | Hello,
I would like to open a pull request to move systemd-resolved service (services.resolved) to a RFC-42 compliant .settings format as the current service options are a little ambiguous: some resolved options have options, but others are forced to be put into extraConfigs, which is confusing.
Is there a specific process for such a change?
| 13:56:56 |
| raf | Or can I go ahead with the pull request, and hope maintainers for the service are able to take a look? | 13:58:44 |
 Ramses 🇵🇸 | raf: just a PR should be fine | 15:10:59 |
| raf | I'll open one soon, thank you | 19:29:27 |
| 27 Feb 2025 |
|  jasper joined the room. | 12:15:49 |
| 28 Feb 2025 |
 jade_ | In reply to @arianvp:matrix.org
The main complaint about nixos that I hear from people is that it's too much like arch Linux and gentoo. The fact that our manual spends the first whole chapter telling you to type manual partitioning commands into a cli is terrible sales pitch given i just archlinux'd another nixos box today partitioning wise, i will say at least this flow is really nice, you do basically whatever you want and it spits out a config that works. the fact that our stuff is this good that you don't have to figure out how to describe zfs inside luks to a DSL is kinda nice in a sense.
but also yeah. eugh. idk. having to discover how to tell the dsl to do the right thing is also hard.
| 04:21:24 |
| jade_ | the fact that i can use the arch wiki and just type in some stuff and have it work is nice. but it is utterly goofy that our first chapter in the docs doesn't just say "use the graphical installer" | 04:22:05 |
