> >> This appears easily fixed, but it is not obvious what the
> >> proc pointer is used for in every case. This might be:
> >> -scheduling (ultimatively to be passed to ltsleep())
> >> -access rights
> >> -accounting
> >> -address space for virtual addresses
> 
> Fair point.  I think the short, honest answer is; ``right now, nobody
> really knows''.  Its also in a state of flux.

i don't think a random proc pointer is better than NULL.

YAMAMOTO Takashi