Subject: Re: should sysinst change MBR_PTYPE_386BSD to MBR_PTYPE_NETBSD?
To: None <>
From: William Allen Simpson <>
List: tech-install
Date: 06/15/2003 14:12:58
On the question posed by the Subject, please don't change any type 

On a related question, please support the MBR_PTYPE and disklabel 
formats from OpenBSD.  

Likewise, support the MBR_TYPE and disklabel format for FreeBSD.

(I have several systems that I haven't upgraded from OpenBSD to NetBSD, 
because they have a lot of data on a second drive that I cannot read 
with NetBSD on the first drive.  If NetBSD can support MSDOS and Linux, 
it should be able to handle other *BSDs.)

"Perry E. Metzger" wrote:
> Frederick Bruckman <> writes:
> > I believe that you'd need a custom kernel without
> > COMPAT_386BSD_MBRPART to actually do that, though.
> > Why is that still on in GENERIC?
> To make it easier for people with the old MBR ID to boot a new
> kernel. Whether it is still needed is a matter for debate.
Let's debate.

 1) systinst is primarily for installing a "new" system. 

 2) new systems will have new MBR numbers.

 3) upgraders of old systems will be using the old-hand method 
    (mentioned below), and compiling their kernels the old way, and 
    thus can turn it on for the rare occasions it's needed.

 4) what we really need is an fstab that recogizes the version flavors 
    of file systems, all at the same time.  COMPAT_386BSD_MBRPART is 
    contrary to that expectation.

(OK, OK, I really do have the 25 diskettes for 386BSD 0.1 over there 
under the desk, covered with dust, but I haven't tried to load them in 
at least a decade.)

> > As long as there's an option to change the ID in sysinstall, it's
> > not needed.
> Not everyone uses sysinst to upgrade systems. I never do, for
> example. I just unpack a new kernel, reboot, and then unpack the sets...
Me Too.  I'm in favor eliminating the "upgrade" option from systinst, 
and better documenting the steps for upgrading by hand.  Especially now 
that the "new" etcupdate is available (that systinst never even solved).

What does the "upgrade" option offer that would not be solved by 
better documentation?

William Allen Simpson
    Key fingerprint =  17 40 5E 67 15 6F 31 26  DD 0D B9 9B 6A 15 2C 32