On Thu, Aug 15, 2024 at 12:30:22PM -0500, G. Branden Robinson wrote: > At 2024-08-15T13:20:02-0400, Michael Stone wrote: > > > This change was noted in NEWS. > > > > > > I would suggest hooking your config into something that uses the > > > network-online.target target, with a timeout like network-manager > > > and networkd do, so that the boot process doesn't hang. If it's a > > > simple unit, it's enough to add RuntimeMaxSec= to it, so that it's > > > killed if it doesn't work within the configured timeout. > > > > It's just so depressing that this is how debian works now. We used to > > try to not break things, now the answer is "you should have read the > > NEWS, and known that unrelated packages were going to break, and > > reconfigured standard debian network tools to add non-default > > timeouts". All because the aesthetic preference for not having the > > same binary appear in two different paths is a higher priority than > > keeping systems working. > > "Move fast and break as much stuff as possible, or Debian will be doomed > to irrelevance. I'll be SABDFL someday!" > > The creed of the _impactful_ developer.
It looks like a pretty pointless change - breaks several scripts for example. It was/is common to assume /sbin/ip to be present and usable. Michael's bug report does make sense to me. Such a change is even causing systems to not bootup. Best, Nilesh
signature.asc
Description: PGP signature
