[comp.sys.att] TCP/IP or SOCKETS on cheap UNIX box

brad@bradley.UUCP (11/16/87)

/* Written 11:29 am  Nov 11, 1987 by stc-auts.UUCP!kak in bradley:comp.sys.att */
>>We have an ethernet application we are converting to run using
>>sockets and TCP/IP running on a BSD 2.10 system.  The PDP-11
>>systems we are running part of the software on are getting old,
>>and we would like to replace them with something cheaper.  At
>>their recent sale price, 3B1's would be a good system (assuming
>>we can handle the TCP/IP conversion and lack of select call)
Am I to understand that TCP/IP for 3B1's has no select(2)?  Question
for all you out there.  We have Convergent Mini-frames with TCP/IP
and missing system calls ( and also bugs in some that are there ).
Did Convergent do the TCP/IP for 3B1's?  How close is the 3B1 to
4.3BSD? What about 3B2 series?  What does it have? I heard for the
3B2 that there are different versions, if so how many and differences?

Thanks,
Bradley Smith			UUCP: {cepu,ihnp4,noao,uiucdcs}!bradley!brad
Text Processing			ARPA: cepu!bradley!brad@CS.UCLA
Bradley University		PH: (309) 677-2337
Peoria, IL 61625

ekrell@hector.UUCP (Eduardo Krell) (11/18/87)

To trully implement select(2) on System V, you need to change the kernel.
A streams-based TCP/IP can use poll(2) (that's a System V Release 3 system
call) that works much like select(2), but ONLY on stream file descriptors.

The problem with select(2) is that it can be done on an ordinary file,
and you can't do that unless you change the i-node structure and keep
track of the ones that are "selectable".  You also have to change other
I/O drivers as well.

Changing kernel drivers might to be trivial, and changing the file system
is a pain.
    
    Eduardo Krell                   AT&T Bell Laboratories, Murray Hill

    {ihnp4,seismo,ucbvax}!ulysses!ekrell