--YwTTlJgQ7QoYB9ta
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, Jan 16, 2006 at 04:41:34PM -0800, Hisashi T Fujinaka wrote:
  | On Mon, 16 Jan 2006, Perry E. Metzger wrote:
  |=20
  | >Elad Efrat <elad@NetBSD.org> writes:
  | >>Perry E. Metzger wrote:
  | >>
  | >>>Why? We can just move to more floppies.
  | >>
  | >>two is already one too many. ;)
  | >
  | >And what precisely does that mean?
  |=20
  | Since ./build.sh sets breaks fairly often because it doesn't fit in two
  | floppies, why isn't the number of floppies made dynamic? I'm sure it's
  | not that easy, but it would be an option.

It's quite trivial to support an arbitrary number of floppies in
the src/distrib/ framework.  Various platforms even support this.

The reason that the i386 floppy build has a 2 disk limit is because
we use the "2.88MB floppy emulation" method of booting CD-ROMs.
Thus, we can't just crank the size up arbitrarily because that
will break those images.

There has been work recently to support booting off a CD-ROM
that doesn't use this "2.88MB floppy emulation" mode.
Once that's in production (if it's not already), then we
can consider changing our "floppy" build mechanism to:
    a)	arbitrary number of floppies for real floppy boots.
    b)	single big file for CD-ROM and network boots, which
	may exceed 2x1.44MB floppies in size

(FWIW: I'm sure this has been explained numerous times in the past ...)


Luke.

--YwTTlJgQ7QoYB9ta
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (NetBSD)

iD8DBQFDzEE4pBhtmn8zJHIRAnRbAJ4/XtiDoFHfoQE6+fUvy/yVhWid6wCfQkmu
/2K610w4yt2zn7xgiNo/BG4=
=t/y2
-----END PGP SIGNATURE-----

--YwTTlJgQ7QoYB9ta--