Xref: utzoo unix-pc.general:5249 comp.sys.att:9337
Path: utzoo!utgpu!watserv1!watmath!uunet!samsung!usc!apple!gateway.qm.apple.com!Eric_Smith.FCP_Quality
From: Eric_Smith.FCP_Quality@gateway.qm.apple.com (Eric Smith)
Newsgroups: unix-pc.general,comp.sys.att
Subject: Re: 68020 for UnixPC (was Re: UNIX3.51m...)
Message-ID: <7687@goofy.Apple.COM>
Date: 13 Apr 90 17:12:30 GMT
Sender: usenet@Apple.COM
Organization: Amalgamated Conglomerates
Lines: 21
References:<1135@icus.ICUS.COM> <1990Apr11.042020.5317@laguna.ccsf.caltech.edu> <104@bagend.UUCP <7669@goofy.Apple.COM> <1085@lectroid.sw.stratus.com>

In article <1085@lectroid.sw.stratus.com> lennox@lectroid.sw.stratus.com 
(Craig Scott Lennox) writes:
> In article <7669@goofy.Apple.COM> 
Eric_Smith.FCP_Quality@gateway.qm.apple.com (Eric Smith) writes:
> 
>    Armed with the kernel .o files and a disassembler, you may be able to
>    hack a working kernel.
> 
> But how would you *boot* that kernel?  Do you know the format of
> a boot tape?  If so, could you tell me?  (If of course that wouldn't be
> legally unwise)

As far as I know, you just put the new kernel in the root file system with
the correct file name (which escapes me at the moment, UNIX?), and it
should work.  Of course, the boot ROMS and the boot loader on the drive
may need to be hacked for the 68020 also.

Eric Smith

Opinions expressed herein are not necessarily those of my
employer, family, friends, computer, or even me!  :-)