Subject: Re: Failed to build 3.99.8 (installation floppy is too big)
To: Steven M. Bellovin <>
From: David Laight <>
List: current-users
Date: 09/03/2005 16:27:48
On Sat, Sep 03, 2005 at 10:13:12AM -0400, Steven M. Bellovin wrote:
> The current -- and recurring -- source of pain is the limit of two 
> floppies.  Let's bump that to three, while switching to cdboot to get 
> away from the 2.88M limit on CDs.

The 'usual' problem is that 'rescue-tiny' explodes, that has to fit
on a single 1.2MB 5.25" floppy.

In this case something different is going on.  The main release floppy
has had a moderate amount of space.  Recent changes have made it bigger,
but it should still fit (IIRC by about 20k).

The other place that can cause grief is addings things to GENERIC.local.
The INSTALL_xxx include this (maybe they shouldn't) and that could
easily cause the size of the install kernels to increase.

Can you try modifying src/sys/conf/ so that the last
line of the definition of SYSTEM_LD is:
	 ${LD} -Map $ --cref ${LINKFLAGS} -o $@ '$${SYSTEM_OBJ}' '$${EXTRA_OBJ}' vers.o
relink the INSTALL kernel and put the file somewhere I can access it.

Similarly apply the folowing patch:

diff -u -p -r1.22 Makefile.ramdisk
--- distrib/i386/floppies/common/Makefile.ramdisk       18 Apr 2004 20:04:26 -0000      1.22
+++ distrib/i386/floppies/common/Makefile.ramdisk       3 Sep 2005 15:21:18 -0000
@@ -26,6 +26,10 @@ IMAGEDEPENDS+=       ${CRUNCHBIN} \
+# This propogates through to the link of ramdiskbin
+# The map file is useful when trying to prune the image
+CRUNCHENV += LDFLAGS='-Wl,-Map,${CRUNCHBIN}.map,-cref'
 .if defined(USE_SYSINST)
 .if ${USE_SYSINST} != yes
 LISTS+=		${DISTRIBDIR}/common/list.sysinst.${USE_SYSINST}

rebuild the ramdisk, and put the file somewhere.

Then I can compare the contents and sizes of the kernel and ramdisk to
ones I've built that fit.

I might even comit the relevant scripts - auto-bloat-blame :-)


David Laight: