Date: Tue, 18 Dec 2007 09:04:17 -0500
From: Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: sshd problem on Windows 2003
Message-ID: <20071218140417.GA19506@ednor.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <fk3t43$79p$1 AT ger DOT gmane DOT org> <000401c84054$c1754de0$0a00a8c0 AT a64x23800p> <20071217033106 DOT GA17135 AT ednor DOT casa DOT cgf DOT cx>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20071217033106.GA17135@ednor.casa.cgf.cx>
User-Agent: Mutt/1.5.16 (2007-06-09)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com

On Sun, Dec 16, 2007 at 10:31:06PM -0500, Christopher Faylor wrote:
>On Sun, Dec 16, 2007 at 06:30:14PM -0800, David Christensen wrote:
>>I moved my C:\cygwin directory aside today and did a fresh install of
>>Cygwin on Windows XP Professional SP2.  I also found that sshd would not
>>start.  There was a clue regarding ownership of the above directory in
>>/var/log/sshd.log.  After RTFM, STFW, and beating my head against the
>>monitor to no avail, my work-around was to go back to a working Cygwin
>>image from November 2006.  As an aside, it seems that Cygwin has become
>>less stable since support for Vista was attempted.
>>
>>Once again, I can only conclude that the underlying problem is
>>insufficient testing of Cygwin and its components.  I understand that
>>this is a monumental, tedious, and largely thankless task.  I
>>volunteered to help with such a few years ago, and the silence was
>>deafening.  When I spoke up about that, I was flamed by key Cygwin
>>maintainers.  We'll see what kind of responses this paragraph generates.
>
>I assume you are referring to this:
>
>http://cygwin.com/ml/cygwin/2004-10/threads.html#00007
>
>although you are clearly misremembering since the silence was not
>deafening and you were not, as far as I can tell, flamed by key Cygwin
>maintainers.
>
>>Given the lack of a significant revenue stream for Cygwin and for
>>GNU/OSS tools, I don't see the stability situation improving.  My
>>strategy remains to take a copy of the C:\cygwin\setup tree every now
>>and then, and keep the images for a long time.
>
>If this is important to you, then why don't you contact Red Hat and
>purchase a support license?  They release stable versions of Cygwin
>on a regular basis.

Hmm.  Still no response.

Just like last time.

It seems to me that if you are interested in making accusations and
assertions you should be willing to defend them.

cgf

--
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/