From: erik quanstrom <quanstro@coraid.com>
To: blstuart@bellsouth.net, 9fans@9fans.net
Subject: Re: [9fans] 9vx and local file systems
Date: Fri, 18 Jul 2008 15:00:33 -0400 [thread overview]
Message-ID: <c721fb338b16b2a277fadf4d05308d80@coraid.com> (raw)
In-Reply-To: <071820081822.3544.4880DF75000734D900000DD822218675169B0A02D2089B>
> - The messiest bit, though, is venti and networking.
> boot/boot figures it needs to set up the loopback
> interface for venti. But /net/ipifc doesn't exit
> and boot/boot considers this fatal. I suppose
> the Right Way(tm) to is to implement /net/ipifc
> and have it translate operations to the underlying
> network stack, but that seems an awful lot of
> work, for rather few applications. The not so
> right way would be to fake it, providing the
> interface, but just pretend all the messages
> succeed. But I copped out. I made one change
> to boot/boot. Now if it fails to open /net/ipifc/clone,
> it's not fatal.
the fact that the networking works differently is
a problem for a number of other applications, too.
dns, snoopy, aoe, cec come immediately to mind
as useful stuff that won't work with 9vx.
my inclination would be to give 9vx a proper
ethernet device, but that idea has been discussed
already.
i just wonder if all the coding around the fact
that the 9vx network is different is going to pay off.
- erik
next parent reply other threads:[~2008-07-18 19:00 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <071820081822.3544.4880DF75000734D900000DD822218675169B0A02D2089B>
2008-07-18 19:00 ` erik quanstrom [this message]
2008-07-18 19:50 ` Roman V. Shaposhnik
2008-07-18 20:20 ` erik quanstrom
2008-07-18 20:28 ` ron minnich
2008-07-19 1:31 ` erik quanstrom
2008-07-19 2:10 ` ron minnich
2008-07-19 2:37 ` Russ Cox
2008-07-21 13:26 ` [9fans] (no subject) kokamoto
2008-07-21 14:45 ` a
2008-07-21 15:17 ` [9fans] 9vx vs drawterm Tim Wiess
2008-07-21 18:32 ` [9fans] Sam Benjamin Huntsman
2008-07-18 20:31 ` [9fans] 9vx and local file systems Russ Cox
2008-07-18 21:55 ` Francisco J Ballesteros
2008-07-18 20:35 ` Russ Cox
2008-07-18 18:22 Brian L. Stuart
2008-07-18 20:39 ` Russ Cox
2008-07-18 20:55 ` Charles Forsyth
2008-07-18 20:55 ` Charles Forsyth
2008-07-18 20:50 ` Sape Mullender
2008-07-18 22:10 ` Brian L. Stuart
2008-07-20 7:53 ` Russ Cox
2008-07-23 14:40 ` Brian L. Stuart
2008-07-23 17:51 ` Russ Cox
2008-07-23 18:50 ` Brian L. Stuart
2008-07-24 19:14 ` Brian L. Stuart
[not found] ` <1cb06bb5ba32c2070a940af01f4d91c3@plan9.bell-labs.com>
2008-07-24 19:24 ` Brian L. Stuart
2008-07-24 19:26 ` David Leimbach
2008-07-24 23:23 ` Francisco J Ballesteros
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=c721fb338b16b2a277fadf4d05308d80@coraid.com \
--to=quanstro@coraid.com \
--cc=9fans@9fans.net \
--cc=blstuart@bellsouth.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).