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 Date: Tue, 1 Feb 2005 17:38:06 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Hyperthreading problem: remote access Message-ID: <20050201223806.GB8400@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com References: <41FD7F9D DOT 9060608 AT pulserate DOT com> <6 DOT 2 DOT 0 DOT 14 DOT 0 DOT 20050130195041 DOT 05c31ec0 AT pop DOT prospeed DOT net> <41FFFC27 DOT 4000808 AT pulserate DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41FFFC27.4000808@pulserate.com> User-Agent: Mutt/1.4.1i On Tue, Feb 01, 2005 at 11:01:11PM +0100, Joris van der Sande wrote: >Larry Hall wrote: >>Chris has already answered that question earlier in the discussion. He >>needs physical access to the machine to resolve this problem. Remote >>access isn't enough. > >Forgive my ignorance, but I read the archives back to 1 jan 2004 but >found no explanation why remote access doesn't help the developers to >track down the problem. Could someone please point me to the relevant >postings? I can't imagine why this would be a useful thing to discuss here. However, here is one of the times I repeated that I don't want to do this over the internet: http://sources.redhat.com/ml/cygwin/2005-01/msg00521.html 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/