From: Jacob Moody <moody@posixcafe.org>
To: tuhs@tuhs.org
Subject: [TUHS] 32V filesystem images to verify code against.
Date: Fri, 9 Feb 2024 12:11:25 -0600 [thread overview]
Message-ID: <75dc61d7-9281-47bf-83db-3e58f261f5bb@posixcafe.org> (raw)
Hello TUHS,
I recently have been working on the Plan 9 fs/v6fs and fs/v32fs programs,
another member of the community had noticed bugs within them and I wanted
to verify that the new code is working as expected. I haven't had an issue
verifying v6fs using files from the TUHS archive but v32fs has proved to
be a bit more tricky. After a little bit of work we were able to get the 'file2'
located at https://www.tuhs.org/Archive/Distributions/USDL/32V/ to mount and read
files. But given that all the files here are binaries it was a bit hard to make sure
we're getting the correct information. I attempted to cross reference the files I get
against the file2.tar also located within that spot in the archive but I am getting tar
errors when extracting this file, so its not exactly obvious if what I am checking against
is correct.
So I would like to ask if someone here knows exactly what the sha1sums of these files are
supposed to be and/or has another image with known contents I could test against. I will
preface this with the fact that I am not very well versed in old UNIX filesystems so
please let me know if I've missed anything.
Thank you,
Jacob Moody
reply other threads:[~2024-02-09 18:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=75dc61d7-9281-47bf-83db-3e58f261f5bb@posixcafe.org \
--to=moody@posixcafe.org \
--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).