From: "Russ Cox" <rsc@swtch.com>
To: 9fans@9fans.net
Subject: Re: [9fans] 9vx and local file systems
Date: Sun, 20 Jul 2008 03:53:27 -0400 [thread overview]
Message-ID: <20080720075052.9F4D41E8C1F@holo.morphisms.net> (raw)
In-Reply-To: <071820082210.18865.488114DC0009E314000049B122193100029B0A02D2089B9A019C04040A0DBF9B9D0E9A9B9C040D@att.net>
>> > - boot/boot did bad things if the localroot
>> > wasn't set, so when using boot/boot it's now .
I think this is fixed in hg now. I found one place where
localroot was going to be used even though
it shouldn't.
> I'm beginning to think the lock-ups some of us have
> seen are somewhere in devfs-posix.c. When I'm using
> it like drawterm, I've never seen it lock up. When
> I was using it with the local fossil/venti as root
> today, it didn't. In neither case was #Z bound.
> It's at least suggestive.
Since the local fossil/venti goes through #Z to get at
the disk device, this doesn't exactly support your theory.
I can still believe it, though. Are you perhaps on a Mac?
I fixed some pthread-related bugs on July 3 in hg,
which is post-0.12.
>> > 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 had been trying not to modify anything outside of
> vx32/src/9vx. In particular, I liked the idea that
> all Plan 9 executables would work unmodified.
I agree, but /boot/boot is not an ordinary Plan 9
executable. It's hard-coded into the running kernel
(or 9vx) and is always kernel-specific (each kernel
config typically builds a different one with slightly
different parameters), so it's fine if you need to build
a slightly different /boot/boot for 9vx too.
Russ
next prev parent reply other threads:[~2008-07-20 7:53 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
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 [this message]
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=20080720075052.9F4D41E8C1F@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).