| 18 Mar 2025 |
 ElvishJerricco | oh shit I have to document that type I factored out into lib now don't I | 23:44:26 |
| 19 Mar 2025 |
|  @jkxyz:matrix.org left the room. | 16:17:35 |
|  Contact @rappet:rappet.xyz instead changed their profile picture. | 23:12:01 |
| 20 Mar 2025 |
| ElvishJerricco | So this is interesting: https://github.com/NixOS/nixpkgs/pull/391329 | 06:39:13 |
| ElvishJerricco | I had assumed that this is covered by boot.kernel.sysctl. But I guess sysfs and sysctl do slightly different things? | 06:39:40 |
 @msanft:matrix.org | I thought that it's just a different interface to the same thing. | 08:09:04 |
| ElvishJerricco | Moritz Sanft: That's kinda what I thought but... I think that might be wrong? Seems like sysctl is for /proc/sys, not /sys, and apparently those are meaningfully different? | 08:32:58 |
| @msanft:matrix.org | Just learned that too. But it kind of makes sense. You don't find e.g. device info in /proc/sys, while you do in /sys | 08:52:08 |
 Ramses 🇵🇸 | Yeah, a lot of drivers expose things under /sys/class where you can write to files to configure stuff | 09:25:15 |
| Ramses 🇵🇸 | A lot of those things are only present when the device has been loaded though, so I feel that we'd need something more dynamic than a single systemd-tmpfiles invocation. I use path units myself to trigger writing to such files when they appear | 09:26:19 |
| ElvishJerricco | that sounds more like a udev thing then, doesn't it? | 09:26:41 |
