From: Xose Vazquez Perez <xose.vazquez@gmail.com>
To: netdev@vger.kernel.org
Subject: [Fwd: net-tools future]
Date: Sat, 28 Mar 2009 14:14:57 +0100 [thread overview]
Message-ID: <49CE22D1.6090109@gmail.com> (raw)
-------- Original Message --------
Subject: net-tools future
Date: Sun, 15 Mar 2009 17:30:18
From: Martín Ferrari <tincho@debian.org>
To: debian-devel@@lists.debian.org
Hi,
Luk Claes and me, as the current maintainers of net-tools, we've been
thinking about it's future. Net-tools has been a core part of Debian and
any other linux based distro for many years, but it's showing its age.
It doesnt support many of the modern features of the linux kernel, the
interface is far from optimal and difficult to use in automatisation,
and also, it hasn't got much love in the last years.
On the other side, the iproute suite, introduced around the 2.2 kernel
line, has both a much better and consistent interface, is more powerful,
and is almost ten years old, so nobody would say it's untested.
Hence, our plans are to replace net-tools completely with iproute, maybe
leading the route for other distributions to follow. Of course, most
people and tools use and remember the venerable old interface, so the
first step would be to write wrappers, trying to be compatible with
net-tools.
At the same time, we believe that most packages using net-tools should
be patched to use iproute instead, while others can continue using the
wrappers for some time. The ifupdown package is obviously the first
candidate, but it seems that a version using iproute has been available
in experimental since 2007.
So, the roadmap would be:
- Send patches to net-tools using packages to use iproute instead
- Development of the wrapper scripts
- Uploading to experimental a net-tools-compat package, to allow wider
testing.
- Upload to unstable
About the wrapper scripts:
* ipconfig, route: the most difficult ones, both can be replaced by
calls to "ip", maybe except for some obscure options.
* netstat : sstat provides almost the same information, just some
formatting changes and parsing the command line
* rarp should be dropped, as the linux kernel doesn't support it
anymore, since the 2.3 series. The replacement, arpd, is already
included in iproute.
* ipmaddr works exactly as "ip maddr", in fact, the code is from the
iproute sources. Same for iptunnel and "ip tunnel". In both cases,
they're just replaced by a symlinkm, as the ip command recognises that.
* nameif: can be replaced by "ip link", not sure if it's worth the
effort (does anybody actually use it?)
Problematic tools:
* mii-tool: it could be dropped and replaced by a pointer to ethtool as
it's not meant to be used automatically by scripts. On the other hand,
it's distributed as a stand-alone tool [0] and we could do the same.
* plipsetup, slattach: we don't know of any replacement for those, but
could be distributed separately too. Also, it's dubious if anyone still
uses them.
0: http://freshmeat.net/projects/mii-tool/
--
Martín Ferrari <tincho@debian.org>
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
---end---
next reply other threads:[~2009-03-28 13:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-28 13:14 Xose Vazquez Perez [this message]
2009-03-28 13:32 ` [Fwd: net-tools future] Xose Vazquez Perez
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49CE22D1.6090109@gmail.com \
--to=xose.vazquez@gmail.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).