Re: Bug#72067: SIZELIMIT is not properly handled when bootable CDs are built
[ Ccing debian-cd so that they can help if needed, that's why i keep many
lines of context ]
Le Tue, Sep 19, 2000 at 10:00:28PM -0400, Daniel Burrows écrivait:
> Package: debian-cd
> Version: 2.2.2
> Severity: normal
>
> This may be pilot error; I'll go sit in the corner with the dunce cap
> on if that turns out to be the case.
>
> I'm trying to build some customized CDs of the Debian distribution
> (containing binary packages only, with non-us, non-free, and
> helix-gnome tacked on) I was having trouble keeping it down to four
> disks, which is ridiculous considering that the "official" CD images
> are only 3 disks, which aren't even all completely filled, and I've
> only added about 300 megabytes of stuff (half of a CD's capacity)
>
> The problem seems to be something weird happening when making the CD
> directory image. "make bin-list" claims to have kept the directory
> trees under SIZELIMIT, but a look at the directory it actually builds
> shows otherwise. (SIZELIMIT is 500000000)
>
> torrent:/usr/local/bulky/bin# du -s /usr/local/bulky/tmp/potato-i386/CD1
> 640080 /usr/local/bulky/tmp/potato-i386/CD1
>
> This happens consistently -- the CD images are all bloated by approximately
> 150,000 megabytes somewhere in the process of building them. (possibly in
> "make packages"?) These are, as shown above, real files (as opposed to some
> horrendous inefficiency in the CD filesystem) -- mounting the CD image
> loopback and running 'du' will actually demonstrate that almost all of that
> space goes into dists/debian. However, about 100 megabytes goes into
> "disks-i386" -- on a hunch, I tried not making the CDs bootable, and tada!
> they shrank down to approximately the right size (still slightly over, but not
> bad) There are several problems that I see here:
>
> (a) making all the CDs bootable. This is not so good. It basically wastes
> several hundred megabytes on redundant copies of disks-i386. I don't see
> why I need more than one bootable CD.
Only CD 1 & 2 are bootable. And disks-i386 is only included on CD1. So
only CD 1 should be bloated by 150Mb.
That's why we have SIZELIMIT1 different from SIZELIMIT in the
documentation (README) :
$ make list COMPLETE=1 SIZELIMIT1=555000000 SRCSIZELIMIT=665000000
And that's why build.sh uses a complicated system to calculate a different
SIZELIMIT for each CD.
> (c) Not documenting that the size of disks-i386 isn't included when ordering
> packages to within SIZELIMIT!! This is the main reason that I'm filing
> this bugreport--I spent several days trying to figure out what was
> wrong with my build procedure before tracking the problem down a few
> minutes ago. PLEASE, document this in README.gz; if someone naively
> says, "Ok, I'll add a bootsector and a few megabytes of install files,"
> and runs "make bootable", they can be in for a nasty surprise.
In the README :
All CD1 of officials images are bootable (CD for ARM are the exception)
and the space required for this stuff may not always be taken into
account in the size calculation. That's why you may need to adjust
manually SIZELIMIT1 following the size of the boot-floppies set that
you're using.
> Off to build non-bootable CD images so they fit on real, physical CDs,
No, you can do whatever you want with debian-cd. You just need to
learn its inconsistencies or limits. :)
Cheers,
--
Raphaël Hertzog -+- http://strasbourg.linuxfr.org/~raphael/
Naviguez sans se fatiguer à chercher : http://www.deenoo.com
Formation Linux et logiciel libre : http://www.logidee.com
Reply to: