From: krewat@kilonet.net (Arthur Krewat)
Subject: [TUHS] BSD 4.2 distribution differences
Date: Thu, 13 Apr 2017 10:00:33 -0400 [thread overview]
Message-ID: <5cbaca48-e04f-5640-50be-b654f5bb0fef@kilonet.net> (raw)
In-Reply-To: <4004e165-88da-5ec4-7502-f18a381a9fac@kilonet.net>
Question: In BSD-land, how do you "version" something like this? Two
different "snapshots" of BSD 4.2 - what file/version #/whatever is used
to definitely put a "version number" on this?
FYI, the distribution I have, vfont.tar is truncated, it was the last
file on the first tape, and at the time may have had a read error.
4,372,480 bytes of it were read, while the TUHS version is 5,888,000
However, the part that I have which is about 80% of the tar matches the
first 74% of the TUHS 4.2BSD distribution after extracting the files,
even though the checksum of that first 74% doesn't match.
So when I cobble this together, I'll just use the TUHS 4.2BSD vfont.tar
and make a note of it in the index.
On 4/12/2017 3:10 PM, Arthur Krewat wrote:
>
>
> On 4/12/2017 2:37 PM, Jeremy C. Reed wrote:
>>
>> From the quick look of the copies I have including from the CSRG
>> archives I purchased, I assume the TUHS version is the same as the CSRG
>> archives.
>>
>> Will you make your copy of the files available?
>>
>
> Absolutely! As soon as I determine without a doubt that it contains
> nothing proprietary.
>
>
>
next prev parent reply other threads:[~2017-04-13 14:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-12 17:18 Arthur Krewat
2017-04-12 18:37 ` Jeremy C. Reed
2017-04-12 19:10 ` Arthur Krewat
2017-04-13 14:00 ` Arthur Krewat [this message]
2017-04-13 14:10 ` Arthur Krewat
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=5cbaca48-e04f-5640-50be-b654f5bb0fef@kilonet.net \
--to=krewat@kilonet.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).