On Mon, 2024-02-05 at 15:17 -0500, Felix Miata wrote:
Martin Wilck composed on 2024-02-05 14:41 (UTC+0100):
On Mon, 2024-02-05 at 08:32 +0100, Antonio Feijoo Factory wrote:
The following requirement was already added for 15.5:
``` Requires: (iputils or arping2 or wicked) ```
But yes, maybe it does no make much sense for desktop-only use cases.
this would only trigger if someone had neither iputils nor arping2 nor wicked installed. It is important because network device bringup in the initrd may fail without it. We can't simply remove it.
I guess we can add NetworkManager in the list (I am not sure what NM uses to check for duplicate address detection; but if NM is in use, I don't think we'll use the network-legacy dracut module, right?)
I can't see how that would help here. I thought I made it evident in OP that neither NM nor Wicked are installed, thus can't be responsible for network setup here. systemd-networkd.socket is all I have explicitly enabled to bring up networking.
Yeah, that would be another exception. And connman, too ;-) The point is, you don't need networking for booting. But other people do, and their systems may fail to boot if no tool for DAD exists. IMO we'd better make sure such boot failures don't occur, even if this means that some people have to install iputils (size 550k, and generally a quite useful package) or arping2 (size 67k). As mentioned, we can split off a dracut-networking package which people who don't need network boot can uninstall together with its dependencies. But we will need to install that package by default, unless we figure out a reliable way to figure out *on the package management level* whether or not network boot capability is required. Regards Martin