From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15068 invoked by alias); 3 Nov 2003 11:05:11 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 15061 invoked from network); 3 Nov 2003 11:05:10 -0000 Received: from unknown (HELO i2kc05-ukbr.domain1.systemhost.net) (217.32.164.139) by sources.redhat.com with SMTP; 3 Nov 2003 11:05:10 -0000 Received: from i2km96-ukbr.domain1.systemhost.net ([193.113.197.84]) by i2kc05-ukbr.domain1.systemhost.net with Microsoft SMTPSVC(5.0.2195.6713); Mon, 3 Nov 2003 11:05:09 +0000 Received: from i2km38-ukdy.domain1.systemhost.net ([193.113.30.77]) by i2km96-ukbr.domain1.systemhost.net with Microsoft SMTPSVC(5.0.2195.6713); Mon, 3 Nov 2003 11:05:09 +0000 X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: cygwin deadlocks due to lack of money Date: Mon, 03 Nov 2003 11:05:00 -0000 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: To: X-OriginalArrivalTime: 03 Nov 2003 11:05:09.0961 (UTC) FILETIME=[58C38390:01C3A1FA] X-SW-Source: 2003-11/txt/msg00083.txt.bz2 -----Original Message----- From: Christopher Faylor [mailto:cgf-no-personal-reply-please@cygwin.com] Sent: 31 October 2003 18:58 To: cygwin@cygwin.com Subject: Re: cygwin deadlocks due to lack of money On Fri, Oct 31, 2003 at 06:13:17PM -0000, kevin.lawton@bt.com wrote: >Okay, I spent some time looking at the mailing list archives but found >nothing which added anything to this discussion. I would have hoped >that my intended offer of use of an Athlon 64 system would have counted >as more than just 'idle curiosity' and, anyway, I'm never 'idle'. I interpreted your response as nonserious since you seemed to be humorously suggesting that we'd be working on a version of cygwin for linux, which is obviously nonsensical. I thought it was self evident that I was talking about getting cygwin working on a 64 bit version of windows and didn't seriously think that you were suggesting that we were thinking about getting cygwin working on some other system. I guess I was wrong. I didn't realise that 64-bit windoze was actually available as yet, so I gu= essed you were thinking of something else.=20 Just because the 'Cygwin on Linux' bit was a joke (and a pretty obvious one= at that), doesn't mean the rest wasn't serious. I notice someone else has = mentioned 'Cygwin on Lindows', which I find even funnier. ROFL=20 >BTW My plan was to either test for you (under direction) or make the >machine available to you via some sort of terminal server and my ADSL >connection. I didn't fancy having it transported. I did actually want >to contribute something to the cygwin project, as I've found it so >valuable over the past couple of years. Shame you weren't interested. Actually, while I appreciate that you wanted to contribute something, I'm not interested in either scenario. The effort of working on cygwin remotely either by having someone else do testing (especially when the someone doesn't really know cygwin internals) or by logging in over the internet was not what I was looking for. Having a system sitting in my office that I could hack on when the mood hit me was more of what I was looking for.=20 I know from experience that working remotely via M$ terminal server and an = ADSL line is close enough to being on the machine itself as to make negligi= ble difference in most cases. Maybe not with cygwin - I'll give it a try.=20 I wasn't seriously suggesting that anyone was going to send me a 64-bit system, either.=20 I get the felling that you are not exactly 'local' to me, or I'd have been = considering lending one for a while.=20 Here's the kind of google search term I would have used to find discussion: 64-bit windows cygwin site:cygwin.com cgf This was my first tray and it unearths some discussion as the first hit. I'm sure that there are search refinements possible but, to answer your aggrieved question, all of the discussions basically revolve around someone reporting that cygwin doesn't work right in some beta or release candidate version of windows for 64 bit platforms and my suggesting that the problem won't be solved until I (or Corinna or Pierre) have a 64 bit system to hack on.=20 When I have a 64-bit Windoze installed on one of my systems I'll let you kn= ow.=20 Kevin.=20 -- 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/ -- 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/