X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Date: Mon, 6 Jul 2009 00:32:16 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: Bash initialization w/cygwin-1.7 on NT4 Message-ID: <20090706043216.GA7958@ednor.casa.cgf.cx> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <4A517753.6000800@verizon.net> <4A517B99.9090303@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4A517B99.9090303@gmail.com> User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On Mon, Jul 06, 2009 at 05:20:41AM +0100, Dave Korn wrote: >Jerry DeLisle wrote: >> I am making the switch to 1.7. I started with a clean windows (nt4) >> environment and went through the usual run of setup-1.7 downloaded today. >> >> All appears fine, but bash does not get initialized. >> >> pwd is /usr/bin >> >> path is not set >> >> home directory is not created >> >> These are all taken care of nicely for the user with cygwin 1.5 >> >> I think this is a bug unless I am missing something in the install process. > >This is symptomatic of a problem preventing the postinstall scripts >from having run correctly, isn't it? Have a look in your >/var/log/setup.log* files, and see what happened to >base-files-profile.sh. I can actually duplicate this problem on my NT4 virtual machine. Unfortunately, I won't have a lot of time to track this down next week but I'll get to it if no one else beats me to it. cgf -- 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