From: "Artem Letko" <aletko@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] plan 9 bridging
Date: Mon, 18 Jun 2007 18:10:01 -0400 [thread overview]
Message-ID: <1055b16f0706181510h6e17bc10maa2c43c73ed8208f@mail.gmail.com> (raw)
In-Reply-To: <cd2e67ed0d092e3dc63acbc206a9560b@coraid.com>
i wonder what are you trying to do with bridge(3)
-art
On 6/18/07, erik quanstrom <quanstro@coraid.com> wrote:
> > Yes, there is now bridge(3).
> >
>
> thank you very much! this will be tons easier than (mis)configuring linux.
>
> i assume that i will need to add jumbo support myself. ;-)
>
> - erik
>
>
next prev parent reply other threads:[~2007-06-18 22:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-18 20:38 erik quanstrom
2007-06-18 20:46 ` geoff
2007-06-18 21:04 ` erik quanstrom
2007-06-18 22:10 ` Artem Letko [this message]
2007-06-18 22:43 ` erik quanstrom
2007-06-19 3:34 ` Artem Letko
2007-06-19 11:42 ` erik quanstrom
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=1055b16f0706181510h6e17bc10maa2c43c73ed8208f@mail.gmail.com \
--to=aletko@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).