Re: cygwin-latest: compile errors related to sockaddr_storage, dirent->d_type and dirent->d_ino

From: Linus Torvalds <torvalds@osdl.org>
Date: Jan 19, 2006, 21:16 UTC
Message-ID: <Pine.LNX.4.64.0601191309130.3240@g5.osdl.org>
In-Reply-To: <20060119203428.GA5090@trixie.casa.cgf.cx>

On Thu, 19 Jan 2006, Christopher Faylor wrote:

Show 5 quoted lines

> 
> Btw, we're looking to roll out a new release of cygwin which fixes the
> embarrassing typo in sockaddr_storage.  It is fixed in cygwin snapshots:
> 
> http://cygwin.com/snapshots/

Quick question for cygwin people (I asked this at an earlier point, but I don't think there was any reply): would cygwin prefer using "vfork()" over "fork()", or is there no advantage? With vfork(), I could imagine that you might avoid a lot of strange VM games..

I think almost all of the git fork usage is of the type where "vfork()" would work fine (git-daemon in non-inetd form is an exception, perhaps the only one).

So if using vfork() is preferable, we probably should do that. It tends to be a small performance improvement on Linux too, although on Linux it's really pretty much in the noise.

Alternatively, is there anything else we can do that makes things easier?

			Linus