From mboxrd@z Thu Jan  1 00:00:00 1970
Date: Mon,  4 Mar 1996 10:48:49 -0500
From: forsyth@plan9.cs.york.ac.uk forsyth@plan9.cs.york.ac.uk
Subject: Another system running
Topicbox-Message-UUID: 3f023c02-eac8-11e9-9e20-41e7f4b1d025
Message-ID: <19960304154849.cnrM_oCd9YcgeI9heaBsn5X82QbZqxaJKjlVnhmxYyw@z>

the 386 has got the 32 bit instructions (unlike the 286).
the 386sx uses a 16-bit bus, but that doesn't
change the set of 32 bit operations available (it just makes the system
slower).

i used a 4mbyte 386sx16 as a Plan 9 terminal for several years
on the old release.  in that configuration you want a bigger machine
somewhere to act as a CPU server for compilations (and floating-point
work), and to run
acme, or the heavy-duty part of sam.

i've even used an 8mbyte 386sx16 as a file server, to test a version
of the file server kernel that used IDE instead of SCSI.
a 386sx16 is a bit slow for production use, but it works.

it might still be attractive to use small, cheap 386sx configurations
as highly specialised cpu servers controlling small devices on a network.