From owner-freebsd-current  Thu Nov 23 11: 8:34 2000
Delivered-To: freebsd-current@freebsd.org
Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20])
	by hub.freebsd.org (Postfix) with ESMTP id C331C37B4CF
	for <current@FreeBSD.ORG>; Thu, 23 Nov 2000 11:08:30 -0800 (PST)
Received: (from bright@localhost)
	by fw.wintelcom.net (8.10.0/8.10.0) id eANJ8TY22735;
	Thu, 23 Nov 2000 11:08:29 -0800 (PST)
Date: Thu, 23 Nov 2000 11:08:28 -0800
From: Alfred Perlstein <bright@wintelcom.net>
To: Mike Meyer <mwm@mired.org>
Cc: current@FreeBSD.ORG
Subject: Re: Confusing error messages from shell image activation
Message-ID: <20001123110828.V18037@fw.wintelcom.net>
References: <14876.48112.785320.465213@guru.mired.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <14876.48112.785320.465213@guru.mired.org>; from mwm@mired.org on Thu, Nov 23, 2000 at 12:40:48AM -0600
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

* Mike Meyer <mwm@mired.org> [001122 22:41] wrote:
> Could I get some feedback on <URL:
> http://www.freebsd.org/cgi/query-pr.cgi?pr=22755 >? It's just a
> one-line kernel patch with some attendant updates in the kernel and
> libc, but it makes dealing with broken #! scripts *much* saner, and no
> one has even seen fit to comment on it yet :-(.

This patch may break compliance, ENOEXEC is the proper error code,
the shell should try to be a bit smarter about explaining why
ENOEXEC was returned.

-- 
-Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org]
"I have the heart of a child; I keep it in a jar on my desk."


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message