Raphael Hertzog wrote: > Le Tue, Oct 28, 2003 at 07:24:26PM -0500, Joey Hess écrivait: > > debian-cd: > > > > What kinds of images do you use/need from the debian-installer tree for > > building CDs on the various architectures? There is both an initrd > > image, and a CD boot "floppy" image, and I do not want to waste space in > > the archive with both if they are not both needed on a given > > architecture. > > We need : > - kernel + initrd for "isolinux" (for multiple choice at boot time) for > the first CD > - kernel + initrd for starting the installation via LoadLin on > Windows > - boot images (2.88MB mainly) for making the CD 2 & above > bootable (the good old way which should still work if isolinux fails) > > That's for i386. I can't tell for non-i386 arches but I bet that most > archs need only boot images.
Apparently powerpc needs only an initrd, which is put in the boot directory along with yaboot. > > The CD also currently contains the d-i floppy-initrd.gz (in install/), > > and I do not understand how this can possibly be of use, but my removal > > of that initrd from the debian-installer daily builds also seemed to > > break the CD builds. > > The actual script downloads floppy-image.img and floppy-initrd.gz ... it > copies the initrd but never use it anywhere. So we should probably > remove any reference to those files in our scripts since they are not > used. That would be a good thing. I'm pretty sure it's not useful to have that initrd. -- see shy jo
signature.asc
Description: Digital signature