Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!ucbvax!ucbcad!pavepaws!chapman
From: chapman@pavepaws.berkeley.edu (Brent Chapman)
Newsgroups: net.micro.amiga
Subject: Re: KickStart disks vs. ROM kernel
Message-ID: <604@ucbcad.BERKELEY.EDU>
Date: Thu, 12-Jun-86 18:26:00 EDT
Article-I.D.: ucbcad.604
Posted: Thu Jun 12 18:26:00 1986
Date-Received: Tue, 17-Jun-86 06:05:54 EDT
References: <18@uw-atm.UUCP> <1261@amiga.amiga.UUCP>
Sender: news@ucbcad.BERKELEY.EDU
Reply-To: chapman@pavepaws.UUCP (Brent Chapman)
Organization: UNIXversity of California, Berkeley
Lines: 30
Keywords: KickStart ROM

>In article <18@uw-atm.UUCP> james@uw-atm.UUCP (James M Synge) writes:
>  There has been some debate about whether the kernel should remain on the
>current KickStart disk, or be placed in ROM (as the name ROM Kernel implies).
>

How about having KickStart in ROM standard, but with an (hopefully not
TOO expensive) option for us hacker types to replace that ROM with RAM
and use a KickStart disk? 

I don't like the idea of "burned-in" operating systems, like the Mac's;
there are BOUND to be bugs, and there is no way to fix them.  Also, it
precludes "customization" of the operating system by people like me
(things like changing default options, and stuff like that). 

On the other hand, with non-"burned" operating systems, if you're not
careful, you can get into a situation where you have 99 different
revisions of the OS floating around, and everyone is limited to using
the "least common denominator" system.  It's definitely something to
consider and discuss.


Brent

--

Brent Chapman
chapman@pavepaws.berkeley.edu
ucbvax!pavepaws!chapman

TANSTAAFL!  (There Ain't No Such Thing As A Free Lunch!)