Subject: Re: Resolving bootfloopy-big size limit
To: Julio M. Merino Vidal <jmmv84@gmail.com>
From: Manuel Bouyer <bouyer@antioche.eu.org>
List: port-i386
Date: 11/12/2006 00:01:03
On Sat, Nov 11, 2006 at 04:16:56PM +0100, Julio M. Merino Vidal wrote:
> Hello,
> 
> [ Please CC me any replies. ]
> 
> The bootfloppy-big installation disk image is every now and then
> giving problems due to its size limit.  This is set to 2.88MB to allow
> its use in El-Torito floppy disk emulation bootable ISO images.
> 
> The limit prevents the addition of new features (such as full LFS
> support).  But it also causes build failures from time to time due to
> the addition of non-optional features that keep enlarging e.g. the
> kernel.
> 
> We now have the ability to build bootable ISO images that use
> El-Torito hard disk emulation, hence not having any size constraints.
> The problem is that we cannot take advantage of them due to the limit
> in bootfloppy-big.  I see several solution:
> 
> 1) Remove the bootfloppy-big image altogether.  This won't happen
>   because people still wants it (think netbooting).
> 
> 2) Remove the size constraints in bootfloppy-big.  This prevents using
>   the image with El-Torito but still allows its use in other situations
>   (as mentioned in the previous point).  Then, this image could be
>   usable for the "new" ISO images.  Seems to be the cleanest
>   approach.

I use almost only netbooting these days, and I boot the INSTALL kernels
directly, not the floppy image. How is a floppy image used in netboot ?
Couldn't a disk image (which we can make as big as needed) be used instead ?

-- 
Manuel Bouyer <bouyer@antioche.eu.org>
     NetBSD: 26 ans d'experience feront toujours la difference
--