From: Coywolf Qi Hunt <qiyong@fc-cn.com>
To: Mathieu Segaud <matt@regala.cx>
Cc: Erik Mouw <erik@harddisk-recovery.com>,
Karel Kulhavy <clock@twibright.com>,
linux-kernel@vger.kernel.org
Subject: Re: number of eth0 device
Date: Wed, 19 Oct 2005 19:36:53 +0800 [thread overview]
Message-ID: <20051019113653.GA3621@localhost.localdomain> (raw)
In-Reply-To: <87psq1da2j.fsf@barad-dur.minas-morgul.org>
On Wed, Oct 19, 2005 at 01:23:48PM +0200, Mathieu Segaud wrote:
> Erik Mouw <erik@harddisk-recovery.com> disait dernièrement que :
>
> > On Wed, Oct 19, 2005 at 12:31:35PM +0200, Karel Kulhavy wrote:
> >> I am looking into Documentation/devices.txt in 2.4.25 and eth0 is not listed
> >> there. If I grep "eth", I get only
> >>
> >> 38 char Myricom PCI Myrinet board
> >> [...]
> >> "This device is used for status query, board control and "user level
> >> packet I/O." This board is also accessible as a standard networking
> >> "eth" device. "
> >>
> >> and then
> >>
> >> /dev/pethr0
> >>
> >> Is eth0 some kind of special device that doesn't have any number
> >> assigned?
> >
> > Yes, there's no such thing as /dev/eth0, network interfaces have their
> > own namespace. Linux uses the defacto standard BSD socket interface for
> > networking, so blame the BSD people for violating the "everything is a
> > file" rule.
>
> well, the way NIC's behave kind of forbids this
> taken from Linux Device Drivers, 3rd Edition, page 497
> "The normal file operations (read, write, and so on) do not make sense
> when applied to network interfaces, so it is not possible to apply the
> Unix ''everything is a file'' approach to them"
I think there're other nodes in /dev on which normal file
operations do not make sense either.
--
Coywolf
-
next prev parent reply other threads:[~2005-10-19 11:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-19 10:31 number of eth0 device Karel Kulhavy
2005-10-19 10:42 ` Erik Mouw
2005-10-19 11:23 ` Mathieu Segaud
2005-10-19 11:36 ` Coywolf Qi Hunt [this message]
2005-10-19 19:34 ` Lee Revell
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=20051019113653.GA3621@localhost.localdomain \
--to=qiyong@fc-cn.com \
--cc=clock@twibright.com \
--cc=erik@harddisk-recovery.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@regala.cx \
/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