X-Spam-Check-By: sourceware.org Message-ID: Date: Thu, 5 Oct 2006 15:51:36 -0400 From: "Doug Harris" To: cygwin AT cygwin DOT com Subject: Fixing /etc/profile MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 I updated cygwin today and got to enjoy the fun of my shell no longer working. Fortunately for my backside, I did search the mailing list archive and found the answer required either setting a shopt or modifying some CR/LF to just LF. No big deal. The big deal, in my eyes, is that the one of the files that I had to fix was /etc/profile. The timestamp on this file (prior to my fix) was May 11, 2004 -- that would be the day I first installed cygwin on this computer. I have not modified this from the original version. Wouldn't it make sense that the default /etc/profile would work out-of-the-box with the default bash installation? Doug p.s. A few quick helpful tips for people who are looking to fix their own /etc/profile (and other files): * The "file" command includes in its output "CRLF line terminators" for files that have that * "d2c /etc/profile" will quickly change the line endings in place. Replace with other file names to fix those. * Don't forget to check .bash_profile, .bashrc, etc cd; file .bash* | grep "CRLF line terminators" -- 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/