For some five months now I'm trying to get you to fix the breakage
you introduced by changing the bootblocks to use booted
(rather than first) partition as root. Can you PLEASE finally
restore the former behaviour, or should I commit the simple
fix myself?

Jaromir

Index: main.c
===================================================================
RCS file: /cvsroot/src/sys/arch/i386/stand/biosboot/main.c,v
retrieving revision 1.31
diff -u -p -r1.31 main.c
--- main.c	2003/05/09 00:16:55	1.31
+++ main.c	2003/08/12 08:52:06
@@ -245,6 +245,7 @@ main(void)
 	/* try to set default device to what BIOS tells us */
 	bios2dev(boot_biosdev, &default_devname, &default_unit,
 		boot_biossector, &default_partition);
+	default_partition = 0;
 
 	/* if the user types "boot" without filename */
 	default_filename = DEFFILENAME;
Index: version
===================================================================
RCS file: /cvsroot/src/sys/arch/i386/stand/biosboot/version,v
retrieving revision 1.16
diff -u -p -r1.16 version
--- version	2003/02/01 14:48:17	1.16
+++ version	2003/08/12 08:52:07
@@ -30,3 +30,4 @@ is taken as the current.
 	Default partition to that passed in by mbr code
 	Support limited filename globbing in 'ls' command
 	Use .code16 and .code32 directives
+2.17:	Default partition back to first partition

David Laight wrote:
> None of them got changed after I modified the boot code :-)
> 
> If you setup multiple netbsd mbr partitions, you can boot with the
> root filesystem at the start of any on the partitions by using the mbr
> bootsel code.  Since there is only a single disklabel (anything else is
> far too fraught) the boot code scans the disklabel to locate the name
> of the partition that was booted.
> 
> The raid1 boot is a hack!  Consider what you would have to do to
> boot a striped raid volume.  The kernel would need to be in the non-raid
> boot filesystem and be told where it's root filesystem was (since it
> wouldn't be where the kernel came from).
> 
> The boot sequence doesn't (at the moment) support loading a kernel from
> other than the root partition (or rather it always tells the kernel that
> the root filesystem is where the kernel came from - which the kernel can
> ignore).
> 
> Raid1 can be made bootable, it isn't actually hard.
> 
> 	David
> 
> -- 
> David Laight: david@l8s.co.uk
> 

-- 
Jaromir Dolecek <jdolecek@NetBSD.org>            http://www.NetBSD.cz/
-=- We should be mindful of the potential goal, but as the tantric    -=-
-=- Buddhist masters say, ``You may notice during meditation that you -=-
-=- sometimes levitate or glow.   Do not let this distract you.''     -=-