Re: ifupdown/dhcp

2022-05-16 Thread Steve Langasek
On Mon, May 16, 2022 at 08:46:04PM +0200, Ben Hutchings wrote: > On Sun, 2022-05-08 at 22:07 +0200, Steve Langasek wrote: > [...] > > Ubuntu no longer uses isc-dhcp by default, because it no longer uses > > ifupdown; NetworkManager and networkd both have their own implementations of > > dhcp

Re: ifupdown/dhcp

2022-05-16 Thread Ben Hutchings
On Sun, 2022-05-08 at 22:07 +0200, Steve Langasek wrote: [...] > Ubuntu no longer uses isc-dhcp by default, because it no longer uses > ifupdown; NetworkManager and networkd both have their own implementations of > dhcp clients which are used by preference. *However*, isc-dhcp is still >

Re: ifupdown/dhcp

2022-05-08 Thread Diederik de Haas
On Sunday, 8 May 2022 21:34:39 CEST Michael Tokarev wrote: > What's up with ISC dhclient? "ISC DHCP Client and Relay End of Maintenance" @ https://www.isc.org/blogs/dhcp-client-relay-eom/ Couple of quotes: "ISC plans to end maintenance of the ISC DHCP client and relay by the end of Q1, 2022."

Re: ifupdown/dhcp

2022-05-08 Thread Raymond Burkholder
On 2022-05-08 2:07 p.m., Steve Langasek wrote: On Sun, May 08, 2022 at 11:24:12AM -0400, Michael Stone wrote: I've been trying to make sense of the NEWS item in isc-dhcp-client (that alternatives are needed) in combination with the functionality of ifupdown and what the implications are for

Re: ifupdown/dhcp

2022-05-08 Thread Michael Hudson-Doyle
On Mon, 9 May 2022 at 08:07, Steve Langasek wrote: > On Sun, May 08, 2022 at 11:24:12AM -0400, Michael Stone wrote: > > [apologies to package aliases getting this twice due to autocomplete > fail] > > > I've been trying to make sense of the NEWS item in isc-dhcp-client (that > > alternatives are

Re: ifupdown/dhcp

2022-05-08 Thread Steve Langasek
On Sun, May 08, 2022 at 11:24:12AM -0400, Michael Stone wrote: > [apologies to package aliases getting this twice due to autocomplete fail] > I've been trying to make sense of the NEWS item in isc-dhcp-client (that > alternatives are needed) in combination with the functionality of ifupdown > and

Re: ifupdown/dhcp

2022-05-08 Thread Michael Tokarev
08.05.2022 18:24, Michael Stone wrote: [apologies to package aliases getting this twice due to autocomplete fail] I've been trying to make sense of the NEWS item in isc-dhcp-client (that alternatives are needed) in combination with the functionality of ifupdown and what the implications are

Re: ifupdown/dhcp

2022-05-08 Thread Jeremy Stanley
On 2022-05-08 21:15:07 +0200 (+0200), Santiago Ruano Rincón wrote: > OpenBSD maintains its own fork of dhclient, just to list another > alternative. [...] Though OpenBSD added dhcpleased[*] last year, so I expect dhclient's days there are numbered too. [*]

Re: ifupdown/dhcp

2022-05-08 Thread Santiago Ruano Rincón
El 08/05/22 a las 11:24, Michael Stone escribió: > [apologies to package aliases getting this twice due to autocomplete fail] > > I've been trying to make sense of the NEWS item in isc-dhcp-client (that > alternatives are needed) in combination with the functionality of ifupdown > and what the

Re: ifupdown/dhcp

2022-05-08 Thread Daniel Gröber
Hi Michael, On Sun, May 08, 2022 at 11:24:12AM -0400, Michael Stone wrote: > So what's the path forward, maintaining compatibility and not breaking > systems upgrading from current stable? Do we come up with a dhcpcd5 variant > that *only* touches interfaces it is directed to touch via >

ifupdown/dhcp

2022-05-08 Thread Michael Stone
[apologies to package aliases getting this twice due to autocomplete fail] I've been trying to make sense of the NEWS item in isc-dhcp-client (that alternatives are needed) in combination with the functionality of ifupdown and what the implications are for debian upgrades generally.