> Whether you typed it yourself or not, those type of disclaimers are
actually not allowed in mail to mailing lists at this site:
> http://sourceware.org/lists.html
OK. I can't post. My mistake was attempting to make a suggestion to a
person asking for help - which is more than you did. What a wa
> Hmm... 9 lines of content, 10 of disclaimer... *sip!*
> Eew, and the disclaimer isn't even line-wrapped...
> (How come PCYMTNILOAUD is not on the OLOCA yet? ;-))
Ah. You think I typed that, myself? I didn't. It was automatically
appended by the local email system. Many corporate email systems
> In any case, it's pretty weird that bash randomly fails to spawn child
processes! It wreaks havoc on a number of my scripts.
Thought: Silent failure to spawn used to happen on some UNIX boxen when
the process table was full (or one slot remained and user != root).
Might something like this be c
http://www.cygwin.com/ml/cygwin/2005-01/msg01100.html
Worked for me. I needed a 2004 vintage to avoid regression testing a big app,
so Mr. Castro's Time Machine was really helpful.
Cygwin is brittle. This is nothing to whine about, because it is caused by
fundamental low level incompatibilities
Hi,
Perhaps someone who knows can confirm that I've got this right:
The executables in a Cygwin download can be much older than the download
date, where "much" > 3 years.
This suggests that executables are only rebuilt when their own sources
change. Previously built executables can continue to b
5 matches
Mail list logo
