The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] Why Linux not another PC/UNIX [was Mach for i386 ...]
Date: Wed, 22 Feb 2017 18:29:50 -0500	[thread overview]
Message-ID: <CAC20D2MdbKk1=n4J1CVhYsuY75BxvnH-b+5XH=eRX5z6SQXxDA@mail.gmail.com> (raw)
In-Reply-To: <20170222220320.mxcjnenf5y2k25qt@ancienthardware.org>

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

Arno - thanks for more on this, as I think you scratched a difference
between your experience and my own.

​By the time Linux shows up in the early 1990s, people like me had been
developing UNIX for a long time and the novelty of hacking on the system,
making changes, bug fixes was gone.   I just wanted to use it on a PC/386.

BSD for the 386 worked and so Linux was a step backwards and I was only
going there because I felt I needed too.  I remember when I first got
Slackware running, after the trying Linus's 0.9 mumble release.... and it
actually sort of ran ...  saying "maybe this will work"  but then I start
running it issues such as I could not back up it like my other systems,
network hosed up, few scripts "just worked",  etc..

Yet, one of my coworkers who was about 2/3 years out of school at that
point, thought Linux was so cool because of all things Arno suggested.   He
could submit bug reports and he changes go in.  When I was b*tching about
something breaking, he would say - "Clem you know how to fix it   And I
would reply "yup I do.  But I don't want to."  This was a the system I
wanted to use ( at home ).​  I get paid to hack at work.  I wanted a
DOS/Windows alternative for home that I could rely on.  I was not looking
for a yet another system to do development (I had that).

Which shows that difference... I was part of Chet's club, so I was hacking
on UNIX already, and I did not need/want another system at home to hack
just to keep my day to day working at home (or my wife being able to print
things etc).   The point was that I did not mind fixing the occasional
thing I ran into with BSD - but those problem were few and usually had to
do with new device bring up.   But once something was was running, I could
just use it.   But the Linux systems I could not do that - they were very
fragile, so it was not "fun" -- it was work.

That was probably different for many of you.   Linux was fun and cool, just
like UNIX had been for me 10-15 years earlier in the mid 1970s.

Clem
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170222/7798de4f/attachment.html>


  parent reply	other threads:[~2017-02-22 23:29 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-22  3:38 Clem Cole
2017-02-22  4:28 ` Dan Cross
2017-02-22 15:36   ` Clem Cole
2017-02-22 16:11     ` Larry McVoy
2017-02-22 17:00       ` Clem Cole
2017-02-22 17:06         ` Chet Ramey
2017-02-22 18:24         ` Larry McVoy
2017-02-22 19:35           ` Clem Cole
2017-02-22 20:18             ` arnold
2017-02-22 22:11               ` Clem Cole
2017-02-22 21:34             ` Larry McVoy
2017-02-22 22:56               ` Clem Cole
2017-02-22 23:13                 ` Larry McVoy
2017-02-22 23:51                   ` Clem Cole
2017-02-22 23:51           ` Paul Ruizendaal
2017-02-23 19:15             ` Clem Cole
2017-02-23 20:31               ` Random832
2017-02-23 22:48                 ` Joerg Schilling
2017-02-24  2:07                   ` Jason Stevens
2017-02-23 23:06                 ` Wesley Parish
2017-02-22 17:41       ` Arthur Krewat
2017-02-22 21:00     ` Michael Kerpan
2017-02-22 22:03       ` Arno Griffioen
2017-02-22 22:51         ` Larry McVoy
2017-02-22 23:29         ` Clem Cole [this message]
2017-02-23  4:53           ` Gregg Levine
2017-02-22 22:18       ` Clem Cole
2017-02-24  3:53     ` Dan Cross
2017-02-22  5:56 ` Steve Nickolas
2017-02-24  5:31   ` John Labovitz

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='CAC20D2MdbKk1=n4J1CVhYsuY75BxvnH-b+5XH=eRX5z6SQXxDA@mail.gmail.com' \
    --to=clemc@ccc.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).