Return to BSD News archive
Xref: sserve comp.os.386bsd.questions:4933 comp.os.386bsd.misc:921 Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!haven.umd.edu!umd5.umd.edu!roissy.umd.edu!mark From: mark@roissy.umd.edu (Mark Sienkiewicz) Newsgroups: comp.os.386bsd.questions,comp.os.386bsd.misc Subject: Re: POSIX, COSE and 386BSD - How do they fit in? Date: 8 Sep 1993 20:47:57 GMT Organization: University of Maryland Lines: 18 Message-ID: <26lgdt$38s@umd5.umd.edu> References: <kjb.747366876@manda.cgl.citri.edu.au> <CCyqCn.1EB@kithrup.com> NNTP-Posting-Host: roissy.umd.edu Keywords: POSIX, COSE, 386BSD In article <CCyqCn.1EB@kithrup.com> sef@kithrup.com (Sean Eric Fagan) writes: >In article <kjb.747366876@manda.cgl.citri.edu.au> kjb@cgl.citri.edu.au (Kendall Bennett) writes: >>Sounds like a great move to me, but I was wondering how POSIX fits into >>this scheme? Isn't this what POSIX was intended to do anyway? Is POSIX >>and integral part of COSE, or is it something separate? > >COSE is based on the X/Open Portability Guide. Version 4, I think (hence, >XPG4). The various versions of XPG are unix standards; POSIX is supposed >to be a standard for an OS, and many operating systems can be POSIX- >compliant (e.g., VMS, Windows/NT, some IBM OSes). From the publicity I've seen, COSE is more than just X/Open portability. For example, it includes HP VUE (Visual User Environment) which is an (IMHO) ugly GUI, but not any much uglier than any other GUI I've seen. But it seems to support some sort of "drag-and-drop" across applications, etc. If that is really true, I wouldn't hold my breath waiting for any freeware to be compliant. POSIX is work enough :).