From: jam@magic.com (James A. Markevitch)
Subject: [Unix-jun72] Kernel built under V1
Date: Sun, 18 May 2008 07:56:53 -0700 (PDT) [thread overview]
Message-ID: <200805181456.HAA01901@mist.magic.com> (raw)
For fun, I tried building the kernel under V1 and booting it and it
looks like it simply works.
I did the following, outside the simulator:
tools/assemv2
mkdir fs/usr/kernel
cp -pi build/u?.s fs/usr/kernel
tools/imgbuild
boot/installboot
tools/pdp11 boot/simh.cfg
Then, I logged in as root and did:
chdir /usr/kernel
as u?.s
chdir ../boot
sh run
msys2 u ../kernel/a.out
More realistically, the kernel should be built in /usr/sys.
James Markevitch
next reply other threads:[~2008-05-18 14:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-18 14:56 James A. Markevitch [this message]
2008-05-18 18:04 ` Tim Newsham
2008-05-20 5:16 ` [Unix-jun72] status on disassembler Doug Merritt
2008-05-20 7:39 ` Warren Toomey
2008-05-20 19:49 ` Tim Newsham
2008-05-21 7:44 ` Doug Merritt
2008-05-21 9:49 ` Brad Parker
2008-05-21 13:40 ` Brad Parker
2008-05-21 14:05 ` Brad Parker
2008-05-21 21:34 ` 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=200805181456.HAA01901@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).