From: Michael Huff <mphuff@gmail.com>
To: UNIX TUHS Group <tuhs@tuhs.org>
Subject: [TUHS] Re: Vax-780 with unix 2.0v2 gdts questions
Date: Sun, 19 Mar 2023 13:23:10 -0800 [thread overview]
Message-ID: <CAFwmL86CCRrkB6P00-Pbsp3T=9q61vEbF9gdM6+1vFqg15f+Jw@mail.gmail.com> (raw)
In-Reply-To: <CAFwmL8609qUOgM5H3ZczHRDTVbcxA6MG-Tz6gULV2ar70ikSjw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1077 bytes --]
Incidentally I say "no big deal" only because the iso itself is available
from the FreeBSD project, so it isn't exactly rare. But I think the scans
are.
On Sun, Mar 19, 2023 at 1:21 PM Michael Huff <mphuff@gmail.com> wrote:
> On Sun, Mar 19, 2023 at 5:46 AM Henry Bent <henry.r.bent@gmail.com> wrote:
>
>>
>> Where did you get this distribution? The one I could easily find,
>> https://archive.org/details/vax-svr2 , has serious filesystem problems
>> that can easily be seen by running an fsck on boot.
>>
>>
> Speaking of Unix History, following that link led me to a copy of what I
> think was the first 4.4BSD-Lite based FreeBSD iso -it's from June 1995. No
> big deal *except* that it includes a scan of the cover, something that
> looks like an insert and it consists of two cds. I haven't had a chance to
> look at the cds yet so I don't know what's on them.
>
> IMO the scans are the big deal and why I'm posting the link to it here.
> Apologies in advance for any lapses in etiquette:
>
> https://archive.org/details/freebsd-205-b
>
>
[-- Attachment #2: Type: text/html, Size: 1921 bytes --]
next prev parent reply other threads:[~2023-03-19 21:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-19 13:10 [TUHS] " KenUnix
2023-03-19 13:46 ` [TUHS] " Henry Bent
2023-03-19 21:21 ` Michael Huff
2023-03-19 21:23 ` Michael Huff [this message]
2023-03-19 22:14 ` Warner Losh
2023-03-19 22:56 ` Michael Huff
2023-03-19 23:23 ` Henry Bent
2023-03-19 23:45 ` Michael Huff
2023-03-20 0:09 ` Michael Huff
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='CAFwmL86CCRrkB6P00-Pbsp3T=9q61vEbF9gdM6+1vFqg15f+Jw@mail.gmail.com' \
--to=mphuff@gmail.com \
--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).