Date: Wed, 1 Nov 1995 02:42:01 +1100 From: Bruce Evans <bde@zeta.org.au> To: freebsd-bugs@freebsd.org, gwk@racer.dkrz.de Cc: jhk@time.cdrom.com Subject: Re: 951026-SNAP: second FBSD slice on a disk Message-ID: <199510311542.CAA22272@godzilla.zeta.org.au>
next in thread | raw e-mail | index | archive | help
>This pretty much proves that the "compatibility" partition which gets >mounted by the boot code ist the 'a' partition in the FBSD slice which >OCCURS FIRST in the slice table in the MBR. This slice does not need >to be located first in the data area. Do you agree? Yes. This behaviour was easiest to code :-), and more resistant to the compatibility slice changing when you create a new slice. >It would be real handy to automate what I have done in order to get >FBSD installed on a second slice. What about a new command in the >slice editor which allows you to DESIGNATE which slice should be the >compatibility slice? The program would only need to move that slice >to the first slot in the slice table, as I did manually with debug. >You would also need to keep the diskeditor from sorting the slices in >disk block order, of course. I don't want more dependencies on the compatibility slice. The thing you want to designate is the default boot slice. sysinstall will have to do something new to support this when the bootstrap supports it. Disk editors shouldn't sort the slice table unless requested to. It's unfortunate that changing the boot slice currently requires sorting.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199510311542.CAA22272>