From: schily@schily.net (Joerg Schilling)
Subject: [TUHS] Ethernet in /dev (was Re: Were all of you.. Hippies?)
Date: Thu, 30 Mar 2017 18:48:30 +0200 [thread overview]
Message-ID: <58dd36de.eTE7TJkq6BWTxw4q%schily@schily.net> (raw)
In-Reply-To: <1490889329.23882.for-standards-violators@oclsc.org>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1438 bytes --]
Norman Wilson <norman at oclsc.org> wrote:
> Josh Good:
>
> Which brings up a question I have: why didn't UNIX implement ethernet
> network interfaces as file names in the filesystem? Was that "novelty" a
> BDS development straying away from AT&T UNIX?
>
> ======
>
> Remember that UNIX has long been a family of systems;
> it's risky to make blanket statements!
>
> The following is from memory; I haven't looked at this
> stuff for a while and am a few kilometers from my
> manuals as I type this. I can dig out the complete
> story later if anyone wants it; for now, this is just
> the flavour and the existence proof.
>
> Research UNIX, once it supported Ethernet at all, did
> so using devices in /dev; e.g. /dev/qe0[0-7] were the
This is done on a UNIX implementation that uses STREAMS.
SVr4 is such a UNIX.
lrwxrwxrwx 1 root root 29 Mrz 3 2009 /dev/bge -> ../devices/pseudo/clone at 0:bge
lrwxrwxrwx 1 root root 38 Mrz 3 2009 /dev/bge0 -> ../devices/pci at 0,0/pci1462,6710 at b:bge0
/dev/bge is a clone device and allows to access and plumb further devices.
/dev/bge0 is the first Broadcom Gigabit Ethernet device.
Jörg
--
EMail:joerg at schily.net (home) Jörg Schilling D-13353 Berlin
joerg.schilling at fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/
URL: http://cdrecord.org/private/ http://sourceforge.net/projects/schilytools/files/
next prev parent reply other threads:[~2017-03-30 16:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-30 15:55 Norman Wilson
2017-03-30 16:05 ` Ron Natalie
2017-03-30 16:14 ` ron minnich
2017-03-30 16:48 ` Joerg Schilling [this message]
2017-03-30 19:24 Norman Wilson
2017-03-30 19:24 Norman Wilson
2017-03-30 22:11 ` Joerg Schilling
2017-03-31 4:39 ` arnold
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=58dd36de.eTE7TJkq6BWTxw4q%schily@schily.net \
--to=schily@schily.net \
/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).