Subject: Re: CVS commit: src/sys/arch/i386/conf
To: <>
From: David Laight <david@l8s.co.uk>
List: source-changes
Date: 04/23/2003 23:13:24
> > > But if this is wrong, the ramdisk size needs to be reduced in some other
> > > way...
> > 
> > We may have to give up on installs for TINY systems.
> 
> Hey! Veto!

I just managed to build and boot a boot-tiny.fs image into 8MB of memory.
However I did the following:

1) Removed bad144 from the list of programs
2) Ran 'objcopy -R .note -R .ident ramdiskbin' to shrink the image slightly

I then tried 4MB, with only 764KB of available memory, ends up with:

fdc0 at isa0 port 0x3f0-0x3f7 irq 6 drq 2
fd0 at fdc0 drive 0: 1.44MB, 80 cyl, 2 head, 18 sec
md0: internal 1550 KB image area
wd0: no disk label
boot device: fd0
root on md0a dumps on md0b
root file system type: ffs
erase ^?, werase ^W, kill ^U, intr ^C

mount: /: Abort trap
mount: /kern: Abort trap
UVM: pid 13 (sysinst), uid 0 killed: out of swap
[1]   Killed
#

AFAICT the floppy image size isn't very dependant on the file system
size, because any free space will be all 0x00 and compress very well.
So a significant increase in the space for the image, and of the fs
image itself will not make much difference to whether the image will
fit in the availavle space on a floppy.

I had to change a lot of sizes to get all the builds done - has taken
over 6 hours :-(

	David

-- 
David Laight: david@l8s.co.uk