List Archive: gentoo-dev
Note: Due to technical difficulties, the Archives are currently not up to date.
provides an alternative service for most mailing lists.c.f. bug 424647
On Fri, 11 Nov 2011 15:53:44 -0600
William Hubbs <firstname.lastname@example.org> wrote:
> Hi all,
> has prompted a discussion of whether or not we should use ifconfig
> in openrc to configure networking on linux systems.
> I'm not asking that we consider removing net-tools from systems,
> because there are tools there that we still need. In my view
> though, two of these tools (ifconfig and route), have been
> surpassed in functionality by iproute2's ip tool. So, what I am
> considering doing is dropping the ifconfig module from openrc and
> using iproute2 for all network configuration on linux systems.
> The other side of the discussion seems to be that openrc needs to
> work on minimal installations, so we need to continue supporting
> using ifconfig.
> I realize there would be a trade-off if I stop supporting linux's
> ifconfig and route in openrc, but how much of a trade-off? Would the
> benefits of iproute2 outweigh the down side of not supporting
> ifconfig and route on linux?
> What does everyone think?
i'm in favor of whatever doesn't force me and our users to install
Yet Another Tool besides what's in the system set, and whatever
doesn't result in a LOT of work for the GDP to update all of our
documentation. there are dozens of places in all the docs that refer
to ifconfig and the other utilities installed with
i'd really prefer it if i didn't have to learn a whole new set of
tools & syntax, and then had to rewrite all of our docs for them.
ifconfig and net-tools work as-is; i've yet to see a compelling case
for installing & learning iproute.
if net-tools isn't being dropped from the system set, don't force our
users to install redundant utilities.