9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Bruce Ellis <bruce.ellis@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] The mother-of-all-gnot?
Date: Thu,  5 Jan 2006 23:24:32 +1100	[thread overview]
Message-ID: <775b8d190601050424u7e2e00f8xf1a54a9a98e346fd@mail.gmail.com> (raw)
In-Reply-To: <20060105032249.FRUX5113.ibm64aec.bellsouth.net@p1.stuart.org>

sorry, i've had a very eventful (last) year so ozinferno ain't out yet.
sorry that i'm actually testing it and fixing bugs.  garbage collection
is now another order of magnitude more efficient.  there is still one
nasty which i have tracked but not fixed.

brucee

On 1/5/06, Brian L. Stuart <blstuart@bellsouth.net> wrote:
> In message <63349e4f7ae73a58077654a3cd628027@vitanuova.com>, C H Forsyth writes
> :
> >>Speaking of such things.  Is there NAT support in either Plan 9
> >>or Inferno?  I looked around and if it's there, I'm missing it.
> >
> >i had a quick look at the archives but couldn't find the right article.
> >still, a previous time this was discussed, i think it was stated
> >by <deleted> that the nat code hadn't been released because it was considered
> >at the time to compete with a lucent product <deleted>
>
> Oh well.  I had thought it would be fun to change my router/NAT
> box over to Inferno from an old Linux install.  But I guess it'll
> have to wait.
>
> Thanks,
> BLS
>


  reply	other threads:[~2006-01-05 12:24 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-03 18:03 Skip Tavakkolian
2006-01-03 17:15 ` Bruce Ellis
2006-01-03 17:25   ` jmk
2006-01-03 17:31     ` Bruce Ellis
2006-01-03 17:46     ` Dan Cross
2006-01-03 17:55       ` jmk
2006-01-03 17:58       ` Paul Lalonde
2006-01-03 18:06         ` Bruce Ellis
2006-01-03 19:07         ` Skip Tavakkolian
2006-01-03 18:16           ` Bruce Ellis
2006-01-03 18:30           ` Paul Lalonde
2006-01-03 18:37             ` Bruce Ellis
2006-01-04  3:54               ` Brian L. Stuart
2006-01-04  5:21                 ` Bruce Ellis
2006-01-04  5:44                   ` Bruce Ellis
2006-01-04 10:59                 ` C H Forsyth
2006-01-04 11:02                   ` Bruce Ellis
2006-01-05  3:21                   ` Brian L. Stuart
2006-01-05 12:24                     ` Bruce Ellis [this message]
2006-01-06  5:28                       ` Jeff Sickel
2006-01-06 15:52                         ` Bruce Ellis
2006-01-03 20:07             ` Skip Tavakkolian
2006-01-03 19:32               ` Bruce Ellis
2006-01-03 20:42                 ` Skip Tavakkolian
2006-01-03 19:55               ` Paul Lalonde
2006-01-03 20:08                 ` Bruce Ellis
2006-01-03 20:10                 ` jmk
2006-01-03 20:33                   ` Christoph Lohmann
2006-01-09  7:21                   ` Gorka guardiola
2006-01-09  8:25                     ` Skip Tavakkolian
2006-01-09 14:30                       ` andrey mirtchovski
2006-01-09 14:32                         ` Sape Mullender
2006-01-03 20:04     ` lucio
2006-01-05 16:15 jmk

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=775b8d190601050424u7e2e00f8xf1a54a9a98e346fd@mail.gmail.com \
    --to=bruce.ellis@gmail.com \
    --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).