This is the mail archive of the
mailing list for the Cygwin project.
Re: stty icrnl
- From: Warren Young <wyml at etr-usa dot com>
- To: The Cygwin Mailing List <cygwin at cygwin dot com>
- Date: Thu, 9 Jun 2016 12:34:12 -0600
- Subject: Re: stty icrnl
- Authentication-results: sourceware.org; auth=none
- References: <loom dot 20160606T135902-517 at post dot gmane dot org> <loom dot 20160608T020226-915 at post dot gmane dot org>
On Jun 7, 2016, at 6:05 PM, Brian Inglis <Brian.Inglis@SystematicSw.ab.ca> wrote:
> cu is the normal Unixy way of using a remote USB->serial line, but I can't
> find it in Cygwin packages
Taylor UUCP builds out of the box on Cygwin:
$ wget ftp://ftp.gnu.org/pub/gnu/uucp/uucp-1.07.tar.gz
$ tar xf uucp-1.07.tar.gz
$ cd uucp-1.07
$ configure && make -j11
$ ./cu --version
cu (Taylor UUCP) 1.07
Copyright (C) 1991, 92, 93, 94, 1995, 2002 Ian Lance Taylor
This program is free software; you may redistribute it under the terms of
the GNU General Public LIcense. This program has ABSOLUTELY NO WARRANTY.
> searching for \<cu\>, and cu spews too many hits.
When searching on the Cygwin package search page, adding .exe to executables narrows the results considerably.
As it happens, there is a Cygwin package shipping *cu.exe, but it is not the cu(1) you are looking for. Move along.
Adding a leading slash fixes that:
Found 0 matches for /cu.exe
If you were searching elsewhere (e.g. Google) then, yes, âcuâ is a bad search term. But if you knew that cu comes from the UUCP package, âcu uucpâ leads you right to Taylor UUCP.
See, I *knew* there was a reason I was spending my days on amber VT220s hacking Unix back when I could have been out making Vitamin D!
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple