From: MOCHIDA Shuji <mochid@netside.co.jp>
To: tuhs@tuhs.org
Subject: [TUHS] i386 binary of 4.4BSD-Alpha
Date: Mon, 05 Sep 2022 12:55:20 +0900 (JST) [thread overview]
Message-ID: <20220905.125520.1044731729545828502.mochid@netside.co.jp> (raw)
I added i386 binary compiled from 4.4BSD-Alpha source.
http://www.netside.co.jp/~mochid/comp/bsd44-build/
Boot with bochs works rather well. qemu-system-i386 also boots, and
NIC (NE2000 ne0) works good, but kernel prints many "ISA strayintr" messages.
I got many useful infomations from below 2 sites:
"Fun with virtualization" https://virtuallyfun.com/ 386bsd bochs qemu
"Computer History Wiki!" https://gunkies.org/wiki/Main_Page
Installing 386BSD on BOCHS
First time, I tried to compile i386 using 4.4BSD final (1995) source,
patching many many pieces from 386BSD, NetBSD, and else..
but then, I felt "Well, we have BSD/OS 2.0, NetBSD 1.0, and FreeBSD 2.0
those are full of good improvements.."
So, I changed target, and remebered Pace Willisson's memo in 4.4BSD
(and in 4.4BSD-Lite2 also) sys/i386/i386/README:
"4.4BSD-alpha 80386/80486 Status" June 20, 1992
that file says "can be compiled into a fairly usable system".
yeah, needed chages not so small, though.
-mochid
reply other threads:[~2022-09-05 3:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220905.125520.1044731729545828502.mochid@netside.co.jp \
--to=mochid@netside.co.jp \
--cc=tuhs@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).