Mail Archives: djgpp/1998/05/19/07:46:37
Eli Zaretskii wrote:
[...]
>
> If none of the above helps in any way, I will need to know where does
> ci fail. I'm afraid the only way to find that out would be to
> download the RCS sources, compile them with -g, then run them under a
> debugger to see where does that ENODEV error come from. If you find
> that out, please post the info here, and I will try to understand what
> goes wrong, and how to solve it.
That'll be the way to go. Sigh.
I just tried under plain vanilla DOS6.22 on a NW drive:
mkdir rcs
echo "Hi" > loginfo
ci -q -u -t- "-minital check in" loginfo
ci: RCS/loginfo: No such file (ENOENT)
ci: saved in RCS/loginf_
./loginfo is still there, untouched and writeable.
./RCS/loginf_ looks fine, write protected.
On a local drive, it works fine.
In the README I saw a problem on NW drives for co that
is alledgedly fixed, I guess this one is similar.
--
Ciao
Tom
*************************************************************
* Thomas Demmer *
* Lehrstuhl fuer Stroemungsmechanik *
* Ruhr-Uni-Bochum *
* Universitaetsstr. 150 *
* D-44780 Bochum *
* Tel: +49 234 700 6434 *
* Fax: +49 234 709 4162 *
* http://www.lstm.ruhr-uni-bochum.de/~demmer *
*************************************************************
- Raw text -