Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com From: Sam Edge To: cygwin@cygwin.com Subject: Re: behaviour of "for (( exp1; exp2; exp3 )); do COMMANDS; done" Date: Wed, 28 May 2003 15:16:39 +0100 Organization: . Reply-To: cygwin@cygwin.com Message-ID: References: <20030527120718.GA22030@convex.org.uk> <002901c32427$2e1553e0$78d96f83@pomello> <20030527120718.GA22030@convex.org.uk> <5.2.1.1.2.20030528062212.01f54ff8@pop.sonic.net> In-Reply-To: <5.2.1.1.2.20030528062212.01f54ff8@pop.sonic.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Posting-Agent: Hamster/2.0.0.1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id h4SEHD612162 Randall R Schulz wrote in <5.2.1.1.2.20030528062212.01f54ff8@pop.sonic.net> in gmane.os.cygwin on Wed, 28 May 2003 06:30:47 -0700: > The interpretation of #! lines is in the kernel (or, hereabout, > Cygwin1.dll, a kernel by any other name), just as the kernel would how > to handle a binary executable by examining its header. * man execve * Well, well. I knew that some unices had to be doing this because they allowed suid scripts. But I thought the behaviour had been phased out of newer versions. (Because Linux and the like don't allow suid scripts, I assumed that this whole script-handling behaviour had been moved out of the kernel.) I learn something new every day. Thanks. :-) Regards, -- Sam Edge -- 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/