* Please report this problem to the public mailing list...
@ 2017-01-24 15:22 Nellis, Kenneth (Conduent)
2017-01-24 15:33 ` cyg Simple
0 siblings, 1 reply; 6+ messages in thread
From: Nellis, Kenneth (Conduent) @ 2017-01-24 15:22 UTC (permalink / raw)
To: cygwin
We have received several postings of people responding to the Cygwin-generated
message: WARNING: ... Please report this problem to the public mailing list
cygwin@cygwin.com.
I wonder how many places such messages are present in the Cygwin code.
Just throwing out an idea here to help people help themselves...
Consider all such messages carrying an error code and referred to a Cygwin web
page that contained links to separate pages for each error code, and those pages,
then, would contain the latest information as to how to recover from the
respective errors.
--Ken Nellis
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Please report this problem to the public mailing list...
2017-01-24 15:22 Please report this problem to the public mailing list Nellis, Kenneth (Conduent)
@ 2017-01-24 15:33 ` cyg Simple
2017-01-24 19:51 ` Corinna Vinschen
0 siblings, 1 reply; 6+ messages in thread
From: cyg Simple @ 2017-01-24 15:33 UTC (permalink / raw)
To: cygwin
On 1/24/2017 10:21 AM, Nellis, Kenneth (Conduent) wrote:
> We have received several postings of people responding to the Cygwin-generated
> message: WARNING: ... Please report this problem to the public mailing list
> cygwin@cygwin.com.
>
> I wonder how many places such messages are present in the Cygwin code.
>
> Just throwing out an idea here to help people help themselves...
>
> Consider all such messages carrying an error code and referred to a Cygwin web
> page that contained links to separate pages for each error code, and those pages,
> then, would contain the latest information as to how to recover from the
> respective errors.
>
Great idea. I can see this
> Problem reports: http://cygwin.com/problems.html
being referenced instead of the mail list which the person may not be
subscribed to. Care to present a patch to the web page? And we need a
patch to the text parts of Cygwin to point to the web page.
--
cyg Simple
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Please report this problem to the public mailing list...
2017-01-24 15:33 ` cyg Simple
@ 2017-01-24 19:51 ` Corinna Vinschen
2017-01-24 19:53 ` Corinna Vinschen
0 siblings, 1 reply; 6+ messages in thread
From: Corinna Vinschen @ 2017-01-24 19:51 UTC (permalink / raw)
To: cygwin
[-- Attachment #1: Type: text/plain, Size: 1431 bytes --]
On Jan 24 10:32, cyg Simple wrote:
> On 1/24/2017 10:21 AM, Nellis, Kenneth (Conduent) wrote:
> > We have received several postings of people responding to the Cygwin-generated
> > message: WARNING: ... Please report this problem to the public mailing list
> > cygwin@cygwin.com.
> >
> > I wonder how many places such messages are present in the Cygwin code.
> >
> > Just throwing out an idea here to help people help themselves...
> >
> > Consider all such messages carrying an error code and referred to a Cygwin web
> > page that contained links to separate pages for each error code, and those pages,
> > then, would contain the latest information as to how to recover from the
> > respective errors.
> >
>
> Great idea. I can see this
>
> > Problem reports: http://cygwin.com/problems.html
>
> being referenced instead of the mail list which the person may not be
> subscribed to. Care to present a patch to the web page? And we need a
> patch to the text parts of Cygwin to point to the web page.
If somebody cares to write a patch for a new FAQ entry, I change the
Cygwin source to point it out.
On second thought, Cygwin should probably simple tell the user to update
the outdated Cygwin installation instead.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Please report this problem to the public mailing list...
2017-01-24 19:51 ` Corinna Vinschen
@ 2017-01-24 19:53 ` Corinna Vinschen
2017-01-24 20:27 ` Brian Inglis
0 siblings, 1 reply; 6+ messages in thread
From: Corinna Vinschen @ 2017-01-24 19:53 UTC (permalink / raw)
To: cygwin
[-- Attachment #1: Type: text/plain, Size: 1944 bytes --]
On Jan 24 20:50, Corinna Vinschen wrote:
> On Jan 24 10:32, cyg Simple wrote:
> > On 1/24/2017 10:21 AM, Nellis, Kenneth (Conduent) wrote:
> > > We have received several postings of people responding to the Cygwin-generated
> > > message: WARNING: ... Please report this problem to the public mailing list
> > > cygwin@cygwin.com.
> > >
> > > I wonder how many places such messages are present in the Cygwin code.
> > >
> > > Just throwing out an idea here to help people help themselves...
> > >
> > > Consider all such messages carrying an error code and referred to a Cygwin web
> > > page that contained links to separate pages for each error code, and those pages,
> > > then, would contain the latest information as to how to recover from the
> > > respective errors.
> > >
> >
> > Great idea. I can see this
> >
> > > Problem reports: http://cygwin.com/problems.html
> >
> > being referenced instead of the mail list which the person may not be
> > subscribed to. Care to present a patch to the web page? And we need a
> > patch to the text parts of Cygwin to point to the web page.
>
> If somebody cares to write a patch for a new FAQ entry, I change the
> Cygwin source to point it out.
>
> On second thought, Cygwin should probably simple tell the user to update
> the outdated Cygwin installation instead.
Oh, wait. The current text already *is*:
Cygwin WARNING:
Couldn't compute FAST_CWD pointer. This typically occurs if you're using
an older Cygwin version on a newer Windows. Please update to the latest
available Cygwin version from https://cygwin.com/. If the problem persists,
please see https://cygwin.com/problems.html
However, this doesn't help with very old and 3PP installations.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Please report this problem to the public mailing list...
2017-01-24 19:53 ` Corinna Vinschen
@ 2017-01-24 20:27 ` Brian Inglis
2017-01-25 20:27 ` cyg Simple
0 siblings, 1 reply; 6+ messages in thread
From: Brian Inglis @ 2017-01-24 20:27 UTC (permalink / raw)
To: cygwin
On 2017-01-24 12:53, Corinna Vinschen wrote:
> On Jan 24 20:50, Corinna Vinschen wrote:
>> On Jan 24 10:32, cyg Simple wrote:
>>> On 1/24/2017 10:21 AM, Nellis, Kenneth (Conduent) wrote:
>>>> We have received several postings of people responding to the
>>>> Cygwin-generated message: WARNING: ... Please report this
>>>> problem to the public mailing list cygwin@cygwin.com.
>>>> I wonder how many places such messages are present in the
>>>> Cygwin code. Just throwing out an idea here to help people help
>>>> themselves...
>>>> Consider all such messages carrying an error code and referred
>>>> to a Cygwin web page that contained links to separate pages for
>>>> each error code, and those pages, then, would contain the
>>>> latest information as to how to recover from the respective
>>>> errors.
>>> Great idea. I can see this
>>>> Problem reports: http://cygwin.com/problems.html
>>> being referenced instead of the mail list which the person may
>>> not be subscribed to. Care to present a patch to the web page?
>>> And we need a patch to the text parts of Cygwin to point to the
>>> web page.
>> If somebody cares to write a patch for a new FAQ entry, I change
>> the Cygwin source to point it out.
>> On second thought, Cygwin should probably simple tell the user to
>> update the outdated Cygwin installation instead.
> Oh, wait. The current text already *is*:
> Cygwin WARNING:
> Couldn't compute FAST_CWD pointer. This typically occurs if you're
> using an older Cygwin version on a newer Windows. Please update to
> the latest available Cygwin version from https://cygwin.com/. If the
> problem persists, please see https://cygwin.com/problems.html
> However, this doesn't help with very old and 3PP installations.
Seems to me most of those messages are generated by third party apps
installing a(n old) version of Cygwin without any update instructions,
or consideration that while *their* app may not need updated when the
system is patched, Cygwin may (*cough* "Windows" BitKeeper *cough*).
Users should be suspicious when a vendor app tells them to report
problems to "some other folks" who are not the vendor: they should
take it as a warning that the vendor disclaims all responsibility
for their own choice of infrastructure, and call up and blast the
vendor's management! ;^>
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Please report this problem to the public mailing list...
2017-01-24 20:27 ` Brian Inglis
@ 2017-01-25 20:27 ` cyg Simple
0 siblings, 0 replies; 6+ messages in thread
From: cyg Simple @ 2017-01-25 20:27 UTC (permalink / raw)
To: cygwin
On 1/24/2017 3:27 PM, Brian Inglis wrote:
> On 2017-01-24 12:53, Corinna Vinschen wrote:
>> On Jan 24 20:50, Corinna Vinschen wrote:
>>> On Jan 24 10:32, cyg Simple wrote:
>>>> On 1/24/2017 10:21 AM, Nellis, Kenneth (Conduent) wrote:
>>>>> We have received several postings of people responding to the
>>>>> Cygwin-generated message: WARNING: ... Please report this
>>>>> problem to the public mailing list cygwin@cygwin.com.
>>>>> I wonder how many places such messages are present in the
>>>>> Cygwin code. Just throwing out an idea here to help people help
>>>>> themselves...
>>>>> Consider all such messages carrying an error code and referred
>>>>> to a Cygwin web page that contained links to separate pages for
>>>>> each error code, and those pages, then, would contain the
>>>>> latest information as to how to recover from the respective
>>>>> errors.
>>>> Great idea. I can see this
>>>>> Problem reports: http://cygwin.com/problems.html
>>>> being referenced instead of the mail list which the person may
>>>> not be subscribed to. Care to present a patch to the web page?
>>>> And we need a patch to the text parts of Cygwin to point to the
>>>> web page.
>>> If somebody cares to write a patch for a new FAQ entry, I change
>>> the Cygwin source to point it out.
>>> On second thought, Cygwin should probably simple tell the user to
>>> update the outdated Cygwin installation instead.
>> Oh, wait. The current text already *is*:
>> Cygwin WARNING:
>> Couldn't compute FAST_CWD pointer. This typically occurs if you're
>> using an older Cygwin version on a newer Windows. Please update to
>> the latest available Cygwin version from https://cygwin.com/. If the
>> problem persists, please see https://cygwin.com/problems.html
>> However, this doesn't help with very old and 3PP installations.
>
> Seems to me most of those messages are generated by third party apps
> installing a(n old) version of Cygwin without any update instructions,
> or consideration that while *their* app may not need updated when the
> system is patched, Cygwin may (*cough* "Windows" BitKeeper *cough*).
> Users should be suspicious when a vendor app tells them to report
> problems to "some other folks" who are not the vendor: they should
> take it as a warning that the vendor disclaims all responsibility
> for their own choice of infrastructure, and call up and blast the
> vendor's management! ;^>
>
Maybe the warning should point out the full path to the cygwin1.dll file
having the issue? Of course this won't solve prior versions but then we
can't do that regardless of the patch.
--
cyg Simple
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2017-01-25 20:27 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-01-24 15:22 Please report this problem to the public mailing list Nellis, Kenneth (Conduent)
2017-01-24 15:33 ` cyg Simple
2017-01-24 19:51 ` Corinna Vinschen
2017-01-24 19:53 ` Corinna Vinschen
2017-01-24 20:27 ` Brian Inglis
2017-01-25 20:27 ` cyg Simple
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).