The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: a.phillip.garcia@gmail.com (A. P. Garcia)
Subject: [TUHS] Bugs in V6 'dcheck'
Date: Sun, 1 Jun 2014 21:10:01 -0500	[thread overview]
Message-ID: <CAFCBnZs3GQ9NHw6AXUsH8OXCCzF0ENC_5hPijJMZiUKXaXYptw@mail.gmail.com> (raw)
In-Reply-To: <A1F9F243-29E6-4831-AB34-BD7BDB312DFA@ronnatalie.com>

On Jun 1, 2014 8:11 PM, "Ronald Natalie" <ron at ronnatalie.com> wrote:
>
> Some UPSTART named RMS in his whole odipherous spledor couldn't even
spell LINUX.

This I've always found ironic, that he's sore because people call the os
linux and don't give gnu credit, when gnu itself was simply a unix ripoff.

Trying to empathize with the creators of unix, I think I would've felt like
someone was stealing things I'd worked hard to produce. But I don't know.
Like you said, he wrote manifestos and rants, so I might just as well have
dismissed him as a nut. You could also take the magnanimous view that he
was actually helping spread your ideas, albeit while putting his own
political spin on things. I'm sorry, I wasn't trying to troll or start a
flame war. RMS is something of an enigma to me.

<snip>

> RMS didn't even enter onto the UNIX scene until after he had been burned
by LMI/Symbolics/MIT over contributions he made to the Lisp Machine that he
assumed would always be freely available.     I was a rather late comer to
UNIX, having not started on it until 1977,   RMS wasn't anywhere around
until over a decade later.

I think he likes to throw 1984 around as the year he wrote the 'gnu
manifesto'.

> I was happy that Ken and Dennis and the folks were coming up with the
design pattern and not worrying about every single bug in the system.
This was RESEARCH.     Those of us in the direct trenches at the places
that got UNIX under the "scrap metal" provisions got to make our own
contribution by increasing robustness and performance as well as extended
the underlying paradigm.

And it's a beautiful design that has adapted remarkably well to new
technologies for decades.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20140601/cd1648ae/attachment.html>


  reply	other threads:[~2014-06-02  2:10 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-31 23:24 Doug McIlroy
2014-06-01  0:17 ` Kevin Schoedel
2014-06-01 22:54   ` scj
2014-06-01 23:48 ` A. P. Garcia
2014-06-02  1:11   ` Ronald Natalie
2014-06-02  2:10     ` A. P. Garcia [this message]
2014-06-03 16:38 ` Nelson H. F. Beebe
  -- strict thread matches above, loose matches on Subject: below --
2014-06-03 17:33 Nelson H. F. Beebe
2014-06-02  3:34 Noel Chiappa
2014-06-02  4:05 ` Mary Ann Horton
2014-06-02  6:12 ` arnold
2014-06-03 12:11 ` emanuel stiebler
2014-06-02  3:18 Noel Chiappa
2014-06-02  2:14 Michael Spacefalcon
2014-06-02  2:51 ` John Cowan
2014-05-31 15:55 Noel Chiappa
2014-05-31 16:18 ` Ron Natalie
2014-05-31 14:19 Noel Chiappa
2014-05-31 13:30 Norman Wilson
2014-05-31 16:03 ` John Cowan
     [not found]   ` <20140531161620.GL28034@mcvoy.com>
2014-05-31 17:16     ` John Cowan
2014-05-31 13:15 Noel Chiappa
2014-05-31 13:23 ` Ronald Natalie
2014-05-31 18:58 ` Tim Newsham
2014-05-31 19:48 ` Clem Cole

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=CAFCBnZs3GQ9NHw6AXUsH8OXCCzF0ENC_5hPijJMZiUKXaXYptw@mail.gmail.com \
    --to=a.phillip.garcia@gmail.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).