Re: Release plans for potato/m68k?
> On Mon, 4 Oct 1999, David Huggins-Daines wrote:
>
> > 3) Who is doing the boot-floppies? I remember that I volunteered to do them
> > for the Macintosh, and I'm now setting up my build and test machines, but I
> > need to coordinate with whoever does them for Amiga, Atari, MVME, and hp300.
>
> I think we can recycle most of the Amiga stuff. amiboot is the same, the
> kernel is not our fault, base.tgz is common to all archs and the rest is
> docs and scripts.
?? Did you ever look at the boot-floppies source? Any idea how the root.bin
ramdisk file is built? Do you mean 'recycle what was done for the Mac for
the 2.2 boot floppies'? In a sense: if the Mac install stuff builds fine,
the Amiga/Atari/VME files will probably be OK, too. But they are separate
builds (example: separate keymaps, possibly fdisk, on the ramdisk, separate
kernels/modules/booter on the rescue etc. image, separate filesystem type
for the rescue/drivers floppy). The only thing common for all machines is
the base archive.
The kernel needs to be built to include specific things, keeping the size to
a minimum, and have a lot of other drivers as modules. Separate kernels for
each machine, and I doubt Jes will have them prebuilt for us.
Reusing the old (2.1) installers is definitely not an option, but that
probably is not what you meant.
> > 4) How do we manage the different kernel-patches (the Mac will most
> > definitely need an additional patch above and beyond Jes' kernel - we are
> > merging only in 2.3)
>
> Truly evil would be to merge all of the kernel patches. Take a clean
> kernel, place it in CVS, apply one patch, commit. Apply the next, resolve
> conflicts, commit, ... This would be some hard work, but definitely worth
> it.
Not hard. Take Jes' 2.2.x patch, apply. CVS update from the Mac CVS server,
diff. Or cvsdiff directly. There won't be conflicts; the Mac CVS server is
well maintained :-)
Michael
Reply to: