Message-Id: <4.0.2.19981103070733.00ad3d70@chesapeake.rps.slb.com>
X-Sender: hackbart AT chesapeake DOT rps DOT slb DOT com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0.2 
Date: Tue, 03 Nov 1998 07:53:03 -0500
To: djgpp AT delorie DOT com
From: Mike Hackbart <hackbart AT chesapeake DOT rps DOT slb DOT com>
Subject: RCS and Network Drives - ENODEV, ENOENT
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Reply-To: djgpp AT delorie DOT com

There was a discussion on the group during March and April 98 covering
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?

The other question is, when I create an archive, say foo.c,v locally, then
copy it to a network drive (in an attempt to work around the creation
problem), say i:\soft\rcs\foo.c,v, and then try to do a checkout:
        co -l foo.c
with rcs file =
        i:\soft\rcs

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)

Can anybody shine some light on this problem?

Thanks for you help!

Mike