From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: From: erik quanstrom Date: Mon, 7 Sep 2009 09:54:16 -0400 To: 9fans@9fans.net In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Subject: Re: [9fans] fossil 'sync' lockup? Topicbox-Message-UUID: 68f727d6-ead5-11e9-9d60-3106f5b1d025 > Why are VtLocks in liboventi? And why does liboventi have an > implementation of a subset of the thread library (rwlocks and > rendezvous?) fossil and venti do seem to break the rules a bit. they don't pass style(6) muster. i can only guess this is for portability. but as p9p already provides a full thread library, so at the least, i don't see a continued need for them. perhaps russ knows more? > Okay, thanks! Luckily nm worked with 9pcf and I found procalloc; I was > going to start at the mach structure (always at KZERO + 0x15000) , > find the current process structure's address, and then trawl memory > for processes around it till I found fossil. it might pay off to teach acid about this. i think by setting the map or creatively fabricating a /proc/n entry. other than mem and segment, i believe you can fake the other files with /dev/zero or /dev/null. - erik