Greetings;
I guess I missed the ftp requirement in the post I replied to.
Is ftp a requirement? If not can you use NFS on USS?
NFS would solve a lot of problems. All you would need to do is
export the file system, then mount it ("Map Network Drive" in
Windows-speak) on your desktop. Then all the copying is quickly
performed with the drag-and-drop GUI operation that all Windows
users know and love!
BTW, Re: the subject line. I think that would be "brain fault"
as in memory fault, page fault and processor fault. While some
of our Far Eastern friends might pronounce it that way, I doubt
they would write it that way.
Good Luck!
Dennis
"Post, Mark K"
<[EMAIL PROTECTED] To: [EMAIL PROTECTED]
com> cc:
Sent by: Linux Subject: Re: Brain fart - redirect
stderr/std out to a file and NOT see an ything after
on 390 Port a command is run
<[EMAIL PROTECTED]
ARIST.EDU>
11/07/2003
11:12 AM
Please respond
to Linux on 390
Port
That's if you access them via HTTP. Not FTP, which is what was being
discussed, for the very reason you mention. CGI, JSP, etc. files wanted,
but not accessible via HTTP.
Mark Post
-----Original Message-----
From: Dennis Wicks [mailto:[EMAIL PROTECTED]
Sent: Friday, November 07, 2003 12:08 PM
To: [EMAIL PROTECTED]
Subject: Re: Brain fart - redirect stderr/std out to a file and NOT see
an ything after a command is run
Greetings;
wget should work. The pages are served in ASCII by the server
else they would be gibberish to any ascii machine receiving
them.
And, yes, I just tried it. Works great and quickly.
One problem you might encounter is when the pages use SSI
or pages are generated by cgi programs. Then wget will get
the results that are sent, not the source to the commands
or programs that greated them. However, you can point wget
directly at the subject script and get it that way ... usually.
I have yet to identify the specific cases where this does not work!
Good Luck!
Dennis
"Post, Mark K"
<[EMAIL PROTECTED] To: [EMAIL PROTECTED]
com> cc:
Sent by: Linux Subject: Re: Brain fart -
redirect stderr/std out to a file and NOT see an ything after
on 390 Port a command is run
<[EMAIL PROTECTED]
ARIST.EDU>
11/07/2003
10:23 AM
Please respond
to Linux on 390
Port
The wget command is one of my favorites, and it is available for Windows,
but from my reading of the man page, wget only does binary transfers, not
text/ASCII ones. So, Jim would wind up with EBCDIC on his Linux/390
system,
not ASCII.
Mark Post
-----Original Message-----
From: McKown, John [mailto:[EMAIL PROTECTED]
Sent: Friday, November 07, 2003 10:37 AM
To: [EMAIL PROTECTED]
Subject: Re: Brain fart - redirect stderr/std out to a file and NOT see
an ything after a command is run
On z/Linux, use the "wget" command. It will do recursive ftp "gets". On
Windows, you are on your own <grin>. Of course, you could use "wget" to get
it to Linux (converting to ASCII), then use zip or tar on Linux to bundle
it
up, then ftp to get the tar file to Windows.
--
John McKown
Senior Systems Programmer
UICI Insurance Center
Applications & Solutions Team
+1.817.255.3225
This message (including any attachments) contains confidential information
intended for a specific individual and purpose, and its' content is
protected by law. If you are not the intended recipient, you should delete
this message and are hereby notified that any disclosure, copying, or
distribution of this transmission, or taking any action based on it, is
strictly prohibited.
> -----Original Message-----
> From: James Melin [mailto:[EMAIL PROTECTED]
> Sent: Friday, November 07, 2003 8:55 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Brain fart - redirect stderr/std out to a file
> and NOT see anything after a command is run
>
>
> Actually, it occurs to me that this will do exactly what I
> wanted it to do,
> but not what I need it to do....
>
> Specifically, I need to manually re-import the file system
> structure of a
> web site built on OS/390 Unix system services to which the developer
> destroyed his 'frontpage' source. The import website thing
> only follows
> links and he has some JavaScript built menus and crap, and
> cannot get the
> whole thing back properly. We want to re-deploy this to z/Linux (minor
> changes to scripts required)
>
> I had looked into having FTP recursively navigate a directory
> structure and
> re-created it on his desktop but I can't seem to see how to
> do that. So I
> was going to just tar the whole thing but the I realized the
> text based
> files will be EBCDIC, so that's kinda useless.
>
> What is the easiest way to bring this USS installed directory
> structure
> into windows so we can used the developer's favorite (gack) tool to
> redeploy this to z/Linux?
>
