Re: Bloat of install ramdisk?

[Havard Eidnes <he%NetBSD.org@localhost>]

> > it appears that lately the contents of the sparc ramdisk has
> > bloated to such an extent that in my local build tree I have
> > needed to bump the size of the ramdisk image and the
> > corresponding space in the INSTALL kernel as shown below.
> >
> > Does anyonw know what caused this rather sudden increase in size
> > for the ramdisk contents?
>
> My guess would be wscons and additional drivers in the INSTALL kernel.

Want to make another guess? :)

Remember, the contents of the ramdisk is the following files:

268940 -r--r--r--   1 he  wheel    5375 Mar 27 10:39 ./.profile
268933 -r-xr-xr-x  18 he  wheel  738972 Mar 27 10:39 ./bin/mt
268933 -r-xr-xr-x  18 he  wheel  738972 Mar 27 10:39 ./bin/pax
268933 -r-xr-xr-x  18 he  wheel  738972 Mar 27 10:39 ./bin/sh
268933 -r-xr-xr-x  18 he  wheel  738972 Mar 27 10:39 ./sbin/halt
268933 -r-xr-xr-x  18 he  wheel  738972 Mar 27 10:39 ./sbin/init
268933 -r-xr-xr-x  18 he  wheel  738972 Mar 27 10:39 ./sbin/mount_cd9660
268933 -r-xr-xr-x  18 he  wheel  738972 Mar 27 10:39 ./sbin/mount_ffs
268933 -r-xr-xr-x  18 he  wheel  738972 Mar 27 10:39 ./sbin/mount_mfs
268933 -r-xr-xr-x  18 he  wheel  738972 Mar 27 10:39 ./sbin/newfs
268933 -r-xr-xr-x  18 he  wheel  738972 Mar 27 10:39 ./sbin/reboot
268933 -r-xr-xr-x  18 he  wheel  738972 Mar 27 10:39 ./sbin/umount
268933 -r-xr-xr-x  18 he  wheel  738972 Mar 27 10:39 ./usr/bin/cpio
268933 -r-xr-xr-x  18 he  wheel  738972 Mar 27 10:39 ./usr/bin/eject
268933 -r-xr-xr-x  18 he  wheel  738972 Mar 27 10:39 ./usr/bin/gunzip
268933 -r-xr-xr-x  18 he  wheel  738972 Mar 27 10:39 ./usr/bin/gzip
268933 -r-xr-xr-x  18 he  wheel  738972 Mar 27 10:39 ./usr/bin/tar
268933 -r-xr-xr-x  18 he  wheel  738972 Mar 27 10:39 ./usr/bin/zcat
268933 -r-xr-xr-x  18 he  wheel  738972 Mar 27 10:39 ./usr/sbin/chroot

where the programs are (as can be seen) linked into a single
executable.  It's the size of the resulting file system which
needed to be bumped.  The resulting file system is stuffed into
the INSTALL kernel's memory-disk file system area, so that size
also needed to be bumped.

So...  If  the kernel executable itself grows through the
addition of new drivers, that will in fact not impact this at
all.

On 23 Mar it built fine:

     create  ramdisk/ramdisk.fs
Calculated size of `ramdisk.fs.tmp': 786432 bytes, 293 inodes
Extent size set to 4096
ramdisk.fs.tmp: 0.8MB (1536 sectors) block size 4096, fragment size 512
        using 1 cylinder groups of 0.75MB, 192 blks, 320 inodes.
super-block backups (for fsck -b #) at:
 32,
Populating `ramdisk.fs.tmp'
Image `ramdisk.fs.tmp' complete

on 26 Mar it didn't anymore:

     create  ramdisk/ramdisk.fs
nbmakefs: `work' size of 819200 is larger than the maxsize of 786432.

*** Failed target:  ramdisk.fs
*** Failed command: [ "work.built" = work.built -a -f ramdisk.fs -a ! 
ramdisk.fs -ot work.built ] || { echo ' ' " create " ramdisk/ramdisk.fs; rm -f 
ramdisk.fs ramdisk.fs.tmp; /u/build/HEAD/tools/sparc/bin/nbmakefs -t ffs -B be 
-s 1536b -F work.spec -N /u/build/HEAD/src/etc -o bsize=4096,fsize=512 -o 
optimization=space,minfree=0 ramdisk.fs.tmp work && mv -f ramdisk.fs.tmp 
ramdisk.fs; }
*** Error code 1

Stop.


It looks like I'll have to do a CVS time-travel to figure this
one out.


Regards,

- Håvard