public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Nellis, Kenneth" <Kenneth.Nellis@conduent.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: How to find out the current cygwin version?
Date: Fri, 08 Sep 2017 13:06:00 -0000	[thread overview]
Message-ID: <BN6PR2001MB10744EF61D075A11B74EE258F1950@BN6PR2001MB1074.namprd20.prod.outlook.com> (raw)
In-Reply-To: <70e25f3b-8086-4e3d-e4b1-7bbbc6a44599@gmail.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 832 bytes --]

From: David Billinghurst 
> On 8/09/2017 14:39, Ben Stover via cygwin wrote:
> 
> > Assume I get to another (Windows) computer where Cygwin is already
> installed.
> >
> > How can I find out which version of Cygwin is currently installed?
> cygcheck --version             # for cygwin dll
> ...

This isn't technically correct, right? This gives the version of
cygcheck itself, not the cygwin DLL, which is what was really
being requested.

Instead, use: cygcheck -c cygwin

Or, as I do (and Corinna already suggested): uname -a
or, more quietly: uname -r

--Ken Nellis

\0ТÒÐÐ¥\a&ö&ÆVÒ\a&W\x06÷'G3¢\x02\x02\x02\x02\x02\x02\x06‡GG\x03¢òö7–wv–âæ6öÒ÷\a&ö&ÆV×2æ‡FÖÀФd\x15\x13¢\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x06‡GG\x03¢òö7–wv–âæ6öÒöf\x17\x12ðФFö7VÖVçF\x17F–öã¢\x02\x02\x02\x02\x02\x02\x02\x02\x06‡GG\x03¢òö7–wv–âæ6öÒöFö72æ‡FÖÀÐ¥Vç7V'67&–&R\x06–æfó¢\x02\x02\x02\x02\x02\x06‡GG\x03¢òö7–wv–âæ6öÒöÖÂò7Vç7V'67&–&R×6–×\x06ÆPРÐ

  parent reply	other threads:[~2017-09-08 13:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-08  4:40 Ben Stover via cygwin
2017-09-08  4:44 ` David Billinghurst
2017-09-08  8:16   ` Corinna Vinschen
2017-09-08 13:06   ` Nellis, Kenneth [this message]
2017-09-08 15:39     ` Ian Lambert via cygwin
2017-09-08 15:41   ` Larry Hall (Cygwin)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=BN6PR2001MB10744EF61D075A11B74EE258F1950@BN6PR2001MB1074.namprd20.prod.outlook.com \
    --to=kenneth.nellis@conduent.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).