public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Ford <david+cert@blue-labs.org>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: Kai Henningsen <kaih@khms.westfalen.de>,
	torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: Re: of ethernet names (was [PATCH] Futex Asynchronous
Date: Mon, 10 Jun 2002 19:46:23 -0400	[thread overview]
Message-ID: <3D053A4F.7010801@blue-labs.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0206091130490.13751-100000@home.transmeta.com> <8QbwdDPmw-B@khms.westfalen.de> <3D051DAF.6020107@mandrakesoft.com>

ifconfig is "so yesterday" as it is, ip is incredibly more capable.  I 
would gently push ifconfig into the dungeons of time.

-d

Jeff Garzik wrote:

> Actually, networking is moving in the direction described --
> yes, as Linus points out, we will need the magic ioctl stuff for back 
> compat.
> But the main way to communicate with a net device is netlink, already 
> a chardev.  ifconfig actually should be updated to use netlink.



  parent reply	other threads:[~2002-06-10 23:46 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-09 18:22 of ethernet names (was [PATCH] Futex Asynchronous Dr. David Alan Gilbert
2002-06-09 18:33 ` Linus Torvalds
2002-06-10 20:53   ` Kai Henningsen
2002-06-10 21:44     ` Jeff Garzik
2002-06-10 22:52       ` Brad Hards
2002-06-10 23:02         ` Jeff Garzik
2002-06-10 23:46       ` David Ford [this message]
     [not found] <0C01A29FBAE24448A792F5C68F5EA47D29DD32@nasdaq.ms.ensim.com>
2002-06-10 23:20 ` Paul Menage
2002-06-10 23:32   ` Brad Hards
2002-06-10 23:36     ` Randy.Dunlap
2002-06-11  0:11       ` Brad Hards
2002-06-11  2:25     ` Andi Kleen
2002-06-11  2:34       ` Brad Hards

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=3D053A4F.7010801@blue-labs.org \
    --to=david+cert@blue-labs.org \
    --cc=jgarzik@mandrakesoft.com \
    --cc=kaih@khms.westfalen.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    /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