Hi Lorenzo et al., On Mon, Jun 02, 2025 at 12:25:41AM +0200, Lorenzo wrote: > What is the default replacement for the client? and for the server? > I looked at the discussion on -devel and I'm still unsure.. > dhcpcd-base + dhcpcd and kea? > without this info I'm not able to decide what to do for runit-services; > there are 3 services for isc-*, two in bookworm, and none for > alternatives so I guess it will be a regression for runit users.
I don't think runit-services needs to do anything except remove at leisure the service definitions for packages that have already been removed from the archive? A service directory for the server replacements would be nice instead of fallback to initscript of course. Personally I'm not using the replacements so don't have one to contribute yet. And I wouldn't expect new clients to get added unless they have service definitions for other init systems, as ifupdown etc. are the way to use them generally - hence the disablement of the dhclient service directory previously. > Overall I think it would work better if the removal is done at the > beginning of the forky cycle. A release note could help pushing users > towards alternatives and leave us a proper time to test the new > defaults. Could you reconsider? I'm glad this seems to have been the decision lower down the thread. Personally I will miss both the server and the client. I don't like the way the replacement client (so far as I am aware) combines IPv4 and IPv6 behaviour when they are mostly independent concerns. Andrew
