X-Recipient: archive-cygwin@delorie.com
X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 	tests=AWL,BAYES_00,SARE_MSGID_LONG40,SPF_PASS
X-Spam-Check-By: sourceware.org
MIME-Version: 1.0
In-Reply-To: <6c18a4f0912280230k601eca9me32c056e09117866@mail.gmail.com>
References: <6c18a4f0912251015k48ff2266l8fca37fc2543772e@mail.gmail.com> 	 <20091226233558.GB21254@ednor.casa.cgf.cx> 	 <6c18a4f0912270223w675ea650k15fadf8eb4c7de15@mail.gmail.com> 	 <20091227151902.GB27191@ednor.casa.cgf.cx> 	 <6c18a4f0912270949o5460c1ceq33f9e93d476614a2@mail.gmail.com> 	 <416096c60912270956l3a82fb8fu3a62d6532dc1988a@mail.gmail.com> 	 <6c18a4f0912271000i3c5f5ecewccf1bb77e30d88b4@mail.gmail.com> 	 <4B37E68C.9000304@cygwin.com> 	 <20091227233155.GA12367@ednor.casa.cgf.cx> 	 <6c18a4f0912280230k601eca9me32c056e09117866@mail.gmail.com>
Date: Tue, 29 Dec 2009 14:34:19 +0100
Message-ID: <6c18a4f0912290534t43d7d9c7y4b4b9cfde4df3237@mail.gmail.com>
Subject: Re: No go after update to 1.7.1
From: Bernd Bartmann <bernd.bartmann@gmail.com>
To: cygwin@cygwin.com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-IsSubscribed: yes
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie.com@cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com

On Mon, Dec 28, 2009 at 11:30 AM, Bernd Bartmann wrote:
> On Mon, Dec 28, 2009 at 12:31 AM, Christopher Faylor
> <cgf-use-the-mailinglist-please@cygwin.com> wrote:
>> I'd suggest at this point that you run sysinternals procmon to see if
>> you can figure out why bash isn't starting. =A0You might also try running
>> with a trimmed down PATH.
>
> Setting the PATH to C:\cygwin\bin only doesn't help either. So I tried
> procmon to monitor what bash is actually doing. As it seems it stops
> because it can't find /etc/passwd and /etc/fstab which indeed are
> missing. Shouldn't they have been created during the setup process?
> Also, /etc does not contain any files just some sub-directories:
>
> alternatives
> defaults
> fonts
> postinstall
> preremove
> profile.d
> setup
> terminfo
>
> I've attached the procmon log for the bash start test in .csv format
> for your inspection. Maybe also of interest is /var/log/setup.log.

No one? No more ideas?

Best regards,
Bernd.

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

