From news Sun Nov 13 01:19:32 90 
From: suzuki@nttcoin.ntt.jp (MUNeYOSHI Suzuki)
Subject: ps alx

I tried "ps alx" on NeXT (OS1.0), but result was

F  UID   PID  PPID CP PRI NI ADDR VSIZE RSIZE WCHAN STAT TT  TIME COMMAND
3    0     0     0  0 -50-25    0 14.3M 3.53M     0 R <  ?  55:37  (kerne
1    0     1     0  0   0  0    0  928K  184K     0 S    ?   0:00 init -x
....                                          ^^^^^

All WCHANs are displayed 0. 
Does anyone know, this is NeXT bug or NeXT/MACH specification?  

Thanks,



From news Sun Nov 14 18:14:35 90 
From: mmeyer@next.com (Morris Meyer)
Subject: Re: ps alx

In article <4098@nttcoin.ntt.jp> suzuki%nttcoin.ntt.jp@relay.cs.net (MUNeYOSHI Suzuki) writes:
>I tried "ps alx" on NeXT (OS1.0), but result was
>
>F  UID   PID  PPID CP PRI NI ADDR VSIZE RSIZE WCHAN STAT TT  TIME COMMAND
>3    0     0     0  0 -50-25    0 14.3M 3.53M     0 R <  ?  55:37  (kerne
>1    0     1     0  0   0  0    0  928K  184K     0 S    ?   0:00 init -x
>
>All WCHANs are displayed 0. 
>Does anyone know, this is NeXT bug or NeXT/MACH specification?  
>
The BSD w_chan field in the proc structure does not exist in the Mach
kernel.  It has been replaced by the wait_event in the kernel's thread
structure.  Nevertheless, this is probably a bug on our part.

		--morris

		morris meyer (mmeyer@next.com)
		software engineer
		NeXT OS Group