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

Update for progress with package issue, note aac problems from within

Browse source 
sysinstall.
This commit is contained in:
Bruce A. Mah 2002-09-20 20:38:06 +00:00
parent 3e6b7e71ad
commit 4b077bd106
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/www/; revision=14334
1 changed files with 13 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

17
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.2 2002/09/06 00:31:47 bmah Exp $">
<!ENTITY date "$FreeBSD: www/en/releases/4.7R/qa.sgml,v 1.3 2002/09/19 15:47:59 bmah Exp $">
<!ENTITY rel '4.7-RELEASE'>
<!ENTITY title "Testing Guide for &rel;">
<!ENTITY email "qa">
@ -94,9 +94,9 @@
<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; one
alternative is to go back to gzip packages for subsequent RC
snapshots, as well as the release.</li>
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>
<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
@ -106,6 +106,15 @@
<li>Loading kernel modules on 4.7-RC1/alpha is broken. 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
tries to load a set of modules from the mfsroot image. For some
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>
</ul>
&footer;