From: Mark Rosenstand <mark@borkware.net>
To: Theodore Tso <tytso@mit.edu>
Cc: doug@mcnaught.org, arjan@infradead.org, linux-kernel@vger.kernel.org
Subject: Re: Executable shell scripts
Date: Sat, 13 May 2006 15:18:50 +0200 (CEST) [thread overview]
Message-ID: <20060513131850.2E732146AF@hunin.borkware.net> (raw)
In-Reply-To: <20060513125911.GA2871@thunk.org>
Theodore Tso <tytso@mit.edu> wrote:
> On Sat, May 13, 2006 at 01:27:54PM +0200, Mark Rosenstand wrote:
> > > Every Unix I've ever seen works this way. It'd be nice to have
> > > unreadable executable scripts, but no one's ever done it.
> >
> > According to
> > http://www.faqs.org/faqs/unix-faq/faq/part4/section-7.html both
> > 4.3BSD and SunOS have. I can confirm that it works on current BSD's
> > as well.
>
> Incorrect. The FAQ stated that BSD4.3 and SunOS support executable
> shell scripts, but both BSD 4.3 and SunOS required that the shell
> scripts be readable. I know, I've personally worked on BSD 4.3
> systems and worked on BSD 4.3 source. Read the FAQ more carefully....
I only confirmed that it works on current BSD's, not that it used to
work that way on 4.3BSD (although that was my impression.)
Anyhow, I don't really mind the 111 mode, the point was to show shell
scripts being treated as executables. What I do want this feature for
is the "more useful case" that somehow got stripped off in the replies,
namely setuid and setgid scripts.
next prev parent reply other threads:[~2006-05-13 13:18 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-13 10:38 Mark Rosenstand
2006-05-13 10:56 ` Arjan van de Ven
2006-05-13 11:03 ` Mark Rosenstand
2006-05-13 11:07 ` Arjan van de Ven
2006-05-13 11:17 ` Mark Rosenstand
2006-05-13 11:18 ` Willy Tarreau
2006-05-13 11:19 ` Douglas McNaught
2006-05-13 11:27 ` Mark Rosenstand
2006-05-13 11:37 ` Joel Jaeggli
2006-05-13 12:59 ` Theodore Tso
2006-05-13 13:18 ` Mark Rosenstand [this message]
2006-05-13 22:42 ` Neil Brown
2006-05-13 11:28 ` Stefan Smietanowski
2006-05-13 11:37 ` Neil Brown
2006-05-13 12:45 ` Willy Tarreau
2006-05-13 14:00 ` Arjan van de Ven
2006-05-13 20:52 ` Douglas McNaught
2006-05-13 11:16 ` J.A. Magallón
2006-05-13 11:22 ` Bernd Petrovitsch
2006-05-13 11:45 ` Mark Rosenstand
2006-05-13 11:56 ` Bernd Petrovitsch
2006-05-13 12:23 ` Mark Rosenstand
2006-05-13 12:58 ` Willy Tarreau
2006-05-13 18:55 ` Bernd Petrovitsch
2006-05-13 11:23 ` CaT
2006-05-13 11:00 ` Willy Tarreau
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060513131850.2E732146AF@hunin.borkware.net \
--to=mark@borkware.net \
--cc=arjan@infradead.org \
--cc=doug@mcnaught.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®