From: tih@hamartun.priv.no (Tom Ivar Helbekkmo)
Subject: [TUHS] 386BSD on Bochs & Qemu...
Date: Sat, 24 Apr 2010 22:59:18 +0200 [thread overview]
Message-ID: <m2vdbg5zyx.fsf@athene.hamartun.priv.no> (raw)
In-Reply-To: <v2v46b366131004241106y9562bd5cv37eb632040e1ff5f@mail.gmail.com> (Jason Stevens's message of "Sat, 24 Apr 2010 14:06:49 -0400")
Jason Stevens <neozeed at gmail.com> writes:
> IMHO the linux thing just released so often, it was a lot of work to
> keep up with (which really hasn't changed) and the BSD stuff was so
> ivory tower, of we'll release when it's ready but the world just
> wouldn't wait.
It was certainly that way with 386BSD. Jolitz released 0.0, and a lot
of us made improvements. Then he released 0.1, with none of our
improvements at all in it. We pulled up all our fixes, and made more.
Then he released 0.2, still with nothing from the net included. That's
when NetBSD was born. (FreeBSD forked off later, due to disagreements
over whether to concentrate on Intel processors (the FreeBSD crowd), or
stick to the multi-platform approach (NetBSD).)
-tih
--
Self documenting code isn't. User application constraints don't. --Ed Prochak
next prev parent reply other threads:[~2010-04-24 20:59 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-17 5:12 Jason Stevens
2010-04-17 19:10 ` Natalia Portillo
2010-04-18 1:12 ` Jason Stevens
2010-04-24 14:28 ` Jacob Goense
2010-04-24 18:06 ` Jason Stevens
2010-04-24 20:59 ` Tom Ivar Helbekkmo [this message]
2010-04-25 2:29 ` Greg 'groggy' Lehey
2010-04-25 9:28 ` Jacob Goense
2010-04-25 17:32 ` Carl Lowenstein
2010-04-25 17:36 ` Jason Stevens
2010-04-26 3:23 ` Greg 'groggy' Lehey
2010-04-26 5:22 ` Jason Stevens
2010-05-04 19:37 ` Jacob Goense
2010-05-04 19:41 ` Natalia Portillo
2010-05-04 18:26 ` Jacob Goense
2010-04-26 7:03 ` Wesley Parish
2010-04-26 8:07 ` Greg 'groggy' Lehey
2010-04-26 9:33 ` Wesley Parish
2010-04-26 17:52 ` Jason Stevens
2010-04-28 2:30 ` Cyrille Lefevre
2010-04-30 7:58 ` [TUHS] UniFlex Jose R. Valverde
2010-04-30 15:38 ` Brad Spencer
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=m2vdbg5zyx.fsf@athene.hamartun.priv.no \
--to=tih@hamartun.priv.no \
/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).