Re: what about potato boot-floppies for powerpc/apus ?
On Sat, Nov 06, 1999 at 08:00:40AM -0800, Joel Klecker wrote:
> At 08:31 -0700 1999-11-05, Matt Porter wrote:
> >On Fri, Nov 05, 1999 at 02:52:36PM +0100, Hartmut Koptein wrote:
> >> > potato will be freezing soon, or at least so they say, so it is
> >>time to add
> >> > some kind of install stuff for apus also.
> >> A little bit late, ehhh? I asked serveral times for this, but without any
> >> help this port is for the next release.
> >I've got to agree here. Quite honestly the only subarch that is in really
> >good shape for the freeze is prep. pmac is also quite good but doesn't
> >have much testing yet.
> pmac is not ready for testing yet, I've discovered that pmac-fdisk
> does not support mac partition tables. I will fix this today.
Ok, no problem, ...
i would have done it before, but i had hardware problems and not much time.
Anyway, there should be no problem in hacking some kind of booting scheme for
apus toegether, and putting it in some unofficial place somewhere.
The problem is i don't quite understand how this stuff works, having always
installed my system by untaring the base tarball on the partition, fixing /etc
stuff by hand and then upgrading with dpkg/apt.
Could someone help me on this, for the next release that is, so i can get
started now ?
if i understood correctly, you need a rescue floppy with the kernel, a root
floppy with the root image, some drivers as a tarball and a set of boot
floppies and naturally the base tarball.
Ok, as i understand now, the base tarball should be subarch independent, the
same goes for root image or maybe not, since i see lots of root1440.bin in
each subarch dir. What is the difference between each of them ?
Also for the kernel and drivers, it should naturally be subarch dependent. But
then, there is no way to build a apus kernel from current kernel-source in
potato, and also the previous gcc (2.95.1.something) only gave me a broken
kernel. Will try again with 2.95.2 that is there now. What is the correct way
to solve this, should i do a kernel-patch-2.2.10-ppc-apus package containing
the the 2.2.10-m68k changes and the 2.2.10-apus patches on top of this ?or
should i make a subpatch containing only the ppc-apus specific stuff, that has
to be applied on top of the m68k one ?
Notice that anyway, the apus kernel will be loaded from an affs partition by a
modified amiboot. but i think that it is similar to what is done with bootX.