From nobody@FreeBSD.org  Sun Jun  3 02:09:02 2007
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id 5632716A421
	for <freebsd-gnats-submit@FreeBSD.org>; Sun,  3 Jun 2007 02:09:02 +0000 (UTC)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (www.freebsd.org [69.147.83.33])
	by mx1.freebsd.org (Postfix) with ESMTP id 475F313C44B
	for <freebsd-gnats-submit@FreeBSD.org>; Sun,  3 Jun 2007 02:09:02 +0000 (UTC)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (localhost [127.0.0.1])
	by www.freebsd.org (8.13.1/8.13.1) with ESMTP id l532927i049692
	for <freebsd-gnats-submit@FreeBSD.org>; Sun, 3 Jun 2007 02:09:02 GMT
	(envelope-from nobody@www.freebsd.org)
Received: (from nobody@localhost)
	by www.freebsd.org (8.13.1/8.13.1/Submit) id l53292Xb049691;
	Sun, 3 Jun 2007 02:09:02 GMT
	(envelope-from nobody)
Message-Id: <200706030209.l53292Xb049691@www.freebsd.org>
Date: Sun, 3 Jun 2007 02:09:02 GMT
From: Mark Stevans<mls@piqqem.com>
To: freebsd-gnats-submit@FreeBSD.org
Subject: Handbook needs file execution troubleshooting section
X-Send-Pr-Version: www-3.0

>Number:         113274
>Category:       docs
>Synopsis:       Handbook needs file execution troubleshooting section
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-doc
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          doc-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sun Jun 03 02:10:07 GMT 2007
>Closed-Date:    Mon Jul 02 18:37:39 GMT 2007
>Last-Modified:  Mon Jul 02 18:37:39 GMT 2007
>Originator:     Mark Stevans
>Release:        6.1
>Organization:
Piqqem
>Environment:
FreeBSD redpen.piqqem.lan 6.1-SECURITY FreeBSD 6.1-SECURITY #0: Thu Apr 26 14:39:24 UTC 2007     root@builder.daemonology.net:/usr/obj/usr/src/sys/SMP  i386
>Description:
One of the most frustrating experiences in the UNIX world is to have a file (often a script) that you just cannot get to execute, especially in a high-pressure scenario.  There is a long list of reasons why a FreeBSD file cannot be executed, e.g. no magic number, file system mounted NOEXEC, no execute permission, no read permission, interpreter cannot be found, etc., etc..  For the benefit of users everywhere, this list needs to be carefully constructed and included in a future FreeBSD Handbook "File Execution Troubleshooting" section.
>How-To-Repeat:
Try to execute a file you have execute permission for, but no read permission on the associated script interpreter, for example, without being a FreeBSD/UNIX guru, and watch how long it takes you to stumble upon the solution, often hours or days.
>Fix:
Break down all the cases for failure to execute a program/script, and list them clearly and completely.

>Release-Note:
>Audit-Trail:

From: Remko Lodder <remko@elvandar.org>
To: Mark Stevans <mls@piqqem.com>
Cc: freebsd-gnats-submit@FreeBSD.org
Subject: Re: docs/113274: Handbook needs file execution troubleshooting section
Date: Sun, 03 Jun 2007 10:39:28 +0200

 Mark Stevans wrote:
 > FreeBSD redpen.piqqem.lan 6.1-SECURITY FreeBSD 6.1-SECURITY #0: Thu Apr 26 14:39:24 UTC 2007     root@builder.daemonology.net:/usr/obj/usr/src/sys/SMP  i386
 >> Description:
 > One of the most frustrating experiences in the UNIX world is to have a file (often a script) that you just cannot get to execute, especially in a high-pressure scenario.  There is a long list of reasons why a FreeBSD file cannot be executed, e.g. no magic number, file system mounted NOEXEC, no execute permission, no read permission, interpreter cannot be found, etc., etc..  For the benefit of users everywhere, this list needs to be carefully constructed and included in a future FreeBSD Handbook "File Exe cution Troubleshooting" section.
 >> How-To-Repeat:
 > Try to execute a file you have execute permission for, but no read permission on the associated script interpreter, for example, without being a FreeBSD/UNIX guru, and watch how long it takes you to stumble upon the solution, often hours or days.
 >> Fix:
 > Break down all the cases for failure to execute a program/script, and list them clearly and completely.
 > 
 Hello,
 
 This -might- be an idea, but on the other end we cannot possibly
 list ever reason for whatever stuff goes wrong within a FreeBSD
 system.
 
 That said; it would be more interesting if someone submits patches
 for this, please feel free to do so.
 
 (Also note that a serious severity and medium priority will not
 make this PR get resolved quicker, IF we at all used these fields
 it would be a minor severity and low priority (in my eyes))
 
 Thanks for using FreeBSD And the willingness to improve FreeBSD!
 
 Regards,
 Remko
 
 -- 
 Kind regards,
 
      Remko Lodder               ** remko@elvandar.org
      FreeBSD                    ** remko@FreeBSD.org
 
      /* Quis custodiet ipsos custodes */
State-Changed-From-To: open->closed 
State-Changed-By: remko 
State-Changed-When: Mon Jul 2 18:37:36 UTC 2007 
State-Changed-Why:  
Since there is no patch yet I will close the PR. IF someone has a patch 
for this, poke me and I will add it to the ticket and reopen it. Till 
that time I will not pretend that wewill be fixing this. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=113274 
>Unformatted:
