WINE crossover to run winscp for ASCII mode files transfer
 

I heard we can run Windows tools / binaries in RHES Linux :

Q1:
Can someone give me all the links (& its dependent rpm packages )
to download WINE / crossover for RHES 4.x / 5.x. I have a Redhat
account

Q2:
How to go about setting up winscp to run on my RHES 4.x / 5.x Linux
box

Q3:
A sample Shell script to run winscp to copy over a text file in ASCII
mode (yes, this is the ASCII mode equivalent in ftp) via sftp / scp
protocol. Yes, I could have used unix2dos or Perl to convert a file
first before copying it using sftp/scp but due to policy in place, I was
told not to do conversion (which I can't understand why)


Sun

--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list

WINE crossover to run winscp for ASCII mode files transfer
 

On Sat, 27 Aug 2011, sunhux G wrote:


I heard we can run Windows tools / binaries in RHES Linux :


Yes. But in many cases you don't need to.



Q1:
Can someone give me all the links (& its dependent rpm packages )
to download WINE / crossover for RHES 4.x / 5.x. I have a Redhat
account


It's probably simpler to just go to RPMForge, install their rpmforge-release
RPM and then do "yum install wine". But again, for this purpose I don't
think you need to.




Q2:
How to go about setting up winscp to run on my RHES 4.x / 5.x Linux
box


As far as I'm aware you'd download the WinSCP .exe (not the installer, no
need for that) and double-click it. If you'd installed Wine via RPM above
you'd be prompted to use Wine to open/run it.




Q3:
A sample Shell script to run winscp to copy over a text file in ASCII
mode (yes, this is the ASCII mode equivalent in ftp) via sftp / scp
protocol. Yes, I could have used unix2dos or Perl to convert a file
first before copying it using sftp/scp but due to policy in place, I was
told not to do conversion (which I can't understand why)


This is what I don't understand. Why not just use the OpenSSH SCP/SFTP
stuff which is almost certainly already installed to copy this file over
from wherever? Then all you need is to set up SSH keys and have a script
similar to:


###########
#!/bin/bash

REMOTE_HOST=remote.host
REMOTE_USER=remoteuser
REMOTE_FILEPATH=/path/to/remotefile.txt
LOCAL_FILEPATH=/path/to/localfile.txt

scp $REMOTE_USER@REMOTE_HOST:$REMOTE_FILEPATH $LOCAL_FILEPATH
# Optionally convert the file (uncomment the correct direction below to
# activate)

#dos2unix $LOCAL_FILEPATH
#unix2dos $LOCAL_FILEPATH
###########

So long as the user you run that as has its public SSH key in
"authorized_keys" on $REMOTE_HOST it should do everything you need.


Can you explain why you have to use WinSCP?

Ben
--
Unix Support, MISD, University of Cambridge, England
Plugger of wire, typer of keyboard, imparter of Clue
Life Is Short. It's All Good.

--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list

WINE crossover to run winscp for ASCII mode files transfer
 

>
> It's probably simpler to just go to RPMForge, install their rpmforge-release
> RPM and then do "yum install wine". *But again, for this purpose I don't
> think you need to.
My Linux box doesn't have access to Internet, thus I can't do "yum".
So I'll still need the WINE rpm (with its dependent packages) &
use "rpm -i ..." to install

.

> This is what I don't understand. *Why not just use the OpenSSH SCP/SFTP
> stuff which is almost certainly already installed to copy this file over
> from wherever? *Then all you need is to set up SSH keys and have a script
> similar to:
I have an RHES 4.x box with ssh/sftp/scp client & I need to do ASCII mode
files transfer to/from a remote Windows Openssh server (customer-owned)..
Honestly I don't understand why management doesn't allow me to touch
the original datafile; not even make a copy of the datafile, convert & then
send it over to the remote Windows server; & on the remote Windows server,
there's checksum files which I'll need to get over in ASCII but not allowed to
ssh into the server.



> Can you explain why you have to use WinSCP?
WinScp supports both binary & Ascii mode files transfer but I'm not
sure if it does this at command line prompt (ie winscp /script=file ...)

--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list

WINE crossover to run winscp for ASCII mode files transfer
 

On Sat, Aug 27, 2011 at 10:09:52PM +0800, sunhux G wrote:
> > This is what I don't understand. *Why not just use the OpenSSH SCP/SFTP
> > stuff which is almost certainly already installed to copy this file over
> > from wherever? *Then all you need is to set up SSH keys and have a script
> > similar to:
> I have an RHES 4.x box with ssh/sftp/scp client & I need to do ASCII mode
> files transfer to/from a remote Windows Openssh server (customer-owned)..
> Honestly I don't understand why management doesn't allow me to touch
> the original datafile; not even make a copy of the datafile, convert & then
> send it over to the remote Windows server; & on the remote Windows server,
> there's checksum files which I'll need to get over in ASCII but not
> allowed to ssh into the server.
> > Can you explain why you have to use WinSCP?
> WinScp supports both binary & Ascii mode files transfer but I'm not
> sure if it does this at command line prompt (ie winscp /script=file ...)

It isn't clear how this is an actual answer. RHEL can read/write
files with DOS newlines. The SCP protocol doesn't care about the text
structure, it just copies binary files. WinSCP apparently does the
dos2unix conversion internally, but it's being done client-side, not
in the protocol. Running unix2dos before copying with scp isn't any
different.

However, if management is forcing you to use a windows client to copy
files (with no understanding of the technicalities), perhaps you would
just be better off using a windows system to copy these files?
Getting WINE and WinSCP seems like an unnecessary hack. Is there a
reason why you are introducing the Linux system into this situation?

--
Jonathan Billings <jsbillin@umich.edu>

--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list

WINE crossover to run winscp for ASCII mode files transfer
 

> just be better off using a windows system to copy these files?
> Getting WINE and WinSCP seems like an unnecessary hack. Is there
> a reason why you are introducing the Linux system into this situation?

The Linux box has been there all these while: it's the ftp client that's
been 'getting/putting' files from a remote military-related Windows
Openssh server. I can't replace this Linux box with a Windows box
at my end as this Linux box also do lots of files transfer with other
backend (at my end) HP-Ux & Linux boxes

--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list