Subject: Re: ramdisk-tiny has grown too large (again) (sort-of)
To: None <gduzan@acm.org>
From: Gary Duzan <gary@duzan.org>
List: port-i386
Date: 12/13/2002 06:22:52
In Message <200212130148.gBD1mwq28290@capo.xnet.duzan.org> ,
   Gary Duzan <gary@duzan.org> wrote:

=>capo { /usr/src } # ./build.sh -D /usr2/i386/build -M /usr2/i386/obj -T /usr2/i386/tools -R /usr2/i386/release -m i386 | & 
tee build_i386.log
=>
=>[ ... ]
=>
=>Creating image into ramdisk-tiny.fs...
=>rm -f ramdisk-tiny.fs ramdisk-tiny.fs.tmp
=>/usr2/i386/tools/bin/nbmakefs -t ffs -B le -s 1452k -F work.spec  -N /usr/src/etc -o bsize=4096,fsize=512  -o optimization=
space,minfree=0,nsectors=1,ntracks=128  -f 10 -f 14 ramdisk-tiny.fs.tmp work  && mv -f ramdisk-tiny.fs.tmp ramdisk-tiny.fs
=>nbmakefs: `work' size of 1495040 is larger than the maxsize of 1486848.
=>*** Error code 1
=>
=>Stop.

   Ok, this isn't quite as bad as I thought. That source tree is
including the nathanw_sa branch (with fixed flists and such), which
appears to add the extra 8k; the trunk is still within the limit.

===========================================================================
Creating image into ramdisk-tiny.fs...
rm -f ramdisk-tiny.fs ramdisk-tiny.fs.tmp
/usr2/tmp/current/i386/tools/bin/nbmakefs -t ffs -B le -s 1452k -F work.spec  -N /usr2/tmp/current/src/etc -o bsize=4096,fsize=512  -o optimization=space,minfree=0,nsectors=1,ntracks=128  -f 10 -f 14 ramdisk-tiny.fs.tmp work  && mv -f ramdisk-tiny.fs.tmp ramdisk-tiny.fs
Calculated size of `ramdisk-tiny.fs.tmp': 1486848 bytes, 396 inodes
Warning: 40 sector(s) in last cylinder unallocated
ramdisk-tiny.fs.tmp:    2904 sectors in 23 cylinders of 128 tracks, 1 sectors
        1.4MB in 1 cyl groups (158 c/g, 9.88MB/g, 416 i/g)
super-block backups (for fsck -b #) at:
 32,
Populating `ramdisk-tiny.fs.tmp'
Image `ramdisk-tiny.fs.tmp' complete
===========================================================================

					Gary Duzan