9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: nigel@9fs.org
To: 9fans@cse.psu.edu
Subject: Re: [9fans] /net/ip*
Date: Fri, 26 Jan 2001 14:42:29 +0000	[thread overview]
Message-ID: <E14MA57-0005YF-0U@anchor-post-30.mail.demon.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 42 bytes --]

If I were Russian, I might say "niet".


[-- Attachment #2: Type: message/rfc822, Size: 1569 bytes --]

From: splite@purdue.edu
To: 9fans@cse.psu.edu
Subject: Re: [9fans] /net/ip*
Date: Fri, 26 Jan 2001 09:34:28 -0500
Message-ID: <20010126093428.A4563@sigint.cs.purdue.edu>

On Thu, Jan 25, 2001 at 07:23:35PM -0500, presotto@plan9.bell-labs.com wrote:
> The way to build a nat with plan 9 is to set up 2 ip stacks, open

Not to pick a nit, but should a nut with a Gnot on the 'net build a nat?

             reply	other threads:[~2001-01-26 14:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-26 14:42 nigel [this message]
2001-01-26 14:52 ` Boyd Roberts
  -- strict thread matches above, loose matches on Subject: below --
2001-01-26 15:02 nigel
2001-01-26 15:02 nigel
2001-01-26  0:23 presotto
2001-01-26 14:34 ` splite
2001-01-25 22:40 Latchesar Ionkov

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=E14MA57-0005YF-0U@anchor-post-30.mail.demon.net \
    --to=nigel@9fs.org \
    --cc=9fans@cse.psu.edu \
    /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).