Bug#240109: Further info
On Thu, Mar 25, 2004 at 06:37:28PM +0000, Chris Tillman wrote:
> I was attempting to find a proper kernel on CD #1 which I had downloaded.
> Here is the list I found:
>
> # cd /cdrom/pool/main/k
> # find . | grep 'kernel-image'
>
> ./kernel-image-2.2.10-powerpc-apus
> ./kernel-image-2.2.10-powerpc-apus/kernel-image-2.2.10-apus_2.2.10-13_powerpc.deb
> ./kernel-image-2.2.10-powerpc-apus/TRANS.TBL
> ./kernel-patch-2.4.20-apus/kernel-image-apus_2.4.20-1_powerpc.deb
> ./kernel-patch-2.4.20-apus/kernel-image-2.4.20-apus_2.4.20-1_powerpc.deb
> ./kernel-patch-2.4.25-powerpc/kernel-image-2.4.25-powerpc-smp-prep_2.4.25-2_powerpc.deb
> ./kernel-patch-2.4.25-powerpc/kernel-image-2.4.25-powerpc-small-pmac_2.4.25-2_powerpc.deb
> ./kernel-patch-2.4.25-powerpc/kernel-image-2.4.25-powerpc-prep_2.4.25-2_powerpc.deb
> ./kernel-patch-2.4.25-powerpc/kernel-image-2.4.25-power4-chrp_2.4.25-2_powerpc.deb
> ./kernel-patch-2.4.25-powerpc/kernel-image-2.4.25-power3-chrp_2.4.25-2_powerpc.deb
The daily netinst images on cdimage.debian.org include
2.4.25-powerpc-pmac. How do the jigdo images get built?
> Did the installer just pick the apus kernel to install because the
> pmac one wasn't available? It should have thrown its cookies instead.
That's a bug too - I'm not quite sure where this happens.
--
Colin Watson [cjwatson@flatline.org.uk]
Reply to: