Return to BSD News archive
Path: sserve!manuel!munnari.oz.au!spool.mu.edu!sdd.hp.com!usc!elroy.jpl.nasa.gov!ucla-cs!rutgers!cmcl2!prism.poly.edu!kapela From: kapela@prism.poly.edu (Theodore S. Kapela) Newsgroups: comp.unix.bsd Subject: Re: I wonder, did AT&T backstab BSDI? Keywords: AT&T speculation lawsuit BSDI Message-ID: <1992Jul29.182141.10399@prism.poly.edu> Date: 29 Jul 92 18:21:41 GMT Article-I.D.: prism.1992Jul29.182141.10399 References: <1992Jul28.153750.8395@mintaka.lcs.mit.edu> <1992Jul29.144859.8222@bas-a.bcc.ac.uk> Organization: Polytechnic University, New York Lines: 30 In article <1992Jul29.144859.8222@bas-a.bcc.ac.uk> ucacmsu@ucl.ac.uk (Mr Stephen R Usher) writes: >In article <1992Jul28.153750.8395@mintaka.lcs.mit.edu> knight@hal.gnu.ai.mit.edu (Knight of the Living Dead) writes: >> >>As I recall when System 5 Revision 4.0 was released, it was described >>(to me, anyway) as an attempt to gain "BSD Compatibility". I'm wondering >The only problem with this idea is that SYSVr4 (NOT System 5, that was >another Unix way back) doesn't look like BSD, it still looks like SYSV to SVR4 is System V, Release 4. System 7 was an early version of Unix way back (in the pre-dawn era :-) ) >the normal user, ie you have horrid syntax for the ps utility where you need >to use a hyphen in front of the arguments and the devices... yuck! Actually, this would make "ps" *consistent* with other unix utilities. In general, options are preceded by a dash, arguments to those options aren't. > >The only real thing I've seen which is BSD is the socket library (not >complete) and the BSD compatibility library which is not complete either. > What about POSIX signals? They are derived from Berkeley signals. The old System V (pre- R4) methods of handling signals was brain-dead. -- ............................................................................... Theodore S. Kapela kapela@poly.edu Center for Applied Large-Scale Computing Polytechnic University