Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com To: cygwin AT cygwin DOT com From: Shankar Unni Subject: Re: ssh configuration that is pulling my hair out! Date: Mon, 26 Jan 2004 11:16:26 -0800 Lines: 18 Message-ID: References: <6 DOT 0 DOT 1 DOT 1 DOT 0 DOT 20040126123546 DOT 03cde5b0 AT 127 DOT 0 DOT 0 DOT 1> <20040126184150 DOT GC15847 AT redhat DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet AT sea DOT gmane DOT org User-Agent: Mozilla Thunderbird 0.5a (Windows/20040120) In-Reply-To: <20040126184150.GC15847@redhat.com> Christopher Faylor wrote: > I actually suspect that this is one of many cases where a FAQ entry > would be of little help and I'm always wary of adding so much verbiage > to the FAQ that it becomes unusable. I suppose it's the same thought process that prompts people who install 3rd party products built on top of ancient versions of Cygwin to come over here to ask for help with their installation. I think a specific FAQ is indicated for this (it's a frequent enough pattern): if they install a Cygwin distribution, or configure any component of the distribution, using instructions or software from anywhere other than cygwin.com or its official mirrors, they need to go back to the source to ask their questions first. Larry's FAQ entry sounds quite reasonable. Maybe add a clause about Cygwin software downloaded from or distributed by non-cygwin sites. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/