<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">On 8/3/23 23:41, Warner Losh wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CANCZdfriAm+nm9BC7BfTyP76QDtEemKASYi1P+FGAex4zZkHww@mail.gmail.com"><br>
<div dir="ltr">
<div class="gmail_quote">
<div><br>
</div>
<div>The TUHS stuff matches what we have on Kirk's CDs.</div>
<div><br>
</div>
<div>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.</div>
<div><br>
</div>
<div>There's usr/man/man8/sysgen.8</div>
<div><br>
</div>
<div>sysgen \- UNIX system generation from the distribution
tape</div>
<div><br>
</div>
<div>I've not tried to grab that tape to see if it has the
same bits as in the archive.<br>
</div>
<div><br>
</div>
<div>Warner<br>
</div>
</div>
</div>
</blockquote>
<br>
Hi Warner,<br>
<br>
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:<br>
<blockquote>The tape contains binary images of the system and all
the user level programs, along with source and<br>
manual sections for them. There are about 4200 UNIX† files
altogether. The first tape file contains boot-<br>
strapping programs. The second tape file is to be put on one
filesystem called the ‘root filesystem’, and<br>
contains essential binaries and enough other files to allow the
system to run. The third tape file has all of<br>
the source and documentation. Altogether the files provided on the
tape occupy approximately 40000 512<br>
byte blocks<br>
</blockquote>
Taking this apart, it seems like:<br>
<blockquote>The tape contains binary images of the system and all
the user level programs, along with source and<br>
manual sections for them. There are about 4200 UNIX† files
altogether.<br>
</blockquote>
Refers to everything in 3bsd.tar.gz - 4130 files.<br>
<br>
And this:<br>
<blockquote>The first tape file contains boot-strapping programs. <br>
</blockquote>
Refers to the files in sys:<br>
<blockquote>boot mkfs restor rp6fmt rpread<br>
</blockquote>
And this:<br>
<blockquote>The second tape file is to be put on one filesystem
called the ‘root filesystem’, and<br>
contains essential binaries and enough other files to allow the
system to run.<br>
</blockquote>
Refers to everything except /usr/src and /usr/doc.<br>
<br>
While this:<br>
<blockquote>The third tape file has all of the source and
documentation.<br>
</blockquote>
Refers to /usr/src and /usr doc.<br>
<br>
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.<br>
<br>
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?<br>
<br>
Thanks,<br>
<br>
Will<br>
</body>
</html>