phil@vaxwaller.UUCP (Phil Newton) (09/28/90)
I'm trying to get the "unix-tex" code that's archived at Ohio
State University (osu-cis).
The only file I have been able to acquire is:
osu-cis\!~/unix-tex/COPYING.POLICY.Z
The uucp commands I'm using look similar to the command listed below
(I have one separate uucp command for each file I'm trying to get):
Ex: uucp command:
/usr/bin/uucp osu-cis\!~/unix-tex/README.Z \
/usr/spool/uucppublic/unix-tex/README.Z
Does anyone have any idea why I would get the following error message
for every other file that I'm trying to access from the 'unix-tex'
directory?
remote access to path/file denied
I would appreciate any help that anyone out there can provide.
Thanks!
--
Philip T. Newton (415)945-2272
Varian Instruments 2700 Mitchell Drive Walnut Creek, CA. 94598
{zehntel,pacbell,lll-winken}!varian!philkarl_kleinpaste@cis.ohio-state.edu (09/28/90)
phil@vaxwaller.uucp writes:
I'm trying to get the "unix-tex" code that's archived at Ohio
State University (osu-cis).
An offhand comment, you'll be much more likely to get a prompt
response to problems at osu-cis just by writing mail to osu-cis!uucp
or something similar (osu-cis!root, osu-cis!postmaster, that ilk).
That assumes, of course, that your system is known to the UUCP maps so
mail can get back to you.
The only file I have been able to acquire is:
osu-cis\!~/unix-tex/COPYING.POLICY.Z
Does anyone have any idea why I would get the following error message
remote access to path/file denied
Because that particular piece of the archive was removed deliberately
about 4 days ago. Our local TeX support person observed that the
version of of TeX we had available was both ancient (version
2.something, when 3.0 is the current release) and incomplete. I
removed it on the expectation that we'd replace it Real Soon Now with
the latest distribution. Since our TeX person is a grad student with
darn little time on her hands, she hasn't gotten around to telling me
what I should be putting there.
Pick up a new ls-lR.Z again in a few days and it'll probably be back.
--karl