From: Clem Cole <clemc@ccc.com>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Set-uid shell scripts
Date: Sun, 4 Aug 2019 16:29:58 -0400 [thread overview]
Message-ID: <CAC20D2MFZ=H9CPU3QMWEffFVU0RsXzJFMgJX78addLZ-sm-cKw@mail.gmail.com> (raw)
In-Reply-To: <20190804201838.0246918C08C@mercury.lcs.mit.edu>
[-- Attachment #1: Type: text/plain, Size: 744 bytes --]
On Sun, Aug 4, 2019 at 4:18 PM Noel Chiappa <jnc@mercury.lcs.mit.edu> wrote:
> Part of the problem is having the kernel involved in starting shell
> scripts; convenient in some ways, but V6 etc worked fine without that
> 'feature'.
>
That's a tough call. I have mixed opinions about it as a feature. I kind
of like the user/kernel interface really, really thin and unadorned.
Adding, it certainly made allowing multiple interpreters to be supported
much easier; but as you say it opens a new can of worms. Given the later
proliferation of what bwk or Jon Bently once referred too as 'little
languages' (awk, perl, tcl, and sigh eventually python), it was probably a
good feature.
But as you said, v6 worked fairly well without it.
Clem
[-- Attachment #2: Type: text/html, Size: 2345 bytes --]
next prev parent reply other threads:[~2019-08-04 20:30 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-04 20:18 Noel Chiappa
2019-08-04 20:29 ` Clem Cole [this message]
2019-08-04 20:42 ` Richard Salz
2019-08-04 23:58 ` Dave Horsfall
-- strict thread matches above, loose matches on Subject: below --
2019-08-05 0:13 Noel Chiappa
2019-08-04 21:27 Norman Wilson
2019-08-06 8:28 ` jason-tuhs
2019-08-06 9:55 ` arnold
2019-08-06 22:48 ` Dave Horsfall
2019-08-06 22:56 ` ron minnich
2019-08-07 1:21 ` Dave Horsfall
[not found] ` <40c92e85142fe7e3@orthanc.ca>
2019-08-07 21:33 ` Dave Horsfall
2019-08-08 6:39 ` Peter Jeremy
2019-08-07 12:56 ` Chet Ramey
2019-08-07 21:40 ` Dave Horsfall
2019-08-08 5:16 ` Adam Thornton
2019-08-14 5:41 ` Efton Collins
2019-08-04 21:18 Norman Wilson
2019-08-04 7:36 Dave Horsfall
2019-08-04 7:43 ` Alec Muffett
2019-08-04 15:58 ` Noel Chiappa
2019-08-04 16:30 ` Michael Kjörling
2019-08-04 16:48 ` Alec Muffett
2019-08-04 17:48 ` Michael Kjörling
2019-08-04 19:45 ` Alec Muffett
2019-08-04 16:50 ` Rico Pajarola
2019-08-04 7:46 ` arnold
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='CAC20D2MFZ=H9CPU3QMWEffFVU0RsXzJFMgJX78addLZ-sm-cKw@mail.gmail.com' \
--to=clemc@ccc.com \
--cc=jnc@mercury.lcs.mit.edu \
--cc=tuhs@tuhs.org \
/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;
as well as URLs for NNTP newsgroup(s).