by Beware !! If you're interested in handling serial I/O, you'll find moreQuote:>Ok, now what about us that are looking at machines for other than X workstation
>usage? I'm setting up an Internet node where the load is mainly I/O bound
>and is of more "classic" characteristics. That is, I'm not really interested
>in tweaking the fastest screen work out the box, I'm interested in responding
>to serial and net I/O.
problems with Solaris than you may be interested in fixing. Since we started
to ship 2.x, we've used Baydel MUXs and SPC boards for asynch I/O, and have
had all sorts of problems with ports* up, only being able to use one
port at a time for dialout, Kermit stuffing ports, system crashes etc etc.
Four months on, and lots of patch installations later, our development system
is just about stable...
Our main products are online systems where access is usually dialin, and we
are now using ethernet TCUs where possible rather than Sun serial hardware.
The only other choices appear to be to ditch Sun hardware as our main platform,
or to wait until they get their act together in the area of asynch comms. Only
time will tell which way we go, and that's running short !! We have had no
problems with other Sun comms (x.25, tcp, DNI), all on the network side, but
asynch ? Ugh !
--
David Byrne, Abacus Software, London, UK Tel: +44 (0)71 930 4884
Here's a koan: If you have ice-cream I will give you some. If you have none,
I will take it away from you. (it's an ice-cream koan).