Date: Tue, 3 Nov 1998 16:12:46 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Mike Hackbart <hackbart AT chesapeake DOT rps DOT slb DOT com>
cc: djgpp AT delorie DOT com
Subject: Re: RCS and Network Drives - ENODEV, ENOENT
In-Reply-To: <4.0.2.19981103070733.00ad3d70@chesapeake.rps.slb.com>
Message-ID: <Pine.SUN.3.91.981103160352.20396B-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com


On Tue, 3 Nov 1998, Mike Hackbart wrote:

> problems with Novel network drives.  I have similar problems.  The problem
> with not being able to create a new archive on a network drive was resolved
> by plugging code from libc.a for the remove.c module into rcsedit.c and
> doing a few little hacks.  I believe that I can reproduce this effort and
> solve this problem too.  However something was done with printf and
> changing EACCES to ENOENT that didn't seem quite right.  Were these issues
> ever resolved?

I believe they were.  The correct solution should be to let DJGPP's
`remove' (or was it `rename'?) to do its job instead of using the
work-arounds in the RCS sources.  (The RCS work-arounds are for other
MSDOS compilers which, in DOS's tradition, won't delete/rename files which
are write-protected.  The DJGPP's version doesn't have this problem, it
works like the Posix standard requires, i.e. like Unix libraries do.)

I don't remember the details, but there should be an option in the way 
RCS is configured when you build it to tell it to simply call `remove'.

If after that you still have problems, please post the details.  I really 
cannot remember all the details after all this time ;-).

And btw, make sure you use the latest version of the patched libc from 
Nate Eldredge's site, since several functions in the stock library had 
problems with Novell-mounted drives.

> the file checks out OK, it says locked and done, but, observing the
> i:\soft\rcs\foo.c,v file using the Win95 Explorer, it changes to a folder
> symbol and has size 0 bytes.  Now  an attempt to ci foo.c results in the
> message:
> ci: i:/soft/rcs/foo.c: Permission denied (EACCES)

Forget how Explorer shows it, and tell what does "DIR" print about it, 
both before and after you check-out the workfile.

Also, please tell what command(s) were used to copy the file to the 
networked drive.