The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Warner Losh <imp@bsdimp.com>
To: Will Senn <will.senn@gmail.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: 3bsd tape image
Date: Thu, 3 Aug 2023 22:41:28 -0600	[thread overview]
Message-ID: <CANCZdfriAm+nm9BC7BfTyP76QDtEemKASYi1P+FGAex4zZkHww@mail.gmail.com> (raw)
In-Reply-To: <a0850a0d-d405-9270-01f1-02932f6579cd@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 866 bytes --]

On Thu, Aug 3, 2023 at 6:13 PM Will Senn <will.senn@gmail.com> wrote:

> Hi All,
>
> Is this the only bootable 3bsd distribution tape we have?
>
>
> http://sourceforge.net/projects/bsd42/files/Install%20tapes/3%20BSD/3bsd.tap.bz2/download
>
> I don't like the idea that sourceforge is the only source, the provenance
> is unclear and I'm just not a big fan of how sourceforge handles downloads
> generally.
>
> I've found tarballs, but not tapes on TUHS.
>

The TUHS stuff matches what we have on Kirk's CDs.

And it looks like one could build a boot tape from what's in sys in the
tarball.  It has the usual standalone files that look like V7 files.

There's usr/man/man8/sysgen.8

sysgen \- UNIX system generation from the distribution tape

I've not tried to grab that tape to see if it has the same bits as in the
archive.

Warner

[-- Attachment #2: Type: text/html, Size: 1608 bytes --]

  reply	other threads:[~2023-08-04  4:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-04  0:13 [TUHS] " Will Senn
2023-08-04  4:41 ` Warner Losh [this message]
2023-08-04 17:17   ` [TUHS] " Will Senn
2023-08-04 19:50     ` Clem Cole
2023-08-28 23:03 ` Phil Budne
2023-08-29 17:18   ` KenUnix
2023-08-30 11:11     ` KenUnix
2023-08-30 14:48       ` Clem Cole
2023-08-30 19:21         ` arnold
2023-08-30 20:06           ` Clem Cole
2023-08-30 20:07           ` Rich Salz
2023-08-30 20:34             ` KenUnix
2023-08-30 15:03       ` Phil Budne

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=CANCZdfriAm+nm9BC7BfTyP76QDtEemKASYi1P+FGAex4zZkHww@mail.gmail.com \
    --to=imp@bsdimp.com \
    --cc=tuhs@tuhs.org \
    --cc=will.senn@gmail.com \
    /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).