The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: lm@bitmover.com (Larry McVoy)
Subject: [TUHS] Ideas for a Unix paper I'm writing
Date: Mon, 27 Jun 2011 17:26:31 -0700	[thread overview]
Message-ID: <20110628002631.GC26343@bitmover.com> (raw)
In-Reply-To: <20110628001140.GA23711@minnie.tuhs.org>

On Tue, Jun 28, 2011 at 10:11:40AM +1000, Warren Toomey wrote:
> Anyway, if you can think of good ideas/references about the elegance of
> Unix, especially from the design perspective, I would much appreciate them.

This may just be me getting old or something, but here's a story that lead
to an aha! moment for me.  Long winded, so let me go get a glass of wine...

I was an undergrad and a grad student in CS at the University of Wisconsin-
Madison, a school that contributed a bit to Unix dev, especially 4BSD series.

It took me a while but eventually I got a login on an 11/750 named slovax
which held the sources.  As a nerd, I spent a lot of time just reading the
sources.  I really didn't know shit, I had read K&R so I could do hello
world as good as the next guy but I was trying to move on.  I had not
yet read Rochkinds book, that would have helped but it came later (for
me at least).

I did not just read the kernel, I read libc, wandered through all of that
stuff.  Had some aha's when I say varargs, but the big one for me was
popen().  I was so naive it just had never occurred to me that a library
call would create a new process to do your bidding.  I didn't have a 
mental model as to how it should work, I just knew popen() did something,
but when I read the (small) amount of could I was stunned.  To me it 
was really cool, it changed how I thought about programming.  popen()
is a pretty elegant combining of the kernel interfaces to make a very
useful interface.

I have to believe that others here had similar (and better) aha moments,
maybe a series of those would make a nice appendix or something?

Good luck with the paper, writing is hard, if you run out of reviewers
I cna try and find some time to make comments if that helps.
-- 
---
Larry McVoy                lm at bitmover.com           http://www.bitkeeper.com



  reply	other threads:[~2011-06-28  0: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 [this message]
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
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=20110628002631.GC26343@bitmover.com \
    --to=lm@bitmover.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).