This file contains post-release ERRATA for 2.2.5 and should always
be considered the definitive place to look *first* before reporting
a problem with this release.  This file will also be periodically
updated as new issues are reported so even if you've checked this
file recently, check it again before filing a bug report.  Any
changes to this file are also automatically emailed to:

	freebsd-stable@freebsd.org

For 2.2.5 security advisories, see:

	ftp://freebsd.org/pub/CERT/

For the latest information (note the URL carefully - this is NOT
ftp.freebsd.org).

---- Security Advisories:

Current active security advisories for 2.2.5:	One

o FreeBSD-SA-97:05 (available from ftp://freebsd.org/pub/CERT/) -
  security compromise via open().  Patches available in
  ftp://freebsd.org/pub/CERT/patches/SA-97:05/

  You may also simply remove /dev/io as a quick work-around if you're
  not running an X server or some other specialized utility which
  requires access to the I/O instructions.
 
---- System Update Information:

o The appletalk stack was broken in 2.2.5 and, if you plan to run
  appletalk, you should apply the following patch:

  ftp://ftp.freebsd.org/pub/FreeBSD/2.2.5-RELEASE/updates/atalk.diff.2.2

o The line printer spooler lpd will, when sending jobs to remote
  printers, kill the child process sending to the remote after the
  timeout specified in the `ct' capability (2 minutes by default).
  For a fix, please upgrade the lpd subsystem to 2.2-stable.  As a
  workaround, increase the `ct' capability to an unreasonably large
  number of seconds (like 3600).

o Intel "F00F bug" enables users to hang machines with Pentium processors
  if they have access to the machine and can execute programs.
  
Fix:  Update to the 2.2-stable version of the kernel or apply the patch
      found in: 
      
      ftp://ftp.freebsd.org/pub/FreeBSD/2.2.5-RELEASE/updates/f00f.diff.2.2

o A bug in the ipfw code exists where using the "reset tcp" firewall command
  causes the kernel to write ethernet headers onto random kernel stack
  locations. 

Fix:    Update to the 2.2-stable version of the kernel or apply the
        patch found in ftp://ftp.freebsd.org/pub/FreeBSD/2.2.5-RELEASE/updates/ipfw.diff
	
o A bug in XF86Setup causes it to fail to create a symbolic link from
  /usr/X11R6/bin/X to the right X server for your hardware if a link
  does not already exist.  When you type startx the following error is
  displayed:
  
  xinit:  No such file or directory (errno 2):  no server "X" found in PATH
  
Fix:	Execute the following commands (as root) and re-run XF86Setup.

	# cd /usr/X11R6/bin
	# ln -s XF86_VGA16 X
	
	If XF86Setup asks you if you want to use the existing XF86Config for
	defaults choose no.  When it asks you if you want to create an 'X'
	link to the server choose yes.