| 19 Jul 2024 |
 ElvishJerricco | Charles: If you want to test the 256 PR, I'm pretty sure you could import that branch separately and set systemd.package = otherPkgs.systemd; without rebuilding the world | 19:18:31 |
 Charles | okay, i might set that up later and report back uhhhh in 30 hours or something 'cause i'll be busy for most of tomorrow | 19:19:05 |
| ElvishJerricco | K900: We added autoPatchelfHook to systemd and added logic to the hook to detect .note.dlopen ELF notes and add those dependencies to rpath | 19:19:07 |
| ElvishJerricco | which allows us to remove our big ball of dlopen hacky patching from the systemd derivation, as well as better detect what binaries are needed in stage 1 | 19:20:14 |
 K900 | Mostly my concern is | 19:20:45 |
| K900 | staging-next is a matter of days | 19:20:59 |
| ElvishJerricco | oh is it/ | 19:21:40 |
| ElvishJerricco | * oh is it? | 19:21:41 |
| ElvishJerricco | hm | 19:21:42 |
| ElvishJerricco | I mean if we're going to go ahead without that review on the autoPatchElf changes, I think the systemd changes are ready to merge. I ran all the systemd nixos tests and everything succeeds | 19:22:32 |
| ElvishJerricco | * I mean if we're going to go ahead without that review on the autoPatchElfHook changes, I think the systemd changes are ready to merge. I ran all the systemd nixos tests and everything succeeds | 19:22:46 |
| K900 | staging-24.05 merged today | 19:23:46 |
 Rémy Grünblatt | In reply to @k900:0upti.me
Like, NixOS as SNMP (netconf, whatever) server? Nah, interacting with NixOS using netconf | 19:26:14 |
| K900 | Well yes, that's what I meant | 19:26:38 |
| Rémy Grünblatt | I mean, netconf provides basic operations (get-config, edit-config, …) | 19:26:49 |
| Rémy Grünblatt | the nixos options are tree-like | 19:27:01 |
| K900 | I don't think that's applicable to NixOS config | 19:27:05 |
| K900 | And even then semantically it expects those options to apply immediately which is just not a thing | 19:27:24 |
| Rémy Grünblatt | the result messages would be delayed, yes | 19:28:00 |
| 20 Jul 2024 |
|  FHD joined the room. | 11:19:09 |
| 21 Jul 2024 |
|  @hanleym:matrix.org left the room. | 11:46:07 |
| 22 Jul 2024 |
|  ·☽•Nameless☆•777 · ± changed their profile picture. | 14:26:32 |
| 23 Jul 2024 |
|  Ezzobir Bezziou joined the room. | 08:21:00 |
| 24 Jul 2024 |
|  Redstone changed their display name from redstone-menace to Redstone. | 10:15:57 |
| 25 Jul 2024 |
|  bumperboat changed their display name from bumperboat (UTC+2) to bumperboat. | 12:47:23 |
| 26 Jul 2024 |
|  71rd joined the room. | 11:44:24 |
 steveej | after a recent update on 24.05 one of my nixos containers has broken networking, because the host ve interface isn't assigned its hostAddress. this is with privateNetworking = true. two interesting findings
- 2 out of 3 containers still work as expected
- all 3 host interfaces have additional private IP addresses in private subnets that i cannot identify
| 14:31:13 |
| steveej | looks like this on the host:
# ip -4 a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
altname eno1
altname enp2s0
inet 192.168.22.99/24 metric 1024 brd 192.168.22.255 scope global dynamic eth0
valid_lft 37388sec preferred_lft 37388sec
55: ve-syncthing@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link-netnsid 0
inet 169.254.29.205/16 metric 2048 brd 169.254.255.255 scope link ve-syncthing
valid_lft forever preferred_lft forever
inet 192.168.242.17/28 brd 192.168.242.31 scope global ve-syncthing
valid_lft forever preferred_lft forever
inet 192.168.100.14/32 scope global ve-syncthing
valid_lft forever preferred_lft forever
56: ve-mailserver@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link-netnsid 1
inet 169.254.2.234/16 metric 2048 brd 169.254.255.255 scope link ve-mailserver
valid_lft forever preferred_lft forever
inet 192.168.170.97/28 brd 192.168.170.111 scope global ve-mailserver
valid_lft forever preferred_lft forever
inet 192.168.100.10/32 scope global ve-mailserver
valid_lft forever preferred_lft forever
95: ve-webserver@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link-netnsid 2
inet 169.254.243.68/16 metric 2048 brd 169.254.255.255 scope link ve-webserver
valid_lft forever preferred_lft forever
inet 192.168.88.17/28 brd 192.168.88.31 scope global ve-webserver
valid_lft forever preferred_lft forever
the ve-webserver interace is lacking the 192.168.100.XX ip which is configured via hostAddress via the config
| 14:36:06 |
| steveej | renaming the container to web helped. there must be some impure state hogging on the ve-webserver interface | 16:08:48 |
| 27 Jul 2024 |
|  captainrob joined the room. | 00:19:56 |
