Enrique Zanardi <[EMAIL PROTECTED]> writes: > On Wed, May 19, 1999 at 05:24:08AM -0700, Aaron Van Couwenberghe wrote: > [...] > > Notably, I'm going to be writing it in C++. This will add > > about 270k to the boot disks' root image, but as the floppy > > install methods are for the most part phasing out under the shadow > > of easier methods, I'm not going to lose any sleep over > > this. libstdc++ can be minimized for static linkage anyway.
> dpkg is not on the boot disks' root image (thanks god). It's on the base > system, with dselect, apt and, of course, libstdc++. You won't have to add > it. (Let's call that luck). :-) > OTOH, your opinion that adding 200k to the boot disks' root image, thus > breaking the "rescue" floppy, doesn't matter because the floppy install > methods are phasing out is just plainly wrong. Currently we have three > ways of booting the installation system: bootable CDs (requires a modern > BIOS), floppy disk and bootp (requires a netword card with the proper > ROM, and a bootp+tftp server on the same network). Our bootable CDs use a > floppy image for booting, the same "resc1440.bin" floppy image that's > used on a floppy based installation. That means two of our three methods > (and I dare to say the third one is used on <5% of Debian installations) > use the same "rescue" floppy disk. I won't say that's "pashing out". ;-) Why would this add 200k to the root disk? We don't have dpkg on the root disk, it's in the base image. Steve [EMAIL PROTECTED]