X-Spam-Check-By: sourceware.org Date: Mon, 11 Sep 2006 14:09:03 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com, mwoehlke Subject: Re: [ANNOUNCEMENT] Updated [experimental]: bash-3.1-7 Message-ID: <20060911180903.GA21327@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com, mwoehlke References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.11 Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On Mon, Sep 11, 2006 at 01:04:30PM -0500, mwoehlke wrote: >Eric Blake wrote: >>NOTICE: >>======= >>This version removes several outdated #defines that were once necessary in >>older versions of cygwin, but which made bash on cygwin different and >>slower than bash on Linux. In the process, there is a major change in >>behavior - bash no longer forces text mode when reading scripts. If your >>script resides on a text mount point, you will not notice any difference. >> If your script resides on a binary mount point, and has normal unix \n >>line endings, you may notice a slight speedup. But if your script resides >>on a binary mount point, and has \r\n line endings, bash will most likely >>encounter syntax errors. The fix is simple - use d2u to convert script >>files residing on a binary mount point to be unix files, or if you must >>use DOS lines, use a text mount point. Because of this change in >>behavior, I am marking this version experimental for a while until I can >>gauge from mailing list traffic that it is safe to promote to current. > >When starting the experimental version with "c:\cygwin\bin\bash.exe -l". >I get: > >mkdir: cannot create directory `/home/mwoehlke\r': No such file or directory >Copying skeleton files. >These files are for the user to personalise >their cygwin experience. >These will never be overwritten. >/usr/bin/install: cannot create directory `/home/mwoehlke\r': No such >file or directory >/usr/bin/install: cannot create directory `/home/mwoehlke\r': No such >file or directory >/usr/bin/install: cannot create directory `/home/mwoehlke\r': No such >file or directory >: No such file or directory >mwoehlke AT Harkness /etc/skel >$ > >So $HOME is being set wrong. "echo $HOME | od -c" gives " / h o m > e / m w o e h l k e \r \n". "echo %HOME%" from a >fresh cmd.exe gives "C:/Documents and Settings/mwoehlke". I ran d2u on >/etc/profile, /etc/default/etc/profile and /etc/passwd. > >If I 'export HOME=/home/mwoehlke', then things work correctly. > >Somehow, before /etc/profile is executed, my $HOME is being set "funny". >Any guesses? Does your /etc/passwd contain \r\n line endings? cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/