Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!linus!decvax!harpo!seismo!hao!hplabs!sri-unix!gwyn@brl-vld From: gwyn%brl-vld@sri-unix.UUCP Newsgroups: net.unix Subject: Re: DIFFERENCES BETWEEN S5 AND 4.2? Message-ID: <16854@sri-arpa.UUCP> Date: Tue, 21-Feb-84 20:23:54 EST Article-I.D.: sri-arpa.16854 Posted: Tue Feb 21 20:23:54 1984 Date-Received: Fri, 2-Mar-84 08:07:08 EST Lines: 24 From: Doug Gwyn (VLD/VMB)It is interesting that you have drawn your conclusion (that you need a 4.2BSD UNIX rather than a UNIX System V) in advance of having the facts you need to back up your conclusion.. The only practical way I know of to develop software under 4.2BSD for a UNIX System V destination is to have a very complete UNIX System V emulation running on top of your 4.2BSD. The systems differ in too many ways to share common source code if you need to use ioctls or signals in non-trivial ways. There are ways of isolating such system dependencies in small "interface" source files, but you would still need to test your interfaces for the other system somehow.. Fortunately there is a public-domain (except of course for an AT&T UNIX license requirement) emulation of UNIX System V available for VAX 4.2BSD. I will mail you the blurb I posted to the UNIX-Wizards mailing list; anyone else who is seriously interested in this package can send mail to gwyn@brl-vld.arpa or {decvax,esquire,research,unc}!brl-bmd!gwyn and I will send you a description and details on how to obtain the tape. If it weren't for the comfort of a UNIX System V environment, I wouldn't be able to stand developing software under raw 4.2BSD. I also enjoy having exactly the same source code across all our flavors of UNIX.