Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!samsung!munnari.oz.au!uniwa!cc.curtin.edu.au!cutmcvax.cs.curtin.edu.au!peter From: peter@cutmcvax.cs.curtin.edu.au (Peter Wemm) Newsgroups: comp.unix.sysv386 Subject: ESIX sockets again Message-ID: Date: 11 Apr 91 15:08:06 GMT Sender: news@cutmcvax.cs.curtin.edu.au (Usenet News System) Organization: Curtin University of Technology, Computing Science Lines: 16 Nntp-Posting-Host: cutmcvax.cs.curtin.edu.au Well, I dont see all that much wrong with the ESIX implementation, just remember that the very first implementation for BSD before the sockets code was moved to the kernel was probably done with send() and recv() too.. (sockets were probably a link library..) A quick #define macro for the socket read/write and a selective search/replace is just about all that is required. The BSD fastfilesystem was also written and debugged as a user process too. I really can't see what all the fuss is about... -- Peter Wemm ------------------------------------------------------------------------------ peter@cs.curtin.edu.au (Home) +61-9-450-5243 Curtin University of Technology, Perth, Western Australia. Amiga... Because life is too short for boring computers. (Dan Zerkle)