From: newsham@lava.net (Tim Newsham)
Subject: [Unix-jun72] UNIX running up to init, I think
Date: Fri, 2 May 2008 14:06:50 -1000 (HST) [thread overview]
Message-ID: <Pine.BSI.4.64.0805021404250.20114@malasada.lava.net> (raw)
In-Reply-To: <200805022351.QAA22591@mist.magic.com>
> 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.
*nod* we're running up to init in the cold boot kernel and getting
into the code that reads the 65th block off the tape. At this
point we only get 1 byte of data into the read buffer, though.
(not sure if this is due to simh, the kernel or some other issue).
to work around the asembler divide issue I had to sed the source
during build time. These hacks are all incorporated into the
tools/assemv7 script.
it might be fun to try to use Warren's mkfs.c program to preload
the root disk and boot warm with it.
> James Markevitch
Tim Newsham
http://www.thenewsh.com/~newsham/
next prev parent reply other threads:[~2008-05-03 0:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-02 23:51 James A. Markevitch
2008-05-03 0:06 ` Tim Newsham [this message]
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=Pine.BSI.4.64.0805021404250.20114@malasada.lava.net \
--to=newsham@lava.net \
/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).