From: Rich Salz rsalz@opengroup.org
Subject: multiple ethernet interfaces, naming
Date: Thu, 3 Jul 1997 19:40:10 -0400 [thread overview]
Message-ID: <19970703234010.doSdXFgpe5kdETIYDBMMpDBe7ZdP9G5AY_-6C9uzgYo@z> (raw)
>I'm even changing 9P,
Without knowing the details of your situation, I'll comment that this
is almost definitely a really bad thing to do. Don't sacrifice
interoperability.
next reply other threads:[~1997-07-03 23:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-07-03 23:40 Rich [this message]
-- strict thread matches above, loose matches on Subject: below --
1997-07-10 5:17 G.David
1997-07-08 19:03 forsyth
1997-07-08 14:15 Lucio
1997-07-08 13:59 G.David
1997-07-07 15:14 jmk
1997-07-07 14:53 presotto
1997-07-07 13:03 G.David
1997-07-03 23:05 beto
1997-07-03 20:32 presotto
1997-07-03 17:39 David
1997-07-03 16:32 G.David
1997-07-03 14:19 presotto
1997-07-03 13:34 G.David
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=19970703234010.doSdXFgpe5kdETIYDBMMpDBe7ZdP9G5AY_-6C9uzgYo@z \
--to=9fans@9fans.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).