The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: dugo@xs4all.nl (Jacob Goense)
Subject: [TUHS] 386BSD on Bochs & Qemu...
Date: Tue, 4 May 2010 21:37:15 +0200	[thread overview]
Message-ID: <69d171f5fd5a71aebb54fec721835024.squirrel@webmail.xs4all.nl> (raw)
In-Reply-To: <n2o46b366131004252222r20610f3bk29ef343230347be0@mail.gmail.com>

On Mon, April 26, 2010 07:22 "Jason Stevens" <neozeed at gmail.com> wrote:
> Well I've been able to find this much out...
>
> The CD has some kind of weird 'live' CD filesystem to it... It would
> seem that 386BSD 1.0 demanded you have an Adaptec 1542 controller
> hooked up, and with special roms & whatnot it could 'boot' from the
> CD...
> Needless to say, this predates anything like IDE CDROM's or or what
> most emulators will emulate.

That "Bootable CD" button on the CD cover is just a marketing fact
AFAICT. I don't have the foggiest how that was done in the pre eltorito
days on an x86.

> That being said, they did include the 'boot' program which is touched
> on in the magazine series, as a MS-DOS bootloader.

Mock code aside, no source code for boot.exe. No source code for the
install program and no Tiny 386BSD Release 1.0 boot floppy image on the
CD. I can't get my head around why they bothered to document to the
point where you can almost port BSD to a Commodore 64 and leave these
bits out.

> So I've just slapped together a MS-DOS floppy, with the boot & 386bsd
> kernel and tried it on on Qemu, to an early kernel panic.

After numerous attect vectors I took the MS-DOS5 floppy route w/ Qemu
as well, but nothing could get it to boot cdrom. Then in a recalcitrant
mood I stuck the image to -hdb, an empty 1G drive to -hda, booted flop
and gave a BOOT.EXE 386BSD.DDB wd1d at the DOS prompt and booted into
The 386BSD SAMPLER. The installer ran fine as long as it didn't have
to deal with swap space. Not that it left me with a bootable system,
but it's a start. Will document on gunkies.org if I can get things
stable.

> I'll have to test later if it can 'mount' an ISO image that's been
> 'dd''d to a hard disk.....

Skip the dd'ing, Qemu eats the image raw ;)

/Jacob





  reply	other threads:[~2010-05-04 19:37 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-17  5:12 Jason Stevens
2010-04-17 19:10 ` Natalia Portillo
2010-04-18  1:12   ` Jason Stevens
2010-04-24 14:28 ` Jacob Goense
2010-04-24 18:06   ` Jason Stevens
2010-04-24 20:59     ` Tom Ivar Helbekkmo
2010-04-25  2:29   ` Greg 'groggy' Lehey
2010-04-25  9:28     ` Jacob Goense
2010-04-25 17:32       ` Carl Lowenstein
2010-04-25 17:36         ` Jason Stevens
2010-04-26  3:23       ` Greg 'groggy' Lehey
2010-04-26  5:22         ` Jason Stevens
2010-05-04 19:37           ` Jacob Goense [this message]
2010-05-04 19:41             ` Natalia Portillo
2010-05-04 18:26         ` Jacob Goense
2010-04-26  7:03     ` Wesley Parish
2010-04-26  8:07       ` Greg 'groggy' Lehey
2010-04-26  9:33         ` Wesley Parish
2010-04-26 17:52           ` Jason Stevens
2010-04-28  2:30             ` Cyrille Lefevre
2010-04-30  7:58               ` [TUHS] UniFlex Jose R. Valverde
2010-04-30 15:38                 ` Brad Spencer

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=69d171f5fd5a71aebb54fec721835024.squirrel@webmail.xs4all.nl \
    --to=dugo@xs4all.nl \
    /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).