From: rminnich@gmail.com (ron minnich)
Subject: [TUHS] Ethernet in /dev (was Re: Were all of you.. Hippies?)
Date: Thu, 30 Mar 2017 16:14:00 +0000 [thread overview]
Message-ID: <CAP6exYKrpe_FCZLeGNUYnJr3ch0-1Cxy4peCZTjZ6nGTJj3apg@mail.gmail.com> (raw)
In-Reply-To: <035c01d2a96f$6555ee00$3001ca00$@ronnatalie.com>
I have a slightly different take on all this, namely, that Unix as it was
worked, and that innovations in interfaces moved to another platform.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170330/f3afe5fb/attachment.html>
next prev parent reply other threads:[~2017-03-30 16:14 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 [this message]
2017-03-30 16:48 ` Joerg Schilling
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=CAP6exYKrpe_FCZLeGNUYnJr3ch0-1Cxy4peCZTjZ6nGTJj3apg@mail.gmail.com \
--to=rminnich@gmail.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;
as well as URLs for NNTP newsgroup(s).