public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Larry Hall (Cygwin)" <reply-to-list-only-lh@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Failure with fork()
Date: Fri, 28 Jun 2013 01:28:00 -0000	[thread overview]
Message-ID: <51CCBD7A.3040903@cygwin.com> (raw)
In-Reply-To: <786EBDA1AC46254B813E200779E7AD3602E7C666@srv1163ex1.flightsafety.com>

On 6/27/2013 4:55 PM, Thrall, Bryan wrote:
> Larry Hall (Cygwin) wrote on 2013-06-27:
>> On 6/27/2013 4:33 PM, Alan W. Irwin wrote:
>>> So the question still remains how do I gain access to a version of
>>> setup.exe with the fork fix that will allow me to not only initialize
>>> my Cygwin distribution for Wine without the fork abort, but also
>>> subsequently update it to install all components of Cygwin that I
>>> need?
>>
>> Since you want to just run 'setup.exe', you need a new cygwin package
>> (i.e. cygwin-1.7.2*-*) before you'll be able to do what you want
>> without any extra effort on your part.  So unless you're willing to
>> build your own version of this package and put it in your download
>> directory in the appropriate spot (after you've downloaded the
>> packages you want), you want to just wait for the next announcement
>> for the cygwin package.
>
> Since the fork bug is only affecting the execution of the postinstall
> scripts, couldn't the OP install the snapshot in the partially-complete
> Cygwin install, then run setup.exe to finish the postinstall scripts?

As Yaakov said, if you time it just right, which may or may not be
tricky.  There are other alternatives as well but they all require
some effort to get right.

-- 
Larry

_____________________________________________________________________

A: Yes.
 > Q: Are you sure?
 >> A: Because it reverses the logical flow of conversation.
 >>> Q: Why is top posting annoying in email?

--
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

  reply	other threads:[~2013-06-27 22:32 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-27 18:58 Alan W. Irwin
2013-06-27 19:01 ` marco atzeri
2013-06-27 19:45   ` Alan W. Irwin
2013-06-27 20:17     ` Achim Gratz
2013-06-27 20:33     ` gmt
2013-06-27 19:13 ` Alan W. Irwin
2013-06-27 19:15   ` marco atzeri
2013-06-27 20:43     ` Alan W. Irwin
2013-06-27 20:47       ` Christopher Faylor
2013-06-27 20:48       ` Larry Hall (Cygwin)
2013-06-27 20:56         ` Thrall, Bryan
2013-06-28  1:28           ` Larry Hall (Cygwin) [this message]
2013-06-27 20:55       ` Peter Rosin
2013-06-27 21:52       ` Yaakov (Cygwin/X)
2013-06-27 21:58         ` Alan W. Irwin
2013-06-27 21:59           ` Yaakov (Cygwin/X)
2013-06-28  9:19             ` Corinna Vinschen
  -- strict thread matches above, loose matches on Subject: below --
2013-06-28  7:55 Alan W. Irwin
2013-06-28  7:59 ` marco atzeri
2013-06-28  8:52   ` Corinna Vinschen
2013-06-28 10:16     ` gmt
2013-06-28 10:20       ` Corinna Vinschen
2013-06-28 19:05         ` Alan W. Irwin
2013-06-28  8:42 ` Alan W. Irwin
2013-06-28  9:40 ` gmt
2013-06-27 10:49 Arjen Markus
2013-06-27 11:27 ` Ryan Johnson
2013-06-27 11:29   ` Corinna Vinschen
2013-06-27 12:19     ` Arjen Markus
2013-06-27 17:01       ` Corinna Vinschen
2013-06-27 17:03       ` Christopher Faylor

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=51CCBD7A.3040903@cygwin.com \
    --to=reply-to-list-only-lh@cygwin.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).