Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!cwjcc!gatech!fabscal!mpx1!mpx2!erik
From: erik@mpx2.UUCP (Erik Murrey)
Newsgroups: comp.unix.xenix
Subject: Re: Mandatory locking (was Re: the 'l' permission)
Keywords: mandatory locking; Xenix seems broken
Message-ID: <283@mpx2.UUCP>
Date: 27 Nov 88 22:13:53 GMT
References: <71@attibr.UUCP> <4594@ptsfa.PacBell.COM> <483@auspex.UUCP> <1988Nov26.220052.19423@ateng.ateng.com>
Reply-To: erik@mpx2.UUCP (Erik Murrey)
Organization: MPX Data Systems, Inc. ,  Wayne, PA
Lines: 16

In article <1988Nov26.220052.19423@ateng.ateng.com> chip@ateng.ateng.com (Chip Salzenberg) writes:
>
>...and unfortunately, despite all protestations to the contrary, SCO Xenix
>does *not* comply with the SVID on this topic.  Even though it's called
>"Xenix System V."

This appears to be fixed in 2.3.1.  The release notes state that you
can select either advisory or mandatory in the x.out header.

I haven't tested this, so don't flame me if it doesn't work...

... Erik-- 
Erik Murrey                            /|   //  /~~~~/  |  /
MPX Data Systems, Inc.                / | / /  /____/   |/
erik@mpx2.UUCP                       /  /  /  /        /|  Data Systems, Inc. 
{spl1,vu-vlsi,bpa}!mpx1!erik        /     /  /       /  |====================