From: jam@magic.com (James A. Markevitch)
Subject: [Unix-jun72] UNIX running up to init, I think
Date: Fri, 2 May 2008 16:51:09 -0700 (PDT) [thread overview]
Message-ID: <200805022351.QAA22591@mist.magic.com> (raw)
Hey guys.
I saw the thread about the assembler doing divide by 2 the wrong way.
I took a look at my assembler and it had a similar bug. I fixed my
assembler, then ran the code again.
It correctly writes the RF11 image (as best as I can tell), then reads
/etc/init into the user area and executes it. I left the TC11 disabled
on my run and it panics when /etc/init tries to read the tape.
To double-check, I ran the warm boot and it successfully gets into
the /etc/init user code as well, so I'm pretty confident the image
is right.
As far as I can tell, the source code I sent out this morning has no
problems. Most likely, you guys are fighting assembler and/or other
tool issues.
I'll cobble together a bootable RF11 image (assuming that there really
are no kernel problems) and send out a copy of that. Once everyone
has that, they should be able to continue generating tapes and RK03
images of other executables, etc. I can include a copy of the
assembler listing file for both warm and cold boots so that everyone
can have a reference while they are debugging.
I've also got the M792 boot (from the documentation) as well as an
untested bos.s. If those work, then the RF11 image I send out will
be pretty close to authentic. Otherwise, you will still need to load
the kernel into core with the "load" command.
James Markevitch
next reply other threads:[~2008-05-02 23:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-02 23:51 James A. Markevitch [this message]
2008-05-03 0:06 ` Tim Newsham
2008-05-03 1:03 ` Brad Parker
2008-05-03 1:41 ` 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=200805022351.QAA22591@mist.magic.com \
--to=jam@magic.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).