Did UNIX/Unix tapes have live file systems to dump in or tree of resources to pull from? Or something else!

@dexter When I was a student sysadmin at St Olaf college, Craig Rice, the senior admin dug out the v6 and v7 tapes and had us take a stab at extracting them, pointing me at Mike Haertel (an Olaf graduate) for help. That was, uh, 1993?

Ahah! I found my notes from talk(1)ing with him!
-----v6----
Greetings from the distant past...
So, you've gotten interested in those old tapes, eh?
You're gonna love this...
the v6 tape is 12100 512-byte blocks.
The first 100 blocks are a "tp" format archive.
Yeah, tp. Dig up the old v6 manuals. :-)
The remaining 12000 blocks are evenly split into 3 4000 block
file system images, the first being root, the second /usr/source,
and the third /usr/docs.
(They had different names in those days.)
So, to read those tapes, you're going to have to understand the v7
(I mean v6) file system format. The stuff in the tp archive at
the beginning doesn't relly matter--it is a boot block, and then
a few programs meant to be booted by the boot block. Its main
purpose is to extract the rest of the tape.
Anyway, I went through all this a few years ago. It turned out
to be remarkably simple to write a simple program to read the file
system image, but I no longer have it.

----v7----
Now, about the v7 tape. The format of that tape is as follows:
There are ... 5 files consisting of 512 byte records,
and 2 files consisting of 10240 byte records.
The first 5 files are basically boot stuff again.
The second or third is just a list of the tape contents,
the others are standalone "cat", standalone "mkfs", and standalone "restor",
and the boot block itself.
Then, the last two files are v7 dumps of root and usr.
I have a program I wrote to extract those.
And I still have the sources for that one. So I'll just email it to you.

@dexter Finally, Mike's comments on filesystem image vs dump format
----
Incidentally, dumps are much more of a pain than file system images
to extract.
It's hard to describe.
No, it's not that. It's just that...(looking at v7restore source)
Ah, that's right. In order to extract a dump, you need to first
build an in-core picture of the hierarchy.
Because the dump is just done of inode numbers in order.
Then, once you know what name to associate with each inode, you
can extract things.
Traversing a file system image is much simpler--you just start
at the root directory inode, and do the moral equivalent of a recursive
walk on the file system, extracting the files as you visit them.
The problem is that dumps are in linear order, and don't contain
convenient seek addresses for traversing in logical order.