Re: [9fans] fossil 'sync' lockup?

[erik quanstrom <quanstro@quanstro.net>]

> 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