From: Michael Huff <mphuff@gmail.com>
To: Henry Bent <henry.r.bent@gmail.com>
Cc: UNIX TUHS Group <tuhs@tuhs.org>
Subject: [TUHS] Re: Vax-780 with unix 2.0v2 gdts questions
Date: Sun, 19 Mar 2023 15:45:03 -0800 [thread overview]
Message-ID: <CAFwmL84BxyMH40KW3bhOThgjPOwoG-Xx0HY=G9y10i=a-OATEQ@mail.gmail.com> (raw)
In-Reply-To: <CAEdTPBc0BSocFn2zgiEG3C++kL47KwPzVhED_g3Ji2c=4UTTYQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2407 bytes --]
On Sun, Mar 19, 2023 at 3:23 PM Henry Bent <henry.r.bent@gmail.com> wrote:
> On Sun, 19 Mar 2023 at 18:56, Michael Huff <mphuff@gmail.com> wrote:
>
>> I think I may have found 2.0 on the Internet Archive too.
>> https://archive.org/details/cdrom-freebsd-2.0-1
>>
>> The dates on the iso are from late November 1994.
>>
>>
>> On Sun, Mar 19, 2023 at 2:14 PM Warner Losh <imp@bsdimp.com> wrote:
>>
>>>
>>>
>>> On Sun, Mar 19, 2023, 3: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
>>>>
>>>
>>> FreeBSD 2.0.0 was the first Lite based release. This looks to be 2.0.5
>>> which was a 7 months later.
>>>
>>> https://ftp-archive.freebsd.org/pub/FreeBSD-Archive/old-releases has
>>> all the old releases from 2.0.5 on...
>>>
>>> Hmmm I think I have the 2.0 cdrom in my basement...
>>>
>>> Warner
>>>
>>
> These are just the regular Walnut Creek (
> https://en.wikipedia.org/wiki/Walnut_Creek_CDROM ) packaged distributions
> of free software. Is there a reason that they are considered special or
> significant?
>
> -Henry
>
Yes. I posted the first one because it included a scan of the packaging and
an insert (which I don't think you can find on the FreeBSD archive -though
I haven't looked), I posted a link to the second one because it pre-dates
the earliest ISO on the FreeBSD archive (2.0 instead of 2.0.5).
I thought people would be interested in the first link as an interesting
curiosity, and the second one was for any software completists.
-Michael
[-- Attachment #2: Type: text/html, Size: 4606 bytes --]
next prev parent reply other threads:[~2023-03-19 23:45 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
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 [this message]
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='CAFwmL84BxyMH40KW3bhOThgjPOwoG-Xx0HY=G9y10i=a-OATEQ@mail.gmail.com' \
--to=mphuff@gmail.com \
--cc=henry.r.bent@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).