RE: cygwin deadlocks due to lack of money

RE: cygwin deadlocks due to lack of money

[kevin.lawton]

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'. 
Quite honestly, I wondered what 64-bit op system you were hoping to test on. As I said: it all seems to be okay running Win-32 on an AMD-64, and I've not seen 64-bit Windoze around yet. 
I would be surprised if you were planning on a Linux version of cygwin for obvious reasons, and AFAIK BeOS, PetrOS, Lindows, Plan9, etc, etc, haven't got 64-bit versions out yet. 
Anyway, you've made your point: why should you spend a minute or so telling me something you already know when, with one simple put-down, you can suggest I go search through archives for an hour ?  Fine ! Nice attitude, mate ! 
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. Bye.   
   
-----Original Message-----
From: Christopher Faylor
[mailto:cgf-no-personal-reply-please@cygwin.com]
Sent: 31 October 2003 17:00
To: cygwin@cygwin.com
Subject: Re: cygwin deadlocks due to lack of money

On Fri, Oct 31, 2003 at 04:30:00PM -0000, kevin.lawton@bt.com wrote:
>You expect cygwin NOT to run on an Athlon 64 system ?  How so ?  Under
>what operating system ?  Under 32-bit Windoze, nothing seems any
>different - you're not planning a Linux version of cygwin, are you ?

Hmm.  It seems like a search of the mailing list archives would be a
pretty simple way of satisfying this kind of idle curiousity.

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/


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

Re: cygwin deadlocks due to lack of money

[Christopher Faylor]

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.

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

I wasn't seriously suggesting that anyone was going to send me a 64-bit
system, either.

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.

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

Cygwin on Lindows (was Re: cygwin deadlocks due to lack of money)

[Linda W.]

Christopher Faylor wrote:

>... suggesting that we'd be working on a version of cygwin for
>linux, 
>
---
    Yeah...I was wondering when there'd be a version available on Lindows. 

I'll volunteer to do counting of linux system calls in the 
cygwin-on-lindows-win-layer-on-linux-find vs. native linux find!

-linda
:-)


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