From owner-freebsd-questions@FreeBSD.ORG Sat Sep 10 01:56:46 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B120716A41F for ; Sat, 10 Sep 2005 01:56:46 +0000 (GMT) (envelope-from garys@opusnet.com) Received: from opusnet.com (mail.opusnet.com [209.210.200.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3482E43D45 for ; Sat, 10 Sep 2005 01:56:46 +0000 (GMT) (envelope-from garys@opusnet.com) Received: from localhost.localhost [70.98.246.232] by opusnet.com with ESMTP (SMTPD32-8.05) id AD56CE04006E; Fri, 09 Sep 2005 18:56:38 -0700 Received: from localhost.localhost (localhost.localhost [127.0.0.1]) by localhost.localhost (8.13.3/8.13.3) with ESMTP id j8A1vM43013983; Fri, 9 Sep 2005 18:57:22 -0700 (PDT) (envelope-from garys@opusnet.com) Received: (from jojo@localhost) by localhost.localhost (8.13.3/8.13.3/Submit) id j8A1vGkE013982; Fri, 9 Sep 2005 18:57:16 -0700 (PDT) (envelope-from garys@opusnet.com) To: "N.J. Thomas" References: <4321DC05.3050509@charter.net> <20050909212305.GC15735@ayvali.org> <43220F9F.9050002@charter.net> <20050910004230.GD15735@ayvali.org> From: garys@opusnet.com (Gary W. Swearingen) Date: Fri, 09 Sep 2005 18:57:16 -0700 In-Reply-To: <20050910004230.GD15735@ayvali.org> (N. J. Thomas's message of "Fri, 9 Sep 2005 20:42:30 -0400") Message-ID: User-Agent: Gnus/5.1007 (Gnus v5.10.7) XEmacs/21.4.17 (Jumbo Shrimp, berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: freebsd-questions@freebsd.org, bob self Subject: Re: Can't execute a script X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Sep 2005 01:56:46 -0000 "N.J. Thomas" writes: > Normally, that doesn't matter because most Unix utilities are > multi-eol-format aware, but you can't have it in the shebang line > because the OS interprets the extra carriage as part of the command, so > it is looking for /bin/sh^M, which doesn't exist. Know any reason that shouldn't be "fixed"? POSIX requirement maybe? What software reads the whole shebang line? (The "sh" shell apparently reads at least part of it, but I suppose some library functions do too.) Should I write a PR on it?