The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: salewski@att.net (Alan D. Salewski)
Subject: [TUHS] Ideas for a Unix paper I'm writing
Date: Sun, 07 Aug 2011 16:26:48 -0400	[thread overview]
Message-ID: <20110807202648.GF5480@att.net> (raw)
In-Reply-To: <32496006.7412.1309232177333.JavaMail.root@zimbraanteil>

On Mon, Jun 27, 2011 at 11:36:17PM -0400, Jim Capp spake thus:
> Warren,
*snip*


> I'm sure you've read these at one time or another, but here are a few of my favorites. Some of them might help you chase down the quotes you are looking for:
> 
> Excerpt from UNIX Time-Sharing System: UNIX Implementation, By K. Thompson, The Bell System Technical Journal, Vol. 57, No. 6, July-August 1978, pp. 1931:
> 
> "The kernel is the only UNIX code that cannot be substituted by a user to his own liking.  For this reason, the kernel should make as few real decisions as possible.  This does not mean to allow the user a million options to do the same thing.  Rather, it means to allow only one way to do one thing, but have that way be the least-common divisor of all the options that might have been provided."
*snip*


> Excerpt from The UNIX Programming Environment, By Brian W. Kernighan & Rob Pike, Prentice-Hall 1984, pp. viii:
> 
> "Even though the UNIX system introduces a number of innovative programs and techniques, no single program or idea makes it work well.  Instead, what makes it effective is an approach to programming, a philosophy of using the computer.  Although that philosophy can't be written down in a single sentence, at its heart is the idea that the power of a system comes more from the relationships among programs than from the programs themselves.  Many UNIX programs do quite trivial tasks in isolation, but, combined with other programs, become general and useful tools."
*snip*
> Cheers,
> 
> Jim


I think those quotes segue nicely to highlighting the importance of the
underlying philosophy that is the foundation for the examples of
technological insight, pragmatic design, and engineering excellence
catalogued thus far. Greg Lehey already provided the link to the
Wikipedia "Unix philosophy" page; I think a quote from one of the items
referenced there really gets to the heart of things:

From _The UNIX Philosopy_, by Mike Gancarz, Digital Press 1995, pp.  xvii:

    "The creators of the UNIX operating system started with a radical
    concept: They assumed that the users of their software would be
    computer literate from the start. The entire UNIX philosophy
    revolves around the idea that the user knows what he is doing."


All tool design branches in one direction or the other on this point;
Unix gets it right.

-Al




  parent reply	other threads:[~2011-08-07 20:26 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-28  0:11 Warren Toomey
2011-06-28  0:26 ` Larry McVoy
2011-06-28  0:32 ` Nick Downing
2011-06-28  1:00 ` Tim Newsham
2011-06-28  3:36 ` Jim Capp
2011-07-02  4:03   ` Warner Losh
2011-08-07 20:26   ` Alan D. Salewski [this message]
2011-09-02 18:33     ` Jose R. Valverde
2011-06-28  3:53 ` Jim Capp
2011-06-28  4:13 ` Greg 'groggy' Lehey
2011-06-28  5:48   ` Nick Downing
2011-06-28  7:22     ` Tim Newsham
2011-06-28 14:18   ` Wesley Parish
2011-06-28  7:32 ` Wilko Bulte
2011-06-28 15:22 ` Al Kossow
2011-06-29  1:30 A. P. Garcia

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=20110807202648.GF5480@att.net \
    --to=salewski@att.net \
    /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).