Subject: Re: _KERNEL cpp symbol in kernel source
To: None <nigel@ind.tansu.com.au>
From: Stephen Brown <sbrown@best.com>
List: port-mac68k
Date: 07/23/1999 13:06:43
Hi Nigel,
It is good to see someone working on the Installer again.
It definitely could use a major overhaul of the filesystem
related code.
As the last one to release a version of the Installer, I'll
be happy to try to answer any questions about the old code,
or at least the parts of it I added(multiple file selection
dialog & progress bar).
Steve B.
sbrown@best.com
> From port-mac68k-owner-sbrown=best.com@netbsd.org Thu Jul 22 19:18:31 1999
> Subject: Re: _KERNEL cpp symbol in kernel source
> To: thorpej@nas.nasa.gov
> Cc: wrstuden@nas.nasa.gov, nigel@ind.tansu.com.au, briggs@ninthwonder.com,
> port-mac68k@netbsd.org
> X-Mailer: ELM [version 2.4 PL25]
> MIME-Version: 1.0
> Content-Type: text/plain; charset=US-ASCII
> Content-Transfer-Encoding: 7bit
> Sender: port-mac68k-owner@netbsd.org
> Delivered-To: port-mac68k@netbsd.org
>
> Bill Studenmund <wrstuden@nas.nasa.gov> wrote:
> > If we're talking the booter, I'd vote going for libsa. If we're talking
> > installer, then I'd vote doing both the same, and going your present
> > routie. :-)
>
> I am doing a MacOS library of stuff common to both the Booter
> and Installer (& mkfs?). At the moment, it has the ext2fs/ffs/ufs/vfs
> code straight from the kernel, plus some glue for stuff like panic().
>
> After I get that fully working, I will add the GUI stuff for
> selecting the device (IDE/SCSI) and partition, and the common stuff
> for gzip & tar extraction.
>
>
> Jason R. Thorpe <thorpej@nas.nasa.gov> wrote:
> >> NetBSD/mac68k *should* be using sysinst, not some MacOS installer tool.
>
> Here I disagree. I think that it is better to have a mouse-
> based graphical tool - it will always be better/easier for new users.
>
> (Interestingly, the latest version of LinuxPPC provides an X-windows
> based installer. It does it by mounting a 60MB live filesystem. Yuk)
>
> There is nothing wrong with NetBSD/Mac68k having a working set
> of tools under the MacOS as well. In fact, we already do. I just want
> to fix them so that they use the kernel code (which hopefully works)
> instead of the old Alice stuff.
>
>
> >> This effort should really be put into a native boot block.
>
> MacOS tools are _my_ passion (and limited coding experience).
> Not that others shouldn't work on native stuff, though :-)
>
> --
> | Nigel Pearson, nigel@ind.tansu.com.au | "reality is that which |
> | Telstra IN&IND, Sydney, Australia. | doesn't go away when you |
> | Office: 9206 3468 Fax: 9212 6329 | stop believing in it." |
> | Mobile: 0408 664435 Home: 9579 3293 | Philip K. Dick |
>