From: reed@reedmedia.net (Jeremy C. Reed)
Subject: [TUHS] Happy 25th Birthday NetBSD!
Date: Wed, 21 Mar 2018 17:35:49 -0500 (CDT) [thread overview]
Message-ID: <alpine.NEB.2.20.1803211456560.25928@t1.m.reedmedia.net> (raw)
Revision 1.1, Sun Mar 21 09:45:37 1993 UTC (25 years ago) by cgd
http://cvsweb.netbsd.org/bsdweb.cgi/src/sbin/init/init.c?rev=1.1&content-type=text/x-cvsweb-markup&only_with_tag=MAIN
Today is commonly considered the birthday of NetBSD.
Theo told me (seven years ago) that he, cgd, and glass (and one other
person) planned it within 30 minutes after discussing with the CSRG and
BSDI guys in the hot tub at the Town & Country Resort in San Diego at
the January 25-29 1993 USENIX conference. (Does anyone have more to
share about this discussion?) Soon, cgd had setup a CVS repository
(forked 386BSD with many patchkits) which was re-rolled a few times (due
to corrupted CVS). (So maybe March 21 is later than the real birthday.)
As far as I know, it is the oldest continuously-maintained complete
open source operating system. (It predates Slackware Linux, FreeBSD,
and Debian Linux by some months.)
"NetBSD" wasn't mentioned by name in the April 19. 1993 release files
(but was named in the announcement).
ftp://ftp.netbsd.org/pub/NetBSD/misc/release/NetBSD/NetBSD-0.8
On April 28, the kernel was renamed to /netbsd, the boot loader
identified it as NetBSD, and various references of 386BSD were changed
to NetBSD.
https://github.com/NetBSD/src/commit/a477732ff85d5557eef2808b5cbf221f3c74553b
https://github.com/NetBSD/src/commit/446115f2d63299e52f34977fb4a88c289dcae92f
next reply other threads:[~2018-03-21 22:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-21 22:35 Jeremy C. Reed [this message]
2018-03-22 0:30 ` Andy Kosela
2018-03-22 1:21 ` Erik Berls
2018-03-22 1:41 ` Jon Forrest
2018-03-22 1:09 ` Dave Horsfall
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=alpine.NEB.2.20.1803211456560.25928@t1.m.reedmedia.net \
--to=reed@reedmedia.net \
/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).