Thanks Maciej,

That is exactly what I was having trouble with.  I have been able to specify 
directories in the same way that you have mentioned using 
"[directory.subdirectory]filename", but I have had no success with any attempts to 
incorporate the "disk:" part into the URL.  That is frustrating.

--
Ben

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Behalf Of Maciej W. Rozycki
Sent: Wednesday, May 26, 2004 3:36 PM
To: Bufford, Benjamin (AGRE)
Cc: Tony Lewis; [EMAIL PROTECTED]
Subject: RE: OpenVMS URL


On Wed, 26 May 2004, Bufford, Benjamin (AGRE) wrote:

> That's the problem I'm having.  With all the looking and reading I've
> done I haven't found a way to specify the type of pathname I used as an
> example ("disk:[directory.subdirectory]filename") as a URL for a broswer
> or anything else that requires a URL to retrieve things over ftp.

 Wget incorporates explicit support for VMS FTP servers, but the code
seems only to support the "[directory.subdirectory]filename" part of your
file path, i.e. an URL of this form: 
"ftp://server/directory/subdirectory/filename"; will order wget to retrieve
"[directory.subdirectory]filename" from "server", but there's no way to
specify the "disk:" part.

--
+  Maciej W. Rozycki, Technical University of Gdansk, Poland   +
+--------------------------------------------------------------+
+        e-mail: [EMAIL PROTECTED], PGP key available        +



******************************************
The information contained in, or attached to, this e-mail, may contain confidential 
information and is intended solely for the use of the individual or entity to whom 
they are addressed and may be subject to legal privilege.  If you have received this 
e-mail in error you should notify the sender immediately by reply e-mail, delete the 
message from your system and notify your system manager.  Please do not copy it for 
any purpose, or disclose its contents to any other person.  The views or opinions 
presented in this e-mail are solely those of the author and do not necessarily 
represent those of the company.  The recipient should check this e-mail and any 
attachments for the presence of viruses.  The company accepts no liability for any 
damage caused, directly or indirectly, by any virus transmitted in this email.
******************************************

Reply via email to