From 99b1e62893e6575448b31dc0b1d4629a9e44d89a Mon Sep 17 00:00:00 2001 From: Poul-Henning Kamp Date: Tue, 22 Oct 2002 07:30:42 +0000 Subject: [PATCH] Update a couple of "my" items. --- en/releases/5.0R/todo.sgml | 25 +++++++++++++------------ 1 file changed, 13 insertions(+), 12 deletions(-) diff --git a/en/releases/5.0R/todo.sgml b/en/releases/5.0R/todo.sgml index cfdaac9a58..202ff23be3 100644 --- a/en/releases/5.0R/todo.sgml +++ b/en/releases/5.0R/todo.sgml @@ -1,7 +1,7 @@ - + %includes; ]> @@ -94,7 +94,7 @@ Switch to GEOM as default storage management framework - FreeBSD CVS HEAD: default now switched + Belived to be OK. phk@FreeBSD.org,sam@FreeBSD.orgMove to using GEOM in the GENERIC kernel as the default storage management framework, supporting out-of-the-box use of new partiton types, data transforms @@ -124,16 +124,17 @@ UFS2 bootable on i386 - In progress - green@FreeBSD.org, phk@FreeBSD.org - 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 mechanism 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. + In progress. We might want to miss on this one. + phk@FreeBSD.org + UFS2 can be successfully booted on sparc64, but on i386 + boot2 cannot fit in the space reserved in front of a UFS1 filesystem. + disklabel, libdisk, sysinstall and newfs needs to learn about this + wrinkle, and we need some makefile magic to build both UFS1 and + UFS1/2 boot2 boot files. + The potential for foot-shooting is very large, and phk@ currently + leans towards defaulting to UFS1 for root and boot, and UFS2 for + all other filesystems. +