Re: m68k boot-floppies
> >
> > Nah, I'll cook up some numbers. 512 k would be plenty (strictly 400k for
> > 1028x768 at 4bpp on Falcon. Less than 200k for TT). I've so far used 1024
> > but that's overkill. And it takes another chunk out of the RAM so 6 MB are
> > probably going to be the minimum requirement.
> Ill see if I can find the place where to put that.
bootargs in the m68k-support.tar. I'll send a working bootargs as soon as
I've tested it.
We also need the new booter for Mac, anything else to be changed?
> > makefile. The slink lowmem stuff never worked as people expected it to
> > work (wrong fdisk in lowmemrd.bin), wasn't documented properly and
> > confused people. It hasn't been worked on, can't be supported properly so
> > it has to go.
> Fine with me. lowmematari.bin and lowmemrd.bin were built, but release.sh uses
> only lowmemrd?
> cts@aahz:/build/boot-floppies>grep lowmem release.sh
> cp lowmemrd.bin $release/atari/debian/
> cp lowmemrd.bin $release/amiga/debian/
Which is because we never ever really wanted to boot from _floppy_. We
prefer a nice little .tgz, .zip or .lha the user can unpack on his disk
which contains kernel, ramdisk, booter, booter settings of some sort
(.info, bootargs, Penguin Prefs). And the funny resc144.bin and
drv1440.bin images which serve no known purpose other than holding kernel
and modules in a way the installer can deal with. Packaging the kernel
inside resc1440.bin makes (made??) sense for ix86 but not m68k - we just
use it to leave the installer code untouched. If boot-floppies would use
amiga-lilo or atari-lilo from floppy we could actually use the floppies
:-)
Speaking of files slated to disappear: I would not recommend to try and
add a Mac HFS boot floppy this time. It's not a boot floppy in the sense
that a MacOS less Mac could boot from it, and we can't easily build such a
floppy (it would need a min. system folder, the booter, kernel, ramdisk
and won't fit on a floppy. Even if it could be made to fit we could never
redistribute it. Pointless.).
Unless someone can easily build it, the Mac Install.sit would also need to
disappear.
> And the next problem... using debian/rules to build, base and bin files are
> all created, my only change to the Makefile was:
> # $(MAKE) resc720atari.bin
> Q: when I kick out resc729atari, is drv72atari-1.bin needed?
No.
> But there is a problem with release.sh:
> cp: drv1440atari.bin: No such file or directory
> E: ./release.sh abort
>
> Problem is from here (release.sh):
> cp resc1440atari.bin $release/atari/debian/resc1440.bin
> cp drv1440atari.bin $release/atari/debian/drv1440.bin
>
> But the bin files I have are called:
> drv14amiga-1.bin
> drv14atari-1.bin
> drv14bvme6000-1.bin
> drv14mac-1.bin
> drv14mvme16x-1.bin
> drv72atari-1.bin
[...]
> The names for the driver images have changed, resc and root seem to be ok...
> Nick? Thanks for fixing this :-)
Yep, Nick fixed the makefile.
How about
cp resc1440atari.bin $release/atari/debian/resc1440.bin
cp drv14atari-1.bin $release/atari/debian/drv1440.bin
and similar for Amiga and Mac? Though I'm not sure, maybe it would need to
be rescue.bin and driver-1.bin like for ix86. Depends on what the
installer looks for.
The whole stuff is just for building the install.lzh (and .tgz) files?
That's not too critical again, people should be able to do (at least test)
without.
Michael
Reply to: