Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!hellgate.utah.edu!uplherc!wicat!michael
From: michael@wicat.UUCP (Mike Weeks)
Newsgroups: comp.binaries.ibm.pc.d
Subject: Re: RCS for DOS (long)
Message-ID: <486@wicat.UUCP>
Date: 22 Aug 90 18:32:50 GMT
References: <1990Aug21.183747.9854@athena.mit.edu>
Distribution: comp
Organization: WICAT Systems, Orem, Utah
Lines: 31

lfk@athena.mit.edu (Lee F Kolakowski) writes:
>There have been a number of comments about DOS RCS in this newsgroup 
>and in my mailbox. Here are the responses. This may be a bit long
>so if you are not interested in RCS for DOS, press ``n'' now.

>BUG #3:
>On 20 Aug 90 10:24:58 BST,
>I.Sparry@gdt.bath.ac.uk (Icarus Sparry) said:
>> I seem to have found a bug.
>> 1) Check in a file, say fred
>> 2) Enable stricy locking 'rcs -L fred'
>> 3) Checkout fred, without locking 'co fred'
>> 4) Checkout fred with lock. 'co -l fred'
>> The last fail, as it can't unlink the readonly copy.
>> The fix would be to chmod the file first, and then unlink, or else blame MS
>> for a faulty 'unlink' routine.

>I have not had a chance to investigate this. But I put it here FYI.

I have found a similar problem on Novell Netware.  With strict locking
enable, if I co a file, it is created with read-only access and I cannot
edit it unless I chmod it.  The RCS/xxx file is also created with read-only
access and I cannot do a co -l xxx because co is unable to write to the
file.  I am waiting for the sources so I can check this out but is anyone
else using rcs with Netware successfully?  I can do all the same functions
on a local drive just fine but when I go to a networked disk, I'm out of
it.

Thanks,
Mike Weeks
Wicat Systems, Inc.