Subject: Re: not enough fragment space in bootcode
To: <>
From: David Laight <david@l8s.co.uk>
List: current-users
Date: 02/02/2003 19:40:34
> what does 'not enough fragment space in bootcode' mean?

That the i386 boot stuff is half brain-dead :-)

The i386 installboot has to grovel through the filesystem internals
and generate an array of sector_number:count pairs for /boot
so the code that loads it doesn't have to understand the file
system internal.  This probably seemed like a good idea at the
time it was written :-)

Recent changes have allowed the boot code to be larger, depending
on how the the filesystem allocates block the current array size
of 10 no longer seems to be large enough!

It is probably worth changing the default eg:

Index: bbinfo.h
===================================================================
RCS file: /cvsroot/src/sys/arch/i386/stand/lib/crt/bootsect/bbinfo.h,v
retrieving revision 1.3
diff -u -r1.3 bbinfo.h
--- bbinfo.h	1997/11/07 16:59:41	1.3
+++ bbinfo.h	2003/02/02 19:35:22
@@ -54,7 +54,7 @@
 
 /* only used by bootsect code (not by installboot) */
 #ifndef MAXFLENTRIES
-#define MAXFLENTRIES 10
+#define MAXFLENTRIES 20
 #endif
 #ifndef PRIM_LOADSZ
 #define PRIM_LOADSZ 15

Rather than the makefile(s) as that will force the items to be
rebuilt.

	David

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