Re: Cygwin 1.5.13 Vs. SETI@Home on Windows XP

2005-03-18 Thread Aaron Humphrey
On Thu, 17 Mar 2005 18:30:03 -0800, David Rothenberger wrote: > On 3/17/2005 6:20 PM, John Whitlock wrote: > > I was having the same problem as Patrick Graebal (see Bash hangs, CTRL-C > > required). The cygwin shell was very slow to start, and executing > > "bash --login -i -x" showed that the tim

Re: Cygwin 1.5.13 Vs. SETI@Home on Windows XP

2005-03-18 Thread Tomasz Rojek
>> I was having the same problem as Patrick Graebal (see Bash hangs, CTRL-C >> required). The cygwin shell was very slow to start, and executing >> "bash --login -i -x" showed that the time consuming programs were the >> same >> (id -un, uname -s, etc.). > I believe you're experiencing the same p

Re: Cygwin 1.5.13 Vs. SETI@Home on Windows XP

2005-03-17 Thread David Rothenberger
On 3/17/2005 6:20 PM, John Whitlock wrote: I was having the same problem as Patrick Graebal (see Bash hangs, CTRL-C required). The cygwin shell was very slow to start, and executing "bash --login -i -x" showed that the time consuming programs were the same (id -un, uname -s, etc.). I also tried r

Cygwin 1.5.13 Vs. SETI@Home on Windows XP

2005-03-17 Thread John Whitlock
I was having the same problem as Patrick Graebal (see Bash hangs, CTRL-C required). The cygwin shell was very slow to start, and executing "bash --login -i -x" showed that the time consuming programs were the same (id -un, uname -s, etc.). I also tried reinstalling base packages, a complete reins

Cygwin 1.5.13 Vs. SETI@Home on Windows XP

2005-03-17 Thread John Whitlock
I was having the same problem as Patrick Graebal (see Bash hangs, CTRL-C required). The cygwin shell was very slow to start, and executing "bash --login -i -x" showed that the time consuming programs were the same (id -un, uname -s, etc.). I also tried reinstalling base packages, a complete reins