From: Will Senn <will.senn@gmail.com>
To: Warner Losh <imp@bsdimp.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: 3bsd tape image
Date: Fri, 4 Aug 2023 12:17:46 -0500 [thread overview]
Message-ID: <c41b88fb-971f-1f03-f55c-eba9a98129d7@gmail.com> (raw)
In-Reply-To: <CANCZdfriAm+nm9BC7BfTyP76QDtEemKASYi1P+FGAex4zZkHww@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2677 bytes --]
On 8/3/23 23:41, Warner Losh wrote:
>
>
> 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
Hi Warner,
I would love to be able to recreate the bootable tape(s) from what we
have available (the tarball) and document that process along the way. In
the setup manual, it says:
The tape contains binary images of the system and all the user level
programs, along with source and
manual sections for them. There are about 4200 UNIX† files
altogether. The first tape file contains boot-
strapping programs. The second tape file is to be put on one
filesystem called the ‘root filesystem’, and
contains essential binaries and enough other files to allow the
system to run. The third tape file has all of
the source and documentation. Altogether the files provided on the
tape occupy approximately 40000 512
byte blocks
Taking this apart, it seems like:
The tape contains binary images of the system and all the user level
programs, along with source and
manual sections for them. There are about 4200 UNIX† files altogether.
Refers to everything in 3bsd.tar.gz - 4130 files.
And this:
The first tape file contains boot-strapping programs.
Refers to the files in sys:
boot mkfs restor rp6fmt rpread
And this:
The second tape file is to be put on one filesystem called the ‘root
filesystem’, and
contains essential binaries and enough other files to allow the
system to run.
Refers to everything except /usr/src and /usr/doc.
While this:
The third tape file has all of the source and documentation.
Refers to /usr/src and /usr doc.
If I'm understanding things, this means I would create three tape images
- one with just the 5 files in sys and that's it, the second with
everything except for /usr/src/ and /usr/doc, and the third with just
/usr/src and /usr/doc. The first tape would have blocksize 512, the
other two, 10240. I could then use any of the plethora of maketape
scripts around to put the tape together.
In looking at what was done previously, it looks like the root fs was on
the tape as a dump, whereas the usr files were on the tape as a .tar.
Why not just have root and usr as .tar on the tape?
Thanks,
Will
[-- Attachment #2: Type: text/html, Size: 3945 bytes --]
next prev parent reply other threads:[~2023-08-04 17:18 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 ` [TUHS] " Warner Losh
2023-08-04 17:17 ` Will Senn [this message]
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=c41b88fb-971f-1f03-f55c-eba9a98129d7@gmail.com \
--to=will.senn@gmail.com \
--cc=imp@bsdimp.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).