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

Move boot0cfg/fdisk item to testing, note some progress on the

Browse source 
sparc64 gdb problem, add a new item for fixes to sysinstall that
are similar to the work just done on boot0cfg/fdisk.
This commit is contained in:
Ken Smith 2005-08-17 18:06:55 +00:00
parent f28fbb8c43
commit 37ecebfc5a
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/www/; revision=25398
1 changed files with 25 additions and 12 deletions
Download patch file Download diff file Expand all files Collapse all files

37
en/releases/6.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/6.0R/todo.sgml,v 1.24 2005/08/16 08:23:37 rwatson Exp $">
<!ENTITY date "$FreeBSD: www/en/releases/6.0R/todo.sgml,v 1.25 2005/08/16 08:25:27 rwatson Exp $">
<!ENTITY title "FreeBSD 6.0 Open Issues">
<!ENTITY % includes SYSTEM "../../includes.sgml"> %includes;
<!ENTITY % developers SYSTEM "../../developers.sgml"> %developers;
@ -56,14 +56,6 @@
<th>Description</th>
</tr>
<tr>
<td>fdisk & boot0cfg</td>
<td>&status.wip;</td>
<td>&a.phk;</td>
<td>The boot0cfg and fdisk utilities need to be updated to use the proper
GEOM model for updating the boot sector of a mounted disk.</td>
</tr>
<tr>
<td>"snaplk" livelock</td>
<td>&status.wip;</td>
@ -218,10 +210,11 @@
<tr>
<td>kgdb on sparc64</td>
<td>&status.new;</td>
<td>&nbsp;</td>
<td>&status.wip;</td>
<td>&a.marcel;</td>
<td>It looks like kgdb is still broken on sparc64. It is better
than it used to be but still can't obtain a traceback.</td>
than it used to be but still can't obtain a traceback. A fix
was just committed to HEAD.</td>
</tr>
<tr>
@ -240,6 +233,18 @@
Once those are cleared, it will be a very desirable feature for 6.0.</td>
</tr>
<tr>
<td>update sysinstall disk labeling</td>
<td>&status.new;</td>
<td>&nbsp;</td>
<td>Sysinstall could use the same fixes recently made to fdisk so it
plays nice with GEOM and disk labeling. This doesn't cause problems
during install because nothing on the disk is mounted when its label
is being manipulated but it can cause problems if sysinstall gets
used on a live system to adjust labels on existing disks which
sys-admins tend to do.</td>
</tr>
</table>
<h3>Documentation items that must be resolved for 6.0</h3>
@ -348,6 +353,14 @@
This should be fixed but more testing would be good.</td>
</tr>
<tr>
<td>fdisk & boot0cfg</td>
<td>&status.untested;</td>
<td>&a.phk;</td>
<td>The boot0cfg and fdisk utilities need to be updated to use the proper
GEOM model for updating the boot sector of a mounted disk.</td>
</tr>
</table>
<h3>Stress Test Panics</h3>