From: "Russ Cox" <rsc@swtch.com>
To: 9fans@9fans.net
Subject: Re: [9fans] 9vx and local file systems
Date: Fri, 18 Jul 2008 16:39:43 -0400 [thread overview]
Message-ID: <20080718203703.2DEAE1E8C22@holo.morphisms.net> (raw)
In-Reply-To: <071820081822.3544.4880DF75000734D900000DD822218675169B0A02D2089B9A019C04040A0DBF9B9D0E9A9B9C040D@att.net>
> A little while back Russ suggested that someone might
> want to look into making 9vx boot using a native
> fossil/venti file system partition for root. For
> anyone who's interested, as of this morning, that
> is working. It's a little kludgy in places, but
> mostly it's not too bad. When I've cleaned it up
> a bit I'll make some patches available.
Thanks for working through this.
I'm glad to hear it works.
> - boot/boot did bad things if the localroot
> wasn't set, so when using boot/boot it's now .
What bad things did it do? The code is supposed
to cope gracefully with localroot == nil. I'd rather
fix the code that couldn't cope.
> - 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.
I think this is a fine solution for this particular case.
I would like to have a /net/ipifc that showed info
about the host IP interfaces, and then /boot/boot
could check whether there is already a loopback
before adding one, but that's certainly not necessary.
Russ
next prev parent reply other threads:[~2008-07-18 20:39 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-18 18:22 Brian L. Stuart
2008-07-18 20:39 ` Russ Cox [this message]
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
[not found] <071820081822.3544.4880DF75000734D900000DD822218675169B0A02D2089B>
2008-07-18 19:00 ` erik quanstrom
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-18 20:31 ` Russ Cox
2008-07-18 21:55 ` Francisco J Ballesteros
2008-07-18 20:35 ` Russ Cox
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=20080718203703.2DEAE1E8C22@holo.morphisms.net \
--to=rsc@swtch.com \
--cc=9fans@9fans.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).