From: wkt@tuhs.org (Warren Toomey)
Subject: [Unix-jun72] ... in case you wanted to play along.
Date: Sat, 3 May 2008 12:25:54 +1000 [thread overview]
Message-ID: <20080503022554.GA36595@minnie.tuhs.org> (raw)
In-Reply-To: <Pine.BSI.4.64.0805021552070.20114@malasada.lava.net>
On Fri, May 02, 2008 at 03:55:13PM -1000, Tim Newsham wrote:
> To build a rf image using the cold boot:
> - svn update to the latest.
> - run "tools/assemv7 cold" to make a cold image
> - run "./simh.cfg"
> - "break 40160" this is the "close" syscall at the end of
> processing the tape
> - "go"
> - "go" again if you're sure you want to overwrite your rf image
Don't forget to "det rf" and "quit" to make sure the rf0.dsk image is
written out correctly.
V1 check gives this output on the above rf0.dsk image:
62 files
62 large
322 indirect
9976 used
406 free
552 missing
but that's skipping the bad/dup i messages.
Cheers,
Warren
prev parent reply other threads:[~2008-05-03 2:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-02 21:03 Tim Newsham
2008-05-03 1:39 ` Warren Toomey
2008-05-03 1:46 ` Tim Newsham
2008-05-03 1:53 ` Warren Toomey
2008-05-03 1:55 ` Tim Newsham
2008-05-03 2:25 ` Warren Toomey [this message]
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=20080503022554.GA36595@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).