DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:in-reply-to:message-id
	:references:mime-version:content-type:content-id; q=dns; s=
	default; b=yDxj99/f8g+oZkJYXQtXwjZ5vaN5YmiWlvAiLtLJWXkn5tu9yk2/+
	54/rodVxdrOKXWQ6lpd0Ej125ymuYZuJS2ANc4MjMdeYLzaY5Hco8jV/BXUyYLlm
	16MLYPInKp6/RZ2CXF5FOMV+QfyYfYT22cRg9C9PYrwQXv9kpcjuBk=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Fri, 5 Jul 2013 12:11:10 -0700 (PDT)
From: "Alan W. Irwin" <irwin@beluga.phys.uvic.ca>
To: cygwin@cygwin.com
Subject: Re: Failure with fork() (Cygwin on Wine install now sort of works)
In-Reply-To: <alpine.DEB.2.02.1307021400090.27492@enira.zlyna.ubzr>
Message-ID: <alpine.DEB.2.02.1307051151450.27492@enira.zlyna.ubzr>
References: <alpine.DEB.2.02.1306272257220.27492@enira.zlyna.ubzr> <51CD4177.1040708@gmail.com> <20130628084157.GP2378@calimero.vinschen.de> <00c401ce73e4$d12b80f0$738282d0$@malth.us> <20130628101630.GS2378@calimero.vinschen.de> <alpine.DEB.2.02.1306280918260.27492@enira.zlyna.ubzr> <alpine.DEB.2.02.1307021400090.27492@enira.zlyna.ubzr>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; FORMAT=flowed; CHARSET=US-ASCII
Content-ID: <alpine.DEB.2.02.1307041245521.27492@enira.zlyna.ubzr>

On 2013-07-04 13:39-0700 Alan W. Irwin wrote:

> So if the consensus here after looking at the setup_install.out
> results is that cygwin on Wine is more or less installed properly from
> these results (except for the rename issue above which I can fix by
> doing that rename manually as suggested by the error message), then
> the next order of business [...]

I have now looked more carefully at the setup_install.out results that
are wrapped inside a tarball I attached to a previous post in this
thread.  At the same time I have also looked at the resulting files in
my cygwin install tree.  It turns out that because of errors the first
install script created an empty /etc/fstab rather than the desired
result and also was unable to create the /dev directory. These issues
very likely had follow-on effects for several of the other postinstall
scripts that were run (for example, all the read-only filesystem error
messages when any attempt was made to write to /dev.) Anyhow, it now
seems likely there are at least a couple of Wine bugs that are still
preventing a clean postinstall phase for setup.exe on Wine, and the
rest of this story will continue for now at
http://bugs.winehq.org/show_bug.cgi?id=24018.  Meanwhile, I thank the
people here that (a) helped to fix the Cygwin fork bug, and (b) gave
me good directions for trying out that fix before it becomes part of
an official Cygwin release.

Alan
__________________________
Alan W. Irwin

Astronomical research affiliation with Department of Physics and Astronomy,
University of Victoria (astrowww.phys.uvic.ca).

Programming affiliations with the FreeEOS equation-of-state
implementation for stellar interiors (freeeos.sf.net); the Time
Ephemerides project (timeephem.sf.net); PLplot scientific plotting
software package (plplot.sf.net); the libLASi project
(unifont.org/lasi); the Loads of Linux Links project (loll.sf.net);
and the Linux Brochure Project (lbproject.sf.net).
__________________________

Linux-powered Science
__________________________

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