Date: Sun, 3 Jun 2007 02:09:02 GMT From: Mark Stevans<mls@piqqem.com> To: freebsd-gnats-submit@FreeBSD.org Subject: docs/113274: Handbook needs file execution troubleshooting section Message-ID: <200706030209.l53292Xb049691@www.freebsd.org> Resent-Message-ID: <200706030210.l532A7aY095835@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 113274 >Category: docs >Synopsis: Handbook needs file execution troubleshooting section >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Sun Jun 03 02:10:07 GMT 2007 >Closed-Date: >Last-Modified: >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: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200706030209.l53292Xb049691>