X-Spam-Check-By: sourceware.org Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: RE: sshd + bash = crush on CRs Date: Mon, 19 Feb 2007 17:03:41 +0300 Message-ID: From: "Pavel Ivanoff" To: X-Spam-Yversion: CBOSS_spam_fighter X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id l1JE3t6d003463 > From: Vaclav Haisman > > Pavel Ivanoff wrote: > > Hi, all! > > > > After updating bash to newest version on my server I've met problems > > with CR on my scripts. I've solved them with setting system variable > > SHELLOPTS to 'igncr'. And now they work fine when I login > to the server > > via Terminal Services. But when I login to the server via sshd (last > > version came with cygwin) it ignores all environment > variables set in > > the system - SHELLOPTS too. So I have all my CR problems > again. I can't > > put SHELLOPTS in my .bashrc or .bash_profile scripts because bash > > complains it's readonly. And I can't move CR out of scripts > because they > Why is your $HOME/.bashrc and $HOME/.bash_profile read only? > These files > are user's and you should be able to edit them however you want. I meant not my .bashrc and .bash_profile are readonly, but when I put into them the line like this: SHELLOPTS='igncr' after logging in bash says to me that SHELLOPTS is readonly variable and cannot be set. > > are checked out from CVS in one bunch with other text files > that have to > > be with windows CR-LF. > > So where can I make my SHELLOPTS environment variable > working in sshd > > too? > All the sensible proposed solution to this change are described in one > or more Cygwin bash package release announcements. Read them. > One way to > work around this is to have the necessary directories mounted > with text > mounts. I've read these announcements and I already use the most applicable to me solution from them - SHELLOPTS=igncr. I don't want to use text mounts because at least as I've understood they are not stable and also all written scripts in there work use the convinience of binary mounts. Is there another solution? Pavel Ivanov -- 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/