Subject: Re: Boot image too big?
To: Richard Rauch <rkr@olib.org>
From: Nicolas Joly <njoly@pasteur.fr>
List: port-amd64
Date: 01/20/2004 19:43:33
On Tue, Jan 20, 2004 at 12:15:32PM -0600, Richard Rauch wrote:
> On Tue, Jan 20, 2004 at 07:07:53PM +0100, Nicolas Joly wrote:
> > On Tue, Jan 20, 2004 at 11:33:10AM -0600, Richard Rauch wrote:
> > >[...]
> > > buildfloppies.sh: Image is 24576 bytes (24 KB) too big to fit on 2 disks
> > > 
> > > Is this a known problem?  Has it been this way for a while?  Should I
> > > file a PR?
> > 
> > I noticed this a few weeks ago ... And locally made some modifications
> > (attached) to allow release target.
> 
> Heh.  Thanks for the patches.
> 
> Do you wind up with a bootable CD, then?  Or is there anything magic about
> the way that a "2 boot floppy" setup interacts with making a boot CD?
> 
> (I can handle it if the CD doesn't boot, but it'd be nice if it would.  And
> I seem to recall that the CD boot mechanism---at least for i386, and presum-
> ably for amd64---is based on a "big" floppy image.)

I never made a bootable CD; i often use a set of floppies
instead. It's a little slow, but works fine with a network install
(sets cross-builded from another i386 host).

> (Of course, if I trimmed the INSTALL kernel, that might help, too, yes?)

CD boot mecanism is based on 2.88M-sized images
(cf. src/distrib/amd64/floppies/bootfloppy-big/Makefile).

In that case, you'll need to restore the big floppy size to the
original value (5760), ... and play with the INSTALL kernel.

-- 
Nicolas Joly

Biological Software and Databanks.
Institut Pasteur, Paris.