From: Kevin Ashley Newsgroups: comp.os.msdos.djgpp Subject: Re: HELP: POSIX standard Date: Fri, 08 May 1998 17:10:22 +0100 Organization: Posted via ULCC Internet Services Message-ID: <35532E6E.41C6@ulcc.ac.uk> References: <19980506001904 DOT AAE3698 AT ppp124 DOT cartsys DOT com> NNTP-Posting-Host: silver.ulcc.ac.uk Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Lines: 33 To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Precedence: bulk Nate Eldredge wrote: > > At 09:59 5/4/1998 -0400, Vic wrote: > >We're making n OS and would like to make it POSIX compliant. Where can > >we find a description of the standard, without buying it from anyone, or > >a book. > [snip] > BTW, I think it's the case (or at least it used to be) that the official > definition of "POSIX-compliant" involved running the package through a > verification suite. This suite is owned by someone (USL?) and they charge a > lot of money to do it. You also need to produce a compliance statement. This consists of, amongst other things, statements about which optional features are supported and definitions of resource limits where POSIX makes minimum requirements but no maximum requirements. One example might be the maximum number of files that one process can open. POSIX sets a minimum bound; you are also required to describe the behaviour. In some systems, the value may be hard-coded. In others, a kernel parameter (can be changed, but kernel rebuild needed.) In others, a boot-time parameter. In others, a user-by-user limit. And in yet others, it may vary depending on what resources are available. ------------------------------------------------------------------------------ Kevin Ashley K DOT Ashley AT Ulcc DOT ac DOT uk Special Projects Manager http://www.ulcc.ac.uk/staff/Kevin+Ashley ULCC ...ukc!ncdlab!K.Ashley (but probably not any more) This is not a signature