Okay, I did try try your suggestion, and here's what I get:

 #('SocketPlugin 21 December 2002 (i)' 'B2DPlugin 21 December 2002 (i)'
'Matrix2x3Plugin 21 December 2002 (i)' 'FloatArrayPlugin 21 December 2002
(i)' 'BitBltPlugin 21 December 2002 (i)' 'LargeIntegers v1.2 21 December
2002 (i)' 'UnixOSProcessPlugin 21 December 2002 (i)' 'SecurityPlugin 21
December 2002 (i)' 'FilePlugin 21 December 2002 (i)' 'MiscPrimitivePlugin
21 December 2002 (i)')

As you can see, UnixOSProcessPlugin is internal.

I also decided to be thorough, so I flushed my vm source directory,
flushed my VM build directory, had VMMaker regenerate all the sources, and
do a complete configure/make/make install (actually, checkinstall)--and it
still happens.  My platform sources come from Ian Pumarta's Unix
distribution, and I'm using version 3.2-6.

So here's a question: perhaps this is more of an OS issue?  I am running
Debian *testing* after all--that means XFree86 version 4.2, and a more
recent libc6 than the stable version (if I remember correctly).  With both
of these, it's quite likely that there is a subtle change that the Squeak
source code has not taken into account.

It's a stumper, isn't it? :)

On Sat, 21 Dec 2002, David T. Lewis wrote:

> You still could be loading an external plugin without knowing it. Try
> evaluating "Smalltalk listLoadedModules" and see what it tells you. If
> the entry for UnixOSProcessPlugin has an "(e)" after it instead of "(i)",
> then you have loaded an external UnixOSProcessPlugin.so over the top of
> your internal plugin. If so, find the UnixOSProcessPlugin.so file that is
> getting loaded and get rid of it. If that's not the case, then I'm just
> confused.
>