Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.1 6/24/83; site hou3c.UUCP Path: utzoo!watmath!clyde!burl!hou3c!ka From: ka@hou3c.UUCP (Kenneth Almquist) Newsgroups: net.news.b Subject: Re: sigtrap & setuid problems Message-ID: <895@hou3c.UUCP> Date: Mon, 22-Oct-84 12:21:08 EDT Article-I.D.: hou3c.895 Posted: Mon Oct 22 12:21:08 1984 Date-Received: Tue, 23-Oct-84 02:03:08 EDT References: <165@scorplx.UUCP> <193@scorplx.UUCP> <1749@sun.uucp> Organization: Bell Labs, Holmdel, NJ Lines: 25 > > Maybe instead of #ifdef USG, someone should consider #ifdef SYS3, > > #ifdef SYSV (or something similiar). Comments? > How about "SYS3" and "SYS5" or "SYSIII" and "SYSV" but please don't mix > Roman and Arabic numbers... Do the USG cpp's specify what version of > Unix they are? What names do they use? AT&T UNIXes simply predefine "unix" to indicate the operating system. (Probably that's to convince people to upgrade to the latest version. :-)) The scheme I have developed for vnews uses two variables; one for V7 and its derivatives from Berkeley, and the other for USG (now USDL) UNIX. The scheme is: BSDREL USGREL Sixth Edition 6 6 Version 7 7 6 4.1 BSD 41 6 4.2 BSD 42 6 System III 6 30 System V 6 50 System V Release 2 6 52 This scheme has problems. There is no room for 4.1C BSD. 2.x BSD should perhaps have its own release number variable, but I was assuming that the 4.1 BSD code work for 2.x BSD. Kenneth Almquist