[PATCH] Clarify FAQ 1.5 What version of Cygwin is this, anyway?

[Brian Inglis]

On 2020-07-04 09:35, Jon Turney wrote:
> On 04/07/2020 04:47, Brian Inglis wrote:
>> On 2020-07-03 17:17, Brian Inglis wrote:
>>> Relate Cygwin DLL to Unix kernel,
>>> add required options to command examples,
>>> differentiate Unix and Cygwin commands;
>>> mention that the cygwin package contains the DLL.
>>>
>>> ---
>>>   faq/faq.html | 34 ++++++++++++++++++++++++----------
>>>   1 file changed, 24 insertions(+), 10 deletions(-)
>>
>> Patch to:
>>     https://cygwin.com/git/?p=cygwin-htdocs.git;f=faq/faq.html;hb=HEAD
>> as a result of thread:
>>     https://cygwin.com/pipermail/cygwin/2020-July/245442.html
> 
> Thanks for looking at this.
> 
> My perspective is that, if (as appears to be the case here) the problem is with
> people who can't or won't read and *absorb* the available information, the
> solution is not to add more words reiterating and expanding, but rather to focus
> on clarifying the existing words.
> 
> So, I'd think this faq should start with a paragraph consisting of a single
> sentence similar to:
> 
> "To find the version of the Cygwin DLL installed, you can use `uname -a`, as you
> would for a Unix kernel".
> 
> Feel free to elaborate on alternatives and refinements on that in later paragraphs.
> 
> If you're touching this FAQ, please also replace the literal `setup.exe` with
> `the setup program` or similar circumlocutions, as we no longer use that literal
> name.

Thanks Jon,

Good point, this will now read:

"1.5. What version of Cygwin is this, anyway?

To find the version of the Cygwin DLL installed, you can use: *uname -a*; as you
would for a Unix kernel. As the Cygwin DLL takes the place of a Unix kernel, you
can also use any of the Unix compatible commands: *uname -srvm*;
*head /proc/version*; or the Cygwin command: *cygcheck -V*. Refer to each
command's `--help` output or the _Cygwin User's Guide_ for more information.

If you are looking for the version number for the whole Cygwin release, there is
none. Each package in the Cygwin release has its own version, and the cygwin
package containing the Cygwin DLL and Cygwin system specific utilities is just
another (but very important!) package. The packages in Cygwin are continually
improving, thanks to the efforts of net volunteers who maintain the Cygwin
binary ports. Each package has its own version numbers and its own release process.

So, how do you get the most up-to-date version of Cygwin? Easy. Just download
the Cygwin Setup program by following the instructions _here_. The Setup program
will handle the task of updating the packages on your system to the latest
version. For more information about using Cygwin's Setup program, see _Setting
Up Cygwin_ in the Cygwin User's Guide."

and I have also changed the other occurrences of setup.exe to use the Cygwin
Setup program or similar.

In the above, I think we should also change the link _here_ (so '90s!) to
_installation instructions_.

Maybe also under 1.6:

	https://cygwin.com/faq.html#faq.what.who

which seems to be from when Redhat sold Cygwin, so:
- comment out or otherwise memorialize Yaakov;
- omit Redhat from Corinna's entry, and clean up;
- change "people; a complete list can be found _here_" link to just _maintainers_;
- anyone else with committer rights who should be added?
- maybe update that guy Jon? ;^>

In the following para:

"Please note that all of us working on Cygwin try to be as responsive as
possible and deal with patches and questions as we get them, but realistically
we don't have time to answer all of the email that is sent to the main mailing
list. Making Net releases of the Win32 tools and helping people on the Net out
is not our primary job function, so some email will have to go unanswered."

"working" to "volunteering";
remove "Win32" and "Net" there and earlier paras;
change "is not our primary job function" to "is an activity in our spare time":

Anyhting else that comes to mind?

-- 
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.]