Add UFS2 boot issue to the required feature list for 5.0. Tentatively

assign ownership of this task to green@ and phk@ since they've both done
some work in this space.  Note that UFS2 boots fine on sparc64, the
problems seem to arise from a combination of large boot block issues
and emulated instruction problems on i386.
This commit is contained in:
Robert Watson 2002-09-30 15:37:10 +00:00
parent 51186f1b1b
commit 09c8d6bcd7
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/www/; revision=14432

View file

@ -1,7 +1,7 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" [
<!ENTITY base CDATA "../..">
<!ENTITY email 'freebsd-qa'>
<!ENTITY date "$FreeBSD: www/en/releases/5.0R/todo.sgml,v 1.4 2002/09/03 03:17:34 rwatson Exp $">
<!ENTITY date "$FreeBSD: www/en/releases/5.0R/todo.sgml,v 1.5 2002/09/30 15:33:04 rwatson Exp $">
<!ENTITY title "FreeBSD 5.0 Open Issues">
<!ENTITY % includes SYSTEM "../../includes.sgml"> %includes;
]>
@ -127,6 +127,20 @@
of the box.</td>
</tr>
<tr>
<td>UFS2 bootable on i386</td>
<td>In progress</td>
<td>green@FreeBSD.org, phk@FreeBSD.org</td>
<td>UFS2 can be successfully booted on sparc64, but on i386 the
emulated 64-bit instructions grow boot2 beyond the 8k traditionally
allocated for that boot loader. There appear to be some combination
of books in various bits of the boot loading mecahnism relating
to this (possibly including in the i386 emulated 64-bit instructions)
that must be resolved. In addition, the installation code now needs
to start leaving room for the larger boot blocks so that freshly
installed systems can be UFS2-bootable.</td>
</tr>
</table>
<h3>Desired Features for 5.0-RELEASE</h3>