NetBSD-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: cu take not working?

Dear Michael,

I am very well aware of minicom and lrzsz,
just did not yet quite figure out how to
use them for file transfer. Therefore,
thank you very much for your comments -
they'll be a good start.

Apart from this, I tried cu mainly for one
reason: it is part of the base system, so
I hoped it would work best. (Well, it does

This morning I discovered how to make it
work though, and I think this also explains
what is going wrong: when I say ~take file,
it hangs indefinitely. However, when you
press a few times wildly Ctrl-D (I guess
that does the trick), Ctrl-C and Ctrl-X, it
stops the transfer - which has been even
quite successful. Just: The received file
has two lines that the original does not
have: an empty line and below it a shell
prompt of the kind myhostname$. - Guess
when I transfer the file, it transfers it,
then kicks up this shell prompt, and then
just stops until you "exit" this prompt,
which of course normally you cannot do as
you do not even expect its existence.

So, in short, ~take file + a lot of Ctrl-D,
Ctrl-C & Ctrl-X works.

Thank you very much for your suggestions!

Kind regards,


-------- Original-Nachricht --------
> Datum: Tue, 9 Jun 2009 09:18:01 -0500 (CDT)
> Von: Michael Parson <>
> An:
> Betreff: Re: cu take not working?

> On Tue, 9 Jun 2009, Nino on NetBSD 4.0 wrote:
> > Dear all,
> >
> > Thanks to your support, I now have a working dial-in connection from
> > one machine to another.  Both are running NetBSD 5.0 - generic kernel.
> > For dialing in, I am using cu; tip somehow does not work for me. I can
> > log in, everything is normal (if somewhat slow).
> >
> > But I am experiencing problems when I try to transfer files. When I
> > try to "put" a file, it works perfectly. When I try to "take" a file,
> > cu just appears to hang; on my local machine, where I try to get the
> > file, a file with the right name is created - but it always stays at
> > zero length. I have to pkill cu at the end, and the file is never
> > filled.
> Back when I was doing terminal based dialup, I never used tip/cu/etc
> for doing modem dialing, I used minicom (which can be found in
> $PKGSRC/comms/minicom) for handling the dialup side of the connection.
> I then used one of the protocols designed for file transfers, depending
> on what was available.  In the earlier days, we used stuff like
> x/ymodem, then later, as the modem speeds increased and the coders got
> smarter, we got the zmodem file transfer protocol.  The 'zmodem' method
> has a number of advantages.  First, it transfered the files in streams
> rather than packets.  Second, most terminal programs could be configured
> to automatically accept a zmodem inbound connection once it was started
> on the remote side.
> To transfer a file from the remote host to local, from the shell prompt,
> run:
> $ sz filename.txt
> Once minicom has been properly configured, it will automatically begin
> the file transfer.
> To transfer a file from the local host to the remote, use the 'rz'
> command on the remote end and then tell minicom to use the 'sz' command
> to initiate an upload.
> You can find the zmodem bits in $PKGSRC/comms/lrzsz
> Maybe not exactly what you were looking for, but it made doing what
> you've described much simpler.
> -- 
> Michael Parson

GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT!
Jetzt freischalten unter

Home | Main Index | Thread Index | Old Index