From: "Buchbinder, Barry (NIH/NIAID) [E]" <BBuchbinder@niaid.nih.gov>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Date: Thu, 26 Jan 2012 07:07:52 -0500
Subject: W7 and rebase [was "YA call for snapshot testing"]
Message-ID: <0105D5C1E0353146B1B222348B0411A20A51C567A5@NIHMLBX02.nih.gov>
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Content-Transfer-Encoding: 8bit

marco atzeri sent the following at Friday, January 20, 2012 3:49 AM
>my 2c$ : As rebaseall is almost mandatory on W7/64 and we are always
>suggesting it to anyone with fork problem,

My box was upgraded from XP Pro to W7 a couple of months ago.  At the
beginning I was getting fork errors all the time when running scripts.
It eventually went away (mostly*), though I don't remember whether it
was as a result of something that knowingly did I did.

(* It is now rare enough to not be a problem in practice.  I'll kill
the script and start over.)

The old guidance was that one shouldn't rebase unless one is told to.
My question is whether that has changed.  Is it now, "rebase if you
have W7"?

--------

For the record, after the switch from XP to W7 I had another problem.
I had the windows and system32 directories at the end of my path.  When
running scripts, bash could sometimes miss /bin/sort and end up using
Windows' sort.  It was intermittant and did not always happen at the
same place in the script.  Bizzarre!

I fixed it by taking windows and system32 out of my path.

No action requested, but I thought I'd mention it as a datum in case
it comes up again for someone else.

- Barry
  Disclaimer: Statements made herein are not made on behalf of NIAID.


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple