===================================================================
RCS file: /cvsrepo/anoncvs/cvs/www/errata24.html,v
retrieving revision 1.58
retrieving revision 1.59
diff -u -r1.58 -r1.59
--- www/errata24.html	2014/03/31 03:12:47	1.58
+++ www/errata24.html	2014/03/31 03:36:54	1.59
@@ -75,43 +75,41 @@
 
 <hr>
 
-<a name="all"></a>
-<h3><font color="#e00000">All architectures</font></h3>
 <ul>
 <li><a name="bmap"></a>
-<font color="#009000"><strong>RELIABILITY FIX</strong></font><br>
+<font color="#009000"><strong>RELIABILITY FIX</strong></font> &nbsp; <i>All architectures</i><br>
 A local user can crash the system by reading a file larger than 64meg
 from an ext2fs partition.
 <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.4/common/bmap.patch">
 A source code patch exists which remedies this problem.</a>
 <p>
 <li><a name="lnpanic"></a>
-<font color="#009000"><strong>RELIABILITY FIX</strong></font><br>
+<font color="#009000"><strong>RELIABILITY FIX</strong></font> &nbsp; <i>All architectures</i><br>
 A local user can crash the system because of a bug in the vfs layer.
 <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.4/common/lnpanic.patch">
 A source code patch exists which remedies this problem.</a>
 <p>
 <li><a name="poll"></a>
-<font color="#009000"><strong>SECURITY FIX</strong></font><br>
+<font color="#009000"><strong>SECURITY FIX</strong></font> &nbsp; <i>All architectures</i><br>
 A machine crash is possible when playing with poll(2).
 <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.4/common/poll.patch">
 A source code patch exists which remedies this problem.</a>
 <p>
 <li><a name="nlink"></a>
-<font color="#009000"><strong>SECURITY FIX</strong></font><br>
+<font color="#009000"><strong>SECURITY FIX</strong></font> &nbsp; <i>All architectures</i><br>
 A machine crash is possible when playing with link(2) on FFS.
 <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.4/common/nlink.patch">
 A source code patch exists which remedies this problem.</a>
 This is version four of the patch.
 <p>
 <li><a name="ping"></a>
-<font color="#009000"><strong>SECURITY FIX</strong></font><br>
+<font color="#009000"><strong>SECURITY FIX</strong></font> &nbsp; <i>All architectures</i><br>
 A buffer overflow existed in ping(8), which may have a security issue.
 <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.4/common/ping.patch">
 A source code patch exists which remedies this problem.</a>
 <p>
 <li><a name="ipqrace"></a>
-<font color="#009000"><strong>SECURITY FIX</strong></font><br>
+<font color="#009000"><strong>SECURITY FIX</strong></font> &nbsp; <i>All architectures</i><br>
 A race condition in IP ipq handling could permit a remote crash.
 <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.4/common/ipqrace.patch">
 A source code patch exists which remedies this problem.</a>
@@ -119,40 +117,40 @@
 and <a href="errata24.html#tcpfix">the tcp decoding patch</a>.
 <p>
 <li><a name="accept"></a>
-<font color="#009000"><strong>SECURITY FIX</strong></font><br>
+<font color="#009000"><strong>SECURITY FIX</strong></font> &nbsp; <i>All architectures</i><br>
 A race condition existed between accept(2) and select(2) which could
 permit an attacker to hang sockets from remote.
 <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.4/common/accept.patch">
 A source code patch exists which remedies this problem.</a>
 <p>
 <li><a name="maxqueue"></a>
-<font color="#009000"><strong>SECURITY FIX</strong></font><br>
+<font color="#009000"><strong>SECURITY FIX</strong></font> &nbsp; <i>All architectures</i><br>
 IP fragment assembly can bog the machine excessively and cause problems.
 <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.4/common/maxqueue.patch">
 A source code patch exists which remedies this problem.</a>
 <p>
 <li><a name="uio"></a>
-<font color="#009000"><strong>FUNCTIONALITY FIX</strong></font><br>
+<font color="#009000"><strong>FUNCTIONALITY FIX</strong></font> &nbsp; <i>All architectures</i><br>
 The readv(2) and writev(2) system calls would not accept a <em>struct iovec</em>
 with an <strong>iov_len</strong> of 0.  This causes a db test in perl to fail.
 <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.4/common/uio.patch">
 A source code patch exists which remedies this problem.</a>
 <p>
 <li><a name="rst"></a>
-<font color="#009000"><strong>SECURITY FIX</strong></font><br>
+<font color="#009000"><strong>SECURITY FIX</strong></font> &nbsp; <i>All architectures</i><br>
 TCP/IP RST handling was too sloppy.
 <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.4/common/rst.patch">
 A source code patch exists which remedies this problem.</a>
 <p>
 <li><a name="kvm_mkdb"></a>
-<font color="#009000"><strong>FUNCTIONALITY FIX</strong></font><br>
+<font color="#009000"><strong>FUNCTIONALITY FIX</strong></font> &nbsp; <i>All architectures</i><br>
 During bootup, kvm_mkdb may exit with the error "kvm_mkdb: cannot allocate
 memory".
 <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.4/common/kvm_mkdb.patch">
 A source code patch exists which remedies this problem.</a>
 <p>
 <li><a name="nfs3_solaris7"></a>
-<font color="#009000"><strong>FUNCTIONALITY FIX</strong></font><br>
+<font color="#009000"><strong>FUNCTIONALITY FIX</strong></font> &nbsp; <i>All architectures</i><br>
 A problem with writing to NFS version 3 mounted filesystems from Solaris 7
 hosts exists.  Attempts to create files will result in an error such as
 "Inappropriate file type or format".
@@ -160,7 +158,7 @@
 A source code patch exists which remedies this problem.</a>
 <p>
 <li><a name="nfs3"></a>
-<font color="#009000"><strong>FUNCTIONALITY FIX</strong></font><br>
+<font color="#009000"><strong>FUNCTIONALITY FIX</strong></font> &nbsp; <i>All architectures</i><br>
 A problem with NFS version 3 mounts on big endian machines (m68k, sparc
 and powerpc) exists when mounting filesystems larger than 2gig.  You
 can see evidence of the bug by running df(1) and checking for negative
@@ -169,7 +167,7 @@
 A source code patch exists which remedies this problem.</a>
 <p>
 <li><a name="termcap"></a>
-<font color="#009000"><strong>SECURITY FIX</strong></font><br>
+<font color="#009000"><strong>SECURITY FIX</strong></font> &nbsp; <i>All architectures</i><br>
 A security problem exists in the curses and ocurses libraries that affect
 setuid programs linked with -lcurses or -locurses.
 <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.4/common/termcap.patch">
@@ -180,7 +178,7 @@
 platform.  Unpack it in /usr/lib.
 <p>
 <li><a name="terminfo"></a>
-<font color="#009000"><strong>FUNCTIONALITY FIX</strong></font><br>
+<font color="#009000"><strong>FUNCTIONALITY FIX</strong></font> &nbsp; <i>All architectures</i><br>
 A workaround for an xterm problem that causes <strong>vi</strong> to not
 restore the correct cursor position on exit.
 <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.4/common/terminfo.src.patch">
@@ -195,13 +193,13 @@
 big endian</a> version.
 <p>
 <li><a name="userdir"></a>
-<font color="#009000"><strong>FUNCTIONALITY FIX</strong></font><br>
+<font color="#009000"><strong>FUNCTIONALITY FIX</strong></font> &nbsp; <i>All architectures</i><br>
 <strong>userdir</strong> support was accidentally left out of httpd(8).
 <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.4/common/userdir.patch">
 A source code patch exists which remedies this problem.</a>
 <p>
 <li><a name="bootpd"></a>
-<font color="#009000"><strong>SECURITY FIX</strong></font><br>
+<font color="#009000"><strong>SECURITY FIX</strong></font> &nbsp; <i>All architectures</i><br>
 A remotely exploitable problem exists in bootpd(8).  bootpd is disabled
 by default, but some people may actually be using it.
 <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.4/common/bootpd.patch">
@@ -209,7 +207,7 @@
 This is the second version of the patch.
 <p>
 <li><a name="tcpfix"></a>
-<font color="#009000"><strong>SECURITY FIX</strong></font><br>
+<font color="#009000"><strong>SECURITY FIX</strong></font> &nbsp; <i>All architectures</i><br>
 A remote machine lockup problem exists in the TCP decoding code.
 <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.4/common/tcpfix.patch">
 A source code patch exists which remedies this problem.</a>