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

Update outstanding items from 4.7-RC1.

Browse source
This commit is contained in:
Bruce A. Mah 2002-09-26 15:08:21 +00:00
parent e0d63bacc0
commit 771f1c0fa8
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/www/; revision=14390
1 changed files with 13 additions and 9 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

22
en/releases/4.7R/qa.sgml
View file

@ -1,6 +1,6 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" [
<!ENTITY base CDATA "../..">
<!ENTITY date "$FreeBSD: www/en/releases/4.7R/qa.sgml,v 1.4 2002/09/20 20:38:06 bmah Exp $">
<!ENTITY date "$FreeBSD: www/en/releases/4.7R/qa.sgml,v 1.5 2002/09/25 13:48:29 jhb Exp $">
<!ENTITY rel '4.7-RELEASE'>
<!ENTITY title "Testing Guide for &rel;">
<!ENTITY email "qa">
@ -97,16 +97,19 @@
<li>The 4.7-RC1 snapshots were built without packages due to some
problems (which only recently came to light) in the bzip2 package
support. The RE team is currently evaluating solutions; we are
planning to back to gzip packages for subsequent RC
snapshots (starting with 4.7-RC2), as well as the release.</li>
support. <em>Resolution:</em> The RE team decided to return to
gzip packages for 4.7-RC2 (as well as any subsequent RC snapshots
and the final release), thus allowing this snapshot to have its
normal package set.</li>
<li>Partially as a result of the above package problems, the ports
tree on the 4.7-RC1/i386 ISO image is not exactly the same as the
4.7-RC1/i386 FTP directory. Both will be eventually updated for
subsequent RC snapshots and the final release.</li>
subsequent RC snapshots and the final release.
<em>Resolution:</em> Not a factor for subsequent snapshots.</li>
<li>Loading kernel modules on 4.7-RC1/alpha is broken. A fix has
<li>Loading kernel modules on 4.7-RC1/alpha is broken.
<em>Resolution:</em> A fix has
been committed and will be present in 4.7-RC2/alpha.</li>
<li>When booting from the install media (e.g. a CDROM), sysinstall
@ -114,9 +117,10 @@
reason, sysinstall cannot load the module containing the aac
driver; this results in an error dialog when starting sysinstall.
Access to aac devices from within sysinstall is, understandably,
broken by this error. The RE team believes that this is due to a
dependency on the linux module; we intend to fix this problem,
but we still need to figure out how.</li>
broken by this error. This appears to be due to a
dependency on the linux module. <em>Resolution:</em> The aac driver was
brought back into the install kernels, and other modules were
moved to modules.</li>
</ul>