[890] in testers
Re: /srvd
daemon@ATHENA.MIT.EDU (daemon@ATHENA.MIT.EDU)
Sat May 26 02:47:37 1990
From: dkk@ATHENA.MIT.EDU
Date: Sat, 26 May 90 02:47:13 -0400
To: Ezra Peisach <epeisach@ATHENA.MIT.EDU>
Cc: testers@ATHENA.MIT.EDU
In-Reply-To: Ezra Peisach's message of Fri, 25 May 90 10:13:23 EDT,
. >>Would it be reasonable to install a symlink:
.
. >> /srvd/usr/.rvdinfo -> /srvd/.rvdinfo
.
. No, it would not be reasonable. We tried to maintain backwards
. compatibility. The hack that your relying upon in order to
. determine if you should activate or never a supported mechanism.
.
. Personally, I test for /*rvd/lib.
.
. Ezra
I'm not trying to test to see if the packs are present. I want to
check if they are the right version. Checking the mod-time on
/?rvd/lib is a rather round-about way of doing that, don't you think?
The whole reason I suggested the link was as a form of backwards
compatibility, so that version checks would still work, since a 6.4
/srvd and a 7.0 /urvd will cause some strange things to happen, at
least on machines that have been modified (with mkserv) from the
standard configuration. As I stated in my original message, there are
other practical ways for the user to get around this problem, I just
don't see one symlink as being difficult, dangerous or costly. (Just
a bit late to add...)
Of course, the track subscription-list would probably have to be
updated, which makes the change unreasonable, due to the risk of
breaking the track. I still consider your argument very weak,
however. (Weaker, even, than mine :-)
