From: brad@heeltoe.com (Brad Parker)
Subject: [Unix-jun72] some progress
Date: Fri, 02 May 2008 17:04:33 -0400 [thread overview]
Message-ID: <22705.1209762273@mini> (raw)
In-Reply-To: <21945.1209760518@mini>
Apparently this instruction:
mov $[systm-inode]\/2,sb0+4 / sets up initial buffers per
is not doing the right thing. I have not looked closely yet, but it should
put -109. in the sb0+4, but instead it puts a large positive number.
This is the top of the buffer, which has a WC and address in it; and it's
used to read the superblock from the RF.
anyway, when I change it to:
mov $-109.,sb0+4
things work much better. I have run to a baseball game (little league :-)
but I'll retry the cold=1 later tonight; it may work better.
-brad
next prev parent reply other threads:[~2008-05-02 21:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-02 15:23 [Unix-jun72] OCR of PreliminaryUnixImplementationDocument_Jun72.pdf James A. Markevitch
2008-05-02 17:52 ` Brad Parker
2008-05-02 18:12 ` Tim Newsham
2008-05-02 18:17 ` Brad Parker
2008-05-02 18:40 ` Tim Newsham
2008-05-02 18:50 ` Brad Parker
2008-05-02 18:59 ` Tim Newsham
2008-05-02 19:01 ` Brad Parker
2008-05-02 19:06 ` Tim Newsham
2008-05-02 20:35 ` Brad Parker
2008-05-02 21:04 ` Brad Parker [this message]
2008-05-02 21:34 ` [Unix-jun72] some progress Tim Newsham
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=22705.1209762273@mini \
--to=brad@heeltoe.com \
/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).