From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: Windows 2019 support?
Date: Sat, 19 Sep 2020 10:10:18 -0600 [thread overview]
Message-ID: <1e8cd4a1-7c19-dd0b-dde5-c49e08ff7d6c@SystematicSw.ab.ca> (raw)
In-Reply-To: <523476b2-98a6-7854-7a5a-b229e2fb36d6@towo.net>
On 2020-09-19 01:37, Thomas Wolff wrote:
>
> Am 19.09.2020 um 05:32 schrieb Brian Inglis:
>> On 2020-09-17 09:52, Bill Stewart wrote:
>>> On Thu, Sep 17, 2020 at 7:58 AM Chris Bovitz wrote:
>>> Cygwin can be expected to run on all modern, released versions of Windows.
>>>> State [sic] January 2016 this includes Windows Vista, Windows Server 2008
>>>> and all later versions of Windows up to Windows 10 and Windows Server 2016.
>>>>
>>>> To me, this implies that Windows Server 2019 is supported, but is that
>>>> true? If so, could the FAQ be updated to show that? Thanks.
>>>>
>>> Windows Server 2019 is just the server version of Windows 10 1809. In my
>>> testing it works without any issues.
>>>
>>> My recommendation is for the FAQ to state:
>>>
>>> "Cygwin can be expected to run on all modern, released versions of Windows.
>>> Since January 2016 this includes Windows Vista, Windows Server 2008, and
>>> all later versions."
>> Wanted to enumerate Vista, 7, 8, 8.1, 10 progression to be clear, exclude S
>> mode, add Cygwin32 on ARM, specify 64 bit only AMD/Intel, and remove any dates
>> to avoid confusion in future, so patched to read:
>>
>> "1.2. What versions of Windows are supported?
>>
>> Cygwin can be expected to run on all modern, released versions of Windows, from
>> Windows Vista, 7, 8, 8.1, 10, Windows Server 2008 and all later versions of
>> Windows, except Windows S mode due to its limitations. The 32 bit version of
>> Cygwin also runs in the WOW64 32 bit environment on released 64 bit versions of
>> Windows including ARM PCs, the 64 bit version of course only on 64 bit AMD/Intel
>> compatible PCs."
> You'd mention WOW64 but not Windows 32 bit. Is that on purpose? It might suggest
> to someone that cygwin does not run on a 32 bit processor but it does.
That wording was in Corinna's update:
https://cygwin.com/git/?p=newlib-cygwin.git;a=blobdiff;f=winsup/doc/faq-what.xml;h=056cf9132fc42da2e9c68c5a27b291a9f78eeb21;hp=beae035c3ca74eb4eeb859f4f5b06282b096a3f8;hb=db9a8c9983066cfd5ebc7b50c47c118143c55a10;hpb=0f5a7b350ff74b5e7649bce03bc212d3a121acea
and took it as obvious that the 32 bit version (only one available at that time)
was built for and runs under 32 bit Windows, but "also runs" in those other
environments.
When prompted by comments we are trying to patch docs to clarify (and update)
the info, with minimal changes necessary.
[No idea even what we ran at home after W98SE before W7, maybe XP SP3?]
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in IEC units and prefixes, physical quantities in SI.]
next prev parent reply other threads:[~2020-09-19 16:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-17 13:58 Chris Bovitz
2020-09-17 15:52 ` Bill Stewart
2020-09-19 3:32 ` Brian Inglis
2020-09-19 7:37 ` Thomas Wolff
2020-09-19 16:10 ` Brian Inglis [this message]
2020-09-21 14:49 ` Bill Stewart
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=1e8cd4a1-7c19-dd0b-dde5-c49e08ff7d6c@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--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).