From: arno.griffioen@ieee.org (Arno Griffioen)
Subject: [TUHS] Why Linux not another PC/UNIX [was Mach for i386 ...]
Date: Wed, 22 Feb 2017 23:03:21 +0100 [thread overview]
Message-ID: <20170222220320.mxcjnenf5y2k25qt@ancienthardware.org> (raw)
In-Reply-To: <CAHfSdrX-Sr3C60+c+jdGJjEEVnkpPTagxuJQe3T2T9Ndsm8oBQ@mail.gmail.com>
IMHO one thing that Linux offered many people/coders/developers, especially
in the early years, was the chance to actually make a contribution and a
difference to the development and growth of the system.
Especially in the early Linux years you could track down bugs or
make improvements, send the patches to Linus and they'd actually end
up in the code in a few days to weeks. How cool was that!?!?
On BSD (at least my experience with NetBSD) it was *hard* to get
fixes incorporated and with new releases only once a year or so
it seemed very 'stale' and boring.
I think this Linux style open-ness of development, the willingness to
accept fixes and patches and perhaps horribly break things along the way,
resonated with a lot of coders and enthousiasts making it popular very
rapidly in those circles.
Heck.. I did some minor low-level and early stuff on the Linux/M68k
kernel port for the Amiga's and even though Linus himself was not interested
in a 'non-i386' port or version of Linux he was also not against it and open to
the idea and did accept fixes for bugs in the mainline kernel that were
exposed by the port (eg. byteorder issues, hardcoded i386 bits, etc.)
and basically sanitized a lot of code.
It also forced some of the early splits in some drivers in platform
independent and dependent pieces because of the vastly different styles
of I/O and interrupt handing between the i386 and the M68k family,
but Linus also saw the merit in such increased abstraction and
portability and accepted such changes even though they did 'nothing'
for the i386.
All in all at the time (early/mid 90's) I feel that the whole 'community'
(a much-abused word these days..) around Linux was much more conductive
and supportive than any of the other *IX-with-source-available options
for those that wanted to help/improve/fix stuff in the OS/kernel so it
drew in more people.
And when the (snow)ball started rolling with the free CD's on magazines
and such then all hell broke loose as far as the popularity goes.
Not saying it's "the best" at all as it can be a horrible mess, but
the earlier mention of 'good enough' (or perhaps being the 'VHS' of
*IX'es) is probably a good description.
Bye, Arno.
next prev parent reply other threads:[~2017-02-22 22:03 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 [this message]
2017-02-22 22:51 ` Larry McVoy
2017-02-22 23:29 ` Clem Cole
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=20170222220320.mxcjnenf5y2k25qt@ancienthardware.org \
--to=arno.griffioen@ieee.org \
/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).