Re: networking packages when using systemd

On Sunday, February 22nd, 2026 at 20: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

So, the new regime's cull has started.

Seriously though, is there some way, outside of reading the commit logs in great
detail, by which anyone, coming new to BLFS (and LFS I guess), might see a list 
of the "no longer maintained, as systemd has absorbed them into the monolith"
packages, so that such people would know that they had been there once, and
that their ghosts still linger on.

Maybe a dedicated plain text file, akin to the CHANGELOG-s, or is it thought
that that would be likely to grow too large to maintain? 

Having suggested the above, I suppose that, over time, as systemd absorbs 
yet more standalone, UNIX-pipeline-approach, utilities into one, monolithic, 
process, there won't even be a need for the BLFS Book, as everything will be
in the systemd that one installs in LFS? (Ha-ha!)

-- 
http://lists.linuxfromscratch.org/sympa/info/blfs-dev
Unsubscribe: See the above information page