From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nick Drage Subject: Re: bad interpreter Date: Wed, 27 Nov 2002 13:28:05 +0000 Sender: netfilter-admin@lists.netfilter.org Message-ID: <20021127132805.H14289@funkyjesus.org> References: <20021127115344.59352.qmail@web9606.mail.yahoo.com> <3.0.1.16.20021127141258.1af7ba26@s-net-04.besancon.org> Reply-To: Nick Drage Mime-Version: 1.0 Return-path: Content-Disposition: inline In-Reply-To: <3.0.1.16.20021127141258.1af7ba26@s-net-04.besancon.org>; from thierry.itty@besancon.org on Wed, Nov 27, 2002 at 02:12:58PM +0000 Errors-To: netfilter-admin@lists.netfilter.org List-Help: List-Post: List-Subscribe: , List-Id: List-Unsubscribe: , List-Archive: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: netfilter@lists.netfilter.org On Wed, Nov 27, 2002 at 02:12:58PM +0000, Thierry ITTY wrote: > this happens when you get a script file from dos (with cr/lf eol) > the first line may look normal Aaaaahhhh, good point :) > #!/bin/sh > > but the CR (which remains invisible within a text editor that silently > adapts itself) is misunderstood by shell > > just edit the file using vi, then ":set ff=unix" and ":wq". this will > remove the CRs cat -v will show the dos line-endings if you have them. -- FunkyJesus System Administration Team