From: Warner Losh <imp@bsdimp.com>
To: Jan Schaumann <jschauma@netmeister.org>,
The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: NetBSD turns 30
Date: Tue, 21 Mar 2023 18:13:50 +0100 [thread overview]
Message-ID: <CANCZdfoUVMuH1yqxXF-E9bAx1G+7NDv_Lyn8aLp2Hts-jQgdJQ@mail.gmail.com> (raw)
In-Reply-To: <ZBnPuJhnwm0EpvHN@netmeister.org>
[-- Attachment #1: Type: text/plain, Size: 1032 bytes --]
On Tue, Mar 21, 2023, 4:39 PM Jan Schaumann via TUHS <tuhs@tuhs.org> wrote:
> Hello,
>
> 30 years ago today on March 21st, 1993 at around
> 09:45:37 UTC, NetBSD was born!
>
> I believe this makes NetBSD the oldest,
> still-maintained and actively developed, free and open
> source descendant of the Berkeley Software
> Distribution (BSD), a true genetic Unix (albeit not
> small-caps UNIX nor UNIX(tm)).
>
2.11BSD is older and continuous... but admittedly much less so than NetBSD.
It was released in 1991 and has had almost 500 patches, the latest in the
last year. It traces back to 2.9BSD released in 1983. But it still is
basically only on the pdp-11...
Warner
If you want to see what the source tree looked like
> back then:
>
> cvs -d anoncvs@anoncvs.netbsd.org:/cvsroot co -D "1993-03-21 09:45:37
> GMT" src
>
> Or browse the tree at that time:
> https://www.netbsd.org/~jschauma/src-1993-03-21/
>
> Unlike me, many on this list were around at the time
> and place. Would love to hear some origin stories...
>
> -Jan
>
[-- Attachment #2: Type: text/html, Size: 1800 bytes --]
next prev parent reply other threads:[~2023-03-21 17:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-21 15:39 [TUHS] " Jan Schaumann via TUHS
2023-03-21 17:13 ` Warner Losh [this message]
2023-03-21 17:56 ` Andy Kosela
2023-03-21 18:27 ` [TUHS] " Dan Cross
2023-03-21 18:55 ` James Frew
2023-03-22 5:19 ` Bakul Shah
2023-03-21 21:08 ` Jon Forrest
2023-03-22 7:25 ` Mehdi Sadeghi via TUHS
2023-03-22 22:35 ` Steffen Nurpmeso
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=CANCZdfoUVMuH1yqxXF-E9bAx1G+7NDv_Lyn8aLp2Hts-jQgdJQ@mail.gmail.com \
--to=imp@bsdimp.com \
--cc=jschauma@netmeister.org \
--cc=tuhs@tuhs.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).