Re: ifupdown maintenance

2024-07-10 Thread Simon Richter
Hi Ansgar, On 7/11/24 06:15, Ansgar 🙀 wrote: It is supported *now*, but the roadmap is unclear -- that support could be discontinued at any moment, and it would not be the first time a feature Debian relied on was removed. I understand your fears about the uncertainty of future developments.

Re: ifupdown maintenance

2024-07-10 Thread Marc Haber
On Wed, 10 Jul 2024 23:15:24 +0200, Ansgar ? wrote: >On Thu, 2024-07-11 at 05:14 +0900, Simon Richter wrote: >> It is supported *now*, but the roadmap is unclear -- that support could >> be discontinued at any moment, and it would not be the first time a >> feature Debian relied on was removed.

Re: default network management tools (was: ifupdown maintenance)

2024-07-10 Thread Marc Haber
On Wed, 10 Jul 2024 18:36:19 +0200, Bernd Zeimetz wrote: >yes please, I would love to see Debian switch from ifupdown to >NM/networkd. ifupdown was the perfect tool for the time it was created >in, but things have advanced, and imho now is a good time to switch. I agree. Nothing has yet reached t

Re: ifupdown maintenance

2024-07-10 Thread Vincent Bernat
On 2024-07-07 15:56, Daniel Gröber wrote: From where I'm sitting ifupdown2 is completely out of the question as *the* Debian ifupdown since it doesn't even support *basic* IPv6 use-cases like DHCPv6. Upstream community seems nonexistant since this is software by a corp for a corp where communit

Re: default network management tools

2024-07-10 Thread Thomas Goirand
On 7/10/24 20:03, Michael Biebl wrote: Since there is a lot of support for this idea, the next logical step as smcv said, would be to make d-i/netcfg networkd aware. At the beginning, this could be opt-in (for testing purposes) and we could make it the default later on. Any takers? If someo

Re: default network management tools

2024-07-10 Thread Thomas Goirand
On 7/9/24 12:45, Simon McVittie wrote: To some extent, we are already there: for new laptop/desktop installations, NM is already the default (certainly true for GNOME, and hopefully for most/all of the other tasksel-supported desktops). Right. For new server/embedded installations, I think ne

Re: ifupdown maintenance

2024-07-10 Thread Thomas Goirand
On 7/9/24 13:31, Simon McVittie wrote: I would tend to count "execute arbitrary user-supplied code on networking changes" as a specialized requirement - by definition, for this to happen, someone (the sysadmin) needs to have written and installed the user-supplied hook script. If the sysadmin has

Re: ifupdown maintenance

2024-07-10 Thread Ansgar 🙀
Hi Simon, On Thu, 2024-07-11 at 05:14 +0900, Simon Richter wrote: > It is supported *now*, but the roadmap is unclear -- that support could > be discontinued at any moment, and it would not be the first time a > feature Debian relied on was removed. I understand your fears about the uncertainty

Re: ifupdown maintenance

2024-07-10 Thread Simon Richter
Hi, On 7/10/24 05:36, Marco d'Itri wrote: That's my question, essentially: is this an interface with full support from upstream, or something that may change in an incompatible way later that will require us to deploy additional infrastructure to support? Multiple people, one of the systemd

Re: default network management tools

2024-07-10 Thread Michael Biebl
Am 10.07.24 um 18:36 schrieb Bernd Zeimetz: On Tue, 2024-07-09 at 11:45 +0100, Simon McVittie wrote: On Tue, 09 Jul 2024 at 10:57:39 +0200, Matthias Urlichs wrote:     Agreed: either it's drop-in compatible or we may as well switch the     default to NM and/or systemd-networkd. Well, here's

Re: default network management tools (was: ifupdown maintenance)

2024-07-10 Thread Bernd Zeimetz
On Tue, 2024-07-09 at 11:45 +0100, Simon McVittie wrote: > On Tue, 09 Jul 2024 at 10:57:39 +0200, Matthias Urlichs wrote: > >     Agreed: either it's drop-in compatible or we may as well switch > > the > >     default to NM and/or systemd-networkd. > > > > Well, here's a heretical thought: why don