From: erik quanstrom <quanstro@quanstro.net>
To: rminnich@gmail.com, 9fans@9fans.net
Subject: Re: [9fans] 9vx dns funny
Date: Sun, 6 Jul 2008 15:36:38 -0400 [thread overview]
Message-ID: <066f7762c9fee5553130692750b99425@quanstro.net> (raw)
> > personally, i feel it would be more useful to be
> > able to use plan 9's native network stack. but
> > i'm biased. i want to send aoe/cec/il packets.
> >
>
> Part of the reason I have not stopped using lguest, although now I use
> both 9vx and lguest.
>
> You could write a plan 9 device for vx that drives raw frames to linux
> I suppose.
i was trying to say that was one of two potential ways to go.
the question is, which way is 9vx going. or,
- is there any reason writing #l for 9vx is not a good idea
technically; and
- is #l something that might have a chance to become part of
9vx?
- erik
p.s. wild idea: 9pxevxload.
next reply other threads:[~2008-07-06 19:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-06 19:36 erik quanstrom [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-07-06 15:56 erik quanstrom
2008-07-06 17:20 ` ron minnich
2008-07-08 17:17 ` Russ Cox
2008-07-08 17:25 ` erik quanstrom
2008-07-10 7:40 ` Nathaniel W Filardo
2008-07-10 10:40 ` maht
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=066f7762c9fee5553130692750b99425@quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
--cc=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).