From: wkt@tuhs.org (Warren Toomey)
Subject: [Unix-jun72] Anyone working on V1 mkfs?
Date: Fri, 2 May 2008 10:58:08 +1000 [thread overview]
Message-ID: <20080502005808.GA79200@minnie.tuhs.org> (raw)
In-Reply-To: <5372.1209688415@mini>
On Thu, May 01, 2008 at 08:33:35PM -0400, Brad Parker wrote:
> The hardware bootstrap process is in the man pages - it looks somewhat
> rational. I have not studied it but I think the fun part will be making
> a dectape image which has the binaries to be populated.
I was hoping to have a populated filesystem to start with, because we
should be able to run V1 bin/check using Apout, to check the filesystem.
> Having said all that, having a working mkfs would be would be very handy
> and would make setting up a boot disk much easier!
The V1 manual for filesystem(5) say "Blocks 0 and 1 are collectively known
as the super-block for the device". Can you confirm that block 0 is part
of the super-block, i.e. it's not reserved for bootstrap code? If block 0
is the super-block, it should contain a word (# of bytes in free-map) followed
by lots of 0177 bytes, which are the free-map.
On another note, I thought of taking V6 mkfs.c as a start-point to rewrite
V1 mkfs. I'm trying to work out what f_m and f_n do:
if(fsys[n] == 'r') {
if(f == 'k') {
f_n = 24; /* RK, why these numbers? */
f_m = 3;
}
if(f == 'p') {
f_n = 10; /* RP, why these numbers? */
f_m = 4;
}
}
Finally, are we going to use RK03 or RK05, as the sizes are different?
Thanks all,
Warren
next prev parent reply other threads:[~2008-05-02 0:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-01 23:42 Warren Toomey
2008-05-01 23:45 ` Tim Newsham
2008-05-02 0:33 ` Brad Parker
2008-05-02 0:58 ` Warren Toomey [this message]
2008-05-02 2:08 ` Tim Newsham
2008-05-02 2:31 ` Warren Toomey
2008-05-02 2:45 ` Tim Newsham
2008-05-02 3:21 ` Tim Newsham
2008-05-02 3:51 ` Warren Toomey
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=20080502005808.GA79200@minnie.tuhs.org \
--to=wkt@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).