Chris Hofstaedtler <z...@debian.org> wrote on 23/09/2024 at 12:25:15+0200:
> * Pierre-Elliott Bécue <p...@debian.org> [240923 11:34]: >> Lukas Märdian <sl...@debian.org> wrote on 20/09/2024 at 13:12:36+0200: >> > # Why >> > The ifupdown package is a Debian only solution that is becoming a >> > maintenance >> > burden. We've had plenty of discussions over the years and consensus is >> > that we >> > want to get rid of it. >> >> I like ifupdown. It's simple and just works. > > I find this quite funny, given a recent discussion about IPv6 dad > issues with ifupdown on #debian-admin. Still looking for the funny bit, except if you're implying that as a DSA member, I should dislike ifupdown because Philipp had to manually intervene on a server managed by it. In that case it'd indeed be really funny, but probably not for the reason you'd think it is. > It's certainly limited in what it can do within reasonable > configuration effort, and it often works. I think both are true for > almost all of the discussed options :-) Well, netplan has no added value in my environments, contrary to some big changes we had in the past (systemd, journald - which still forwards logs to rsyslog, …), so I'd rather not being force-fed this tool. I'd react the same if someone were to try making me adopt resolved or timesyncd. But in the whole, I don't care that much, I'm perfectly fine with apt purge netplan.io after bootstrapping a server if the "consensus" is to force-feed it. -- PEB
signature.asc
Description: PGP signature
