On Sun, Oct 05, 2003 at 08:56:57PM +0200, Goswin von Brederlow wrote: > Sven Luther <[EMAIL PROTECTED]> writes:
> > For powerpc, this would be : > > > > oldpmac miboot floppy install : needs one kernel floppy + miboot, > > initrd on one floppy also, but maybe a two phase installation (would > > need 3 floppies) as the initrd will not fit on one floppy. > CD1/dists/sarge/main/disks-powerpc/... > CD1/disks link to ^^^ > Netboot images will be on CD1 too. > > oldpmac bootx/newpmac yaboot : both will be the same, exception is > > that newpmac will use yaboot, while oldpmac will give instructions on > > getting and making bootx work. > CD1 bootblock > > chrp/chrp-rs6k builtin initrd : this one would need a initrd builtin > > the kernel image, and will easily be booted from either yaboot (chrp) > > or from OF directly (chrp-rs6k or pegasos). > CD2 bootblock > > prep : no idea, but the above method should do also. > CD3 bootblock Do these subarchs really each need separate, incompatible bootblocks? For comparison, alpha has two different bootloaders that have to be supported, but they can coexist on the same CD. Being able to add additional bootable CDs to the set is a nice feature when some subarchitectures require boot strategies incompatible with the predominant set, but it's always better to support as many machines from disk 1 as possible to save on CDs. Otherwise, you have people who would normally burn just the first disk downloading an extra 650MB just for a boot disk. > And then start from the begining with different kernel flavours or > low-mem versions or just non-bootable CDs. Better to use that space for packages, unless there are known issues. -- Steve Langasek postmodern programmer
signature.asc
Description: Digital signature
