From: Lee Revell <rlrevell@joe-job.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 15:34:14 -0400 [thread overview]
Message-ID: <1129750454.5203.19.camel@mindpipe> (raw)
In-Reply-To: <87psq1da2j.fsf@barad-dur.minas-morgul.org>
On Wed, 2005-10-19 at 13:23 +0200, Mathieu Segaud wrote:
> 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"
>
Ditto sound cards, which is why ALSA abandoned the OSS "everything is a
file" paradigm for sound cards. Read/write etc. don't take into account
the inherent realtime constraints in streaming audio to/from a device.
Lee
prev parent reply other threads:[~2005-10-19 20:04 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
2005-10-19 19:34 ` Lee Revell [this message]
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=1129750454.5203.19.camel@mindpipe \
--to=rlrevell@joe-job.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.