os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Move the i386 bootblock item to RC3. Remove the item about OpenSSH since

Browse source 
it appears not to affect RELENG_5_0.  Add two new items about sysinstall.
This commit is contained in:
Scott Long 2002-12-21 18:07:06 +00:00
parent 77f5d56690
commit dcb6318295
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/www/; revision=15401
1 changed files with 35 additions and 28 deletions
Download patch file Download diff file Expand all files Collapse all files

63
en/releases/5.0R/todo.sgml
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.117 2002/12/19 21:36:54 scottl Exp $">
<!ENTITY date "$FreeBSD: www/en/releases/5.0R/todo.sgml,v 1.118 2002/12/21 00:59:47 rwatson Exp $">
<!ENTITY title "FreeBSD 5.0 Open Issues">
<!ENTITY % includes SYSTEM "../../includes.sgml"> %includes;
<!ENTITY % developers SYSTEM "../../developers.sgml"> %developers;
@ -79,16 +79,6 @@
a mature configuration format.</td>
</tr>
<tr>
<td>KerberosV, OpenSSH, and PAM</td>
<td>In progress</td>
<td>&a.markm;, &a.des;, &a.nectar;</td>
<td>The KerberosV/PAM/OpenSSH issue is considered errata for
5.0-RELEASE due to the complexity of the fix; however, there
may now be other stability problems in the authentication
phase (see recent reports on freebsd-current).</td>
</tr>
<tr>
<td>Update Handbook for 5.0 installation</td>
<td>In progress</td>
@ -112,6 +102,40 @@
<code>-D_PTHREADS_INVARIANTS</code> compile flags in libc_r.</td>
</tr>
<tr>
<td>Teach sysinstall about rpcbind.</td>
<td>--</td>
<td>--</td>
<td>Need to convert references of portmap to rpcbind and add references
to rpc.lockd and rpc.statd</td>
</tr>
<tr>
<td>Investigate sysinstall problem reports</td>
<td>--</td>
<td>--</td>
<td>There are reported problems with sysinstall on i386 not working when
the user specifies something other that slice 1 during labeling. More
details are forthcoming.</td>
</tr>
<tr>
<td>UFS2 bootable on i386</td>
<td>Patch committed to HEAD; merge pending testing.</td>
<td>&a.imp;, &a.peter;</td>
<td>Support for booting UFS2 on non-64-bit platforms required an
increase in the size of the boot blocks due to the size of the
emulated 64-bit arithmetic instructions. In later revisions
of the boot code, we've managed to reduce that size, but as of
RC2, those changes had not been merged to the release branch.
As a result, in RC1 and RC2, UFS2 may only be used for non-root
file systems, not the root file system on 32-bit platforms. On
64-bit platforms, no such limit exists. We're currently
exploring merging the changes to the boot block to support UFS2
as the boot file system on all platforms.
</td>
</tr>
</table>
<h3>Must Resolve Issues for 5.0-RELEASE</h3>
@ -129,23 +153,6 @@
information.</td>
</tr>
<tr>
<td>UFS2 bootable on i386</td>
<td>Patch committed to HEAD; merge pending testing.</td>
<td>&a.phk;</td>
<td>Support for booting UFS2 on non-64-bit platforms required an
increase in the size of the boot blocks due to the size of the
emulated 64-bit arithmetic instructions. In later revisions
of the boot code, we've managed to reduce that size, but as of
RC2, those changes had not been merged to the release branch.
As a result, in RC1 and RC2, UFS2 may only be used for non-root
file systems, not the root file system on 32-bit platforms. On
64-bit platforms, no such limit exists. We're currently
exploring merging the changes to the boot block to support UFS2
as the boot file system on all platforms.
</td>
</tr>
</table>
<h3>Desired Features for 5.0-RELEASE</h3>