X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Message-ID: <92af9b620710031014y4fe106c7je3e911e74b09f483@mail.gmail.com> Date: Wed, 3 Oct 2007 10:14:02 -0700 From: "Alexey Illarionov" To: cygwin AT cygwin DOT com Subject: Re: newbie question -- problem with launching shell script files In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <92af9b620710022153u1d56488erbc58010cc56ad9ef AT mail DOT gmail DOT com> X-Google-Sender-Auth: af8aeb42782465c3 X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: 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 Thanks to everyone for your help. On 10/3/07, Steve Holden wrote: > Alexey Illarionov wrote: > > Hello, > > > > I have just installed cygwin using setup.exe and know almost nothing > > about it. I made no changes in any configuration files and launch my > > cygwin session just by starting the unchanged 'cygwin.bat' file. > > > > I wrote a small script. Here is the content of the 'run.sh' > > > > #!/bin/sh > > cd /cygdrive/c > > > > Unfortunately, it does not work. The command './run.sh' does nothing. > > That's not true. It does something, but it does it in a sub-process > that's started by your interactive shell (then waits for that process to > terminate before issuing another prompt). So that new process does > indeed change directory, but the shell process that's waiting doesn't. > > > I found in FAQ that the problem is not new, but I'm not sure that I > > understand correctly the way to overcome it. There are two possible > > sources of this problem as it is wrote in FAQ. > > 1. Bash does not understand that it is executable file. This should be > > fixed by first line of my script '#!/bin/sh' > > 2. Some problems with chmod. I don't really understand what I should > > do in this case, but it looks like this is not the case because 'chmod > > +x run.sh' works fine. > > > Both those issues are to do with making sure your shell script is > correcttly treated as executable. > > > I would really appreciate if anyone could help to deal with this problem. > > > Hope this helps. > > regards > Steve > -- > Steve Holden +1 571 484 6266 +1 800 494 3119 > Holden Web LLC/Ltd http://www.holdenweb.com > Skype: holdenweb http://del.icio.us/steve.holden > > Sorry, the dog ate my .sigline > > > -- > 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/ > > -- Best regards, Alexey A. Illarionov -- 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/