> I notice that v1.10 is up in -current...does this patch still apply?
>
> Dennis
v1.10 is just a variation on this patch, with support for dynamic
configuration using boot0cfg(8) rather than by way of a build option.
For instance
boot0cfg -m 0xd da0
will cause the second partition to be ignored. (Needs boot0cfg.c v1.5
as well, though.)
RN
> At 06:58 PM 6/19/99 +0200, Robert Nordier wrote:
> >Dennis wrote:
> >
> >> F1: FreeBSD
> >> F2: LINUX
> >> F3: FreeBSD
> >>
> >> F3 is a non-bootable file system...is there a way to get the boot manager
> >> to only display F1 and F2?
> >
> >At the moment, no. Though you could use the following patch, which
> >allows the slices to be individually disabled. (The B0FLAGS setting in
> >Makefile enables slices 1 and 2; use B0FLAGS=0xf to enable all four
> >slices.)
> >
> >If worthwhile, boot0cfg(8) can later be modified to set/unset the
> >flags, rather than using a build option.
> >
> >Note that the patch is against boot0.s rev 1.9 committed yesterday.
> >
> >--
> >Robert Nordier
> >
> >
> >--- Makefile.orig Sat Jun 19 18:48:42 1999
> >+++ Makefile Sat Jun 19 18:43:07 1999
> >@@ -8,7 +8,7 @@
> >
> > M4?= m4
> >
> >-B0FLAGS=0x0
> >+B0FLAGS=0x3
> > B0TICKS=0xb6
> >
> > ORG= 0x600
> >--- boot0.s.orig Sat Jun 19 18:51:10 1999
> >+++ boot0.s Sat Jun 19 18:51:21 1999
> >@@ -71,6 +71,8 @@
> > movwir(partbl+0x4,_bx) # Partition table
> > xorl %edx,%edx # Item number
> > main.3: movbr1(_ch,-0x4,_bx_) # Zero active flag
> >+ btwr1(_dx,_FLAGS,_bp_) # Entry enabled?
> >+ jnc main.5 # No
> > movb0r(_bx_,_al) # Load type
> > movwir(tables,_di) # Lookup tables
> > movb $TBL0SZ,%cl # Number of entries
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message
