From mboxrd@z Thu Jan 1 00:00:00 1970 To: 9fans@9fans.net Subject: Re: [9fans] 9vx and local file systems From: "Russ Cox" Date: Sun, 20 Jul 2008 03:53:27 -0400 In-Reply-To: <071820082210.18865.488114DC0009E314000049B122193100029B0A02D2089B9A019C04040A0DBF9B9D0E9A9B9C040D@att.net> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Message-Id: <20080720075052.9F4D41E8C1F@holo.morphisms.net> Topicbox-Message-UUID: eceec528-ead3-11e9-9d60-3106f5b1d025 >> > - 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