Printable View
From a MAC, I ftp to a vms box, and then issue:
SEND ~/Desktop/VT500_parser.png
The file that gets created on VMS is:
_Users_JFMEZEI_Desktop_vt500_parser.png;1
Would it be correct to state that it is the MAC's fault for not removing
path information from the filename being sent to the remote FTP server ?
In article <de410$46ca6b2c$cef8887a$15243@TEKSAVVY.COM>,
JF Mezei <jfmezei.spamnot@vaxination.ca> wrote:
[color=blue]
> From a MAC, I ftp to a vms box, and then issue:
>
> SEND ~/Desktop/VT500_parser.png
>
> The file that gets created on VMS is:
>
> _Users_JFMEZEI_Desktop_vt500_parser.png;1
>[/color]
Ooh! So it does.
[color=blue]
> Would it be correct to state that it is the MAC's fault for not removing
> path information from the filename being sent to the remote FTP server ?[/color]
You are giving it the full path by specifying ~/
I you do a CD ~/Desktop
first, followed by the SEND, then no problem.
--
Paul Sture
Sue's OpenVMS bookmarks:
[url]http://eisner.encompasserve.org/~sture/ovms-bookmarks.html[/url]
In article <de410$46ca6b2c$cef8887a$15243@TEKSAVVY.COM>, JF Mezei <jfmezei.spamnot@vaxination.ca> writes:[color=blue]
> From a MAC, I ftp to a vms box, and then issue:
>
> SEND ~/Desktop/VT500_parser.png
>
> The file that gets created on VMS is:
>
> _Users_JFMEZEI_Desktop_vt500_parser.png;1
>
> Would it be correct to state that it is the MAC's fault for not removing
> path information from the filename being sent to the remote FTP server ?[/color]
I don't believe the RFC calls for path removal. I think SEND just
takes a "file name" and says nothing about presence or manipulation
of path.
IMHO, it should have sent "~/Desktop/" as the path, not the resolved
path. But I don't think the RFC says.
In article <de410$46ca6b2c$cef8887a$15243@teksavvy.com>,
JF Mezei <jfmezei.spamnot@vaxination.ca> writes:[color=blue]
> From a MAC, I ftp to a vms box, and then issue:
>
> SEND ~/Desktop/VT500_parser.png
>
> The file that gets created on VMS is:
>
> _Users_JFMEZEI_Desktop_vt500_parser.png;1
>
> Would it be correct to state that it is the MAC's fault for not removing
> path information from the filename being sent to the remote FTP server ?[/color]
No, it's your fault for not providing the name you wanted on the other
end. :-)
FTP used the name you provided and VMS did it's best to intrepret it, the
result not being what you wanted.
bill
--
Bill Gunshannon | de-moc-ra-cy (di mok' ra see) n. Three wolves
[email]bill@cs.scranton.edu[/email] | and a sheep voting on what's for dinner.
University of Scranton |
Scranton, Pennsylvania | #include <std.disclaimer.h>
In article <paul.sture.nospam-4AF52F.07243821082007@mac.sture.ch>,
"P. Sture" <paul.sture.nospam@hispeed.ch> writes:[color=blue]
> In article <de410$46ca6b2c$cef8887a$15243@TEKSAVVY.COM>,
> JF Mezei <jfmezei.spamnot@vaxination.ca> wrote:
>[color=green]
>> From a MAC, I ftp to a vms box, and then issue:
>>
>> SEND ~/Desktop/VT500_parser.png
>>
>> The file that gets created on VMS is:
>>
>> _Users_JFMEZEI_Desktop_vt500_parser.png;1
>>[/color]
>
> Ooh! So it does.
>[color=green]
>> Would it be correct to state that it is the MAC's fault for not removing
>> path information from the filename being sent to the remote FTP server ?[/color]
>
> You are giving it the full path by specifying ~/
>
> I you do a CD ~/Desktop
>
> first, followed by the SEND, then no problem.
>[/color]
Or just say:
SEND ~/Desktop/VT500_parser.png parser.png
bill
--
Bill Gunshannon | de-moc-ra-cy (di mok' ra see) n. Three wolves
[email]bill@cs.scranton.edu[/email] | and a sheep voting on what's for dinner.
University of Scranton |
Scranton, Pennsylvania | #include <std.disclaimer.h>
On 08/23/07 12:02, Bill Gunshannon wrote:[color=blue]
> In article <paul.sture.nospam-4AF52F.07243821082007@mac.sture.ch>,
> "P. Sture" <paul.sture.nospam@hispeed.ch> writes:[color=green]
>> In article <de410$46ca6b2c$cef8887a$15243@TEKSAVVY.COM>,
>> JF Mezei <jfmezei.spamnot@vaxination.ca> wrote:
>>[color=darkred]
>>> From a MAC, I ftp to a vms box, and then issue:
>>>
>>> SEND ~/Desktop/VT500_parser.png
>>>
>>> The file that gets created on VMS is:
>>>
>>> _Users_JFMEZEI_Desktop_vt500_parser.png;1
>>>[/color]
>> Ooh! So it does.
>>[color=darkred]
>>> Would it be correct to state that it is the MAC's fault for not removing
>>> path information from the filename being sent to the remote FTP server ?[/color]
>> You are giving it the full path by specifying ~/
>>
>> I you do a CD ~/Desktop
>>
>> first, followed by the SEND, then no problem.
>>[/color]
>
> Or just say:
>
> SEND ~/Desktop/VT500_parser.png parser.png[/color]
What's the difference between SEND and PUT?
--
Ron Johnson, Jr.
Jefferson LA USA
Give a man a fish, and he eats for a day.
Hit him with a fish, and he goes away for good!
In article <%Ikzi.234338$5y.177154@newsfe18.lga>,
Ron Johnson <ron.l.johnson@cox.net> writes:[color=blue]
> On 08/23/07 12:02, Bill Gunshannon wrote:[color=green]
>> In article <paul.sture.nospam-4AF52F.07243821082007@mac.sture.ch>,
>> "P. Sture" <paul.sture.nospam@hispeed.ch> writes:[color=darkred]
>>> In article <de410$46ca6b2c$cef8887a$15243@TEKSAVVY.COM>,
>>> JF Mezei <jfmezei.spamnot@vaxination.ca> wrote:
>>>
>>>> From a MAC, I ftp to a vms box, and then issue:
>>>>
>>>> SEND ~/Desktop/VT500_parser.png
>>>>
>>>> The file that gets created on VMS is:
>>>>
>>>> _Users_JFMEZEI_Desktop_vt500_parser.png;1
>>>>
>>> Ooh! So it does.
>>>
>>>> Would it be correct to state that it is the MAC's fault for not removing
>>>> path information from the filename being sent to the remote FTP server ?
>>> You are giving it the full path by specifying ~/
>>>
>>> I you do a CD ~/Desktop
>>>
>>> first, followed by the SEND, then no problem.
>>>[/color]
>>
>> Or just say:
>>
>> SEND ~/Desktop/VT500_parser.png parser.png[/color]
>
> What's the difference between SEND and PUT?[/color]
send local-file [remote-file]
A synonym for put.
I used SEND in my example because he used SEND in his question.
I have never used send myself, always put.
bill
--
Bill Gunshannon | de-moc-ra-cy (di mok' ra see) n. Three wolves
[email]bill@cs.scranton.edu[/email] | and a sheep voting on what's for dinner.
University of Scranton |
Scranton, Pennsylvania | #include <std.disclaimer.h>
In article <5j63mmF38ok0hU1@mid.individual.net>,
[email]bill@cs.uofs.edu[/email] (Bill Gunshannon) wrote:
[color=blue]
> send local-file [remote-file]
> A synonym for put.
>
> I used SEND in my example because he used SEND in his question.
> I have never used send myself, always put.[/color]
Same here, I usually use put.
--
Paul Sture
Sue's OpenVMS bookmarks:
[url]http://eisner.encompasserve.org/~sture/ovms-bookmarks.html[/url]