From owner-freebsd-chat Sun Mar 3 09:14:19 1996 Return-Path: owner-chat Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA03267 for chat-outgoing; Sun, 3 Mar 1996 09:14:19 -0800 (PST) Received: from distortion.eng.umd.edu (distortion.eng.umd.edu [129.2.98.6]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id JAA03262 for ; Sun, 3 Mar 1996 09:14:16 -0800 (PST) Received: from skipper.eng.umd.edu (skipper.eng.umd.edu [129.2.98.208]) by distortion.eng.umd.edu (8.7.4/8.7) with ESMTP id MAA01516; Sun, 3 Mar 1996 12:14:14 -0500 (EST) Received: (from chuckr@localhost) by skipper.eng.umd.edu (8.7.4/8.7) id MAA10331; Sun, 3 Mar 1996 12:14:13 -0500 (EST) Date: Sun, 3 Mar 1996 12:14:12 -0500 (EST) From: Chuck Robey X-Sender: chuckr@skipper.eng.umd.edu To: Charles Green cc: chat@freebsd.org Subject: Re: UNIX Specification In-Reply-To: <199603030506.AAA21311@fang.cs.sunyit.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-chat@freebsd.org Precedence: bulk On Sun, 3 Mar 1996, Charles Green wrote: > Chuck Robey stands accused of saying: > } > } I wasn't being fascetious. You define what you actually mean by your > } reference to SINGLE UNIX SPECIFICATION, then you can get an answer. > > Actually that was a cut and paste off of > http://www.xopen.co.uk/public/tech/unix/overview.htm > The technical specification for UNIX (as they refer to it :-) > > } I'm > } horrible at names, but I think I've seen yours before; I wasn't sure, so > > Yeah I've been hanging around and throwing my two cents worth every > once and awhile. > > } I gave you an answer I would give to an absolute newbie. You know as > } well as I there isn't any one true unix yet. If this wasn't flamebait, > } and you still want an answer, be more specific and you might get one. > > The truth is, I was fishing to see what kind of answer I would > get. How much and what kind of opinions such a tearse question might > generate. > > } > } My personal gripe is actually the lack of the SINGLE UNIX SPECIFICATION. > } It's generally conceded that this lack is unixland's biggest failing. > } > X/Open seem to think they have one. But again I'm not too familiar > with the politics involved. But I would like to see FreeBSD branded with > the official UNIX name. Rather that UN*X-like... Now that we have all the initial misunderstandings past, you know, I can really agree with you. The reason that I went with FreeBSD initially over Linux was quite specifically because FreeBSD had a standard to cleave to, while it seemed that Linux was ruled by mob order. Now, I'm not innocent enough to say that BSD 4.4 is my ideal standard, written as it is more by example than spec, but it does serve in this instance as a spec. There has been lots of attention given to trying to keep FreeBSD Posix compliant, even in those cases where this might be construed as requiring pathological behavior on FreeBSD's part. I appreciate your URL reference above to the standards WEB page, I haven't looked at it yet, but I will. Are you suggesting that FreeBSD make some additional effort towards satisfying another technical spec? Which one? ========================================================================== Chuck Robey chuckr@eng.umd.edu, I run FreeBSD-current on n3lxx + Journey2 Three Accounts for the Super-users in the sky, Seven for the Operators in their halls of fame, Nine for Ordinary Users doomed to crie, One for the Illegal Cracker with his evil game In the Domains of Internet where the data lie. One Account to rule them all, One Account to watch them, One Account to make them all and in the network bind them.