From Axel.Thimm at ATrpms.net Sat Jul 1 09:17:21 2006 From: Axel.Thimm at ATrpms.net (Axel Thimm) Date: Sat, 1 Jul 2006 11:17:21 +0200 Subject: Disttags for FL (was: Upgrade path consistency among all Fedora Projects) In-Reply-To: <44A62B12.2040801@gtw.net> References: <44A62B12.2040801@gtw.net> Message-ID: <20060701091721.GB15707@neu.nirvana> On Sat, Jul 01, 2006 at 02:58:10AM -0500, David D. Eisenstein wrote: > Have a quick question for you, Tom. Is there a methodolgy in place > already for how Core and/or Extras packages are to be versioned in the > "Release:" part of the packages' .spec files? I am thinking that if > there is such, then we in Legacy will need to follow that and revise our > package numbering guidelines > (current: ) > to follow it from now on. If no such methodology is used or mandated, > then does numbering of the "Release:" tag needs to be codified among all > Fedora projects? > > I look forward to your answer, Tom. Thanks! -David > > ps: How may I participate in the Packaging group? > I'll try to answer on the questions raised to Tom: The (now common to both core and extras) Fedora Packaging Guidelines http://www.fedoraproject.org/wiki/Packaging/Guidelines don't yet explicitely mention the usage of (the optional) disttags http://www.fedoraproject.org/wiki/DistTag but they are in common use throughout extras and will hopefully make their way to core soon. But note that the disttags used here for rhlX would generate broken upgrade paths ("rhl" > "fc"). These are very early suggestions and since extras started with FC3 it never became an actual issue, but if FL is seeking for following the packaging guidelines including disttags taking this implementation would be wrong. If there is interest in FL to introduce and use disttags before RH7.,3 and RH9 are EOL'd, RHL7.3 and RH9 would need to get disttags < fcX. Examples stated in the past were "RHL7.3" or "fc0.7.3" (upper case is less than lower case and RHL would be considered like subversions of FC0). I would vote for the first version (even though it looks like fortran/shouting) as fc0.7.3 will probably confuse end users. You can get involved with the packaging group (if you mean the newly created packaging committee) by subscribing to fedora-packaging and visiting the IRC meetings on Thursdays 16:00 UTC. Jesse Keating is also on board so there. -- Axel.Thimm at ATrpms.net -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From jkeating at j2solutions.net Sat Jul 1 12:44:23 2006 From: jkeating at j2solutions.net (Jesse Keating) Date: Sat, 1 Jul 2006 08:44:23 -0400 Subject: Disttags for FL (was: Upgrade path consistency among all Fedora Projects) In-Reply-To: <20060701091721.GB15707@neu.nirvana> References: <44A62B12.2040801@gtw.net> <20060701091721.GB15707@neu.nirvana> Message-ID: <200607010844.27291.jkeating@j2solutions.net> On Saturday 01 July 2006 05:17, Axel Thimm wrote: > If there is interest in FL to introduce and use disttags before RH7.,3 > and RH9 are EOL'd, RHL7.3 and RH9 would need to get disttags < fcX. > Examples stated in the past were "RHL7.3" or "fc0.7.3" (upper case is > less than lower case and RHL would be considered like subversions of > FC0). I would vote for the first version (even though it looks like > fortran/shouting) as fc0.7.3 will probably confuse end users. At this time Fedora Legacy doesn't have an interest in introducing the %{?dist} tag to packages that didn't already have it. This means no RHL packages. In fact, RHL is hopefully going to be phased out of Legacy support in about 6 months. Our current build system does not support dist tags, however when we move to the Fedora infrastructure instead of our own we will gain that ability, and we will use the same dist tag that was appropriate for said releases during the time they were active. FC3 .fc3, FC4 .fc4, etc... -- Jesse Keating RHCE (geek.j2solutions.net) Fedora Legacy Team (www.fedoralegacy.org) GPG Public Key (geek.j2solutions.net/jkeating.j2solutions.pub) -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From sheltren at cs.ucsb.edu Sat Jul 1 13:50:37 2006 From: sheltren at cs.ucsb.edu (Jeff Sheltren) Date: Sat, 1 Jul 2006 09:50:37 -0400 Subject: Disttags for FL (was: Upgrade path consistency among all Fedora Projects) In-Reply-To: <200607010844.27291.jkeating@j2solutions.net> References: <44A62B12.2040801@gtw.net> <20060701091721.GB15707@neu.nirvana> <200607010844.27291.jkeating@j2solutions.net> Message-ID: <30558C48-1391-4785-AAAB-6ADC34E7C4F9@cs.ucsb.edu> On Jul 1, 2006, at 8:44 AM, Jesse Keating wrote: > > At this time Fedora Legacy doesn't have an interest in introducing > the %{?dist} tag to packages that didn't already have it. This > means no RHL > packages. In fact, RHL is hopefully going to be phased out of > Legacy support > in about 6 months. > > Our current build system does not support dist tags, however when > we move to > the Fedora infrastructure instead of our own we will gain that > ability, and > we will use the same dist tag that was appropriate for said > releases during > the time they were active. FC3 .fc3, FC4 .fc4, etc... > Jesse, yes our system does support %dist tags. We could also easily use them for RHL releases, but I agree that it's not really worth it since we are planning to stop supporting those very soon. -Jeff From jkeating at j2solutions.net Sat Jul 1 13:56:15 2006 From: jkeating at j2solutions.net (Jesse Keating) Date: Sat, 1 Jul 2006 09:56:15 -0400 Subject: Disttags for FL (was: Upgrade path consistency among all Fedora Projects) In-Reply-To: <30558C48-1391-4785-AAAB-6ADC34E7C4F9@cs.ucsb.edu> References: <44A62B12.2040801@gtw.net> <200607010844.27291.jkeating@j2solutions.net> <30558C48-1391-4785-AAAB-6ADC34E7C4F9@cs.ucsb.edu> Message-ID: <200607010956.18643.jkeating@j2solutions.net> On Saturday 01 July 2006 09:50, Jeff Sheltren wrote: > Jesse, yes our system does support %dist tags. ?We could also easily ? > use them for RHL releases, but I agree that it's not really worth it ? > since we are planning to stop supporting those very soon. Do we have buildsys-macros in the buildroots? I was thinking our make files don't support them, but then I realized we aren't using any make files in any kind of CVS (: The real solution here is to move to the Fedora infrastructure. /me posts another email to infrastructure list asking for a cvs tree. -- Jesse Keating RHCE (geek.j2solutions.net) Fedora Legacy Team (www.fedoralegacy.org) GPG Public Key (geek.j2solutions.net/jkeating.j2solutions.pub) -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From sheltren at cs.ucsb.edu Sat Jul 1 14:27:39 2006 From: sheltren at cs.ucsb.edu (Jeff Sheltren) Date: Sat, 1 Jul 2006 10:27:39 -0400 Subject: Disttags for FL (was: Upgrade path consistency among all Fedora Projects) In-Reply-To: <200607010956.18643.jkeating@j2solutions.net> References: <44A62B12.2040801@gtw.net> <200607010844.27291.jkeating@j2solutions.net> <30558C48-1391-4785-AAAB-6ADC34E7C4F9@cs.ucsb.edu> <200607010956.18643.jkeating@j2solutions.net> Message-ID: <53311350-D63F-4270-A845-33A0309AF236@cs.ucsb.edu> On Jul 1, 2006, at 9:56 AM, Jesse Keating wrote: > > Do we have buildsys-macros in the buildroots? We do, at least for the fedora releases. > > I was thinking our make files don't support them, but then I > realized we > aren't using any make files in any kind of CVS (: > > The real solution here is to move to the Fedora infrastructure. / > me posts > another email to infrastructure list asking for a cvs tree. Agreed :) Thanks for working on this. -Jeff From deisenst at gtw.net Tue Jul 4 07:33:00 2006 From: deisenst at gtw.net (David D. Eisenstein) Date: Tue, 04 Jul 2006 02:33:00 -0500 Subject: "fedoralegacy.org" not resolving Message-ID: <44AA19AC.5090408@gtw.net> Looks like all the name-servers for fedoralegacy.org are down or something. Looks like there are multiple problems with the domain. See: for the gory details. -David From mattdm at mattdm.org Tue Jul 4 14:28:15 2006 From: mattdm at mattdm.org (Matthew Miller) Date: Tue, 4 Jul 2006 10:28:15 -0400 Subject: "fedoralegacy.org" not resolving In-Reply-To: <44AA19AC.5090408@gtw.net> References: <44AA19AC.5090408@gtw.net> Message-ID: <20060704142815.GA19083@jadzia.bu.edu> On Tue, Jul 04, 2006 at 02:33:00AM -0500, David D. Eisenstein wrote: > Looks like all the name-servers for fedoralegacy.org are down or something. > Looks like there are multiple problems with the domain. May be related to: -- Matthew Miller mattdm at mattdm.org Boston University Linux ------> From sheltren at cs.ucsb.edu Wed Jul 5 23:55:58 2006 From: sheltren at cs.ucsb.edu (Jeff Sheltren) Date: Wed, 5 Jul 2006 19:55:58 -0400 Subject: Fedora Core 4 coming . . . sunset, infrastructure issues . . . meeting? In-Reply-To: <44A30786.3070508@gtw.net> References: <44A30786.3070508@gtw.net> Message-ID: <859EB3E2-2032-49D2-9940-344C622A1EDA@cs.ucsb.edu> On Jun 28, 2006, at 6:49 PM, David Eisenstein wrote: > > I will likely not be available the rest of this week, and next > Monday and > Tuesday are holiday evenings in the United States of America. > Shall we > shoot for an meeting on IRC mid-week next week? If we meet on > Wednesday, > July 7th, that will leave us 12 calendar days to get stuff done > between > that meeting and the time we are due to inherit Fedora Core 4. > > Has a meeting time been finalized yet - or has a meeting happened and I just missed it? Also, I just realized that Wednesday (today) isn't the 7th, it's the 5th... -Jeff From marcdeslauriers at videotron.ca Thu Jul 6 02:30:17 2006 From: marcdeslauriers at videotron.ca (Marc Deslauriers) Date: Wed, 05 Jul 2006 22:30:17 -0400 Subject: Fedora Legacy Test Update Notification: php Message-ID: <44AC75B9.90907@videotron.ca> --------------------------------------------------------------------- Fedora Legacy Test Update Notification FEDORALEGACY-2006-175040 Bugzilla https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=175040 2006-07-05 --------------------------------------------------------------------- Name : php Versions : rh73: php-4.1.2-7.3.20.legacy Versions : rh9: php-4.2.2-17.21.legacy Versions : fc1: php-4.3.11-1.fc1.6.legacy Versions : fc2: php-4.3.11-1.fc2.7.legacy Versions : fc3: php-4.3.11-2.8.4.legacy Summary : The PHP HTML-embedded scripting language. Description : PHP is an HTML-embedded scripting language. PHP attempts to make it easy for developers to write dynamically generated webpages. PHP also offers built-in database integration for several commercial and non-commercial database management systems, so writing a database-enabled webpage with PHP is fairly simple. The most common use of PHP coding is probably as a replacement for CGI scripts. The mod_php module enables the Apache Web server to understand and process the embedded PHP language in Web pages. --------------------------------------------------------------------- Update Information: Updated PHP packages that fix multiple security issues are now available. PHP is an HTML-embedded scripting language commonly used with the Apache HTTP Web server. A buffer overflow flaw was discovered in uw-imap, the University of Washington's IMAP Server. php-imap is compiled against the static c-client libraries from imap and therefore needed to be recompiled against the fixed version. (CVE-2005-2933). An input validation error was found in the "mb_send_mail()" function. An attacker could use this flaw to inject arbitrary headers in a mail sent via a script calling the "mb_send_mail()" function where the "To" parameter can be controlled by the attacker. (CVE-2005-3883) The error handling output was found to not properly escape HTML output in certain cases. An attacker could use this flaw to perform cross-site scripting attacks against sites where both display_errors and html_errors are enabled. (CVE-2006-0208) The phpinfo() PHP function did not properly sanitize long strings. An attacker could use this to perform cross-site scripting attacks against sites that have publicly-available PHP scripts that call phpinfo(). (CVE-2006-0996) The html_entity_decode() PHP function was found to not be binary safe. An attacker could use this flaw to disclose a certain part of the memory. In order for this issue to be exploitable the target site would need to have a PHP script which called the "html_entity_decode()" function with untrusted input from the user and displayed the result. (CVE-2006-1490) The wordwrap() PHP function did not properly check for integer overflow in the handling of the "break" parameter. An attacker who could control the string passed to the "break" parameter could cause a heap overflow. (CVE-2006-1990) Users of PHP should upgrade to these updated packages, which contain backported patches that resolve these issues. --------------------------------------------------------------------- Changelogs rh73: * Thu Jun 15 2006 Marc Deslauriers 4.1.2-7.3.20.legacy - replaced CVE-2006-0996 and CVE-2006-0208 patches with the ones from RHEL21 - prevent integer overflow in wordwrap (CVE-2006-1990) * Sat Apr 29 2006 Marc Deslauriers 4.1.2-7.3.19.legacy - add fix for imap DoS (#175040) - add security fix for new phpinfo XSS (CVE-2006-0996) - add security fix for XSS issues in "html_errors" mode (CVE-2006-0208) - add security fix for mbstring header validation (CVE-2005-3383) rh9: * Sat Jun 24 2006 Marc Deslauriers 4.2.2-17.21.legacy - replaced CVE-2006-0208 patch with the one from RHEL21 - prevent integer overflow in wordwrap (CVE-2006-1990) * Sat Apr 29 2006 Marc Deslauriers 4.2.2-17.20.legacy - removed TSRMLS_CC from CVE-2006-0996 patch * Sat Apr 29 2006 Marc Deslauriers 4.2.2-17.19.legacy - add fix for imap DoS (#175040) * Fri Apr 28 2006 Marc Deslauriers 4.2.2-17.18.legacy - add security fix for new phpinfo XSS (CVE-2006-0996) - add security fix for XSS issues in "html_errors" mode (CVE-2006-0208) - add security fix for mbstring header validation (CVE-2005-3383) fc1: * Wed Jun 14 2006 Marc Deslauriers 4.3.11-1.fc1.6.legacy - prevent integer overflow in wordwrap (CVE-2006-1990) * Sun Apr 30 2006 Marc Deslauriers 4.3.11-1.fc1.5.legacy - remove TSRMLS_CC from CVE-2006-0996 patch * Thu Apr 27 2006 Marc Deslauriers 4.3.11-1.fc1.4.legacy - add security fix for new phpinfo XSS (CVE-2006-0996) - add binary safeness fix for php_unescape_html_entities (CVE-2006-1490) - add security fix for XSS issues in "html_errors" mode (CVE-2006-0208) - add security fix for mbstring header validation (CVE-2005-3383) fc2: * Tue Jun 13 2006 Marc Deslauriers 4.3.11-1.fc2.7.legacy - prevent integer overflow in wordwrap (CVE-2006-1990) * Sun Apr 30 2006 Marc Deslauriers 4.3.11-1.fc2.6.legacy - removed TSRMLS_CC from CVE-2006-0996 patch * Wed Apr 26 2006 Marc Deslauriers 4.3.11-1.fc2.5.legacy - add security fix for new phpinfo XSS (CVE-2006-0996) - add binary safeness fix for php_unescape_html_entities (CVE-2006-1490) - add security fix for XSS issues in "html_errors" mode (CVE-2006-0208) - add security fix for mbstring header validation (CVE-2005-3383) fc3: * Tue Jul 04 2006 Marc Deslauriers 4.3.11-2.8.4.legacy - added sendmail, w3c-libwww-devel, flex and gnupg to BuildRequires * Wed Jun 14 2006 Marc Deslauriers 4.3.11-2.8.3.legacy - prevent integer overflow in wordwrap (CVE-2006-1990) * Sun Apr 30 2006 Marc Deslauriers 4.3.11-2.8.2.legacy - removed TSRMLS_CC from CVE-2006-0996 patch * Wed Apr 26 2006 Marc Deslauriers 4.3.11-2.8.1.legacy - add security fix for new phpinfo XSS (CVE-2006-0996) - add binary safeness fix for php_unescape_html_entities (CVE-2006-1490) - add security fix for XSS issues in "html_errors" mode (CVE-2006-0208) - add security fix for mbstring header validation (CVE-2005-3383) --------------------------------------------------------------------- This update can be downloaded from: http://download.fedoralegacy.org/ (sha1sums) rh73: 716216fdf1ddc42bb8d210d1e121ba8d0e7f4d7c redhat/7.3/updates-testing/i386/php-4.1.2-7.3.20.legacy.i386.rpm 61612a0c2e6244ccfb4e35ea04865d48f75f7c48 redhat/7.3/updates-testing/i386/php-devel-4.1.2-7.3.20.legacy.i386.rpm d29efdfdd669875715c0956fedc59b99ef7681f3 redhat/7.3/updates-testing/i386/php-imap-4.1.2-7.3.20.legacy.i386.rpm 1e09ae807ccf160ef9011818d4dda590bab224d7 redhat/7.3/updates-testing/i386/php-ldap-4.1.2-7.3.20.legacy.i386.rpm 0dfa25adffe75db47fbf2a366eb456d8fcfca918 redhat/7.3/updates-testing/i386/php-manual-4.1.2-7.3.20.legacy.i386.rpm 9141e782d32739b5bc2a9b611d7cdc352e523c26 redhat/7.3/updates-testing/i386/php-mysql-4.1.2-7.3.20.legacy.i386.rpm f1e88cf8e7f644f81473efc561f4df502ef7bc24 redhat/7.3/updates-testing/i386/php-odbc-4.1.2-7.3.20.legacy.i386.rpm dd58b7187e116874558c5567b8c6897d1d1d4154 redhat/7.3/updates-testing/i386/php-pgsql-4.1.2-7.3.20.legacy.i386.rpm 0575467b89a44d1e5b0bebc00fac018666a8b827 redhat/7.3/updates-testing/i386/php-snmp-4.1.2-7.3.20.legacy.i386.rpm 8541c7eefbf6162eeca5f12f834ccf3af8fee85b redhat/7.3/updates-testing/SRPMS/php-4.1.2-7.3.20.legacy.src.rpm rh9: 1cd4a11bf52c1b18dce2937a7f15789b059c1967 redhat/9/updates-testing/i386/php-4.2.2-17.21.legacy.i386.rpm 109a96dc0633b661e6789d9b41a3cf298e140401 redhat/9/updates-testing/i386/php-devel-4.2.2-17.21.legacy.i386.rpm f5df6f259745f0050c15a50b75e2114381c07fb1 redhat/9/updates-testing/i386/php-imap-4.2.2-17.21.legacy.i386.rpm 8223f6cc4e84478523cd8560bdc9b75d90c33a14 redhat/9/updates-testing/i386/php-ldap-4.2.2-17.21.legacy.i386.rpm 18ac761d897ba89e94086facdb7b529e7d60c0e2 redhat/9/updates-testing/i386/php-manual-4.2.2-17.21.legacy.i386.rpm 714057b386abaa03573d14c8757ef97858ba2b17 redhat/9/updates-testing/i386/php-mysql-4.2.2-17.21.legacy.i386.rpm c2002f4f520ea2f7dbe11402ad460a181c44175a redhat/9/updates-testing/i386/php-odbc-4.2.2-17.21.legacy.i386.rpm 26a858731e032c0622003c8d9398a6b5ead86b24 redhat/9/updates-testing/i386/php-pgsql-4.2.2-17.21.legacy.i386.rpm 258887bd3e690dad1b88dfcbc280a8523fa52338 redhat/9/updates-testing/i386/php-snmp-4.2.2-17.21.legacy.i386.rpm fe815ab1d505fcef7629e0abe4b25f2c66054f1c redhat/9/updates-testing/SRPMS/php-4.2.2-17.21.legacy.src.rpm fc1: 5cc63a63de0057797737ceefbdfeb0f466d87beb fedora/1/updates-testing/i386/php-4.3.11-1.fc1.6.legacy.i386.rpm 315b0ae174f33d437178982f47dd24ba48848346 fedora/1/updates-testing/i386/php-devel-4.3.11-1.fc1.6.legacy.i386.rpm 92d36fe3e062b33e6b22bcd101dd85dc03803616 fedora/1/updates-testing/i386/php-domxml-4.3.11-1.fc1.6.legacy.i386.rpm 7083eb87cdcb9e83ef83e6ba7aee63a2a259ce89 fedora/1/updates-testing/i386/php-imap-4.3.11-1.fc1.6.legacy.i386.rpm acb18926452c2faf331fc8b25a09de3f4da2d7cb fedora/1/updates-testing/i386/php-ldap-4.3.11-1.fc1.6.legacy.i386.rpm c90c744840ebff6c9149b9df9513db63a10a6247 fedora/1/updates-testing/i386/php-mbstring-4.3.11-1.fc1.6.legacy.i386.rpm e84b242476b61b0aa19b2b71af4f69043cc4ecee fedora/1/updates-testing/i386/php-mysql-4.3.11-1.fc1.6.legacy.i386.rpm a765f1e3d73d9d5cbd1fb5cbfb868f70baf2ce4a fedora/1/updates-testing/i386/php-odbc-4.3.11-1.fc1.6.legacy.i386.rpm 0ef956e24befd3a9b462f0953edc164595ac27cf fedora/1/updates-testing/i386/php-pgsql-4.3.11-1.fc1.6.legacy.i386.rpm e5e9f011f9d403881a9350d5395db6ccaa402b6a fedora/1/updates-testing/i386/php-snmp-4.3.11-1.fc1.6.legacy.i386.rpm f29d6f88cd780e32e9307c1d8ad8446e559c8a29 fedora/1/updates-testing/i386/php-xmlrpc-4.3.11-1.fc1.6.legacy.i386.rpm edbf95d5ea4944e3a41ccebcebaf2702b4545f98 fedora/1/updates-testing/SRPMS/php-4.3.11-1.fc1.6.legacy.src.rpm fc2: f2ec94d1069ff3214ac031f7f5c6a1e29f22e90d fedora/2/updates-testing/i386/php-4.3.11-1.fc2.7.legacy.i386.rpm 34c8d44ccd71a3f09dc289d4f0fc826dc34f9a60 fedora/2/updates-testing/i386/php-devel-4.3.11-1.fc2.7.legacy.i386.rpm 09d8100aea583b0b47f87190b6a557ed3f7e3636 fedora/2/updates-testing/i386/php-domxml-4.3.11-1.fc2.7.legacy.i386.rpm f11bc7846717d98b73e73d9bf9870b2f5e19d341 fedora/2/updates-testing/i386/php-imap-4.3.11-1.fc2.7.legacy.i386.rpm 69d11e09f15a6acb488a28a8e4751f468e332c73 fedora/2/updates-testing/i386/php-ldap-4.3.11-1.fc2.7.legacy.i386.rpm a07b390dc004d6a330c49cf1e8262471c93e9108 fedora/2/updates-testing/i386/php-mbstring-4.3.11-1.fc2.7.legacy.i386.rpm 2820fb1d8832d034b2529ec7087c5839baebccfe fedora/2/updates-testing/i386/php-mysql-4.3.11-1.fc2.7.legacy.i386.rpm ed69c77a9e312348a6ca73ad2d7f270459bc16dc fedora/2/updates-testing/i386/php-odbc-4.3.11-1.fc2.7.legacy.i386.rpm 5ff64a9b70c418ce762ff815be8fcefb5aa89d15 fedora/2/updates-testing/i386/php-pear-4.3.11-1.fc2.7.legacy.i386.rpm 9251da041356734713a644ff778ae4afc2ab2879 fedora/2/updates-testing/i386/php-pgsql-4.3.11-1.fc2.7.legacy.i386.rpm eabd9dd422934c99902429c311f61a4a4a26e3c7 fedora/2/updates-testing/i386/php-snmp-4.3.11-1.fc2.7.legacy.i386.rpm 7b027d1cd8844312ed20711bef92013078e33b83 fedora/2/updates-testing/i386/php-xmlrpc-4.3.11-1.fc2.7.legacy.i386.rpm 026b3dd063586fe6e29f6cb482206e4f5631ac0f fedora/2/updates-testing/SRPMS/php-4.3.11-1.fc2.7.legacy.src.rpm fc3: cafefc39811f7923007e522aa5ca84a0e073dd96 fedora/3/updates-testing/i386/php-4.3.11-2.8.4.legacy.i386.rpm e2d84ad62c2703b5a7f3875d0d52e9461f5f81fe fedora/3/updates-testing/i386/php-devel-4.3.11-2.8.4.legacy.i386.rpm 7b90726025ff13e815509216a73fa9c2914a6ad0 fedora/3/updates-testing/i386/php-domxml-4.3.11-2.8.4.legacy.i386.rpm 6367004e4200fcb44778088c911495458b08cde4 fedora/3/updates-testing/i386/php-gd-4.3.11-2.8.4.legacy.i386.rpm abb3cdd3dcc030b85e03a409372daac6093a63d0 fedora/3/updates-testing/i386/php-imap-4.3.11-2.8.4.legacy.i386.rpm df673e8e983ea6cec3b50f65e50950f625493223 fedora/3/updates-testing/i386/php-ldap-4.3.11-2.8.4.legacy.i386.rpm 4e95b2f44661683fd17c72f881323f36757793ef fedora/3/updates-testing/i386/php-mbstring-4.3.11-2.8.4.legacy.i386.rpm a891c751c82acc9bf1cc6ac59332196344b42a8c fedora/3/updates-testing/i386/php-mysql-4.3.11-2.8.4.legacy.i386.rpm 865dde39429ac6fc59296af9ed938c4e7b30216c fedora/3/updates-testing/i386/php-ncurses-4.3.11-2.8.4.legacy.i386.rpm 32b5075e4e3406c4ab9715ef970f1e5ec4f808e3 fedora/3/updates-testing/i386/php-odbc-4.3.11-2.8.4.legacy.i386.rpm 5867c11e75d26edbcd79e815bc79a1c2354878ec fedora/3/updates-testing/i386/php-pear-4.3.11-2.8.4.legacy.i386.rpm 5f05fae3bc0ef2841ed479cb5968443fee448698 fedora/3/updates-testing/i386/php-pgsql-4.3.11-2.8.4.legacy.i386.rpm 71591b13628f0db7a0818c9bb818b63e176c9904 fedora/3/updates-testing/i386/php-snmp-4.3.11-2.8.4.legacy.i386.rpm c5f9dcb4c6e8bc117b88ffa06a60049a80f68287 fedora/3/updates-testing/i386/php-xmlrpc-4.3.11-2.8.4.legacy.i386.rpm 78fb1d65369f96b86027bc04e91d2c058fbd1e73 fedora/3/updates-testing/x86_64/php-4.3.11-2.8.4.legacy.x86_64.rpm 102f14f60d3dc134cb6f698f6d4d1f4264006940 fedora/3/updates-testing/x86_64/php-devel-4.3.11-2.8.4.legacy.x86_64.rpm 333d7213daf29f486ad7e047e1adc418c3258500 fedora/3/updates-testing/x86_64/php-domxml-4.3.11-2.8.4.legacy.x86_64.rpm 59c18b269a3a1712684d8fab00c7577033ac2108 fedora/3/updates-testing/x86_64/php-gd-4.3.11-2.8.4.legacy.x86_64.rpm ce155d28b0e81eb5527cf0e2f496bc8a9e5ce75d fedora/3/updates-testing/x86_64/php-imap-4.3.11-2.8.4.legacy.x86_64.rpm 39e63584c3419002a43d71973ff93a356fc278c0 fedora/3/updates-testing/x86_64/php-ldap-4.3.11-2.8.4.legacy.x86_64.rpm b5131dae7d6908114b959d3ab0e1661158e66e0f fedora/3/updates-testing/x86_64/php-mbstring-4.3.11-2.8.4.legacy.x86_64.rpm 5b366cf0918e314c52e2da44baac70c81dd6fa38 fedora/3/updates-testing/x86_64/php-mysql-4.3.11-2.8.4.legacy.x86_64.rpm eae4616e39e8a82a4cf931352d4610a293499e5e fedora/3/updates-testing/x86_64/php-ncurses-4.3.11-2.8.4.legacy.x86_64.rpm c3c95fb30901f381376be17003f29ed36a7f22d8 fedora/3/updates-testing/x86_64/php-odbc-4.3.11-2.8.4.legacy.x86_64.rpm 4bc178a084fe1df33ac0a92c15f8d7b817f4a2c7 fedora/3/updates-testing/x86_64/php-pear-4.3.11-2.8.4.legacy.x86_64.rpm 9ce8349a77d7817e505629c5944a9c7c59a6e284 fedora/3/updates-testing/x86_64/php-pgsql-4.3.11-2.8.4.legacy.x86_64.rpm d631abea1dd6cad2bd3d16d52877b5b3f310a2f5 fedora/3/updates-testing/x86_64/php-snmp-4.3.11-2.8.4.legacy.x86_64.rpm c91a27a8bf159f2586d0d6e8ba1ce07f4651e5bd fedora/3/updates-testing/x86_64/php-xmlrpc-4.3.11-2.8.4.legacy.x86_64.rpm b560a17c4ad7954b0184660d900ea2bb37ee1b4a fedora/3/updates-testing/SRPMS/php-4.3.11-2.8.4.legacy.src.rpm --------------------------------------------------------------------- Please test and comment in bugzilla. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: OpenPGP digital signature URL: From deisenst at gtw.net Thu Jul 6 02:36:06 2006 From: deisenst at gtw.net (David D. Eisenstein) Date: Wed, 05 Jul 2006 21:36:06 -0500 Subject: Fedora Core 4 coming . . . sunset, infrastructure issues . . . meeting? In-Reply-To: <859EB3E2-2032-49D2-9940-344C622A1EDA@cs.ucsb.edu> References: <44A30786.3070508@gtw.net> <859EB3E2-2032-49D2-9940-344C622A1EDA@cs.ucsb.edu> Message-ID: <44AC7716.2080804@gtw.net> Jeff Sheltren wrote: > On Jun 28, 2006, at 6:49 PM, David Eisenstein wrote: > >> >> I will likely not be available the rest of this week, and next Monday and >> Tuesday are holiday evenings in the United States of America. Shall we >> shoot for an meeting on IRC mid-week next week? If we meet on Wednesday, >> July 7th, that will leave us 12 calendar days to get stuff done between >> that meeting and the time we are due to inherit Fedora Core 4. >> >> > > Has a meeting time been finalized yet - or has a meeting happened and I > just missed it? > > Also, I just realized that Wednesday (today) isn't the 7th, it's the > 5th... > > -Jeff Hello, I apologize. Family matters came up that kept me out of town at my parents' house longer than I had thought I'd be (I am still there; was expecting to be home on Monday), so firming up a meeting time didn't happen. Having just talked on IRC to Jesse Keating and Marc Deslauriers, they both indicated they would be available at 8pm EDT tomorrow evening (Thursday, July 6th, 2006). 7:00pm CDT. 6pm MDT. 5pm Pacific Daylight time. (That is also 00:00 UTC Friday, July 7th.) Those of you interested in helping us vote on and finalize a decision on what distros we will be dropping support for when, please come if you are available. Also we will be discussing matters regarding FL's inheritance of FC4. Thanks. Warm regards, David Eisenstein From madlists at teaparty.net Thu Jul 6 11:04:21 2006 From: madlists at teaparty.net (Tom Yates) Date: Thu, 6 Jul 2006 12:04:21 +0100 (BST) Subject: Fedora Core 4 coming . . . sunset, infrastructure issues . . . meeting? In-Reply-To: <44AC7716.2080804@gtw.net> References: <44A30786.3070508@gtw.net> <859EB3E2-2032-49D2-9940-344C622A1EDA@cs.ucsb.edu> <44AC7716.2080804@gtw.net> Message-ID: On Wed, 5 Jul 2006, David D. Eisenstein wrote: > I apologize. Family matters came up that kept me out of town at my > parents' house longer than I had thought I'd be (I am still there; was > expecting to be home on Monday), so firming up a meeting time didn't > happen. well, there was a very small meeting (ie, me and jesse) yesterday, at the appointed time (or thereabouts); but that's hardly representative. a couple of others were present but didn't chime in on the issue of EOLs. > Having just talked on IRC to Jesse Keating and Marc Deslauriers, they > both indicated they would be available at 8pm EDT tomorrow evening > (Thursday, July 6th, 2006). 7:00pm CDT. 6pm MDT. 5pm Pacific > Daylight time. (That is also 00:00 UTC Friday, July 7th.) being in cambridge (the cambridge, not the other cambridge), i'm not sure i can stay awake after midnight. if i'm not there, 1) i completely accept we're going to drop both RHs at some point, and that that point is fast approaching. 2) i wouldn't dream of speaking for jesse, but the idea of 3 months for RH73 and 6 months for RH9 was floated (20061001 and 20070101 respectively). 3) if we're re-examining the question, i *beg* for six months notice for RH73 as well as RH9. i honestly believe that six months is a more professional sort of notice period than three, when it comes to upgrading production boxes. declaration of interest: i have a huge stack of RH73 boxes - some 60 of them - that have to be reinstalled with CentOS by the EOL date. half of them i can only take down between 0200 and 0400 every other sunday - hence my feeling that 6 months is a reasonable notice period. i also have a personal RH9 colo'ed box, but i'm going to be doing that on 20060731. this isn't a justification, just me coming clean about my point of view! -- Tom Yates - madhatter at teaparty.net - http://www.teaparty.net From sheltren at cs.ucsb.edu Thu Jul 6 13:29:28 2006 From: sheltren at cs.ucsb.edu (Jeff Sheltren) Date: Thu, 06 Jul 2006 09:29:28 -0400 Subject: Fedora Core 4 coming . . . sunset, infrastructure issues . . . meeting? In-Reply-To: <44AC7716.2080804@gtw.net> References: <44A30786.3070508@gtw.net> <859EB3E2-2032-49D2-9940-344C622A1EDA@cs.ucsb.edu> <44AC7716.2080804@gtw.net> Message-ID: <44AD1038.9000609@cs.ucsb.edu> David D. Eisenstein wrote: > > Having just talked on IRC to Jesse Keating and Marc Deslauriers, they > both indicated they would be available at 8pm EDT tomorrow evening > (Thursday, July 6th, 2006). 7:00pm CDT. 6pm MDT. 5pm Pacific > Daylight time. (That is also 00:00 UTC Friday, July 7th.) > > Those of you interested in helping us vote on and finalize a decision > on what distros we will be dropping support for when, please come if > you are available. Also we will be discussing matters regarding FL's > inheritance of FC4. > Great, I should be able to make it at that time. See you all then! -Jeff From jkeating at j2solutions.net Fri Jul 7 01:43:39 2006 From: jkeating at j2solutions.net (Jesse Keating) Date: Thu, 6 Jul 2006 21:43:39 -0400 Subject: Meeting results Message-ID: <200607062143.44486.jkeating@j2solutions.net> A proposal was made in the meeting tonight / last night that makes a lot of sense to me and the others that were there. I would like to float it here and if there isn't significant issue with it, make it so. Fedora Core 1 and Fedora Core 2 go EOL (dropped by us) when we pick up Fedora Core 4. This follows our stated lifespan policy. RHL7.3/9 get a staged death: New issues (bugs) will be accepted until October 1st. No new bugs after that mark. Existing bugs will be resolved by Dec 31st or never resolved. This should give people a good enough notice to migrate to an appropriate platform and even a bit of a cushion on the other side of Oct 1st. I like this plan, I think its fair. As do the folks in the meeting. What do you think? -- Jesse Keating RHCE (geek.j2solutions.net) Fedora Legacy Team (www.fedoralegacy.org) GPG Public Key (geek.j2solutions.net/jkeating.j2solutions.pub) -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From rostetter at mail.utexas.edu Fri Jul 7 02:22:22 2006 From: rostetter at mail.utexas.edu (Eric Rostetter) Date: Thu, 6 Jul 2006 21:22:22 -0500 Subject: Meeting results In-Reply-To: <200607062143.44486.jkeating@j2solutions.net> References: <200607062143.44486.jkeating@j2solutions.net> Message-ID: <20060706212222.pm4o6emd6fzkss0c@mail.ph.utexas.edu> Quoting Jesse Keating : > Fedora Core 1 and Fedora Core 2 go EOL (dropped by us) when we pick up Fedora > Core 4. This follows our stated lifespan policy. > > RHL7.3/9 get a staged death: New issues (bugs) will be accepted > until October > 1st. No new bugs after that mark. Existing bugs will be resolved by Dec > 31st or never resolved. I can live with this, if we announce it asap. If we don't get a decision and announce it in the by July 15th, then I would add one month to everything. -- Eric Rostetter The Department of Physics The University of Texas at Austin Go Longhorns! From donjr at maner.org Fri Jul 7 02:30:00 2006 From: donjr at maner.org (Donald Maner) Date: Thu, 6 Jul 2006 21:30:00 -0500 Subject: Meeting results In-Reply-To: <200607062143.44486.jkeating@j2solutions.net> References: <200607062143.44486.jkeating@j2solutions.net> Message-ID: <4A5DA14CF063A54C9DB0C98CCE35B37398AA@selket.home.maner.org> > -----Original Message----- > From: fedora-legacy-list-bounces at redhat.com [mailto:fedora-legacy-list- > bounces at redhat.com] On Behalf Of Jesse Keating > Sent: Thursday, July 06, 2006 8:44 PM > To: Discussion of the Fedora Legacy Project > Subject: Meeting results > > A proposal was made in the meeting tonight / last night that makes a > lot of > sense to me and the others that were there. I would like to float it > here > and if there isn't significant issue with it, make it so. > > Fedora Core 1 and Fedora Core 2 go EOL (dropped by us) when we pick up > Fedora > Core 4. This follows our stated lifespan policy. > > RHL7.3/9 get a staged death: New issues (bugs) will be accepted until > October > 1st. No new bugs after that mark. Existing bugs will be resolved by > Dec > 31st or never resolved. I second this plan. Sounds good to me. From jimpop at yahoo.com Fri Jul 7 03:34:22 2006 From: jimpop at yahoo.com (Jim Popovitch) Date: Thu, 06 Jul 2006 23:34:22 -0400 Subject: Meeting results In-Reply-To: <200607062143.44486.jkeating@j2solutions.net> References: <200607062143.44486.jkeating@j2solutions.net> Message-ID: <44ADD63E.1090207@yahoo.com> Jesse Keating wrote: > A proposal was made in the meeting tonight / last night that makes a lot of > sense to me and the others that were there. I would like to float it here > and if there isn't significant issue with it, make it so. > > Fedora Core 1 and Fedora Core 2 go EOL (dropped by us) when we pick up Fedora > Core 4. This follows our stated lifespan policy. > > RHL7.3/9 get a staged death: New issues (bugs) will be accepted until October > 1st. No new bugs after that mark. Existing bugs will be resolved by Dec > 31st or never resolved. > > This should give people a good enough notice to migrate to an appropriate > platform and even a bit of a cushion on the other side of Oct 1st. > > I like this plan, I think its fair. As do the folks in the meeting. What do > you think? Sounds solid to me. -Jim P. From jedgecombe at carolina.rr.com Fri Jul 7 12:10:08 2006 From: jedgecombe at carolina.rr.com (Jason Edgecombe) Date: Fri, 07 Jul 2006 08:10:08 -0400 Subject: Meeting results In-Reply-To: <200607062143.44486.jkeating@j2solutions.net> References: <200607062143.44486.jkeating@j2solutions.net> Message-ID: <44AE4F20.7060008@carolina.rr.com> Jesse Keating wrote: > A proposal was made in the meeting tonight / last night that makes a lot of > sense to me and the others that were there. I would like to float it here > and if there isn't significant issue with it, make it so. > > Fedora Core 1 and Fedora Core 2 go EOL (dropped by us) when we pick up Fedora > Core 4. This follows our stated lifespan policy. > > RHL7.3/9 get a staged death: New issues (bugs) will be accepted until October > 1st. No new bugs after that mark. Existing bugs will be resolved by Dec > 31st or never resolved. > > This should give people a good enough notice to migrate to an appropriate > platform and even a bit of a cushion on the other side of Oct 1st. > > I like this plan, I think its fair. As do the folks in the meeting. What do > you think? > Works for me. Jason Edgecombe From jkosin at beta.intcomgrp.com Fri Jul 7 12:38:41 2006 From: jkosin at beta.intcomgrp.com (James Kosin) Date: Fri, 07 Jul 2006 08:38:41 -0400 Subject: Meeting results In-Reply-To: <200607062143.44486.jkeating@j2solutions.net> References: <200607062143.44486.jkeating@j2solutions.net> Message-ID: <44AE55D1.1070606@beta.intcomgrp.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jesse Keating wrote: > A proposal was made in the meeting tonight / last night that makes a lot of > sense to me and the others that were there. I would like to float it here > and if there isn't significant issue with it, make it so. > > Fedora Core 1 and Fedora Core 2 go EOL (dropped by us) when we pick up Fedora > Core 4. This follows our stated lifespan policy. > > RHL7.3/9 get a staged death: New issues (bugs) will be accepted until October > 1st. No new bugs after that mark. Existing bugs will be resolved by Dec > 31st or never resolved. > > This should give people a good enough notice to migrate to an appropriate > platform and even a bit of a cushion on the other side of Oct 1st. > > I like this plan, I think its fair. As do the folks in the meeting. What do > you think? > Sounds good to me also. Even though I do so reluctantly. I can't fight the powers that be.... and I have advanced notice, which gives me time to prepare. - -James Kosin Long time FC1 user, and proud supporter of RedHat / Fedora. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFErlXQkNLDmnu1kSkRAkMYAJ9wj6s8FDzJLk84lFcgYgzRlpK5zACeMiAi LfF0ZmxrEzBB4fd8PB4I7Ck= =Peys -----END PGP SIGNATURE----- -- Scanned by ClamAV - http://www.clamav.net From mattdm at mattdm.org Fri Jul 7 17:33:46 2006 From: mattdm at mattdm.org (Matthew Miller) Date: Fri, 7 Jul 2006 13:33:46 -0400 Subject: Fedora Core 4 coming . . . sunset, infrastructure issues . . . meeting? In-Reply-To: <019801c69bf9$1cd7bb20$6401a8c0@vdavide> References: <20060630014312.GA2781@jadzia.bu.edu> <019801c69bf9$1cd7bb20$6401a8c0@vdavide> Message-ID: <20060707173346.GA15208@jadzia.bu.edu> On Thu, Jun 29, 2006 at 10:55:52PM -0500, David Eisenstein wrote: > I think it would be great if you did that. Would you mind doing it when I > can be online to chat with you about the process while you perform it? I > would like to document this process for our wiki / documentation efforts > so going forward, we will have information about how one goes about doing > this. I'm about to go and do the FC3 thing.... -- Matthew Miller mattdm at mattdm.org Boston University Linux ------> From jimpop at yahoo.com Fri Jul 14 20:41:21 2006 From: jimpop at yahoo.com (Jim Popovitch) Date: Fri, 14 Jul 2006 16:41:21 -0400 Subject: Help. Kernel errors, can't find common consensus Message-ID: <44B80171.8010808@yahoo.com> Sorry for the chatter, but I am running out of places to look/ask... What does this mean, wrt a stock+FL-updated RH7.3 server (no ACPID, APM, etc): kernel: Uhhuh. NMI received for unknown reason 31 on CPU 0. kernel: Dazed and confused, but trying to continue kernel: Do you have a strange power saving mode enabled? It repeats abt every minute, over and over. Clues? Hints? Possibilities? Tia, -Jim P. From tthome at cox.net Sat Jul 15 03:11:18 2006 From: tthome at cox.net (Tim Thome) Date: Fri, 14 Jul 2006 20:11:18 -0700 Subject: Help. Kernel errors, can't find common consensus In-Reply-To: <44B80171.8010808@yahoo.com> References: <44B80171.8010808@yahoo.com> Message-ID: <60CE21B6-F565-4AD9-9628-5F2B9D1C8123@cox.net> Couple of questions... is this a SMP box? PCI Raid Controller? Broadcomm ethernet? More info on the HW config would be helpful. dmesg dump would also be very helpful... Tim On Jul 14, 2006, at 1:41 PM, Jim Popovitch wrote: > Sorry for the chatter, but I am running out of places to look/ask... > > What does this mean, wrt a stock+FL-updated RH7.3 server (no ACPID, > APM, etc): > > kernel: Uhhuh. NMI received for unknown reason 31 on CPU 0. > kernel: Dazed and confused, but trying to continue > kernel: Do you have a strange power saving mode enabled? > > It repeats abt every minute, over and over. > > Clues? Hints? Possibilities? > > Tia, > > -Jim P. > > -- > fedora-legacy-list mailing list > fedora-legacy-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-legacy-list From jimpop at yahoo.com Sat Jul 15 03:40:29 2006 From: jimpop at yahoo.com (Jim Popovitch) Date: Fri, 14 Jul 2006 23:40:29 -0400 Subject: Help. Kernel errors, can't find common consensus In-Reply-To: <60CE21B6-F565-4AD9-9628-5F2B9D1C8123@cox.net> References: <44B80171.8010808@yahoo.com> <60CE21B6-F565-4AD9-9628-5F2B9D1C8123@cox.net> Message-ID: <44B863AD.3070502@yahoo.com> Hi Tim, This system is using raid1 but not on the root partition, only on a few data partitions. Additionally there is a broadcom ethernet controller. I've had this host up and online for over 3 years and nothing has changed significantly on in in the past 2 years except for regular FL updates. Here's some info: lspci: 00:00.0 Host bridge: ServerWorks: Unknown device 0017 (rev 32) 00:00.1 Host bridge: ServerWorks: Unknown device 0017 00:03.0 VGA compatible controller: ATI Technologies Inc Rage XL (rev 27) 00:0f.0 ISA bridge: ServerWorks CSB5 South Bridge (rev 93) 00:0f.1 IDE interface: ServerWorks CSB5 IDE Controller (rev 93) 00:0f.2 USB Controller: ServerWorks OSB4/CSB5 USB Controller (rev 05) 00:0f.3 Host bridge: ServerWorks: Unknown device 0225 00:10.0 Host bridge: ServerWorks: Unknown device 0101 (rev 03) 00:10.2 Host bridge: ServerWorks: Unknown device 0101 (rev 03) 01:02.0 Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro 100] (rev 08) 02:04.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5703X Gigabit Ethernet (rev 02) 02:05.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5703X Gigabit Ethernet (rev 02) cat /proc/cpuinfo: processor : 0 vendor_id : GenuineIntel cpu family : 15 model : 2 model name : Intel(R) Pentium(R) 4 CPU 2.40GHz stepping : 7 cpu MHz : 2399.435 cache size : 512 KB fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 2 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm bogomips : 4784.12 dmesg: Pysical RAM map: BIOS-e820: 0000000000000000 - 00000000000a0000 (usable) BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved) BIOS-e820: 0000000000100000 - 000000001ffe0000 (usable) BIOS-e820: 000000001ffe0000 - 000000001ffe8000 (ACPI data) BIOS-e820: 000000001ffe8000 - 000000001fff0000 (ACPI NVS) BIOS-e820: 000000001fff0000 - 0000000020000000 (reserved) BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved) 0MB HIGHMEM available. 511MB LOWMEM available. On node 0 totalpages: 131040 zone(0): 4096 pages. zone(1): 126944 pages. zone(2): 0 pages. IBM machine detected. Enabling interrupts during APM calls. Kernel command line: auto BOOT_IMAGE=linux ro root=302 BOOT_FILE=/boot/vmlinuz-2.4.20-46.7.legacy pa nic=60 fastboot Initializing CPU#0 Detected 2399.435 MHz processor. Console: colour VGA+ 80x25 Calibrating delay loop... 4784.12 BogoMIPS Memory: 511628k/524160k available (1182k kernel code, 9972k reserved, 988k data, 120k init, 0k highm em) Dentry cache hash table entries: 65536 (order: 7, 524288 bytes) Inode cache hash table entries: 32768 (order: 6, 262144 bytes) Mount cache hash table entries: 512 (order: 0, 4096 bytes) Buffer-cache hash table entries: 32768 (order: 5, 131072 bytes) Page-cache hash table entries: 131072 (order: 7, 524288 bytes) CPU: Trace cache: 12K uops, L1 D cache: 8K CPU: L2 cache: 512K Intel machine check architecture supported. Intel machine check reporting enabled on CPU#0. CPU: After generic, caps: bfebfbff 00000000 00000000 00000000 CPU: Common caps: bfebfbff 00000000 00000000 00000000 CPU: Intel(R) Pentium(R) 4 CPU 2.40GHz stepping 07 Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Checking 'hlt' instruction... OK. POSIX conformance testing by UNIFIX mtrr: v1.40 (20010327) Richard Gooch (rgooch at atnf.csiro.au) mtrr: detected mtrr type: Intel PCI: PCI BIOS revision 2.10 entry at 0xf0220, last bus=2 PCI: Using configuration type 1 PCI: Probing PCI hardware PCI: Ignoring BAR0-3 of IDE controller 00:0f.1 PCI: Discovered peer bus 01 PCI: Discovered peer bus 02 isapnp: Scanning for PnP cards... isapnp: No Plug & Play device found Linux NET4.0 for Linux 2.4 Based upon Swansea University Computer Society NET3.039 Initializing RT netlink socket apm: BIOS not found. Starting kswapd VFS: Disk quotas vdquot_6.5.1 pty: 2048 Unix98 ptys configured Serial driver version 5.05c (2001-07-08) with MANY_PORTS MULTIPORT SHARE_IRQ SERIAL_PCI ISAPNP enabl ed ttyS0 at 0x03f8 (irq = 4) is a 16550A Real Time Clock Driver v1.10e Floppy drive(s): fd0 is 1.44M FDC 0 is a National Semiconductor PC87306 NET4: Frame Diverter 0.46 RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize Uniform Multi-Platform E-IDE driver Revision: 7.00beta3-.2.4 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx SvrWks CSB5: IDE controller at PCI slot 00:0f.1 SvrWks CSB5: chipset revision 147 SvrWks CSB5: not 100% native mode: will probe irqs later ide0: BM-DMA at 0x3400-0x3407, BIOS settings: hda:DMA, hdb:DMA ide1: BM-DMA at 0x3408-0x340f, BIOS settings: hdc:DMA, hdd:pio hda: ST340016A, ATA DISK drive hdb: CD-224E, ATAPI CD/DVD-ROM drive blk: queue c037a4c0, I/O limit 4095Mb (mask 0xffffffff) hdc: ST340016A, ATA DISK drive blk: queue c037a924, I/O limit 4095Mb (mask 0xffffffff) ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 ide1 at 0x170-0x177,0x376 on irq 15 hda: attached ide-disk driver. hda: host protected area => 1 hda: 78156288 sectors (40016 MB) w/2048KiB Cache, CHS=4865/255/63, UDMA(66) hdc: attached ide-disk driver. hdc: host protected area => 1 hdc: 78156288 sectors (40016 MB) w/2048KiB Cache, CHS=77536/16/63, UDMA(66) ide-floppy driver 0.99.newide Partition check: hda: hda1 hda2 hda3 hda4 < hda5 hda6 hda7 hda8 hda9 hda10 hda11 hda12 > hdc: hdc1 hdc2 hdc3 hdc4 < hdc5 hdc6 hdc7 hdc8 hdc9 hdc10 hdc11 hdc12 > ide-floppy driver 0.99.newide md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27 md: Autodetecting RAID arrays. [events: 000000ab] [events: 000000a7] [events: 000000ab] [events: 000000ab] [events: 000000ab] [events: 000000ab] [events: 00000008] [events: 000000ab] [events: 000000a7] [events: 000000ab] [events: 000000ab] [events: 000000ab] [events: 000000ab] [events: 00000008] md: autorun ... md: considering hdc12 ... md: adding hdc12 ... md: adding hda12 ... md: created md12 md: bind md: bind md: running: md: hdc12's event counter: 00000008 md: hda12's event counter: 00000008 md: RAID level 1 does not need chunksize! Continuing anyway. kmod: failed to exec /sbin/modprobe -s -k md-personality-3, errno = 2 md: personality 3 is not loaded! md :do_md_run() returned -22 md: md12 stopped. md: unbind md: export_rdev(hdc12) md: unbind md: export_rdev(hda12) md: considering hdc11 ... md: adding hdc11 ... md: adding hda11 ... md: created md11 md: bind md: bind md: running: md: hdc11's event counter: 000000ab md: hda11's event counter: 000000ab md: RAID level 1 does not need chunksize! Continuing anyway. kmod: failed to exec /sbin/modprobe -s -k md-personality-3, errno = 2 md: personality 3 is not loaded! md :do_md_run() returned -22 md: md11 stopped. md: unbind md: export_rdev(hdc11) md: unbind md: export_rdev(hda11) md: considering hdc10 ... md: adding hdc10 ... md: adding hda10 ... md: created md10 md: bind md: bind md: running: md: hdc10's event counter: 000000ab md: hda10's event counter: 000000ab md: RAID level 1 does not need chunksize! Continuing anyway. kmod: failed to exec /sbin/modprobe -s -k md-personality-3, errno = 2 md: personality 3 is not loaded! md :do_md_run() returned -22 md: md10 stopped. md: unbind md: export_rdev(hdc10) md: unbind md: export_rdev(hda10) md: considering hdc9 ... md: adding hdc9 ... md: adding hda9 ... md: created md9 md: bind md: bind md: running: md: hdc9's event counter: 000000ab md: hda9's event counter: 000000ab md: RAID level 1 does not need chunksize! Continuing anyway. kmod: failed to exec /sbin/modprobe -s -k md-personality-3, errno = 2 md: personality 3 is not loaded! md :do_md_run() returned -22 md: md9 stopped. md: unbind md: export_rdev(hdc9) md: unbind md: export_rdev(hda9) md: considering hdc8 ... md: adding hdc8 ... md: adding hda8 ... md: created md8 md: bind md: bind md: running: md: hdc8's event counter: 000000ab md: hda8's event counter: 000000ab md: RAID level 1 does not need chunksize! Continuing anyway. kmod: failed to exec /sbin/modprobe -s -k md-personality-3, errno = 2 md: personality 3 is not loaded! md :do_md_run() returned -22 md: md8 stopped. md: unbind md: export_rdev(hdc8) md: unbind md: export_rdev(hda8) md: considering hdc7 ... md: adding hdc7 ... md: adding hda7 ... md: created md7 md: bind md: bind md: running: md: hdc7's event counter: 000000a7 md: hda7's event counter: 000000a7 md: RAID level 1 does not need chunksize! Continuing anyway. kmod: failed to exec /sbin/modprobe -s -k md-personality-3, errno = 2 md: personality 3 is not loaded! md :do_md_run() returned -22 md: md7 stopped. md: unbind md: export_rdev(hdc7) md: unbind md: export_rdev(hda7) md: considering hdc6 ... md: adding hdc6 ... md: adding hda6 ... md: created md6 md: bind md: bind md: running: md: hdc6's event counter: 000000ab md: hda6's event counter: 000000ab md: RAID level 1 does not need chunksize! Continuing anyway. kmod: failed to exec /sbin/modprobe -s -k md-personality-3, errno = 2 md: personality 3 is not loaded! md :do_md_run() returned -22 md: md6 stopped. md: unbind md: export_rdev(hdc6) md: unbind md: export_rdev(hda6) md: ... autorun DONE. NET4: Linux TCP/IP 1.0 for NET4.0 IP Protocols: ICMP, UDP, TCP, IGMP IP: routing cache hash table of 4096 buckets, 32Kbytes TCP: Hash tables configured (established 32768 bind 65536) Linux IP multicast router 0.06 plus PIM-SM NET4: Unix domain sockets 1.0/SMP for Linux NET4.0. RAMDISK: Compressed image found at block 0 Freeing initrd memory: 129k freed VFS: Mounted root (ext2 filesystem). md: raid1 personality registered as nr 3 Journalled Block Device driver loaded md: Autodetecting RAID arrays. [events: 00000008] [events: 00000008] [events: 000000ab] [events: 000000ab] [events: 000000ab] [events: 000000ab] [events: 000000ab] [events: 000000ab] [events: 000000ab] [events: 000000ab] [events: 000000a7] [events: 000000a7] [events: 000000ab] [events: 000000ab] md: autorun ... md: considering hda6 ... md: adding hda6 ... md: adding hdc6 ... md: created md6 md: bind md: bind md: running: md: hda6's event counter: 000000ab md: hdc6's event counter: 000000ab md: RAID level 1 does not need chunksize! Continuing anyway. md6: max total readahead window set to 124k md6: 1 data-disks, max readahead per data-disk: 124k raid1: device hda6 operational as mirror 0 raid1: device hdc6 operational as mirror 1 raid1: raid set md6 active with 2 out of 2 mirrors md: updating md6 RAID superblock on device md: hda6 [events: 000000ac]<6>(write) hda6's sb offset: 2104384 md: hdc6 [events: 000000ac]<6>(write) hdc6's sb offset: 2097536 md: considering hda7 ... md: adding hda7 ... md: adding hdc7 ... md: created md7 md: bind md: bind md: running: md: hda7's event counter: 000000a7 md: hdc7's event counter: 000000a7 md: RAID level 1 does not need chunksize! Continuing anyway. md7: max total readahead window set to 124k md7: 1 data-disks, max readahead per data-disk: 124k raid1: device hda7 operational as mirror 0 raid1: device hdc7 operational as mirror 1 raid1: raid set md7 active with 2 out of 2 mirrors md: updating md7 RAID superblock on device md: hda7 [events: 000000a8]<6>(write) hda7's sb offset: 4200896 md: hdc7 [events: 000000a8]<6>(write) hdc7's sb offset: 4194688 md: considering hda8 ... md: adding hda8 ... md: adding hdc8 ... md: created md8 md: bind md: bind md: running: md: hda8's event counter: 000000ab md: hdc8's event counter: 000000ab md: RAID level 1 does not need chunksize! Continuing anyway. md8: max total readahead window set to 124k md8: 1 data-disks, max readahead per data-disk: 124k raid1: device hda8 operational as mirror 0 raid1: device hdc8 operational as mirror 1 raid1: raid set md8 active with 2 out of 2 mirrors md: updating md8 RAID superblock on device md: hda8 [events: 000000ac]<6>(write) hda8's sb offset: 4200896 md: hdc8 [events: 000000ac]<6>(write) hdc8's sb offset: 4194688 md: considering hda9 ... md: adding hda9 ... md: adding hdc9 ... md: created md9 md: bind md: bind md: running: md: hda9's event counter: 000000ab md: hdc9's event counter: 000000ab md: RAID level 1 does not need chunksize! Continuing anyway. md9: max total readahead window set to 124k md9: 1 data-disks, max readahead per data-disk: 124k raid1: device hda9 operational as mirror 0 raid1: device hdc9 operational as mirror 1 raid1: raid set md9 active with 2 out of 2 mirrors md: updating md9 RAID superblock on device md: hda9 [events: 000000ac]<6>(write) hda9's sb offset: 2152576 md: hdc9 [events: 000000ac]<6>(write) hdc9's sb offset: 2146432 md: considering hda10 ... md: adding hda10 ... md: adding hdc10 ... md: created md10 md: bind md: bind md: running: md: hda10's event counter: 000000ab md: hdc10's event counter: 000000ab md: RAID level 1 does not need chunksize! Continuing anyway. md10: max total readahead window set to 124k md10: 1 data-disks, max readahead per data-disk: 124k raid1: device hda10 operational as mirror 0 raid1: device hdc10 operational as mirror 1 raid1: raid set md10 active with 2 out of 2 mirrors md: updating md10 RAID superblock on device md: hda10 [events: 000000ac]<6>(write) hda10's sb offset: 2152576 md: hdc10 [events: 000000ac]<6>(write) hdc10's sb offset: 2146432 md: considering hda11 ... md: adding hda11 ... md: adding hdc11 ... md: created md11 md: bind md: bind md: running: md: hda11's event counter: 000000ab md: hdc11's event counter: 000000ab md: RAID level 1 does not need chunksize! Continuing anyway. md11: max total readahead window set to 124k md11: 1 data-disks, max readahead per data-disk: 124k raid1: device hda11 operational as mirror 0 raid1: device hdc11 operational as mirror 1 raid1: raid set md11 active with 2 out of 2 mirrors md: updating md11 RAID superblock on device md: hda11 [events: 000000ac]<6>(write) hda11's sb offset: 4200896 md: hdc11 [events: 000000ac]<6>(write) hdc11's sb offset: 4194688 md: considering hda12 ... md: adding hda12 ... md: adding hdc12 ... md: created md12 md: bind md: bind md: running: md: hda12's event counter: 00000008 md: hdc12's event counter: 00000008 md: RAID level 1 does not need chunksize! Continuing anyway. md12: max total readahead window set to 124k md12: 1 data-disks, max readahead per data-disk: 124k raid1: device hda12 operational as mirror 0 raid1: device hdc12 operational as mirror 1 raid1: raid set md12 active with 2 out of 2 mirrors md: updating md12 RAID superblock on device md: hda12 [events: 00000009]<6>(write) hda12's sb offset: 14779648 md: hdc12 [events: 00000009]<6>(write) hdc12's sb offset: 14834112 md: ... autorun DONE. kjournald starting. Commit interval 5 seconds EXT3-fs: mounted filesystem with ordered data mode. Freeing unused kernel memory: 120k freed Adding Swap: 1052248k swap-space (priority -1) Adding Swap: 1048816k swap-space (priority -2) EXT3 FS 2.4-0.9.19, 19 August 2002 on ide0(3,2), internal journal kjournald starting. Commit interval 5 seconds EXT3 FS 2.4-0.9.19, 19 August 2002 on ide0(3,1), internal journal EXT3-fs: mounted filesystem with ordered data mode. kjournald starting. Commit interval 5 seconds EXT3 FS 2.4-0.9.19, 19 August 2002 on md(9,6), internal journal EXT3-fs: mounted filesystem with ordered data mode. kjournald starting. Commit interval 5 seconds EXT3 FS 2.4-0.9.19, 19 August 2002 on md(9,8), internal journal EXT3-fs: mounted filesystem with ordered data mode. kjournald starting. Commit interval 5 seconds EXT3 FS 2.4-0.9.19, 19 August 2002 on md(9,9), internal journal EXT3-fs: mounted filesystem with ordered data mode. kjournald starting. Commit interval 5 seconds EXT3 FS 2.4-0.9.19, 19 August 2002 on md(9,10), internal journal EXT3-fs: mounted filesystem with ordered data mode. kjournald starting. Commit interval 5 seconds EXT3 FS 2.4-0.9.19, 19 August 2002 on md(9,11), internal journal EXT3-fs: mounted filesystem with ordered data mode. kjournald starting. Commit interval 5 seconds EXT3 FS 2.4-0.9.19, 19 August 2002 on md(9,12), internal journal EXT3-fs: mounted filesystem with ordered data mode. ide-floppy driver 0.99.newide hdb: attached ide-cdrom driver. hdb: ATAPI 24X CD-ROM drive, 128kB Cache, UDMA(33) Uniform CD-ROM driver Revision: 3.12 hdb: DMA disabled Thanks, -Jim P. Tim Thome wrote: > Couple of questions... is this a SMP box? PCI Raid Controller? Broadcomm > ethernet? > > More info on the HW config would be helpful. dmesg dump would also be > very helpful... > > Tim > > On Jul 14, 2006, at 1:41 PM, Jim Popovitch wrote: > >> Sorry for the chatter, but I am running out of places to look/ask... >> >> What does this mean, wrt a stock+FL-updated RH7.3 server (no ACPID, >> APM, etc): >> >> kernel: Uhhuh. NMI received for unknown reason 31 on CPU 0. >> kernel: Dazed and confused, but trying to continue >> kernel: Do you have a strange power saving mode enabled? >> >> It repeats abt every minute, over and over. >> >> Clues? Hints? Possibilities? >> >> Tia, >> >> -Jim P. >> >> -- >> fedora-legacy-list mailing list >> fedora-legacy-list at redhat.com >> https://www.redhat.com/mailman/listinfo/fedora-legacy-list > > -- > fedora-legacy-list mailing list > fedora-legacy-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-legacy-list > From jimpop at yahoo.com Sun Jul 16 06:15:25 2006 From: jimpop at yahoo.com (Jim Popovitch) Date: Sun, 16 Jul 2006 02:15:25 -0400 Subject: Help. Kernel errors, can't find common consensus In-Reply-To: <44B863AD.3070502@yahoo.com> References: <44B80171.8010808@yahoo.com> <60CE21B6-F565-4AD9-9628-5F2B9D1C8123@cox.net> <44B863AD.3070502@yahoo.com> Message-ID: <44B9D97D.8040509@yahoo.com> This issue is no longer of any concern. The system has been disabled and applications moved to others. -Jim P. Jim Popovitch wrote: > Hi Tim, > > This system is using raid1 but not on the root partition, only on a few > data partitions. Additionally there is a broadcom ethernet controller. > I've had this host up and online for over 3 years and nothing has > changed significantly on in in the past 2 years except for regular FL > updates. Here's some info: > > lspci: > 00:00.0 Host bridge: ServerWorks: Unknown device 0017 (rev 32) > 00:00.1 Host bridge: ServerWorks: Unknown device 0017 > 00:03.0 VGA compatible controller: ATI Technologies Inc Rage XL (rev 27) > 00:0f.0 ISA bridge: ServerWorks CSB5 South Bridge (rev 93) > 00:0f.1 IDE interface: ServerWorks CSB5 IDE Controller (rev 93) > 00:0f.2 USB Controller: ServerWorks OSB4/CSB5 USB Controller (rev 05) > 00:0f.3 Host bridge: ServerWorks: Unknown device 0225 > 00:10.0 Host bridge: ServerWorks: Unknown device 0101 (rev 03) > 00:10.2 Host bridge: ServerWorks: Unknown device 0101 (rev 03) > 01:02.0 Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro 100] > (rev 08) > 02:04.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5703X > Gigabit Ethernet (rev 02) > 02:05.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5703X > Gigabit Ethernet (rev 02) > > cat /proc/cpuinfo: > processor : 0 > vendor_id : GenuineIntel > cpu family : 15 > model : 2 > model name : Intel(R) Pentium(R) 4 CPU 2.40GHz > stepping : 7 > cpu MHz : 2399.435 > cache size : 512 KB > fdiv_bug : no > hlt_bug : no > f00f_bug : no > coma_bug : no > fpu : yes > fpu_exception : yes > cpuid level : 2 > wp : yes > flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge > mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm > bogomips : 4784.12 > > dmesg: > Pysical RAM map: > BIOS-e820: 0000000000000000 - 00000000000a0000 (usable) > BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved) > BIOS-e820: 0000000000100000 - 000000001ffe0000 (usable) > BIOS-e820: 000000001ffe0000 - 000000001ffe8000 (ACPI data) > BIOS-e820: 000000001ffe8000 - 000000001fff0000 (ACPI NVS) > BIOS-e820: 000000001fff0000 - 0000000020000000 (reserved) > BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved) > 0MB HIGHMEM available. > 511MB LOWMEM available. > On node 0 totalpages: 131040 > zone(0): 4096 pages. > zone(1): 126944 pages. > zone(2): 0 pages. > IBM machine detected. Enabling interrupts during APM calls. > Kernel command line: auto BOOT_IMAGE=linux ro root=302 > BOOT_FILE=/boot/vmlinuz-2.4.20-46.7.legacy pa > nic=60 fastboot > Initializing CPU#0 > Detected 2399.435 MHz processor. > Console: colour VGA+ 80x25 > Calibrating delay loop... 4784.12 BogoMIPS > Memory: 511628k/524160k available (1182k kernel code, 9972k reserved, > 988k data, 120k init, 0k highm > em) > Dentry cache hash table entries: 65536 (order: 7, 524288 bytes) > Inode cache hash table entries: 32768 (order: 6, 262144 bytes) > Mount cache hash table entries: 512 (order: 0, 4096 bytes) > Buffer-cache hash table entries: 32768 (order: 5, 131072 bytes) > Page-cache hash table entries: 131072 (order: 7, 524288 bytes) > CPU: Trace cache: 12K uops, L1 D cache: 8K > CPU: L2 cache: 512K > Intel machine check architecture supported. > Intel machine check reporting enabled on CPU#0. > CPU: After generic, caps: bfebfbff 00000000 00000000 00000000 > CPU: Common caps: bfebfbff 00000000 00000000 00000000 > CPU: Intel(R) Pentium(R) 4 CPU 2.40GHz stepping 07 > Enabling fast FPU save and restore... done. > Enabling unmasked SIMD FPU exception support... done. > Checking 'hlt' instruction... OK. > POSIX conformance testing by UNIFIX > mtrr: v1.40 (20010327) Richard Gooch (rgooch at atnf.csiro.au) > mtrr: detected mtrr type: Intel > PCI: PCI BIOS revision 2.10 entry at 0xf0220, last bus=2 > PCI: Using configuration type 1 > PCI: Probing PCI hardware > PCI: Ignoring BAR0-3 of IDE controller 00:0f.1 > PCI: Discovered peer bus 01 > PCI: Discovered peer bus 02 > isapnp: Scanning for PnP cards... > isapnp: No Plug & Play device found > Linux NET4.0 for Linux 2.4 > Based upon Swansea University Computer Society NET3.039 > Initializing RT netlink socket > apm: BIOS not found. > Starting kswapd > VFS: Disk quotas vdquot_6.5.1 > pty: 2048 Unix98 ptys configured > Serial driver version 5.05c (2001-07-08) with MANY_PORTS MULTIPORT > SHARE_IRQ SERIAL_PCI ISAPNP enabl > ed > ttyS0 at 0x03f8 (irq = 4) is a 16550A > Real Time Clock Driver v1.10e > Floppy drive(s): fd0 is 1.44M > FDC 0 is a National Semiconductor PC87306 > NET4: Frame Diverter 0.46 > RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize > Uniform Multi-Platform E-IDE driver Revision: 7.00beta3-.2.4 > ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx > SvrWks CSB5: IDE controller at PCI slot 00:0f.1 > SvrWks CSB5: chipset revision 147 > SvrWks CSB5: not 100% native mode: will probe irqs later > ide0: BM-DMA at 0x3400-0x3407, BIOS settings: hda:DMA, hdb:DMA > ide1: BM-DMA at 0x3408-0x340f, BIOS settings: hdc:DMA, hdd:pio > hda: ST340016A, ATA DISK drive > hdb: CD-224E, ATAPI CD/DVD-ROM drive > blk: queue c037a4c0, I/O limit 4095Mb (mask 0xffffffff) > hdc: ST340016A, ATA DISK drive > blk: queue c037a924, I/O limit 4095Mb (mask 0xffffffff) > ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 > ide1 at 0x170-0x177,0x376 on irq 15 > hda: attached ide-disk driver. > hda: host protected area => 1 > hda: 78156288 sectors (40016 MB) w/2048KiB Cache, CHS=4865/255/63, UDMA(66) > hdc: attached ide-disk driver. > hdc: host protected area => 1 > hdc: 78156288 sectors (40016 MB) w/2048KiB Cache, CHS=77536/16/63, UDMA(66) > ide-floppy driver 0.99.newide > Partition check: > hda: hda1 hda2 hda3 hda4 < hda5 hda6 hda7 hda8 hda9 hda10 hda11 hda12 > > hdc: hdc1 hdc2 hdc3 hdc4 < hdc5 hdc6 hdc7 hdc8 hdc9 hdc10 hdc11 hdc12 > > ide-floppy driver 0.99.newide > md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27 > md: Autodetecting RAID arrays. > [events: 000000ab] > [events: 000000a7] > [events: 000000ab] > [events: 000000ab] > [events: 000000ab] > [events: 000000ab] > [events: 00000008] > [events: 000000ab] > [events: 000000a7] > [events: 000000ab] > [events: 000000ab] > [events: 000000ab] > [events: 000000ab] > [events: 00000008] > md: autorun ... > md: considering hdc12 ... > md: adding hdc12 ... > md: adding hda12 ... > md: created md12 > md: bind > md: bind > md: running: > md: hdc12's event counter: 00000008 > md: hda12's event counter: 00000008 > md: RAID level 1 does not need chunksize! Continuing anyway. > kmod: failed to exec /sbin/modprobe -s -k md-personality-3, errno = 2 > md: personality 3 is not loaded! > md :do_md_run() returned -22 > md: md12 stopped. > md: unbind > md: export_rdev(hdc12) > md: unbind > md: export_rdev(hda12) > md: considering hdc11 ... > md: adding hdc11 ... > md: adding hda11 ... > md: created md11 > md: bind > md: bind > md: running: > md: hdc11's event counter: 000000ab > md: hda11's event counter: 000000ab > md: RAID level 1 does not need chunksize! Continuing anyway. > kmod: failed to exec /sbin/modprobe -s -k md-personality-3, errno = 2 > md: personality 3 is not loaded! > md :do_md_run() returned -22 > md: md11 stopped. > md: unbind > md: export_rdev(hdc11) > md: unbind > md: export_rdev(hda11) > md: considering hdc10 ... > md: adding hdc10 ... > md: adding hda10 ... > md: created md10 > md: bind > md: bind > md: running: > md: hdc10's event counter: 000000ab > md: hda10's event counter: 000000ab > md: RAID level 1 does not need chunksize! Continuing anyway. > kmod: failed to exec /sbin/modprobe -s -k md-personality-3, errno = 2 > md: personality 3 is not loaded! > md :do_md_run() returned -22 > md: md10 stopped. > md: unbind > md: export_rdev(hdc10) > md: unbind > md: export_rdev(hda10) > md: considering hdc9 ... > md: adding hdc9 ... > md: adding hda9 ... > md: created md9 > md: bind > md: bind > md: running: > md: hdc9's event counter: 000000ab > md: hda9's event counter: 000000ab > md: RAID level 1 does not need chunksize! Continuing anyway. > kmod: failed to exec /sbin/modprobe -s -k md-personality-3, errno = 2 > md: personality 3 is not loaded! > md :do_md_run() returned -22 > md: md9 stopped. > md: unbind > md: export_rdev(hdc9) > md: unbind > md: export_rdev(hda9) > md: considering hdc8 ... > md: adding hdc8 ... > md: adding hda8 ... > md: created md8 > md: bind > md: bind > md: running: > md: hdc8's event counter: 000000ab > md: hda8's event counter: 000000ab > md: RAID level 1 does not need chunksize! Continuing anyway. > kmod: failed to exec /sbin/modprobe -s -k md-personality-3, errno = 2 > md: personality 3 is not loaded! > md :do_md_run() returned -22 > md: md8 stopped. > md: unbind > md: export_rdev(hdc8) > md: unbind > md: export_rdev(hda8) > md: considering hdc7 ... > md: adding hdc7 ... > md: adding hda7 ... > md: created md7 > md: bind > md: bind > md: running: > md: hdc7's event counter: 000000a7 > md: hda7's event counter: 000000a7 > md: RAID level 1 does not need chunksize! Continuing anyway. > kmod: failed to exec /sbin/modprobe -s -k md-personality-3, errno = 2 > md: personality 3 is not loaded! > md :do_md_run() returned -22 > md: md7 stopped. > md: unbind > md: export_rdev(hdc7) > md: unbind > md: export_rdev(hda7) > md: considering hdc6 ... > md: adding hdc6 ... > md: adding hda6 ... > md: created md6 > md: bind > md: bind > md: running: > md: hdc6's event counter: 000000ab > md: hda6's event counter: 000000ab > md: RAID level 1 does not need chunksize! Continuing anyway. > kmod: failed to exec /sbin/modprobe -s -k md-personality-3, errno = 2 > md: personality 3 is not loaded! > md :do_md_run() returned -22 > md: md6 stopped. > md: unbind > md: export_rdev(hdc6) > md: unbind > md: export_rdev(hda6) > md: ... autorun DONE. > NET4: Linux TCP/IP 1.0 for NET4.0 > IP Protocols: ICMP, UDP, TCP, IGMP > IP: routing cache hash table of 4096 buckets, 32Kbytes > TCP: Hash tables configured (established 32768 bind 65536) > Linux IP multicast router 0.06 plus PIM-SM > NET4: Unix domain sockets 1.0/SMP for Linux NET4.0. > RAMDISK: Compressed image found at block 0 > Freeing initrd memory: 129k freed > VFS: Mounted root (ext2 filesystem). > md: raid1 personality registered as nr 3 > Journalled Block Device driver loaded > md: Autodetecting RAID arrays. > [events: 00000008] > [events: 00000008] > [events: 000000ab] > [events: 000000ab] > [events: 000000ab] > [events: 000000ab] > [events: 000000ab] > [events: 000000ab] > [events: 000000ab] > [events: 000000ab] > [events: 000000a7] > [events: 000000a7] > [events: 000000ab] > [events: 000000ab] > md: autorun ... > md: considering hda6 ... > md: adding hda6 ... > md: adding hdc6 ... > md: created md6 > md: bind > md: bind > md: running: > md: hda6's event counter: 000000ab > md: hdc6's event counter: 000000ab > md: RAID level 1 does not need chunksize! Continuing anyway. > md6: max total readahead window set to 124k > md6: 1 data-disks, max readahead per data-disk: 124k > raid1: device hda6 operational as mirror 0 > raid1: device hdc6 operational as mirror 1 > raid1: raid set md6 active with 2 out of 2 mirrors > md: updating md6 RAID superblock on device > md: hda6 [events: 000000ac]<6>(write) hda6's sb offset: 2104384 > md: hdc6 [events: 000000ac]<6>(write) hdc6's sb offset: 2097536 > md: considering hda7 ... > md: adding hda7 ... > md: adding hdc7 ... > md: created md7 > md: bind > md: bind > md: running: > md: hda7's event counter: 000000a7 > md: hdc7's event counter: 000000a7 > md: RAID level 1 does not need chunksize! Continuing anyway. > md7: max total readahead window set to 124k > md7: 1 data-disks, max readahead per data-disk: 124k > raid1: device hda7 operational as mirror 0 > raid1: device hdc7 operational as mirror 1 > raid1: raid set md7 active with 2 out of 2 mirrors > md: updating md7 RAID superblock on device > md: hda7 [events: 000000a8]<6>(write) hda7's sb offset: 4200896 > md: hdc7 [events: 000000a8]<6>(write) hdc7's sb offset: 4194688 > md: considering hda8 ... > md: adding hda8 ... > md: adding hdc8 ... > md: created md8 > md: bind > md: bind > md: running: > md: hda8's event counter: 000000ab > md: hdc8's event counter: 000000ab > md: RAID level 1 does not need chunksize! Continuing anyway. > md8: max total readahead window set to 124k > md8: 1 data-disks, max readahead per data-disk: 124k > raid1: device hda8 operational as mirror 0 > raid1: device hdc8 operational as mirror 1 > raid1: raid set md8 active with 2 out of 2 mirrors > md: updating md8 RAID superblock on device > md: hda8 [events: 000000ac]<6>(write) hda8's sb offset: 4200896 > md: hdc8 [events: 000000ac]<6>(write) hdc8's sb offset: 4194688 > md: considering hda9 ... > md: adding hda9 ... > md: adding hdc9 ... > md: created md9 > md: bind > md: bind > md: running: > md: hda9's event counter: 000000ab > md: hdc9's event counter: 000000ab > md: RAID level 1 does not need chunksize! Continuing anyway. > md9: max total readahead window set to 124k > md9: 1 data-disks, max readahead per data-disk: 124k > raid1: device hda9 operational as mirror 0 > raid1: device hdc9 operational as mirror 1 > raid1: raid set md9 active with 2 out of 2 mirrors > md: updating md9 RAID superblock on device > md: hda9 [events: 000000ac]<6>(write) hda9's sb offset: 2152576 > md: hdc9 [events: 000000ac]<6>(write) hdc9's sb offset: 2146432 > md: considering hda10 ... > md: adding hda10 ... > md: adding hdc10 ... > md: created md10 > md: bind > md: bind > md: running: > md: hda10's event counter: 000000ab > md: hdc10's event counter: 000000ab > md: RAID level 1 does not need chunksize! Continuing anyway. > md10: max total readahead window set to 124k > md10: 1 data-disks, max readahead per data-disk: 124k > raid1: device hda10 operational as mirror 0 > raid1: device hdc10 operational as mirror 1 > raid1: raid set md10 active with 2 out of 2 mirrors > md: updating md10 RAID superblock on device > md: hda10 [events: 000000ac]<6>(write) hda10's sb offset: 2152576 > md: hdc10 [events: 000000ac]<6>(write) hdc10's sb offset: 2146432 > md: considering hda11 ... > md: adding hda11 ... > md: adding hdc11 ... > md: created md11 > md: bind > md: bind > md: running: > md: hda11's event counter: 000000ab > md: hdc11's event counter: 000000ab > md: RAID level 1 does not need chunksize! Continuing anyway. > md11: max total readahead window set to 124k > md11: 1 data-disks, max readahead per data-disk: 124k > raid1: device hda11 operational as mirror 0 > raid1: device hdc11 operational as mirror 1 > raid1: raid set md11 active with 2 out of 2 mirrors > md: updating md11 RAID superblock on device > md: hda11 [events: 000000ac]<6>(write) hda11's sb offset: 4200896 > md: hdc11 [events: 000000ac]<6>(write) hdc11's sb offset: 4194688 > md: considering hda12 ... > md: adding hda12 ... > md: adding hdc12 ... > md: created md12 > md: bind > md: bind > md: running: > md: hda12's event counter: 00000008 > md: hdc12's event counter: 00000008 > md: RAID level 1 does not need chunksize! Continuing anyway. > md12: max total readahead window set to 124k > md12: 1 data-disks, max readahead per data-disk: 124k > raid1: device hda12 operational as mirror 0 > raid1: device hdc12 operational as mirror 1 > raid1: raid set md12 active with 2 out of 2 mirrors > md: updating md12 RAID superblock on device > md: hda12 [events: 00000009]<6>(write) hda12's sb offset: 14779648 > md: hdc12 [events: 00000009]<6>(write) hdc12's sb offset: 14834112 > md: ... autorun DONE. > kjournald starting. Commit interval 5 seconds > EXT3-fs: mounted filesystem with ordered data mode. > Freeing unused kernel memory: 120k freed > Adding Swap: 1052248k swap-space (priority -1) > Adding Swap: 1048816k swap-space (priority -2) > EXT3 FS 2.4-0.9.19, 19 August 2002 on ide0(3,2), internal journal > kjournald starting. Commit interval 5 seconds > EXT3 FS 2.4-0.9.19, 19 August 2002 on ide0(3,1), internal journal > EXT3-fs: mounted filesystem with ordered data mode. > kjournald starting. Commit interval 5 seconds > EXT3 FS 2.4-0.9.19, 19 August 2002 on md(9,6), internal journal > EXT3-fs: mounted filesystem with ordered data mode. > kjournald starting. Commit interval 5 seconds > EXT3 FS 2.4-0.9.19, 19 August 2002 on md(9,8), internal journal > EXT3-fs: mounted filesystem with ordered data mode. > kjournald starting. Commit interval 5 seconds > EXT3 FS 2.4-0.9.19, 19 August 2002 on md(9,9), internal journal > EXT3-fs: mounted filesystem with ordered data mode. > kjournald starting. Commit interval 5 seconds > EXT3 FS 2.4-0.9.19, 19 August 2002 on md(9,10), internal journal > EXT3-fs: mounted filesystem with ordered data mode. > kjournald starting. Commit interval 5 seconds > EXT3 FS 2.4-0.9.19, 19 August 2002 on md(9,11), internal journal > EXT3-fs: mounted filesystem with ordered data mode. > kjournald starting. Commit interval 5 seconds > EXT3 FS 2.4-0.9.19, 19 August 2002 on md(9,12), internal journal > EXT3-fs: mounted filesystem with ordered data mode. > ide-floppy driver 0.99.newide > hdb: attached ide-cdrom driver. > hdb: ATAPI 24X CD-ROM drive, 128kB Cache, UDMA(33) > Uniform CD-ROM driver Revision: 3.12 > hdb: DMA disabled > > Thanks, > > -Jim P. > > Tim Thome wrote: >> Couple of questions... is this a SMP box? PCI Raid Controller? >> Broadcomm ethernet? >> >> More info on the HW config would be helpful. dmesg dump would also be >> very helpful... >> >> Tim >> >> On Jul 14, 2006, at 1:41 PM, Jim Popovitch wrote: >> >>> Sorry for the chatter, but I am running out of places to look/ask... >>> >>> What does this mean, wrt a stock+FL-updated RH7.3 server (no ACPID, >>> APM, etc): >>> >>> kernel: Uhhuh. NMI received for unknown reason 31 on CPU 0. >>> kernel: Dazed and confused, but trying to continue >>> kernel: Do you have a strange power saving mode enabled? >>> >>> It repeats abt every minute, over and over. >>> >>> Clues? Hints? Possibilities? >>> >>> Tia, >>> >>> -Jim P. >>> >>> -- >>> fedora-legacy-list mailing list >>> fedora-legacy-list at redhat.com >>> https://www.redhat.com/mailman/listinfo/fedora-legacy-list >> >> -- >> fedora-legacy-list mailing list >> fedora-legacy-list at redhat.com >> https://www.redhat.com/mailman/listinfo/fedora-legacy-list >> > > -- > fedora-legacy-list mailing list > fedora-legacy-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-legacy-list > From laroche at redhat.com Mon Jul 17 08:56:29 2006 From: laroche at redhat.com (Florian La Roche) Date: Mon, 17 Jul 2006 10:56:29 +0200 Subject: unofficial updates for Fedora Core 4 In-Reply-To: <20060713173320.GA12246@jadzia.bu.edu> References: <20060713173320.GA12246@jadzia.bu.edu> Message-ID: <20060717085628.GA3453@dudweiler.stuttgart.redhat.com> On Thu, Jul 13, 2006 at 01:33:20PM -0400, Matthew Miller wrote: > As I'm sure everyone Core developer knows (and probably can't wait for), FC4 > is going to Legacy in a couple of weeks. Hello all, I still have a fc4 machine running along, so I have re-compiled a few packages to be really updated to their newest versions. Pushing these out as official updates probably doesn't make any sense, but maybe some people also want to use these newer packages (most from current FC-development): - bind-9.3.2 - cvs-1.11.22 - ntp-4.2.2 - openssh-4.3p2 - pychecker-0.8.17 - sendmail-8.13.7 - squid-2.5.STABLE14 I'd love to hear comments about the above packages, but also have to warn that I am probably soon migrating over to FC6 with that machine, so I might discontinue the backports any day. All packages are at http://www.jur-linux.org/rpms/fc-updates/4/ . regards, Florian La Roche From Axel.Thimm at ATrpms.net Mon Jul 17 10:38:46 2006 From: Axel.Thimm at ATrpms.net (Axel Thimm) Date: Mon, 17 Jul 2006 12:38:46 +0200 Subject: Meeting results In-Reply-To: <200607062143.44486.jkeating@j2solutions.net> References: <200607062143.44486.jkeating@j2solutions.net> Message-ID: <20060717103846.GA15167@neu.nirvana> Hi, On Thu, Jul 06, 2006 at 09:43:39PM -0400, Jesse Keating wrote: > A proposal was made in the meeting tonight / last night that makes a lot of > sense to me and the others that were there. I would like to float it here > and if there isn't significant issue with it, make it so. > > Fedora Core 1 and Fedora Core 2 go EOL (dropped by us) when we pick up Fedora > Core 4. This follows our stated lifespan policy. > > RHL7.3/9 get a staged death: New issues (bugs) will be accepted until October > 1st. No new bugs after that mark. Existing bugs will be resolved by Dec > 31st or never resolved. > > This should give people a good enough notice to migrate to an appropriate > platform and even a bit of a cushion on the other side of Oct 1st. > > I like this plan, I think its fair. As do the folks in the meeting. What do > you think? > is this plan agreed upon? Any announcements? Thanks. -- Axel.Thimm at ATrpms.net -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From rostetter at mail.utexas.edu Mon Jul 17 14:55:57 2006 From: rostetter at mail.utexas.edu (Eric Rostetter) Date: Mon, 17 Jul 2006 09:55:57 -0500 Subject: Meeting results In-Reply-To: <20060717103846.GA15167@neu.nirvana> References: <200607062143.44486.jkeating@j2solutions.net> <20060717103846.GA15167@neu.nirvana> Message-ID: <20060717095557.i2zq1gy7ezi8w4c0@mail.ph.utexas.edu> Quoting Axel Thimm : >> I like this plan, I think its fair. As do the folks in the >> meeting. What do >> you think? >> > > is this plan agreed upon? Any announcements? I've only heard people in agreement; I don't remember anyone against it. So I would think we should call it agreed upon. As for an announcement, it should be made asap, else all the dates will need to be pushed back. > Thanks. > -- > Axel.Thimm at ATrpms.net -- Eric Rostetter The Department of Physics The University of Texas at Austin Go Longhorns! From agibson at ptm.com Wed Jul 19 18:56:30 2006 From: agibson at ptm.com (Adam Gibson) Date: Wed, 19 Jul 2006 14:56:30 -0400 Subject: sendmail DOS (CVE-2006-1173) Message-ID: <44BE805E.7040704@ptm.com> Anyone know if this is being worked on? http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-1173 From jkosin at beta.intcomgrp.com Wed Jul 19 19:03:27 2006 From: jkosin at beta.intcomgrp.com (James Kosin) Date: Wed, 19 Jul 2006 15:03:27 -0400 Subject: sendmail DOS (CVE-2006-1173) In-Reply-To: <44BE805E.7040704@ptm.com> References: <44BE805E.7040704@ptm.com> Message-ID: <44BE81FF.5000902@beta.intcomgrp.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Adam Gibson wrote: > Anyone know if this is being worked on? > > http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-1173 > > -- > fedora-legacy-list mailing list > fedora-legacy-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-legacy-list Should be done... - -James -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEvoH/kNLDmnu1kSkRAgyTAJ90sHkp1fc0kfpUchnrByjCmUVORACeL9JA toigEC5FRcs/bDh05oGBJDk= =ofDP -----END PGP SIGNATURE----- -- Scanned by ClamAV - http://www.clamav.net From jkeating at j2solutions.net Sat Jul 22 17:44:54 2006 From: jkeating at j2solutions.net (Jesse Keating) Date: Sat, 22 Jul 2006 13:44:54 -0400 Subject: Announcing End of Life times (Fedora Core 1, 2, Red Hat Linux 7.3, 9) Message-ID: <200607221344.54567.jkeating@j2solutions.net> With Fedora Core 6 Test 2 set to be released July 26th, it is time we announce the End of Life of our various Legacy supported releases. After much discussion on fedora-legacy-list and the #fedora-legacy IRC channel on the freenode network, we have decided to end of life the following releases when FC6 Test2 is released: Fedora Core 1 Fedora Core 2 This will leave us with supporting just releases 3 and 4 of Fedora Core. As to our Red Hat Linux releases (7.3 and 9) the following has been decided: New issues (bugs) will be accepted until October 1st of this year. No new bugs will be accepted after that mark. All existing bugs will be resolved to the best of our ability by December 31st of this year. What hasn't been completed by then will not be completed by the Fedora Legacy project. This will be the end of Fedora Legacy's support of the Red Hat Linux line of distributions. We will continue focusing our efforts on the Fedora Core line, and improving our integration with the Fedora project in whole. Please watch for more announcements regarding our integration with the Fedora project, and for schedule information should it change (Fedora Core release schedules can and do slip from time to time) Please direct any questions to the fedora-legacy-list at redhat.com email list. -- Jesse Keating RHCE (geek.j2solutions.net) Fedora Legacy Team (www.fedoralegacy.org) GPG Public Key (geek.j2solutions.net/jkeating.j2solutions.pub) -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From nils at lemonbit.nl Sun Jul 23 12:45:30 2006 From: nils at lemonbit.nl (Nils Breunese (Lemonbit Internet)) Date: Sun, 23 Jul 2006 14:45:30 +0200 Subject: Announcing End of Life times (Fedora Core 1, 2, Red Hat Linux 7.3, 9) In-Reply-To: <200607221344.54567.jkeating@j2solutions.net> References: <200607221344.54567.jkeating@j2solutions.net> Message-ID: <6A574BAE-830E-4FF3-A012-966E92911270@lemonbit.nl> Jesse Keating wrote: > With Fedora Core 6 Test 2 set to be released July 26th, it is time > we announce > the End of Life of our various Legacy supported releases. > Shouldn't this info be on the website as well? The EOLs are three days away, but I have only seen this info pop up here on this mailinglist. I guess a notice via fedora-announce would be nice as well as probably more FC1/FC2 users subscribe to that list than this one. Maybe this is something for Fedora News as well? Nils Breunese. From mattdm at mattdm.org Sun Jul 23 13:52:16 2006 From: mattdm at mattdm.org (Matthew Miller) Date: Sun, 23 Jul 2006 09:52:16 -0400 Subject: Announcing End of Life times (Fedora Core 1, 2, Red Hat Linux 7.3, 9) In-Reply-To: <6A574BAE-830E-4FF3-A012-966E92911270@lemonbit.nl> References: <200607221344.54567.jkeating@j2solutions.net> <6A574BAE-830E-4FF3-A012-966E92911270@lemonbit.nl> Message-ID: <20060723135216.GA12461@jadzia.bu.edu> On Sun, Jul 23, 2006 at 02:45:30PM +0200, Nils Breunese (Lemonbit Internet) wrote: > Shouldn't this info be on the website as well? The EOLs are three > days away, but I have only seen this info pop up here on this > mailinglist. I guess a notice via fedora-announce would be nice as > well as probably more FC1/FC2 users subscribe to that list than this > one. Maybe this is something for Fedora News as well? Yeah, it's a know problem that the web site needs a total updating. -- Matthew Miller mattdm at mattdm.org Boston University Linux ------> From jkeating at j2solutions.net Sun Jul 23 15:47:20 2006 From: jkeating at j2solutions.net (Jesse Keating) Date: Sun, 23 Jul 2006 11:47:20 -0400 Subject: Announcing End of Life times (Fedora Core 1, 2, Red Hat Linux 7.3, 9) In-Reply-To: <20060723135216.GA12461@jadzia.bu.edu> References: <200607221344.54567.jkeating@j2solutions.net> <6A574BAE-830E-4FF3-A012-966E92911270@lemonbit.nl> <20060723135216.GA12461@jadzia.bu.edu> Message-ID: <200607231147.23295.jkeating@j2solutions.net> On Sunday 23 July 2006 09:52, Matthew Miller wrote: > On Sun, Jul 23, 2006 at 02:45:30PM +0200, Nils Breunese (Lemonbit Internet) wrote: > > Shouldn't this info be on the website as well? The EOLs are three ? > > days away, but I have only seen this info pop up here on this ? > > mailinglist. I guess a notice via fedora-announce would be nice as ? > > well as probably more FC1/FC2 users subscribe to that list than this ? > > one. Maybe this is something for Fedora News as well? > > Yeah, it's a know problem that the web site needs a total updating. I've updated the fedoralegacy.org homepage. I'll forward my announcement on to Fedora News. -- Jesse Keating RHCE (geek.j2solutions.net) Fedora Legacy Team (www.fedoralegacy.org) GPG Public Key (geek.j2solutions.net/jkeating.j2solutions.pub) -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From nils at lemonbit.nl Mon Jul 24 08:39:24 2006 From: nils at lemonbit.nl (Nils Breunese (Lemonbit Internet)) Date: Mon, 24 Jul 2006 10:39:24 +0200 Subject: Squirrelmail 1.4.7 security fixes Message-ID: Hello, I see squirrelmail 1.4.7 fixes several security issues (see http:// www.squirrelmail.org/changelog.php), but I couldn't find any bugs related to these in bugzilla. I'm not a bugzilla wizard however, so I didn't open any, I might just be blind. Can anyone tell me if these issues affect current installations and should bug reports be opened? Nils Breunese. -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 186 bytes Desc: Dit deel van het bericht is digitaal ondertekend URL: From philip at datafoundry.com Mon Jul 24 12:48:38 2006 From: philip at datafoundry.com (Philip Molter) Date: Mon, 24 Jul 2006 07:48:38 -0500 Subject: Announcing End of Life times (Fedora Core 1, 2, Red Hat Linux 7.3, 9) In-Reply-To: <200607221344.54567.jkeating@j2solutions.net> References: <200607221344.54567.jkeating@j2solutions.net> Message-ID: <44C4C1A6.2090602@datafoundry.com> > New issues (bugs) will be accepted until October 1st of this year. No new > bugs will be accepted after that mark. All existing bugs will be resolved to > the best of our ability by December 31st of this year. What hasn't been > completed by then will not be completed by the Fedora Legacy project. This > will be the end of Fedora Legacy's support of the Red Hat Linux line of > distributions. We will continue focusing our efforts on the Fedora Core > line, and improving our integration with the Fedora project in whole. As part of this EOL process, will FL continue to host the old archives of RPMs past the EOL date or will that hosting also be going away? Will FL be doing a final build of all packages for FC2 x86_64 to finally bring the security fixes to that architecture (old Fedora updates are built for x86_64, just not legacy updates)? It would be a nice thing to do, as there are some packages (PHP, for example) that don't compile right out of the source RPM for x86_64. Philip From jkeating at j2solutions.net Mon Jul 24 18:30:53 2006 From: jkeating at j2solutions.net (Jesse Keating) Date: Mon, 24 Jul 2006 14:30:53 -0400 Subject: Announcing End of Life times (Fedora Core 1, 2, Red Hat Linux 7.3, 9 ) In-Reply-To: <44C4C1A6.2090602@datafoundry.com> References: <200607221344.54567.jkeating@j2solutions.net> <44C4C1A6.2090602@datafoundry.com> Message-ID: <200607241430.53320.jkeating@j2solutions.net> On Monday 24 July 2006 08:48, Philip Molter wrote: > As part of this EOL process, will FL continue to host the old archives > of RPMs past the EOL date or will that hosting also be going away? > > Will FL be doing a final build of all packages for FC2 x86_64 to finally > bring the security fixes to that architecture (old Fedora updates are > built for x86_64, just not legacy updates)? ?It would be a nice thing to > do, as there are some packages (PHP, for example) that don't compile > right out of the source RPM for x86_64. yes, I think we can do this. For efficiency, I'd like to just rebuild then and push them to the update repo w/out sending update announcements and such. Any objections? -- Jesse Keating RHCE (geek.j2solutions.net) Fedora Legacy Team (www.fedoralegacy.org) GPG Public Key (geek.j2solutions.net/jkeating.j2solutions.pub) -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From philip at datafoundry.com Mon Jul 24 18:37:46 2006 From: philip at datafoundry.com (Philip Molter) Date: Mon, 24 Jul 2006 13:37:46 -0500 Subject: Announcing End of Life times (Fedora Core 1, 2, Red Hat Linux 7.3, 9 ) In-Reply-To: <200607241430.53320.jkeating@j2solutions.net> References: <200607221344.54567.jkeating@j2solutions.net> <44C4C1A6.2090602@datafoundry.com> <200607241430.53320.jkeating@j2solutions.net> Message-ID: <44C5137A.2010306@datafoundry.com> Jesse Keating wrote: > On Monday 24 July 2006 08:48, Philip Molter wrote: >> As part of this EOL process, will FL continue to host the old archives >> of RPMs past the EOL date or will that hosting also be going away? >> >> Will FL be doing a final build of all packages for FC2 x86_64 to finally >> bring the security fixes to that architecture (old Fedora updates are >> built for x86_64, just not legacy updates)? It would be a nice thing to >> do, as there are some packages (PHP, for example) that don't compile >> right out of the source RPM for x86_64. > > yes, I think we can do this. For efficiency, I'd like to just rebuild then > and push them to the update repo w/out sending update announcements and such. > Any objections? That's exactly what I'm be looking for. From marcdeslauriers at videotron.ca Mon Jul 24 21:36:40 2006 From: marcdeslauriers at videotron.ca (Marc Deslauriers) Date: Mon, 24 Jul 2006 17:36:40 -0400 Subject: Squirrelmail 1.4.7 security fixes In-Reply-To: References: Message-ID: <1153777000.26270.13.camel@mdlinux> On Mon, 2006-07-24 at 10:39 +0200, Nils Breunese (Lemonbit Internet) wrote: > I see squirrelmail 1.4.7 fixes several security issues (see http:// > www.squirrelmail.org/changelog.php), but I couldn't find any bugs > related to these in bugzilla. I'm not a bugzilla wizard however, so I > didn't open any, I might just be blind. Can anyone tell me if these > issues affect current installations and should bug reports be opened? Yeah, current installation are probably vulnerable. There are no bugs open against this. Please feel free to open one. Thanks. Marc. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From mattdm at mattdm.org Tue Jul 25 01:35:51 2006 From: mattdm at mattdm.org (Matthew Miller) Date: Mon, 24 Jul 2006 21:35:51 -0400 Subject: Announcing End of Life times (Fedora Core 1, 2, Red Hat Linux 7.3, 9) In-Reply-To: <200607231147.23295.jkeating@j2solutions.net> References: <200607221344.54567.jkeating@j2solutions.net> <6A574BAE-830E-4FF3-A012-966E92911270@lemonbit.nl> <20060723135216.GA12461@jadzia.bu.edu> <200607231147.23295.jkeating@j2solutions.net> Message-ID: <20060725013551.GA17019@jadzia.bu.edu> On Sun, Jul 23, 2006 at 11:47:20AM -0400, Jesse Keating wrote: > I've updated the fedoralegacy.org homepage. I'll forward my announcement on > to Fedora News. Cool, thanks. -- Matthew Miller mattdm at mattdm.org Boston University Linux ------> From tkevans at tkevans.com Tue Jul 25 18:28:44 2006 From: tkevans at tkevans.com (Tim Evans) Date: Tue, 25 Jul 2006 14:28:44 -0400 Subject: All rpm Commands Hang Indefinitely (RH 9) Message-ID: <20060725182844.M99265@tkevans.com> I've just found FedoraLegacy; this is great. I have a batch of RH 9 systems that badly need updating, and have already started working with 'yum' to get them done. One system, however, has hung while installing 'yum' itself per the instructions at http://fedoraproject.org/wiki/Legacy/Yum9Detailed The hang was indefinite; I left it sit all night and shell prompt never returned. Process listing shows 'rpm' still running, even after logging off the terminal; ctrl-c does not kill the process either. Only 'kill -9' will end it. In looking into this, I see all 'rpm' commands (even simple queries) hang in the same way. Man page doesn't mention it, but is there a lockfile somewhere that's holding things up? Or something else? Thanks. -- Tim Evans, TKEvans.com, Inc. | 5 Chestnut Court tkevans at tkevans.com | Owings Mills, MD 21117 http://www.tkevans.com/ | 443-394-3864 http://www.come-here.com/News/ | From jkeating at j2solutions.net Tue Jul 25 18:38:39 2006 From: jkeating at j2solutions.net (Jesse Keating) Date: Tue, 25 Jul 2006 14:38:39 -0400 Subject: All rpm Commands Hang Indefinitely (RH 9) In-Reply-To: <20060725182844.M99265@tkevans.com> References: <20060725182844.M99265@tkevans.com> Message-ID: <200607251438.39878.jkeating@j2solutions.net> On Tuesday 25 July 2006 14:28, Tim Evans wrote: > In looking into this, I see all 'rpm' commands (even simple queries) hang > in the same way. ?Man page doesn't mention it, but is there a lockfile > somewhere that's holding things up? ?Or something else? rm -f /var/lib/rpm/__db* -- Jesse Keating RHCE (geek.j2solutions.net) Fedora Legacy Team (www.fedoralegacy.org) GPG Public Key (geek.j2solutions.net/jkeating.j2solutions.pub) -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From rdieter at math.unl.edu Tue Jul 25 18:37:52 2006 From: rdieter at math.unl.edu (Rex Dieter) Date: Tue, 25 Jul 2006 13:37:52 -0500 Subject: All rpm Commands Hang Indefinitely (RH 9) References: <20060725182844.M99265@tkevans.com> Message-ID: Tim Evans wrote: > The hang was indefinite; I left it sit all night and shell prompt never > returned. Process listing shows 'rpm' still running, even after logging > off > the terminal; ctrl-c does not kill the process either. Only 'kill -9' > will end it. > > In looking into this, I see all 'rpm' commands (even simple queries) hang > in > the same way. Man page doesn't mention it, but is there a lockfile > somewhere > that's holding things up? Or something else? rm -f /var/lib/rpm/__db.* rpm --rebuilddb -- Rex From tkevans at tkevans.com Tue Jul 25 18:48:11 2006 From: tkevans at tkevans.com (Tim Evans) Date: Tue, 25 Jul 2006 14:48:11 -0400 Subject: All rpm Commands Hang Indefinitely (RH 9) In-Reply-To: <200607251438.39878.jkeating@j2solutions.net> References: <20060725182844.M99265@tkevans.com> <200607251438.39878.jkeating@j2solutions.net> Message-ID: <20060725184811.M52002@tkevans.com> On Tue, 25 Jul 2006 14:38:39 -0400, Jesse Keating wrote > On Tuesday 25 July 2006 14:28, Tim Evans wrote: > > In looking into this, I see all 'rpm' commands (even simple queries) hang > > in the same way. Man page doesn't mention it, but is there a lockfile > > somewhere that's holding things up? Or something else? > > rm -f /var/lib/rpm/__db* Thanks. # rpm --rebuilddb error: db4 error(16) from dbenv->remove: Device or resource busy The removed files have reappeared... -- Tim Evans, TKEvans.com, Inc. | 5 Chestnut Court tkevans at tkevans.com | Owings Mills, MD 21117 http://www.tkevans.com/ | 443-394-3864 http://www.come-here.com/News/ | From nils at lemonbit.nl Tue Jul 25 18:50:58 2006 From: nils at lemonbit.nl (Nils Breunese (Lemonbit Internet)) Date: Tue, 25 Jul 2006 20:50:58 +0200 Subject: All rpm Commands Hang Indefinitely (RH 9) In-Reply-To: <20060725182844.M99265@tkevans.com> References: <20060725182844.M99265@tkevans.com> Message-ID: <52894828-36D5-41BE-9425-E6CDC9BE25FF@lemonbit.nl> Tim Evans wrote: > I've just found FedoraLegacy; this is great. I have a batch of RH > 9 systems > that badly need updating, and have already started working with > 'yum' to get > them done. Remember Fedora Legacy will EOL RH9 by the end of this year. Nils Breunese. -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 186 bytes Desc: Dit deel van het bericht is digitaal ondertekend URL: From mattdm at mattdm.org Tue Jul 25 19:12:47 2006 From: mattdm at mattdm.org (Matthew Miller) Date: Tue, 25 Jul 2006 15:12:47 -0400 Subject: All rpm Commands Hang Indefinitely (RH 9) In-Reply-To: <20060725182844.M99265@tkevans.com> References: <20060725182844.M99265@tkevans.com> Message-ID: <20060725191247.GA20409@jadzia.bu.edu> On Tue, Jul 25, 2006 at 02:28:44PM -0400, Tim Evans wrote: > The hang was indefinite; I left it sit all night and shell prompt never > returned. Process listing shows 'rpm' still running, even after logging > off the terminal; ctrl-c does not kill the process either. Only 'kill -9' > will end it. This is a known problem: I think it'd be good for Legacy to ship this update -- we've still got 5 months of nominal RHL9 support. -- Matthew Miller mattdm at mattdm.org Boston University Linux ------> From wesley at aandw.net Tue Jul 25 20:18:01 2006 From: wesley at aandw.net (Wesley Harrell) Date: Tue, 25 Jul 2006 16:18:01 -0400 Subject: Self-Introduction: Wesley Harrell Message-ID: <20060725201801.GA22205@hogtown.bu.edu> Name: Wesley Harrell Location: US, Massachusetts, Somerville Profession: Sysadmin Employer: Boston University Goals and Qualifications: -I am interested in helping QA and other duties as needed for the FC releases being cared for and fed by the Legacy Project. I work with a group of sysadmins and developers on the Boston University Linux Project. We use FC as a base for our desktop releases and it is important that we be able to keep these as stable and secure as possible. One method for doing that is helping with upstream QA. This helps us and the community. -I am experienced with package building, bash scripting, some perl and have been developing with python for a few months (basic scripts, yum plugins). -Trustworthiness. Well if I was dishonest or even had an ethical lapse, my wife would surely find out and I don't need that kind of pain :) Also Matt Miller can hopefully vouch for me as being a trustworthy fellow, right Matt? I have been and will continue to read through the legacy documents, howtos, and other info to become more familiar with the process. If I can be of help please let me know, otherwise I will keep my eye out for bugs or other items that I can assist with. Below is my GPG key, thanks and I look forward to working with you. pub 1024D/3F23A1A9 2003-09-11 Wesley Harrell (AandW.net) Key fingerprint = 90CE 5B5E 4680 160B D42E C308 D0BC 1E65 3F23 A1A9 uid Wesley Harrell (AandW.net) uid Wesley Harrell (AandW.net) sub 1024g/33BA958C 2003-09-11 From mattdm at mattdm.org Tue Jul 25 23:05:06 2006 From: mattdm at mattdm.org (Matthew Miller) Date: Tue, 25 Jul 2006 19:05:06 -0400 Subject: Self-Introduction: Wesley Harrell In-Reply-To: <20060725201801.GA22205@hogtown.bu.edu> References: <20060725201801.GA22205@hogtown.bu.edu> Message-ID: <20060725230506.GA29395@jadzia.bu.edu> On Tue, Jul 25, 2006 at 04:18:01PM -0400, Wesley Harrell wrote: > -Trustworthiness. Well if I was dishonest or even had an ethical > lapse, my wife would surely find out and I don't need that kind of > pain :) Also Matt Miller can hopefully vouch for me as being a > trustworthy fellow, right Matt? Yes indeed. Hi Wes! -- Matthew Miller mattdm at mattdm.org Boston University Linux ------> From smooge at gmail.com Thu Jul 27 21:11:29 2006 From: smooge at gmail.com (Stephen John Smoogen) Date: Thu, 27 Jul 2006 15:11:29 -0600 Subject: Moving Mozilla to Seamonkey Message-ID: <80d7e4090607271411i269557fj8918343cdc2dcf90@mail.gmail.com> I think it might be a good idea to evaluate a change of Firefox/Thunderbird/Mozilla to the latest tree set. This would mean changing Mozilla to Seamonkey, and moving Firefox/Thunderbird to 1.5.x series. I know this is a big change, but is the time to backport fixes worth the headache in time of bug open in this case? -- Stephen J Smoogen. CSIRT/Linux System Administrator From marcdeslauriers at videotron.ca Thu Jul 27 22:08:10 2006 From: marcdeslauriers at videotron.ca (Marc Deslauriers) Date: Thu, 27 Jul 2006 18:08:10 -0400 Subject: Moving Mozilla to Seamonkey In-Reply-To: <80d7e4090607271411i269557fj8918343cdc2dcf90@mail.gmail.com> References: <80d7e4090607271411i269557fj8918343cdc2dcf90@mail.gmail.com> Message-ID: <1154038090.20781.1.camel@mdlinux> On Thu, 2006-07-27 at 15:11 -0600, Stephen John Smoogen wrote: > I think it might be a good idea to evaluate a change of > Firefox/Thunderbird/Mozilla to the latest tree set. This would mean > changing Mozilla to Seamonkey, and moving Firefox/Thunderbird to 1.5.x > series. > > I know this is a big change, but is the time to backport fixes worth > the headache in time of bug open in this case? We should stick to what RHEL is doing. Seamonkey is coming out for RHEL, so that's a change we should make. I suggest waiting to see what happens with Firefox... Marc. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From sundaram at fedoraproject.org Thu Jul 27 22:12:09 2006 From: sundaram at fedoraproject.org (Rahul) Date: Fri, 28 Jul 2006 03:42:09 +0530 Subject: Moving Mozilla to Seamonkey In-Reply-To: <80d7e4090607271411i269557fj8918343cdc2dcf90@mail.gmail.com> References: <80d7e4090607271411i269557fj8918343cdc2dcf90@mail.gmail.com> Message-ID: <44C93A39.4080301@fedoraproject.org> Stephen John Smoogen wrote: > I think it might be a good idea to evaluate a change of > Firefox/Thunderbird/Mozilla to the latest tree set. This would mean > changing Mozilla to Seamonkey, and moving Firefox/Thunderbird to 1.5.x > series. > > I know this is a big change, but is the time to backport fixes worth > the headache in time of bug open in this case? In general, IMO, Fedora Legacy errata policy should be to bump up to the newer upstream version on ancillary packages and backport fixes to only libraries or software that have other visible major dependencies and externally defined interfaces which are known to be used by third parties. If there isnt any opposition to this, I will add this piece of info to the wiki pages and FAQ on legacy. Rahul From marcdeslauriers at videotron.ca Thu Jul 27 22:56:25 2006 From: marcdeslauriers at videotron.ca (Marc Deslauriers) Date: Thu, 27 Jul 2006 18:56:25 -0400 Subject: Moving Mozilla to Seamonkey In-Reply-To: <44C93A39.4080301@fedoraproject.org> References: <80d7e4090607271411i269557fj8918343cdc2dcf90@mail.gmail.com> <44C93A39.4080301@fedoraproject.org> Message-ID: <1154040985.21064.3.camel@mdlinux> On Fri, 2006-07-28 at 03:42 +0530, Rahul wrote: > In general, IMO, Fedora Legacy errata policy should be to bump up to > the newer upstream version on ancillary packages and backport fixes to > only libraries or software that have other visible major dependencies > and externally defined interfaces which are known to be used by third > parties. If there isnt any opposition to this, I will add this piece of > info to the wiki pages and FAQ on legacy. Who is going to test the bump up to the newer upstream version? We have tried this in the past and got hit by more bugs and more work than simply backporting the security fixes. How do we determine what's considered an ancillary package? Is Firefox an ancillary package? What about PHP or sendmail? Marc. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From sundaram at fedoraproject.org Thu Jul 27 23:10:26 2006 From: sundaram at fedoraproject.org (Rahul) Date: Fri, 28 Jul 2006 04:40:26 +0530 Subject: Moving Mozilla to Seamonkey In-Reply-To: <1154040985.21064.3.camel@mdlinux> References: <80d7e4090607271411i269557fj8918343cdc2dcf90@mail.gmail.com> <44C93A39.4080301@fedoraproject.org> <1154040985.21064.3.camel@mdlinux> Message-ID: <44C947E2.9020608@fedoraproject.org> Marc Deslauriers wrote: > On Fri, 2006-07-28 at 03:42 +0530, Rahul wrote: >> In general, IMO, Fedora Legacy errata policy should be to bump up to >> the newer upstream version on ancillary packages and backport fixes to >> only libraries or software that have other visible major dependencies >> and externally defined interfaces which are known to be used by third >> parties. If there isnt any opposition to this, I will add this piece of >> info to the wiki pages and FAQ on legacy. > > Who is going to test the bump up to the newer upstream version? The same people testing out the current updates. We have > tried this in the past and got hit by more bugs and more work than > simply backporting the security fixes. That would have be to evaluated to judge the merits and there are bound to exceptions either way but in general, would you get any benefits from backporting fixes on say Gaim? > > How do we determine what's considered an ancillary package? Is Firefox > an ancillary package? What about PHP or sendmail? As I pointed out earlier packages there are few criteria's by which we can define them. Desktop packages would be obvious candidates. Rahul From marcdeslauriers at videotron.ca Fri Jul 28 02:46:58 2006 From: marcdeslauriers at videotron.ca (Marc Deslauriers) Date: Thu, 27 Jul 2006 22:46:58 -0400 Subject: Fedora Legacy Test Update Notification: sendmail Message-ID: <44C97AA2.7070403@videotron.ca> --------------------------------------------------------------------- Fedora Legacy Test Update Notification FEDORALEGACY-2006-195418 Bugzilla https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=195418 2006-07-27 --------------------------------------------------------------------- Name : sendmail Versions : rh73: sendmail-8.12.11-4.22.11.legacy Versions : rh9: sendmail-8.12.11-4.24.4.legacy Versions : fc1: sendmail-8.12.11-4.25.4.legacy Versions : fc2: sendmail-8.12.11-4.26.1.legacy Versions : fc3: sendmail-8.13.1-4.legacy Summary : A widely used Mail Transport Agent (MTA). Description : The Sendmail program is a very widely used Mail Transport Agent (MTA). MTAs send mail from one machine to another. Sendmail is not a client program, which you use to read your email. Sendmail is a behind-the-scenes program which actually moves your email over networks or the Internet to where you want it to go. --------------------------------------------------------------------- Update Information: Updated sendmail packages are now available to fix a denial of service security issue. Sendmail is a Mail Transport Agent (MTA) used to send mail between machines. A flaw in the handling of multi-part MIME messages was discovered in Sendmail. A remote attacker could create a carefully crafted message that could crash the sendmail process during delivery (CVE-2006-1173). Users of Sendmail are advised to upgrade to these erratum packages, which contain a backported patch from the Sendmail team to correct this issue. --------------------------------------------------------------------- Changelogs rh73: * Wed Jun 14 2006 David Eisenstein 8.12.11-4.22.11.legacy - Fold in patch for CVE-2006-1173 from RHEL 3. (Next two changelog items). rh9: * Wed Jun 14 2006 David Eisenstein 8.12.11-4.24.4.legacy - Fold in patch for CVE-2006-1173 from RHEL 3. (Next two changelog items). - Bug #195418 fc1: * Wed Jun 14 2006 David Eisenstein 8.12.11-4.24.4.legacy - Fold in patch for CVE-2006-1173 from RHEL 3. (Next two changelog items). - Bug #195418 fc2: * Wed Jun 14 2006 David Eisenstein 8.12.11-4.26.1.legacy - Fold in patch for CVE-2006-1173 from RHEL 3. (Next two changelog items). - Bug #195418 fc3: * Thu Jul 27 2006 Marc Deslauriers 8.13.1-4.legacy - Change release tag * Wed Jun 14 2006 David Eisenstein 8.13.1-3.fc3.1.legacy - Fold in patch for CVE-2006-1173 from RHEL 4. (Next two changelog items). - Bug #195418 --------------------------------------------------------------------- This update can be downloaded from: http://download.fedoralegacy.org/ (sha1sums) rh73: de3219959a42e413f4add01a96fe5bd4e5c2e25b redhat/7.3/updates-testing/i386/sendmail-8.12.11-4.22.11.legacy.i386.rpm 6651ffec675ad29d60dae0b538cc4ab00833b7e9 redhat/7.3/updates-testing/i386/sendmail-cf-8.12.11-4.22.11.legacy.i386.rpm a863e902dac5362e8922e62358f00e76fccfb0dd redhat/7.3/updates-testing/i386/sendmail-devel-8.12.11-4.22.11.legacy.i386.rpm 8b02c451d2ed59b530f3e6976e3bbf4ce0ea535c redhat/7.3/updates-testing/i386/sendmail-doc-8.12.11-4.22.11.legacy.i386.rpm 76086504341d07d4ee88c15a5060c1088d6f3057 redhat/7.3/updates-testing/SRPMS/sendmail-8.12.11-4.22.11.legacy.src.rpm rh9: 31695348a11ac9b47d5470249072f2175131bdab redhat/9/updates-testing/i386/sendmail-8.12.11-4.24.4.legacy.i386.rpm 05c883b5a6b218f69a08c711ca71e4d14d958141 redhat/9/updates-testing/i386/sendmail-cf-8.12.11-4.24.4.legacy.i386.rpm 7bc9aef8a1a8794eb6ad6c8496ede743bc61fd76 redhat/9/updates-testing/i386/sendmail-devel-8.12.11-4.24.4.legacy.i386.rpm 470d3a9ada94a6d1735176050cfa94c8eefc8c70 redhat/9/updates-testing/i386/sendmail-doc-8.12.11-4.24.4.legacy.i386.rpm 5715d14fec8f303271ee7ef3ace828f80af76902 redhat/9/updates-testing/SRPMS/sendmail-8.12.11-4.24.4.legacy.src.rpm fc1: b4e627654290a72eb736678f9ddf6c19031daed6 fedora/1/updates-testing/i386/sendmail-8.12.11-4.25.4.legacy.i386.rpm 6e631fda5b975b4cd40b8e580b1562888addc272 fedora/1/updates-testing/i386/sendmail-cf-8.12.11-4.25.4.legacy.i386.rpm c9e37c442488d4079983ad47d74c843b2e835b52 fedora/1/updates-testing/i386/sendmail-devel-8.12.11-4.25.4.legacy.i386.rpm c3d8da108fb47db91a3bd9513de4e5e403e34656 fedora/1/updates-testing/i386/sendmail-doc-8.12.11-4.25.4.legacy.i386.rpm 1198d4465b351b6555b510fe22ff93c3accdc794 fedora/1/updates-testing/SRPMS/sendmail-8.12.11-4.25.4.legacy.src.rpm fc2: 719954687788a5194cde32eb235d3d542fa62690 fedora/2/updates-testing/i386/sendmail-8.12.11-4.26.1.legacy.i386.rpm 840bf9b1d018965963ceaffec85e0be2dced5345 fedora/2/updates-testing/i386/sendmail-cf-8.12.11-4.26.1.legacy.i386.rpm b44e5ba3a369885111d74232960b3de5e5e1207e fedora/2/updates-testing/i386/sendmail-devel-8.12.11-4.26.1.legacy.i386.rpm 2a8eaa15f1c7e50dbc16542e5d93b88e1933d522 fedora/2/updates-testing/i386/sendmail-doc-8.12.11-4.26.1.legacy.i386.rpm 48fce3c232e313a1648d04bdd0ffe727b1cb9867 fedora/2/updates-testing/SRPMS/sendmail-8.12.11-4.26.1.legacy.src.rpm fc3: 27a009c764d367c5bb32c003ef79611602709808 fedora/3/updates-testing/i386/sendmail-8.13.1-4.legacy.i386.rpm aa4ae72b7747269f6d20519e3fefd83a28e52df6 fedora/3/updates-testing/i386/sendmail-cf-8.13.1-4.legacy.i386.rpm ea0d29481a712d42927f15da4fcc2709d4e5fbd0 fedora/3/updates-testing/i386/sendmail-devel-8.13.1-4.legacy.i386.rpm 428282ff79c56f0f0bda0607612c38ca4253ab04 fedora/3/updates-testing/i386/sendmail-doc-8.13.1-4.legacy.i386.rpm 14661dcec23213f5337e1eba749e8657daf5ef4b fedora/3/updates-testing/x86_64/sendmail-8.13.1-4.legacy.x86_64.rpm c6fdccb6edf57d18aad1c955809ea74cbee333cd fedora/3/updates-testing/x86_64/sendmail-cf-8.13.1-4.legacy.x86_64.rpm 67f50ca7957b1cef314f9ab2e5d5dba81376573c fedora/3/updates-testing/x86_64/sendmail-devel-8.13.1-4.legacy.x86_64.rpm 05be329d3ec2df28d49b1e7f91e2eea9daf0159f fedora/3/updates-testing/x86_64/sendmail-doc-8.13.1-4.legacy.x86_64.rpm 0167c72624710207c4c4b16afdce87e5fb161dd0 fedora/3/updates-testing/SRPMS/sendmail-8.13.1-4.legacy.src.rpm --------------------------------------------------------------------- Please test and comment in bugzilla. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: OpenPGP digital signature URL: From marcdeslauriers at videotron.ca Fri Jul 28 02:46:12 2006 From: marcdeslauriers at videotron.ca (Marc Deslauriers) Date: Thu, 27 Jul 2006 22:46:12 -0400 Subject: [FLSA-2006:175040] Updated php packages fix security issues Message-ID: <44C97A74.4090501@videotron.ca> --------------------------------------------------------------------- Fedora Legacy Update Advisory Synopsis: Updated php packages fix security issues Advisory ID: FLSA:175040 Issue date: 2006-07-27 Product: Red Hat Linux, Fedora Core Keywords: Bugfix CVE Names: CVE-2005-2933 CVE-2005-3883 CVE-2006-0208 CVE-2006-0996 CVE-2006-1490 CVE-2006-1990 --------------------------------------------------------------------- --------------------------------------------------------------------- 1. Topic: Updated PHP packages that fix multiple security issues are now available. PHP is an HTML-embedded scripting language commonly used with the Apache HTTP Web server. 2. Relevant releases/architectures: Red Hat Linux 7.3 - i386 Red Hat Linux 9 - i386 Fedora Core 1 - i386 Fedora Core 2 - i386 Fedora Core 3 - i386, x86_64 3. Problem description: A buffer overflow flaw was discovered in uw-imap, the University of Washington's IMAP Server. php-imap is compiled against the static c-client libraries from imap and therefore needed to be recompiled against the fixed version. (CVE-2005-2933). An input validation error was found in the "mb_send_mail()" function. An attacker could use this flaw to inject arbitrary headers in a mail sent via a script calling the "mb_send_mail()" function where the "To" parameter can be controlled by the attacker. (CVE-2005-3883) The error handling output was found to not properly escape HTML output in certain cases. An attacker could use this flaw to perform cross-site scripting attacks against sites where both display_errors and html_errors are enabled. (CVE-2006-0208) The phpinfo() PHP function did not properly sanitize long strings. An attacker could use this to perform cross-site scripting attacks against sites that have publicly-available PHP scripts that call phpinfo(). (CVE-2006-0996) The html_entity_decode() PHP function was found to not be binary safe. An attacker could use this flaw to disclose a certain part of the memory. In order for this issue to be exploitable the target site would need to have a PHP script which called the "html_entity_decode()" function with untrusted input from the user and displayed the result. (CVE-2006-1490) The wordwrap() PHP function did not properly check for integer overflow in the handling of the "break" parameter. An attacker who could control the string passed to the "break" parameter could cause a heap overflow. (CVE-2006-1990) Users of PHP should upgrade to these updated packages, which contain backported patches that resolve these issues. 4. Solution: Before applying this update, make sure all previously released errata relevant to your system have been applied. To update all RPMs for your particular architecture, run: rpm -Fvh [filenames] where [filenames] is a list of the RPMs you wish to upgrade. Only those RPMs which are currently installed will be updated. Those RPMs which are not installed but included in the list will not be updated. Note that you can also use wildcards (*.rpm) if your current directory *only* contains the desired RPMs. Please note that this update is also available via yum and apt. Many people find this an easier way to apply updates. To use yum issue: yum update or to use apt: apt-get update; apt-get upgrade This will start an interactive process that will result in the appropriate RPMs being upgraded on your system. This assumes that you have yum or apt-get configured for obtaining Fedora Legacy content. Please visit http://www.fedoralegacy.org/docs for directions on how to configure yum and apt-get. 5. Bug IDs fixed: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=175040 6. RPMs required: Red Hat Linux 7.3: SRPM: http://download.fedoralegacy.org/redhat/7.3/updates/SRPMS/php-4.1.2-7.3.20.legacy.src.rpm i386: http://download.fedoralegacy.org/redhat/7.3/updates/i386/php-4.1.2-7.3.20.legacy.i386.rpm http://download.fedoralegacy.org/redhat/7.3/updates/i386/php-devel-4.1.2-7.3.20.legacy.i386.rpm http://download.fedoralegacy.org/redhat/7.3/updates/i386/php-imap-4.1.2-7.3.20.legacy.i386.rpm http://download.fedoralegacy.org/redhat/7.3/updates/i386/php-ldap-4.1.2-7.3.20.legacy.i386.rpm http://download.fedoralegacy.org/redhat/7.3/updates/i386/php-manual-4.1.2-7.3.20.legacy.i386.rpm http://download.fedoralegacy.org/redhat/7.3/updates/i386/php-mysql-4.1.2-7.3.20.legacy.i386.rpm http://download.fedoralegacy.org/redhat/7.3/updates/i386/php-odbc-4.1.2-7.3.20.legacy.i386.rpm http://download.fedoralegacy.org/redhat/7.3/updates/i386/php-pgsql-4.1.2-7.3.20.legacy.i386.rpm http://download.fedoralegacy.org/redhat/7.3/updates/i386/php-snmp-4.1.2-7.3.20.legacy.i386.rpm Red Hat Linux 9: SRPM: http://download.fedoralegacy.org/redhat/9/updates/SRPMS/php-4.2.2-17.21.legacy.src.rpm i386: http://download.fedoralegacy.org/redhat/9/updates/i386/php-4.2.2-17.21.legacy.i386.rpm http://download.fedoralegacy.org/redhat/9/updates/i386/php-devel-4.2.2-17.21.legacy.i386.rpm http://download.fedoralegacy.org/redhat/9/updates/i386/php-imap-4.2.2-17.21.legacy.i386.rpm http://download.fedoralegacy.org/redhat/9/updates/i386/php-ldap-4.2.2-17.21.legacy.i386.rpm http://download.fedoralegacy.org/redhat/9/updates/i386/php-manual-4.2.2-17.21.legacy.i386.rpm http://download.fedoralegacy.org/redhat/9/updates/i386/php-mysql-4.2.2-17.21.legacy.i386.rpm http://download.fedoralegacy.org/redhat/9/updates/i386/php-odbc-4.2.2-17.21.legacy.i386.rpm http://download.fedoralegacy.org/redhat/9/updates/i386/php-pgsql-4.2.2-17.21.legacy.i386.rpm http://download.fedoralegacy.org/redhat/9/updates/i386/php-snmp-4.2.2-17.21.legacy.i386.rpm Fedora Core 1: SRPM: http://download.fedoralegacy.org/fedora/1/updates/SRPMS/php-4.3.11-1.fc1.6.legacy.src.rpm i386: http://download.fedoralegacy.org/fedora/1/updates/i386/php-4.3.11-1.fc1.6.legacy.i386.rpm http://download.fedoralegacy.org/fedora/1/updates/i386/php-devel-4.3.11-1.fc1.6.legacy.i386.rpm http://download.fedoralegacy.org/fedora/1/updates/i386/php-domxml-4.3.11-1.fc1.6.legacy.i386.rpm http://download.fedoralegacy.org/fedora/1/updates/i386/php-imap-4.3.11-1.fc1.6.legacy.i386.rpm http://download.fedoralegacy.org/fedora/1/updates/i386/php-ldap-4.3.11-1.fc1.6.legacy.i386.rpm http://download.fedoralegacy.org/fedora/1/updates/i386/php-mbstring-4.3.11-1.fc1.6.legacy.i386.rpm http://download.fedoralegacy.org/fedora/1/updates/i386/php-mysql-4.3.11-1.fc1.6.legacy.i386.rpm http://download.fedoralegacy.org/fedora/1/updates/i386/php-odbc-4.3.11-1.fc1.6.legacy.i386.rpm http://download.fedoralegacy.org/fedora/1/updates/i386/php-pgsql-4.3.11-1.fc1.6.legacy.i386.rpm http://download.fedoralegacy.org/fedora/1/updates/i386/php-snmp-4.3.11-1.fc1.6.legacy.i386.rpm http://download.fedoralegacy.org/fedora/1/updates/i386/php-xmlrpc-4.3.11-1.fc1.6.legacy.i386.rpm Fedora Core 2: SRPM: http://download.fedoralegacy.org/fedora/2/updates/SRPMS/php-4.3.11-1.fc2.7.legacy.src.rpm i386: http://download.fedoralegacy.org/fedora/2/updates/i386/php-4.3.11-1.fc2.7.legacy.i386.rpm http://download.fedoralegacy.org/fedora/2/updates/i386/php-devel-4.3.11-1.fc2.7.legacy.i386.rpm http://download.fedoralegacy.org/fedora/2/updates/i386/php-domxml-4.3.11-1.fc2.7.legacy.i386.rpm http://download.fedoralegacy.org/fedora/2/updates/i386/php-imap-4.3.11-1.fc2.7.legacy.i386.rpm http://download.fedoralegacy.org/fedora/2/updates/i386/php-ldap-4.3.11-1.fc2.7.legacy.i386.rpm http://download.fedoralegacy.org/fedora/2/updates/i386/php-mbstring-4.3.11-1.fc2.7.legacy.i386.rpm http://download.fedoralegacy.org/fedora/2/updates/i386/php-mysql-4.3.11-1.fc2.7.legacy.i386.rpm http://download.fedoralegacy.org/fedora/2/updates/i386/php-odbc-4.3.11-1.fc2.7.legacy.i386.rpm http://download.fedoralegacy.org/fedora/2/updates/i386/php-pear-4.3.11-1.fc2.7.legacy.i386.rpm http://download.fedoralegacy.org/fedora/2/updates/i386/php-pgsql-4.3.11-1.fc2.7.legacy.i386.rpm http://download.fedoralegacy.org/fedora/2/updates/i386/php-snmp-4.3.11-1.fc2.7.legacy.i386.rpm http://download.fedoralegacy.org/fedora/2/updates/i386/php-xmlrpc-4.3.11-1.fc2.7.legacy.i386.rpm Fedora Core 3: SRPM: http://download.fedoralegacy.org/fedora/3/updates/SRPMS/php-4.3.11-2.8.4.legacy.src.rpm i386: http://download.fedoralegacy.org/fedora/3/updates/i386/php-4.3.11-2.8.4.legacy.i386.rpm http://download.fedoralegacy.org/fedora/3/updates/i386/php-devel-4.3.11-2.8.4.legacy.i386.rpm http://download.fedoralegacy.org/fedora/3/updates/i386/php-domxml-4.3.11-2.8.4.legacy.i386.rpm http://download.fedoralegacy.org/fedora/3/updates/i386/php-gd-4.3.11-2.8.4.legacy.i386.rpm http://download.fedoralegacy.org/fedora/3/updates/i386/php-imap-4.3.11-2.8.4.legacy.i386.rpm http://download.fedoralegacy.org/fedora/3/updates/i386/php-ldap-4.3.11-2.8.4.legacy.i386.rpm http://download.fedoralegacy.org/fedora/3/updates/i386/php-mbstring-4.3.11-2.8.4.legacy.i386.rpm http://download.fedoralegacy.org/fedora/3/updates/i386/php-mysql-4.3.11-2.8.4.legacy.i386.rpm http://download.fedoralegacy.org/fedora/3/updates/i386/php-ncurses-4.3.11-2.8.4.legacy.i386.rpm http://download.fedoralegacy.org/fedora/3/updates/i386/php-odbc-4.3.11-2.8.4.legacy.i386.rpm http://download.fedoralegacy.org/fedora/3/updates/i386/php-pear-4.3.11-2.8.4.legacy.i386.rpm http://download.fedoralegacy.org/fedora/3/updates/i386/php-pgsql-4.3.11-2.8.4.legacy.i386.rpm http://download.fedoralegacy.org/fedora/3/updates/i386/php-snmp-4.3.11-2.8.4.legacy.i386.rpm http://download.fedoralegacy.org/fedora/3/updates/i386/php-xmlrpc-4.3.11-2.8.4.legacy.i386.rpm x86_64: http://download.fedoralegacy.org/fedora/3/updates/x86_64/php-4.3.11-2.8.4.legacy.x86_64.rpm http://download.fedoralegacy.org/fedora/3/updates/x86_64/php-devel-4.3.11-2.8.4.legacy.x86_64.rpm http://download.fedoralegacy.org/fedora/3/updates/x86_64/php-domxml-4.3.11-2.8.4.legacy.x86_64.rpm http://download.fedoralegacy.org/fedora/3/updates/x86_64/php-gd-4.3.11-2.8.4.legacy.x86_64.rpm http://download.fedoralegacy.org/fedora/3/updates/x86_64/php-imap-4.3.11-2.8.4.legacy.x86_64.rpm http://download.fedoralegacy.org/fedora/3/updates/x86_64/php-ldap-4.3.11-2.8.4.legacy.x86_64.rpm http://download.fedoralegacy.org/fedora/3/updates/x86_64/php-mbstring-4.3.11-2.8.4.legacy.x86_64.rpm http://download.fedoralegacy.org/fedora/3/updates/x86_64/php-mysql-4.3.11-2.8.4.legacy.x86_64.rpm http://download.fedoralegacy.org/fedora/3/updates/x86_64/php-ncurses-4.3.11-2.8.4.legacy.x86_64.rpm http://download.fedoralegacy.org/fedora/3/updates/x86_64/php-odbc-4.3.11-2.8.4.legacy.x86_64.rpm http://download.fedoralegacy.org/fedora/3/updates/x86_64/php-pear-4.3.11-2.8.4.legacy.x86_64.rpm http://download.fedoralegacy.org/fedora/3/updates/x86_64/php-pgsql-4.3.11-2.8.4.legacy.x86_64.rpm http://download.fedoralegacy.org/fedora/3/updates/x86_64/php-snmp-4.3.11-2.8.4.legacy.x86_64.rpm http://download.fedoralegacy.org/fedora/3/updates/x86_64/php-xmlrpc-4.3.11-2.8.4.legacy.x86_64.rpm 7. Verification: SHA1 sum Package Name --------------------------------------------------------------------- rh73: 716216fdf1ddc42bb8d210d1e121ba8d0e7f4d7c redhat/7.3/updates/i386/php-4.1.2-7.3.20.legacy.i386.rpm 61612a0c2e6244ccfb4e35ea04865d48f75f7c48 redhat/7.3/updates/i386/php-devel-4.1.2-7.3.20.legacy.i386.rpm d29efdfdd669875715c0956fedc59b99ef7681f3 redhat/7.3/updates/i386/php-imap-4.1.2-7.3.20.legacy.i386.rpm 1e09ae807ccf160ef9011818d4dda590bab224d7 redhat/7.3/updates/i386/php-ldap-4.1.2-7.3.20.legacy.i386.rpm 0dfa25adffe75db47fbf2a366eb456d8fcfca918 redhat/7.3/updates/i386/php-manual-4.1.2-7.3.20.legacy.i386.rpm 9141e782d32739b5bc2a9b611d7cdc352e523c26 redhat/7.3/updates/i386/php-mysql-4.1.2-7.3.20.legacy.i386.rpm f1e88cf8e7f644f81473efc561f4df502ef7bc24 redhat/7.3/updates/i386/php-odbc-4.1.2-7.3.20.legacy.i386.rpm dd58b7187e116874558c5567b8c6897d1d1d4154 redhat/7.3/updates/i386/php-pgsql-4.1.2-7.3.20.legacy.i386.rpm 0575467b89a44d1e5b0bebc00fac018666a8b827 redhat/7.3/updates/i386/php-snmp-4.1.2-7.3.20.legacy.i386.rpm 8541c7eefbf6162eeca5f12f834ccf3af8fee85b redhat/7.3/updates/SRPMS/php-4.1.2-7.3.20.legacy.src.rpm rh9: 1cd4a11bf52c1b18dce2937a7f15789b059c1967 redhat/9/updates/i386/php-4.2.2-17.21.legacy.i386.rpm 109a96dc0633b661e6789d9b41a3cf298e140401 redhat/9/updates/i386/php-devel-4.2.2-17.21.legacy.i386.rpm f5df6f259745f0050c15a50b75e2114381c07fb1 redhat/9/updates/i386/php-imap-4.2.2-17.21.legacy.i386.rpm 8223f6cc4e84478523cd8560bdc9b75d90c33a14 redhat/9/updates/i386/php-ldap-4.2.2-17.21.legacy.i386.rpm 18ac761d897ba89e94086facdb7b529e7d60c0e2 redhat/9/updates/i386/php-manual-4.2.2-17.21.legacy.i386.rpm 714057b386abaa03573d14c8757ef97858ba2b17 redhat/9/updates/i386/php-mysql-4.2.2-17.21.legacy.i386.rpm c2002f4f520ea2f7dbe11402ad460a181c44175a redhat/9/updates/i386/php-odbc-4.2.2-17.21.legacy.i386.rpm 26a858731e032c0622003c8d9398a6b5ead86b24 redhat/9/updates/i386/php-pgsql-4.2.2-17.21.legacy.i386.rpm 258887bd3e690dad1b88dfcbc280a8523fa52338 redhat/9/updates/i386/php-snmp-4.2.2-17.21.legacy.i386.rpm fe815ab1d505fcef7629e0abe4b25f2c66054f1c redhat/9/updates/SRPMS/php-4.2.2-17.21.legacy.src.rpm fc1: 5cc63a63de0057797737ceefbdfeb0f466d87beb fedora/1/updates/i386/php-4.3.11-1.fc1.6.legacy.i386.rpm 315b0ae174f33d437178982f47dd24ba48848346 fedora/1/updates/i386/php-devel-4.3.11-1.fc1.6.legacy.i386.rpm 92d36fe3e062b33e6b22bcd101dd85dc03803616 fedora/1/updates/i386/php-domxml-4.3.11-1.fc1.6.legacy.i386.rpm 7083eb87cdcb9e83ef83e6ba7aee63a2a259ce89 fedora/1/updates/i386/php-imap-4.3.11-1.fc1.6.legacy.i386.rpm acb18926452c2faf331fc8b25a09de3f4da2d7cb fedora/1/updates/i386/php-ldap-4.3.11-1.fc1.6.legacy.i386.rpm c90c744840ebff6c9149b9df9513db63a10a6247 fedora/1/updates/i386/php-mbstring-4.3.11-1.fc1.6.legacy.i386.rpm e84b242476b61b0aa19b2b71af4f69043cc4ecee fedora/1/updates/i386/php-mysql-4.3.11-1.fc1.6.legacy.i386.rpm a765f1e3d73d9d5cbd1fb5cbfb868f70baf2ce4a fedora/1/updates/i386/php-odbc-4.3.11-1.fc1.6.legacy.i386.rpm 0ef956e24befd3a9b462f0953edc164595ac27cf fedora/1/updates/i386/php-pgsql-4.3.11-1.fc1.6.legacy.i386.rpm e5e9f011f9d403881a9350d5395db6ccaa402b6a fedora/1/updates/i386/php-snmp-4.3.11-1.fc1.6.legacy.i386.rpm f29d6f88cd780e32e9307c1d8ad8446e559c8a29 fedora/1/updates/i386/php-xmlrpc-4.3.11-1.fc1.6.legacy.i386.rpm edbf95d5ea4944e3a41ccebcebaf2702b4545f98 fedora/1/updates/SRPMS/php-4.3.11-1.fc1.6.legacy.src.rpm fc2: f2ec94d1069ff3214ac031f7f5c6a1e29f22e90d fedora/2/updates/i386/php-4.3.11-1.fc2.7.legacy.i386.rpm 34c8d44ccd71a3f09dc289d4f0fc826dc34f9a60 fedora/2/updates/i386/php-devel-4.3.11-1.fc2.7.legacy.i386.rpm 09d8100aea583b0b47f87190b6a557ed3f7e3636 fedora/2/updates/i386/php-domxml-4.3.11-1.fc2.7.legacy.i386.rpm f11bc7846717d98b73e73d9bf9870b2f5e19d341 fedora/2/updates/i386/php-imap-4.3.11-1.fc2.7.legacy.i386.rpm 69d11e09f15a6acb488a28a8e4751f468e332c73 fedora/2/updates/i386/php-ldap-4.3.11-1.fc2.7.legacy.i386.rpm a07b390dc004d6a330c49cf1e8262471c93e9108 fedora/2/updates/i386/php-mbstring-4.3.11-1.fc2.7.legacy.i386.rpm 2820fb1d8832d034b2529ec7087c5839baebccfe fedora/2/updates/i386/php-mysql-4.3.11-1.fc2.7.legacy.i386.rpm ed69c77a9e312348a6ca73ad2d7f270459bc16dc fedora/2/updates/i386/php-odbc-4.3.11-1.fc2.7.legacy.i386.rpm 5ff64a9b70c418ce762ff815be8fcefb5aa89d15 fedora/2/updates/i386/php-pear-4.3.11-1.fc2.7.legacy.i386.rpm 9251da041356734713a644ff778ae4afc2ab2879 fedora/2/updates/i386/php-pgsql-4.3.11-1.fc2.7.legacy.i386.rpm eabd9dd422934c99902429c311f61a4a4a26e3c7 fedora/2/updates/i386/php-snmp-4.3.11-1.fc2.7.legacy.i386.rpm 7b027d1cd8844312ed20711bef92013078e33b83 fedora/2/updates/i386/php-xmlrpc-4.3.11-1.fc2.7.legacy.i386.rpm 026b3dd063586fe6e29f6cb482206e4f5631ac0f fedora/2/updates/SRPMS/php-4.3.11-1.fc2.7.legacy.src.rpm fc3: cafefc39811f7923007e522aa5ca84a0e073dd96 fedora/3/updates/i386/php-4.3.11-2.8.4.legacy.i386.rpm e2d84ad62c2703b5a7f3875d0d52e9461f5f81fe fedora/3/updates/i386/php-devel-4.3.11-2.8.4.legacy.i386.rpm 7b90726025ff13e815509216a73fa9c2914a6ad0 fedora/3/updates/i386/php-domxml-4.3.11-2.8.4.legacy.i386.rpm 6367004e4200fcb44778088c911495458b08cde4 fedora/3/updates/i386/php-gd-4.3.11-2.8.4.legacy.i386.rpm abb3cdd3dcc030b85e03a409372daac6093a63d0 fedora/3/updates/i386/php-imap-4.3.11-2.8.4.legacy.i386.rpm df673e8e983ea6cec3b50f65e50950f625493223 fedora/3/updates/i386/php-ldap-4.3.11-2.8.4.legacy.i386.rpm 4e95b2f44661683fd17c72f881323f36757793ef fedora/3/updates/i386/php-mbstring-4.3.11-2.8.4.legacy.i386.rpm a891c751c82acc9bf1cc6ac59332196344b42a8c fedora/3/updates/i386/php-mysql-4.3.11-2.8.4.legacy.i386.rpm 865dde39429ac6fc59296af9ed938c4e7b30216c fedora/3/updates/i386/php-ncurses-4.3.11-2.8.4.legacy.i386.rpm 32b5075e4e3406c4ab9715ef970f1e5ec4f808e3 fedora/3/updates/i386/php-odbc-4.3.11-2.8.4.legacy.i386.rpm 5867c11e75d26edbcd79e815bc79a1c2354878ec fedora/3/updates/i386/php-pear-4.3.11-2.8.4.legacy.i386.rpm 5f05fae3bc0ef2841ed479cb5968443fee448698 fedora/3/updates/i386/php-pgsql-4.3.11-2.8.4.legacy.i386.rpm 71591b13628f0db7a0818c9bb818b63e176c9904 fedora/3/updates/i386/php-snmp-4.3.11-2.8.4.legacy.i386.rpm c5f9dcb4c6e8bc117b88ffa06a60049a80f68287 fedora/3/updates/i386/php-xmlrpc-4.3.11-2.8.4.legacy.i386.rpm 78fb1d65369f96b86027bc04e91d2c058fbd1e73 fedora/3/updates/x86_64/php-4.3.11-2.8.4.legacy.x86_64.rpm 102f14f60d3dc134cb6f698f6d4d1f4264006940 fedora/3/updates/x86_64/php-devel-4.3.11-2.8.4.legacy.x86_64.rpm 333d7213daf29f486ad7e047e1adc418c3258500 fedora/3/updates/x86_64/php-domxml-4.3.11-2.8.4.legacy.x86_64.rpm 59c18b269a3a1712684d8fab00c7577033ac2108 fedora/3/updates/x86_64/php-gd-4.3.11-2.8.4.legacy.x86_64.rpm ce155d28b0e81eb5527cf0e2f496bc8a9e5ce75d fedora/3/updates/x86_64/php-imap-4.3.11-2.8.4.legacy.x86_64.rpm 39e63584c3419002a43d71973ff93a356fc278c0 fedora/3/updates/x86_64/php-ldap-4.3.11-2.8.4.legacy.x86_64.rpm b5131dae7d6908114b959d3ab0e1661158e66e0f fedora/3/updates/x86_64/php-mbstring-4.3.11-2.8.4.legacy.x86_64.rpm 5b366cf0918e314c52e2da44baac70c81dd6fa38 fedora/3/updates/x86_64/php-mysql-4.3.11-2.8.4.legacy.x86_64.rpm eae4616e39e8a82a4cf931352d4610a293499e5e fedora/3/updates/x86_64/php-ncurses-4.3.11-2.8.4.legacy.x86_64.rpm c3c95fb30901f381376be17003f29ed36a7f22d8 fedora/3/updates/x86_64/php-odbc-4.3.11-2.8.4.legacy.x86_64.rpm 4bc178a084fe1df33ac0a92c15f8d7b817f4a2c7 fedora/3/updates/x86_64/php-pear-4.3.11-2.8.4.legacy.x86_64.rpm 9ce8349a77d7817e505629c5944a9c7c59a6e284 fedora/3/updates/x86_64/php-pgsql-4.3.11-2.8.4.legacy.x86_64.rpm d631abea1dd6cad2bd3d16d52877b5b3f310a2f5 fedora/3/updates/x86_64/php-snmp-4.3.11-2.8.4.legacy.x86_64.rpm c91a27a8bf159f2586d0d6e8ba1ce07f4651e5bd fedora/3/updates/x86_64/php-xmlrpc-4.3.11-2.8.4.legacy.x86_64.rpm b560a17c4ad7954b0184660d900ea2bb37ee1b4a fedora/3/updates/SRPMS/php-4.3.11-2.8.4.legacy.src.rpm These packages are GPG signed by Fedora Legacy for security. Our key is available from http://www.fedoralegacy.org/about/security.php You can verify each package with the following command: rpm --checksig -v If you only wish to verify that each package has not been corrupted or tampered with, examine only the sha1sum with the following command: sha1sum 8. References: http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2005-2933 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2005-3883 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-0208 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-0996 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-1490 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-1990 9. Contact: The Fedora Legacy security contact is . More project details at http://www.fedoralegacy.org --------------------------------------------------------------------- -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: OpenPGP digital signature URL: From jpdalbec at ysu.edu Fri Jul 28 20:13:49 2006 From: jpdalbec at ysu.edu (John Dalbec) Date: Fri, 28 Jul 2006 16:13:49 -0400 Subject: MySQL CVE-2006-3469 Message-ID: <44CA6FFD.20609@ysu.edu> Does this affect Fedora-Legacy? 06.29.31 CVE: CVE-2006-3469 Platform: Cross Platform Title: MySQL Server Date_Format Denial of Service Description: MySQL is susceptible to a remote denial of service vulnerability because the database server fails if the "select date_format" SQL function is called with "('%d%s', 1);" argument. MySQL versions prior to 4.1.18, 5.0.19 and 5.1.6 are affected. Ref: http://www.securityfocus.com/bid/19032 From jpdalbec at ysu.edu Fri Jul 28 21:06:35 2006 From: jpdalbec at ysu.edu (John Dalbec) Date: Fri, 28 Jul 2006 17:06:35 -0400 Subject: CVE-2006-3672 KDE Konqueror ReplaceChild Denial of Service Message-ID: <44CA7C5B.6050609@ysu.edu> Does this affect Fedora-Legacy? Which KDE package contains Konqueror? 06.28.23 CVE: CVE-2006-3672 Platform: Unix Title: KDE Konqueror ReplaceChild Denial of Service Description: KDE Konqueror is prone to a denial of service vulnerability. The vulnerability presents itself when the browser processes the "replaceChild()" method for any DOM element. KDE Konqueror version 3.5.1 is affected. Ref: http://www.securityfocus.com/bid/18978 From tthome at cox.net Fri Jul 28 21:00:58 2006 From: tthome at cox.net (Tim Thome) Date: Fri, 28 Jul 2006 14:00:58 -0700 Subject: MySQL CVE-2006-3469 In-Reply-To: <44CA6FFD.20609@ysu.edu> References: <44CA6FFD.20609@ysu.edu> Message-ID: John, It affects FC3 and earlier as included with the distributions. FC4 is currently including 4.1.20 on the updates-released directory. Do note that FC3 can run the regular mysql rpm's as provided by mysql... so an advisory should be posted (imho)... Not sure about FC1/2 (I moved over to FC3 from another distro) Tim On Jul 28, 2006, at 1:13 PM, John Dalbec wrote: > Does this affect Fedora-Legacy? > > 06.29.31 CVE: CVE-2006-3469 > Platform: Cross Platform > Title: MySQL Server Date_Format Denial of Service > Description: MySQL is susceptible to a remote denial of service > vulnerability because the database server fails if the "select > date_format" SQL function is called with "('%d%s', 1);" argument. > MySQL versions prior to 4.1.18, 5.0.19 and 5.1.6 are affected. > Ref: http://www.securityfocus.com/bid/19032 > > -- > fedora-legacy-list mailing list > fedora-legacy-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-legacy-list From nils at lemonbit.nl Sun Jul 30 12:47:08 2006 From: nils at lemonbit.nl (Nils Breunese (Lemonbit Internet)) Date: Sun, 30 Jul 2006 14:47:08 +0200 Subject: FL repositories down? Message-ID: <836FBB68-3998-4292-83C5-B1A101D466EF@lemonbit.nl> Hi all, My servers are currently unable to run yum update because the Fedora Legacy repositories seem unavailable. I also can't get to http:// download.fedoralegacy.org/fedora/3 in my browser. Is this known downtime or is the problem on my end? Nils Breunese. From skvidal at linux.duke.edu Sun Jul 30 12:54:51 2006 From: skvidal at linux.duke.edu (seth vidal) Date: Sun, 30 Jul 2006 08:54:51 -0400 Subject: FL repositories down? In-Reply-To: <836FBB68-3998-4292-83C5-B1A101D466EF@lemonbit.nl> References: <836FBB68-3998-4292-83C5-B1A101D466EF@lemonbit.nl> Message-ID: <1154264091.10327.26.camel@cutter> On Sun, 2006-07-30 at 14:47 +0200, Nils Breunese wrote: > Hi all, > > My servers are currently unable to run yum update because the Fedora > Legacy repositories seem unavailable. I also can't get to http:// > download.fedoralegacy.org/fedora/3 in my browser. Is this known > downtime or is the problem on my end? > this should be fixed, now. -sv From nils at lemonbit.nl Sun Jul 30 13:02:54 2006 From: nils at lemonbit.nl (Nils Breunese (Lemonbit Internet)) Date: Sun, 30 Jul 2006 15:02:54 +0200 Subject: FL repositories down? In-Reply-To: <1154264091.10327.26.camel@cutter> References: <836FBB68-3998-4292-83C5-B1A101D466EF@lemonbit.nl> <1154264091.10327.26.camel@cutter> Message-ID: <5B56471A-E5F8-4E95-AB05-A099676A04FB@lemonbit.nl> Seth Vidal wrote: > On Sun, 2006-07-30 at 14:47 +0200, Nils Breunese wrote: >> >> My servers are currently unable to run yum update because the Fedora >> Legacy repositories seem unavailable. I also can't get to http:// >> download.fedoralegacy.org/fedora/3 in my browser. Is this known >> downtime or is the problem on my end? > > this should be fixed, now. It is, thanks. Nils Breunese. From gerry at pathtech.org Sun Jul 30 13:16:32 2006 From: gerry at pathtech.org (G. Roderick Singleton) Date: Sun, 30 Jul 2006 09:16:32 -0400 Subject: FL repositories down? In-Reply-To: <1154264091.10327.26.camel@cutter> References: <836FBB68-3998-4292-83C5-B1A101D466EF@lemonbit.nl> <1154264091.10327.26.camel@cutter> Message-ID: <1154265392.3649.37.camel@www.pathtech.org> On Sun, 2006-07-30 at 08:54 -0400, seth vidal wrote: > On Sun, 2006-07-30 at 14:47 +0200, Nils Breunese wrote: > > Hi all, > > > > My servers are currently unable to run yum update because the Fedora > > Legacy repositories seem unavailable. I also can't get to http:// > > download.fedoralegacy.org/fedora/3 in my browser. Is this known > > downtime or is the problem on my end? > > > > this should be fixed, now. > > Nope. Not fixed. Get Err http://download.fedoralegacy.org apt/redhat/9/i386/updates php-devel 4.2.2-17.21.legacy Could not connect to download.fedoralegacy.org:80 (152.3.183.83). - connect (111 Connection refused) Get:1 http://dl.atrpms.net rh9-i386/atrpms/stable autofs 1:4.1.3-0_12.rh9.at [130kB] Fetched 130kB in 2s (53.4kB/s) Failed to fetch http://download.fedoralegacy.org/apt/redhat/9/i386/RPMS.updates/php-devel-4.2.2-17.21.legacy.i386.rpm Could not connect to download.fedoralegacy.org:80 (152.3.183.83). - connect (111 Connection refused) E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing? when attempting to upgrade. -- G. Roderick Singleton PATH tech -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 1956 bytes Desc: not available URL: From jkeating at j2solutions.net Sun Jul 30 13:54:14 2006 From: jkeating at j2solutions.net (Jesse Keating) Date: Sun, 30 Jul 2006 09:54:14 -0400 Subject: FL repositories down? In-Reply-To: <1154265392.3649.37.camel@www.pathtech.org> References: <836FBB68-3998-4292-83C5-B1A101D466EF@lemonbit.nl> <1154264091.10327.26.camel@cutter> <1154265392.3649.37.camel@www.pathtech.org> Message-ID: <200607300954.20617.jkeating@j2solutions.net> On Sunday 30 July 2006 09:16, G. Roderick Singleton wrote: > ? ? ? ? Nope. Not fixed. Get Err http://download.fedoralegacy.org > ? ? ? ? apt/redhat/9/i386/updates php-devel 4.2.2-17.21.legacy It is now. Load was very high. -- Jesse Keating RHCE (geek.j2solutions.net) Fedora Legacy Team (www.fedoralegacy.org) GPG Public Key (geek.j2solutions.net/jkeating.j2solutions.pub) -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From nils at lemonbit.nl Mon Jul 31 09:36:17 2006 From: nils at lemonbit.nl (Nils Breunese (Lemonbit Internet)) Date: Mon, 31 Jul 2006 11:36:17 +0200 Subject: FC1/2 EOL? FC4 legacy? Message-ID: Hello list, I was just wondering what the status of the EOL of FC1 and FC2 is and whether FC4 has already entered FL. On the website there's the announcement that the EOL will be on July 26. Has support indeed been suspended by that day? The website still mentions FC1-3 being supported and there is no mention of FC4. What's happening? Nils Breunese. From sheltren at cs.ucsb.edu Mon Jul 31 10:33:23 2006 From: sheltren at cs.ucsb.edu (Jeff Sheltren) Date: Mon, 31 Jul 2006 06:33:23 -0400 Subject: FC1/2 EOL? FC4 legacy? In-Reply-To: References: Message-ID: On Jul 31, 2006, at 5:36 AM, Nils Breunese (Lemonbit Internet) wrote: > Hello list, > > I was just wondering what the status of the EOL of FC1 and FC2 is > and whether FC4 has already entered FL. On the website there's the > announcement that the EOL will be on July 26. Has support indeed > been suspended by that day? The website still mentions FC1-3 being > supported and there is no mention of FC4. What's happening? > > Nils Breunese. > As far as I know, the release of FC6 test 2 has been delayed. Once it is released, legacy will pick up FC4 and drop FC1 & FC2. -Jeff From jkeating at j2solutions.net Mon Jul 31 11:41:33 2006 From: jkeating at j2solutions.net (Jesse Keating) Date: Mon, 31 Jul 2006 07:41:33 -0400 Subject: FC1/2 EOL? FC4 legacy? In-Reply-To: References: Message-ID: <200607310741.43718.jkeating@j2solutions.net> On Monday 31 July 2006 05:36, Nils Breunese (Lemonbit Internet) wrote: > I was just wondering what the status of the EOL of FC1 and FC2 is and ? > whether FC4 has already entered FL. On the website there's the ? > announcement that the EOL will be on July 26. Has support indeed been ? > suspended by that day? The website still mentions FC1-3 being ? > supported and there is no mention of FC4. What's happening? We're waiting for FC4 to come our way, and that's waiting for the release of FC6 Test2, which right now is on a day to day freeze. I should know a few days ahead of time of when Red Hat will release FC6 Test2 and I'll make appropriate announcements. -- Jesse Keating RHCE (geek.j2solutions.net) Fedora Legacy Team (www.fedoralegacy.org) GPG Public Key (geek.j2solutions.net/jkeating.j2solutions.pub) -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From rdieter at math.unl.edu Mon Jul 31 11:47:38 2006 From: rdieter at math.unl.edu (Rex Dieter) Date: Mon, 31 Jul 2006 06:47:38 -0500 Subject: CVE-2006-3672 KDE Konqueror ReplaceChild Denial of Service References: <44CA7C5B.6050609@ysu.edu> Message-ID: <200607311147.k6VBlc1B007428@mathstat.unl.edu> John Dalbec wrote: > Does this affect Fedora-Legacy? Which KDE package contains Konqueror? Most likely, kdebase, respectively. -- Rex From blynch at ameliaschools.com Mon Jul 31 18:49:17 2006 From: blynch at ameliaschools.com (Bo Lynch) Date: Mon, 31 Jul 2006 14:49:17 -0400 (EDT) Subject: FC1 and FC2 end of life Message-ID: <49134.65.161.127.94.1154371757.squirrel@www.ameliaschools.com> Just read about the end of life of FC1 and FC2 on the fedoralegacy page. I understand that there will be no more bug fixes for these OS's, but does that mean that there will bo no more security fixes as well? -- Bo Lynch Systems Administrator RedHat Academy Instructor Energy Manager Amelia County Public Schools From sundaram at fedoraproject.org Mon Jul 31 20:14:03 2006 From: sundaram at fedoraproject.org (Rahul) Date: Tue, 01 Aug 2006 01:44:03 +0530 Subject: FC1 and FC2 end of life In-Reply-To: <49134.65.161.127.94.1154371757.squirrel@www.ameliaschools.com> References: <49134.65.161.127.94.1154371757.squirrel@www.ameliaschools.com> Message-ID: <44CE648B.809@fedoraproject.org> Bo Lynch wrote: > Just read about the end of life of FC1 and FC2 on the fedoralegacy page. I > understand that there will be no more bug fixes for these OS's, but does > that mean that there will bo no more security fixes as well? Yes when FC6 test 2 is released all updates for FC1 and FC2 will be stopped. Rahul From blynch at ameliaschools.com Mon Jul 31 20:24:30 2006 From: blynch at ameliaschools.com (Bo Lynch) Date: Mon, 31 Jul 2006 16:24:30 -0400 (EDT) Subject: FC1 and FC2 end of life In-Reply-To: <44CE648B.809@fedoraproject.org> References: <49134.65.161.127.94.1154371757.squirrel@www.ameliaschools.com> <44CE648B.809@fedoraproject.org> Message-ID: <33166.65.161.127.94.1154377470.squirrel@www.ameliaschools.com> Rahul, Thanks for the input. I have a couple of mail servers that I will need to upgrade I suppose. -- Bo Lynch Systems Administrator RedHat Academy Instructor Energy Manager Amelia County Public Schools On Mon, July 31, 2006 4:14 pm, Rahul wrote: > Bo Lynch wrote: >> Just read about the end of life of FC1 and FC2 on the fedoralegacy page. >> I >> understand that there will be no more bug fixes for these OS's, but does >> that mean that there will bo no more security fixes as well? > > Yes when FC6 test 2 is released all updates for FC1 and FC2 will be > stopped. > > Rahul > > -- > fedora-legacy-list mailing list > fedora-legacy-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-legacy-list > From guolin at alexa.com Mon Jul 31 20:19:36 2006 From: guolin at alexa.com (Guolin Cheng) Date: Mon, 31 Jul 2006 13:19:36 -0700 Subject: when is the estimated EOL date for FC3/FC4 -- RE: FC1 and FC2 end of life Message-ID: <41089CB27BD8D24E8385C8003EDAF7AB04464155@karl.presidio.alexa.com> Rahul, DO you know when is the estimated EOL data for FC3/FC4? Thanks. --Guolin -----Original Message----- From: fedora-legacy-list-bounces at redhat.com [mailto:fedora-legacy-list-bounces at redhat.com] On Behalf Of Bo Lynch Sent: Monday, July 31, 2006 1:25 PM To: Discussion of the Fedora Legacy Project Subject: Re: FC1 and FC2 end of life Rahul, Thanks for the input. I have a couple of mail servers that I will need to upgrade I suppose. -- Bo Lynch Systems Administrator RedHat Academy Instructor Energy Manager Amelia County Public Schools On Mon, July 31, 2006 4:14 pm, Rahul wrote: > Bo Lynch wrote: >> Just read about the end of life of FC1 and FC2 on the fedoralegacy page. >> I >> understand that there will be no more bug fixes for these OS's, but does >> that mean that there will bo no more security fixes as well? > > Yes when FC6 test 2 is released all updates for FC1 and FC2 will be > stopped. > > Rahul > > -- > fedora-legacy-list mailing list > fedora-legacy-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-legacy-list > -- fedora-legacy-list mailing list fedora-legacy-list at redhat.com https://www.redhat.com/mailman/listinfo/fedora-legacy-list From sundaram at redhat.com Mon Jul 31 20:26:59 2006 From: sundaram at redhat.com (Rahul) Date: Tue, 01 Aug 2006 01:56:59 +0530 Subject: when is the estimated EOL date for FC3/FC4 -- RE: FC1 and FC2 end of life In-Reply-To: <41089CB27BD8D24E8385C8003EDAF7AB04464155@karl.presidio.alexa.com> References: <41089CB27BD8D24E8385C8003EDAF7AB04464155@karl.presidio.alexa.com> Message-ID: <44CE6793.4060807@redhat.com> Guolin Cheng wrote: > Rahul, > > DO you know when is the estimated EOL data for FC3/FC4? Thanks. > > --Guolin Thats answered in the FAQ. See the 1-2-3 and out policy. http://fedoraproject.org/wiki/Legacy/FAQ Rahul From mattdm at mattdm.org Mon Jul 31 20:36:52 2006 From: mattdm at mattdm.org (Matthew Miller) Date: Mon, 31 Jul 2006 16:36:52 -0400 Subject: FC1 and FC2 end of life In-Reply-To: <49134.65.161.127.94.1154371757.squirrel@www.ameliaschools.com> References: <49134.65.161.127.94.1154371757.squirrel@www.ameliaschools.com> Message-ID: <20060731203652.GA25656@jadzia.bu.edu> On Mon, Jul 31, 2006 at 02:49:17PM -0400, Bo Lynch wrote: > Just read about the end of life of FC1 and FC2 on the fedoralegacy page. I > understand that there will be no more bug fixes for these OS's, but does > that mean that there will bo no more security fixes as well? There are _already_ only security fixes. -- Matthew Miller mattdm at mattdm.org Boston University Linux ------> From blynch at ameliaschools.com Mon Jul 31 18:47:22 2006 From: blynch at ameliaschools.com (Bo Lynch) Date: Mon, 31 Jul 2006 14:47:22 -0400 (EDT) Subject: FC1 and FC2 end of life Message-ID: <48889.65.161.127.94.1154371642.squirrel@www.ameliaschools.com> Just read about the end of life of FC1 and FC2 on the fedoralegacy page. I understand that there will be no more bug fixes for these OS's, but does that mean that there will bo no more security fixes as well? -- Bo Lynch Systems Administrator RedHat Academy Instructor Energy Manager Amelia County Public Schools From mattdm at mattdm.org Mon Jul 31 20:38:24 2006 From: mattdm at mattdm.org (Matthew Miller) Date: Mon, 31 Jul 2006 16:38:24 -0400 Subject: when is the estimated EOL date for FC3/FC4 -- RE: FC1 and FC2 end of life In-Reply-To: <44CE6793.4060807@redhat.com> References: <41089CB27BD8D24E8385C8003EDAF7AB04464155@karl.presidio.alexa.com> <44CE6793.4060807@redhat.com> Message-ID: <20060731203824.GB25656@jadzia.bu.edu> On Tue, Aug 01, 2006 at 01:56:59AM +0530, Rahul wrote: > > DO you know when is the estimated EOL data for FC3/FC4? Thanks. > Thats answered in the FAQ. See the 1-2-3 and out policy. > http://fedoraproject.org/wiki/Legacy/FAQ And the schedule for FC6 Test 2 is: (Currently "REPLY HAZY / ASK AGAIN LATER".) -- Matthew Miller mattdm at mattdm.org Boston University Linux ------> From jkosin at beta.intcomgrp.com Mon Jul 31 20:39:47 2006 From: jkosin at beta.intcomgrp.com (James Kosin) Date: Mon, 31 Jul 2006 16:39:47 -0400 Subject: FC1 and FC2 end of life In-Reply-To: <49134.65.161.127.94.1154371757.squirrel@www.ameliaschools.com> References: <49134.65.161.127.94.1154371757.squirrel@www.ameliaschools.com> Message-ID: <44CE6A93.40704@beta.intcomgrp.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Bo Lynch wrote: > Just read about the end of life of FC1 and FC2 on the fedoralegacy page. I > understand that there will be no more bug fixes for these OS's, but does > that mean that there will bo no more security fixes as well? Yes, it means NO MORE ANYTHING. - -James -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEzmqTkNLDmnu1kSkRAnT/AJkBgKjvDbGFKRT/mFQo62QKt3JPpgCdG2Kv YUeYET4W0a2s7kDu8/f94p8= =mWvu -----END PGP SIGNATURE----- -- Scanned by ClamAV - http://www.clamav.net