Re: networking packages when using systemd
"Eric Clothier" ([email protected] via blfs-dev Mailing List) <[email protected]> Sun, 22 Feb 2026 15:47:45 -0500
| Newsgroups | gmane.linux.lfs.beyond.devel,gmane.linux.lfs.beyond.support |
|---|---|
| Message-ID | <CAAGwWFWD8xCm4i2GgVTR671gvhmDVtqg627P_ZmV+XaOjPsBmA@mail.gmail.com> |
On Sun, Feb 22, 2026, 15:40 Bruce Dubbs <[email protected]> wrote: > I am thinking about dropping the dhcpcd and bridge-utils from the > forthcoming version > of BLFS. They seem redundant and unneeded when using systemd-networkd. > > I am looking for opinions about this. > > Note that the current versions of these packages (they do not change > often) would > remain in the source and would be rendered for anyone building the System > V version > of BLFS. > > -- Bruce > > -- > Just my personal two-cents worth here, but when I run systemd, I tend to use systemd-networkd making dhcpcd or bridge-utils redundant and unneeded. With that being said, there are cases where they (or other networking programs such as ifupdown) can come in handy, such as when working with containerization or exotic networks. On the other hand, those use cases are far more rare and tend to have users that are more comfortable with branching out on their own, so dropping them from the default systemd BLFS render wouldn't seem an issue, in my opinion anyway. -- Eric -- http://lists.linuxfromscratch.org/sympa/info/blfs-dev Unsubscribe: See the above information page