Re: Extend faq.using to discuss fork failures

2011-11-04 Thread Jon TURNEY
On 03/11/2011 21:05, Christopher Faylor wrote: I would still prefer eschewing actively negative words like hostile and just neutrally stating that Windows does not use a fork/exec model and does not offer any easy way to implement fork. Hmm, yes, I'll fix that. I'd also like to see specific

Re: Extend faq.using to discuss fork failures

2011-11-04 Thread Jon TURNEY
On 03/11/2011 17:17, Corinna Vinschen wrote: Thanks for doing that. I looks good to me, with just one exception. +listitemAddress space layout randomization (ASLR). Starting with +Vista, Windows implements ASLR, which means that thread stacks, +heap, memory-mapped files, and statically-linked

Re: Extend faq.using to discuss fork failures

2011-11-04 Thread Christopher Faylor
On Fri, Nov 04, 2011 at 01:34:09PM +, Jon TURNEY wrote: On 03/11/2011 21:05, Christopher Faylor wrote: I would still prefer eschewing actively negative words like hostile and just neutrally stating that Windows does not use a fork/exec model and does not offer any easy way to implement

Re: Extend faq.using to discuss fork failures

2011-11-03 Thread Jon TURNEY
On 30/08/2011 14:41, Ryan Johnson wrote: That sounds reasonable, though I suspect we'd want want to keep the concluding bits in the FAQ as well. Unfortunately, summertime free time has come to an end so I don't know when I'll get to this next. Perhaps a good compromise for now would be for you

Re: Extend faq.using to discuss fork failures

2011-11-03 Thread Corinna Vinschen
Hi Jon, On Nov 3 16:35, Jon TURNEY wrote: On 30/08/2011 14:41, Ryan Johnson wrote: That sounds reasonable, though I suspect we'd want want to keep the concluding bits in the FAQ as well. Unfortunately, summertime free time has come to an end so I don't know when I'll get to this next.

Re: Extend faq.using to discuss fork failures

2011-11-03 Thread Christopher Faylor
On Thu, Nov 03, 2011 at 04:35:25PM +, Jon TURNEY wrote: On 30/08/2011 14:41, Ryan Johnson wrote: That sounds reasonable, though I suspect we'd want want to keep the concluding bits in the FAQ as well. Unfortunately, summertime free time has come to an end so I don't know when I'll get to

Re: Extend faq.using to discuss fork failures

2011-08-30 Thread Corinna Vinschen
Hi Ryan, Thanks for the FAQ entry. I had a look now, finally. Two nits: On Aug 25 22:08, Ryan Johnson wrote: Index: winsup/doc/faq-using.xml === RCS file: /cvs/src/src/winsup/doc/faq-using.xml,v retrieving revision 1.35 diff

Re: Extend faq.using to discuss fork failures

2011-08-30 Thread Ryan Johnson
Hi Corinna, That sounds reasonable, though I suspect we'd want want to keep the concluding bits in the FAQ as well. Unfortunately, summertime free time has come to an end so I don't know when I'll get to this next. Perhaps a good compromise for now would be for you to post only the first FAQ

Re: Extend faq.using to discuss fork failures

2011-08-30 Thread Christopher Faylor
On Tue, Aug 30, 2011 at 11:00:20AM +0200, Corinna Vinschen wrote: Hi Ryan, Thanks for the FAQ entry. I had a look now, finally. Two nits: On Aug 25 22:08, Ryan Johnson wrote: Index: winsup/doc/faq-using.xml === RCS file:

Re: Extend faq.using to discuss fork failures

2011-08-26 Thread Eric Blake
On 08/25/2011 08:08 PM, Ryan Johnson wrote: Based on the feedback on cygwin-dev, I've put together a revised pair of faq.using entries: one listing briefly the symptoms of fork failures and what to do about it, and the other giving some details about why fork fails (sometimes in spite of

Extend faq.using to discuss fork failures

2011-08-25 Thread Ryan Johnson
Hi all, Based on the feedback on cygwin-dev, I've put together a revised pair of faq.using entries: one listing briefly the symptoms of fork failures and what to do about it, and the other giving some details about why fork fails (sometimes in spite of everything we do to compensate).