From: Giorgos Keramidas <keramida@ceid.upatras.gr>
To: Mike Bristow <mike@urgle.com>
Cc: Bill Studenmund <wrstuden@netbsd.org>,
arief_mulya <arief@bna.telkomsel.co.id>,
linux-kernel@vger.kernel.org, tech@openbsd.org,
freebsd-hackers@FreeBSD.ORG, tech-kern@netbsd.org
Subject: Re: Technical Differences of *BSD and Linux
Date: Sun, 26 Jan 2003 09:46:46 +0200 [thread overview]
Message-ID: <20030126074646.GA1683@gothmog.gr> (raw)
In-Reply-To: <20030124225624.GB23410@lindt.urgle.com>
On 2003-01-24 22:56, Mike Bristow <mike@urgle.com> wrote:
> [ Reply-To set to me: This is probably off topic for all of the lists:
> all of the ones I read, anyway. ]
>
> On Fri, Jan 24, 2003 at 10:03:53AM -0800, Bill Studenmund wrote:
> > > 2. How does it differ? What are the technical reasoning
> > > behind the decisions?
> >
> > They differ in most technical areas. Mainly as the *BSD kernels were
> > derived from 4.4-Lite, and Linux was derived, I believe, from Minux.
>
> Point of order: Linux was a cleanroom implementation, using IIRC Minux
> as the host OS until such time as it became self-hosting.
It was "Minix", not Minux. And Linux started as a clean room
implementation that was free from any Minix code, to avoid problems
with the license of Minix. See the thread where Linus Torvalds
announced the creation of Linux in comp.os.minix below (if the URL
wraps, cut n' paste it to one line before checking it out):
http://groups.google.com/groups?amp;th=d161e94858c4c0b9&rnum=6
next prev parent reply other threads:[~2003-01-26 7:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-24 4:35 Technical Differences of *BSD and Linux arief_mulya
2003-01-24 4:55 ` Theo de Raadt
2003-01-24 5:01 ` Greg Black
2003-01-24 18:03 ` Bill Studenmund
2003-01-24 22:56 ` Mike Bristow
2003-01-26 7:46 ` Giorgos Keramidas [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-24 11:00 Josef El-Rayes
2003-01-24 13:15 ` Rik van Riel
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=20030126074646.GA1683@gothmog.gr \
--to=keramida@ceid.upatras.gr \
--cc=arief@bna.telkomsel.co.id \
--cc=freebsd-hackers@FreeBSD.ORG \
--cc=linux-kernel@vger.kernel.org \
--cc=mike@urgle.com \
--cc=tech-kern@netbsd.org \
--cc=tech@openbsd.org \
--cc=wrstuden@netbsd.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