The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: scj@yaccman.com (Steve Johnson)
Subject: [TUHS] How Unix brings people together, or it's a small
Date: Tue, 07 Feb 2017 15:38:40 -0800	[thread overview]
Message-ID: <930c52a0c279cdd7d44953aa403a504a8622bb83@webmail.yaccman.com> (raw)
In-Reply-To: <CAC20D2O8dXan9hX5Sv6LyBD6dEFPwpV5wYZJ_XsFCHtVw6Gb3Q@mail.gmail.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2851 bytes --]

Looking back, the social dynamics of the Unix group helped a lot in
keeping the bloat small.   The rule was, whoever touches something
last becomes its owner.  Of course, we were all free to complain
about things, and did, but the amalgamation of tinkerings that
characterizes most of the Linux commands just didn't happen.  At
times this hot-potato activity worked very well.  In a moment of
inspiration I thought up the syntax for the 'at' command  (  "at 3am
cc -o *.c", etc. ).  I implemented it as a shell script and it was
pretty feeble.  My implementation lasted about a week -- I came in on
a Monday and Dennis had plugged the majority of the holes -- got the
permissions right, saved the search path and current directory, etc. 
I think we were both happy with the process...

I think the other thing we understood was that if you added an on/off
option to your application you had a choice of either doing twice as
much testing as previously, or testing both configurations of the code
half as much.   If you look at the gcc manual, you can see the
result -- many dozen pages just listing the options.  It's probably
up around the age of the universe now to reliably test the whole
thing.   And it seems like if you set the options differently than
usual, thing break, can't be debugged reliably, or something else
surprising.  One rule with Linux: do it vanilla or go home...

Steve

----- Original Message -----
From:
 "Clem Cole" <clemc at ccc.com>

To:
"Marc Rochkind" <rochkind at basepath.com>
Cc:
"TUHS main list" <tuhs at minnie.tuhs.org>
Sent:
Tue, 7 Feb 2017 18:10:52 -0500
Subject:
Re: [TUHS] How Unix brings people together, or it's a small

And I think it has been peed on by many different people trying to
leave their own mark on it along the way.

On Mon, Feb 6, 2017 at 11:06 PM, Marc Rochkind <rochkind at basepath.com
[1]>
 wrote:
Of course. Linux is:

1. old,
2. designed by a huge group,
3. intended to serve many purposes

UNIX was, at least in its early days, the opposite in all three ways.
But, after 15 years or so, it also was numbers 1 - 3. (Speaking of
System V here.)

There have been OSes that remained beautifully sleek and uncluttered
forever. Such as BeOS. However, all such systems failed to achieve
critical mass. Which is why they remained true.

No way out of this trap.

--Marc

On Mon, Feb 6, 2017 at 8:03 PM, Doug McIlroy <doug at cs.dartmouth.edu
[2]>
 wrote:

 >  Lots of commands are now little shells
 ...
 > Linux today is much more like the systems
 > Unix displaced than it is like Unix

 So depressingly true!

 Doug

 

Links:
------
[1] mailto:rochkind at basepath.com
[2] mailto:doug at cs.dartmouth.edu

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170207/3866b843/attachment.html>


  reply	other threads:[~2017-02-07 23:38 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-07  3:03 Doug McIlroy
2017-02-07  4:06 ` Marc Rochkind
2017-02-07 23:10   ` Clem Cole
2017-02-07 23:38     ` Steve Johnson [this message]
2017-02-08  2:55       ` [TUHS] Code bloat (was: How Unix brings people together, or it's a small...) Greg 'groggy' Lehey
2017-02-08  3:47         ` Nick Downing
2017-02-08  3:56           ` Jason Stevens
2017-02-08  8:25             ` Wesley Parish
2017-02-08  9:57               ` Steve Nickolas
2017-02-08 11:21             ` Nick Downing
2017-02-08 11:59               ` [TUHS] Code bloat (was: How Unix brings people together, or it'sa small...) jsteve
2017-02-08 12:24                 ` Nick Downing
2017-02-08 12:29               ` [TUHS] Code bloat Jacob Goense
2017-02-08 12:57                 ` Nick Downing
2017-02-08 13:10                 ` jsteve
2017-02-08 14:10                   ` Jacob Goense
2017-02-08 14:34                     ` Ron Natalie
2017-02-08 14:43                       ` Brantley Coile
2017-02-08 15:09                       ` Dan Cross
2017-02-08 15:26                         ` Nick Downing
2017-02-08 15:18                     ` Jason Stevens
2017-02-08 16:25                 ` Tony Finch
2017-02-09 14:03                   ` Jacob Goense
2017-02-09 14:41                     ` jsteve
2017-02-09 15:03                       ` Jacob Goense
2017-02-09 15:08                         ` Jason Stevens
2017-02-09 15:30                     ` Tony Finch
2017-02-09 16:14                       ` Warner Losh
2017-02-09 23:38                         ` [TUHS] Free/NetBSD revision history (was Code bloat) Jacob Goense
2017-02-10  4:11                           ` Warner Losh
2017-02-10  4:17                           ` Warner Losh
2017-02-08 13:56               ` [TUHS] Code bloat (was: How Unix brings people together, or it's a small...) Paul Ruizendaal
     [not found]                 ` <CAH1jEzZqRPYenwzBbUwFVanA-NVvWMGzYiADVoAXCDOqnUrMrg@mail.gmail.com>
2017-02-09  3:02                   ` [TUHS] Fwd: " Nick Downing
2017-02-09  9:19                     ` [TUHS] " Paul Ruizendaal
2017-02-09  9:58                       ` Michael Kjörling
2017-02-09 10:08                         ` Paul Ruizendaal
2017-02-09 16:36                       ` Larry McVoy
2017-02-09 16:42                         ` Warner Losh
2017-02-09 16:49                           ` Larry McVoy
2017-02-09 17:24                             ` Steffen Nurpmeso
2017-02-09 17:27                               ` [TUHS] offtopic: broadband (redirect from bloat) Larry McVoy
2017-02-09 19:05                                 ` Steffen Nurpmeso
2017-02-09 22:48                                 ` Joerg Schilling
2017-02-09 19:54                             ` [TUHS] Code bloat (was: How Unix brings people together, Corey Lindsly
2017-02-09 20:08                               ` pechter
2017-02-09 20:30                               ` Arthur Krewat
2017-02-09 23:47                                 ` Jacob Goense
2017-02-09 21:06                               ` Larry McVoy
2017-02-09 21:02                             ` [TUHS] Code bloat (was: How Unix brings people together, or it's a small...) Joerg Schilling
2017-02-09 16:58                         ` [TUHS] Code bloat William Pechter
2017-02-09 19:50                       ` [TUHS] Code bloat (was: How Unix brings people together, or it's a small...) Clem Cole
2017-02-08  5:37           ` Peter Jeremy
2017-02-08 12:16       ` [TUHS] How Unix brings people together, or it's a small ches@Cheswick.com

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=930c52a0c279cdd7d44953aa403a504a8622bb83@webmail.yaccman.com \
    --to=scj@yaccman.com \
    /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).