Return to BSD News archive
Xref: sserve comp.os.386bsd.questions:4954 comp.os.386bsd.misc:934 Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!howland.reston.ans.net!newsserver.jvnc.net!igor.rutgers.edu!geneva.rutgers.edu!hedrick From: hedrick@geneva.rutgers.edu (Charles Hedrick) Newsgroups: comp.os.386bsd.questions,comp.os.386bsd.misc Subject: Re: POSIX, COSE and 386BSD - How do they fit in? Keywords: POSIX, COSE, 386BSD Message-ID: <Sep.10.02.39.55.1993.18514@geneva.rutgers.edu> Date: 10 Sep 93 06:39:58 GMT References: <kjb.747366876@manda.cgl.citri.edu.au> Followup-To: comp.os.386bsd.questions Organization: Rutgers Univ., New Brunswick, N.J. Lines: 11 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? As far as I can tell, all current Unix standards are consistent with POSIX. POSIX seems to standardize the basic traditional Unix system calls, subroutines, and utilities. COSE seems to be oriented at the next layer up, i.e. application-level architecture. It will involve GUI issues, NIS+, and various things of that sort.