On Mon, Jan 16, 2006 at 04:41:34PM -0800, Hisashi T Fujinaka wrote:
| On Mon, 16 Jan 2006, Perry E. Metzger wrote:
|
| >Elad Efrat <elad%NetBSD.org@localhost> 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?
|
| 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.
Attachment:
pgpHkdLrwDzTH.pgp
Description: PGP signature