Discuss August 2006

discuss@lists.centos.org

269 participants
332 discussions

CentOS-announce Digest, Vol 18, Issue 16
by centos-announce-request＠centos.org 26 Aug '06

26 Aug '06

Send CentOS-announce mailing list submissions to centos-announce(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request(a)centos.org You can reach the person managing the list at centos-announce-owner(a)centos.org When replying, please edit your Subject line so it is more specific than "Re: Contents of CentOS-announce digest..." Today's Topics: 1. Subject: CentOS 3.8 is released for i386 and x86_64 (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Fri, 25 Aug 2006 07:43:09 -0500 From: Johnny Hughes <johnny(a)centos.org> Subject: [CentOS-announce] Subject: CentOS 3.8 is released for i386 and x86_64 To: CentOS-Announce <centos-announce(a)centos.org> Cc: distro(a)distrowatch.com Message-ID: <1156509789.15080.184.camel(a)myth.home.local> Content-Type: text/plain; charset="us-ascii" The CentOS development team is please to announce the release of CentOS 3.8 for i386 and x86_64. CentOS 3.8 is available on all mirrors and via bittorrent. This release corresponds to the upstream vendor U8 release together with updates through August 11th (depending on architecture). The serverCD version (1 cdrom) is available for i386 and x86_64. The work for the other arches is still in progress. -------------------------------------------------------------------- All the previously released CentOS-3 versions are available at: http://vault.centos.org -------------------------------------------------------------------- ISOs available from here: http://isoredirect.centos.org/centos/3/isos/ -------------------------------------------------------------------- To stay current with CentOS: Visit our website at: http://www.centos.org Join the CentOS mailing list at: http://lists.centos.org/mailman/listinfo/centos Join various team members on IRC at irc.freenode.net #centos -------------------------------------------------------------------- Note: There was an upstream bug that prevented using the DVD, CD-1, or ServerCD in rescue mode. Tru Huynh found and fixed this issue on the CentOS ISOs, though they are still broken on the upstream ISOs (thanks Tru, great work) ... however this caused us to have to change those specific ISOs after we had already started populating the external mirrors. Because of this, you need to ensure that the ISOs you download have the correct MD5SUMS. If you use the link above to get ISOs, only the newer ISOs will be retrieved. The MD%SUMS are listed here for your convenience: i386: 6719c1ca27ec1d2a614a44f282de22ac CentOS-3.8-i386-bin2of3.iso 694a9c37d881113c0ae9f92118d0412c CentOS-3.8-i386-bin3of3.iso 1c15f624139947423ab5e7a494308575 CentOS-3.8-i386-src1of3.iso 2f17aa141e9cc7a33a6e6cb31368039d CentOS-3.8-i386-src2of3.iso 381e9a633433f619c21bcee9888b6697 CentOS-3.8-i386-src3of3.iso 395016400baf6495fbd4cf134ccc0631 CentOS-3.8-server-i386.iso 8a278b040f0b17d7debd27a9aa8ca6ea CentOS-3.8-i386-bin1of3.iso 69d7b30ae980201f3ff58aca8810124d CentOS-3.8-i386-binDVD.iso x86_64: 2b9e817b3df46c80b5585355f689c3e2 CentOS-3.8-x86_64-bin2of4.iso eeefc50a2336264e488c78253aca1b0a CentOS-3.8-x86_64-bin3of4.iso 52301c7bbe730045c550f15f90f86fdc CentOS-3.8-x86_64-bin4of4.iso c6fa03ec0dd2f998f3340b53467a0d24 CentOS-3.8-x86_64-src1of3.iso 9dd4c127373d5dcdd7abea6e6e991e1f CentOS-3.8-x86_64-src2of3.iso 2e96ab04443a23ba6bda3be558de9a91 CentOS-3.8-x86_64-src3of3.iso b1227442b5d367da4e156bf3c77d7236 CentOS-3.8-server-x86_64.iso 709e9a9f9c6a26fb27996a603910f054 CentOS-3.8-x86_64-bin1of4.iso f6c2c98a9836175af9c5fd03330a49d2 CentOS-3.8-x86_64-binDVD.iso SRPMS: 1c15f624139947423ab5e7a494308575 CentOS-3.8-src1of3.iso 2f17aa141e9cc7a33a6e6cb31368039d CentOS-3.8-src2of3.iso 381e9a633433f619c21bcee9888b6697 CentOS-3.8-src3of3.iso efd11713ce89a4c37c015fd4a3ace14e CentOS-3.8-srcDVD.iso -------------------------------------------------------------------- Note: It may take a couple days for some of the mirrors to catch up. -------------------------------------------------------------------- Enjoy, The CentOS Development Team

1 0

Problems after performing yum update
by Robert 26 Aug '06

26 Aug '06

I performed the update yesterday that included installing kernel 2.6.9-42.0.2.EL and replacing ethereal with wireshark. First, the trivial... Wireshark would not run from the KDE menu without editing the menu to change the command from "wireshark" to "kdesu wireshark" because dumpcap is at usr/sbin/dumpcap instead of /usr/bin/dumpcap . Making the change causes wireshark to open root password dialog like ethereal, which it replaced. (And which makes sense.) Now, the puzzling. This is an AMD Athlon XP 2600+ on an ASUS A7N8X deluxe ver 2.0 m/b. The symptom is that ntpd refuses to sync. Dropping back to kernel 2.6.9-34.0.2.EL restores ntpd to proper operation. My first thought was that the smp code must have been incorporated in the non-smp kernel because the system mis-behaves exactly as it has in the past when Anaconda mistakenly installed the smp kernel. What clouds the picture is that when I checked the updates repository, I found both http://isoredirect.centos.org/centos/4/updates/i386/RPMS/kernel-smp-2.6.9-4… and http://isoredirect.centos.org/centos/4/updates/i386/RPMS/kernel-2.6.9-42.0.… which then made me wonder if there was a glitch in the build process. Has anyone else seen this?

5 6

Fetching Obsoletes list of channel: Centos4-addons
by Rajeev R Veedu 26 Aug '06

26 Aug '06

Hi I am trying to update my system and I get the following message:- "Fetching Obsoletes list of channel: Centos4-addons." The last potion of message varies form add on to extras or updates or base depends on the selection of channels. This screen was there since yesterday evening but the system is not hanging since I can cancel this operation. I don't know why this could happen and would appreciate if some one could guide me. Thanks Rajeev

4 4

3DLabs Wildcat
by Alexandru E. Ungur 26 Aug '06

26 Aug '06

Hi all, Has anybody managed to make this board: 3DLabs Wildcat III 6210 work under CentOS 4/Xorg ? I see on their website they had support for it until RHEL3 but no more support for RHEL4... I tried the 'glint' driver but it does not support this particular chipset. I tried the 'vesa' mode and I could get a 640x480 @ 60Hz but it's a little hard to work at that resolution ;) Any thoughts? TIA, Alex

1 0

Re: [CentOS] Network interface fails after kernel upgrade
by Clive Gould 26 Aug '06

26 Aug '06

Thanks to everyone for their suggestions. I can't try most of them out until after the long UK bank holiday weekend as I only have ssh access to the server from home and don't want to disable networking! There are three network cards in the server, but I've only got the RealTek connected. Looking at /var/log/messages suggests the new kernel is handling all three NIC's differently from the old kernel. Does anyone know what no GSI means with NICs and the new kernel? Thanks in advance Clive old kernel:- Aug 25 08:14:53 cc kernel: 8139too Fast Ethernet driver 0.9.27 Aug 25 08:14:53 cc kernel: ACPI: PCI interrupt 0000:00:0e.0[A] -> GSI 5 (level, low) -> IRQ 5 Aug 25 08:14:53 cc kernel: eth0: RealTek RTL8139 at 0xa800, 00:10:dc:59:bd:dc, IRQ 5 Aug 25 08:14:53 cc kernel: ACPI: PCI interrupt 0000:00:06.0[A] -> GSI 5 (level, low) -> IRQ 5 Aug 25 08:14:54 cc kernel: 3c59x: Donald Becker and others. www.scyld.com/network/vortex.html Aug 25 08:14:54 cc kernel: 0000:00:06.0: 3Com PCI 3c905B Cyclone 100baseTx at 0xa400. Vers LK1.1.19 Aug 25 08:14:54 cc kernel: via-rhine.c:v1.10-LK1.2.0-2.6 June-10-2004 Written by Donald Becker Aug 25 08:14:54 cc kernel: ACPI: PCI interrupt 0000:00: 05.0[A] -> GSI 11 (level, low) -> IRQ 11 Aug 25 08:14:54 cc rpcidmapd: rpc.idmapd startup succeeded Aug 25 08:14:54 cc kernel: eth2: VIA Rhine at 0xe3000000, 00:50:ba:a1:86:44, IRQ 11. Aug 25 08:14:54 cc kernel: eth2: MII PHY found at address 8, status 0x7809 advertising 05e1 Link 0000. Aug 25 08:14:54 cc kernel: ACPI: PCI interrupt 0000:00:11.5[C] -> GSI 10 (level, low) -> IRQ 10 Aug 25 08:14:54 cc kernel: pciehp: acpi_pciehprm:\_SB_.PCI0 evaluate _BBN fail=0x5 Aug 25 08:14:54 cc kernel: pciehp: acpi_pciehprm:get_device PCI ROOT HID fail=0x5 Aug 25 08:14:54 cc kernel: USB Universal Host Controller Interface driver v2.2 Aug 25 08:14:54 cc kernel: ACPI: PCI interrupt 0000:00:11.2[D] -> GSI 11 (level, low) -> IRQ 11 Aug 25 08:14:54 cc kernel: uhci_hcd 0000:00: 11.2: UHCI Host Controller Aug 25 08:14:54 cc kernel: uhci_hcd 0000:00:11.2: irq 11, io base 0000b000 new kernel Aug 25 08:07:53 cc kernel: 8139too Fast Ethernet driver 0.9.27 Aug 25 08:07:53 cc kernel: ACPI: PCI interrupt 0000:00:0e.0[A]: no GSI - using IRQ 5 Aug 25 08:07:53 cc kernel: eth0: RealTek RTL8139 at 0xa800, 00:10:dc:59:bd:dc, IRQ 5 Aug 25 08:07:53 cc kernel: ACPI: PCI interrupt 0000:00:06.0[A]: no GSI - using IRQ 5 Aug 25 08:07:53 cc kernel: 3c59x: Donald Becker and others. www.scyld.com/network/vortex.html Aug 25 08:07:53 cc kernel: 0000:00:06.0: 3Com PCI 3c905B Cyclone 100baseTx at 0xa400. Vers LK1.1.19 Aug 25 08:07:53 cc kernel: via-rhine.c:v1.10-LK1.2.0-2.6 June-10-2004 Written by Donald Becker Aug 25 08:07:53 cc kernel: ACPI: PCI interrupt 0000:00: 05.0[A]: no GSI - using IRQ 11 Aug 25 08:07:53 cc kernel: eth2: VIA Rhine at 0xe3000000, 00:50:ba:a1:86:44, IRQ 11. Aug 25 08:07:53 cc kernel: eth2: MII PHY found at address 8, status 0x7809 advertising 05e1 Link 0000. Aug 25 08:07:53 cc kernel: ACPI: PCI interrupt 0000:00:11.5[C]: no GSI - using IRQ 9 Aug 25 08:07:53 cc kernel: pciehp: acpi_pciehprm:\_SB_.PCI0 evaluate _BBN fail=0x5 Aug 25 08:07:53 cc kernel: pciehp: acpi_pciehprm:get_device PCI ROOT HID fail=0x5 Aug 25 08:07:53 cc kernel: USB Universal Host Controller Interface driver v2.2 Aug 25 08:07:53 cc kernel: ACPI: PCI interrupt 0000:00:11.2[D]: no GSI - using IRQ 11 Aug 25 08:07:53 cc kernel: uhci_hcd 0000:00:11.2 : UHCI Host Controller Aug 25 08:07:53 cc kernel: uhci_hcd 0000:00:11.2: irq 11, io base 0000b000 > Hi > > Yum has just updated 5 of my Linux boxes running CentOS 4.3 to the > 2.6.9-42 kernel. > > All is well on four of the boxes, but on the fifth the network card (eth0) > will not work. I've downgraded the kernel to the previous version and the > network card works fine again. > > I've tried removing and re-installing the new kernel, but the network card > won't work with it. > > The details of the card are as follows: > > lspci:- > 00:0e.0 Ethernet controller: Realtek Semiconductor Co., Ltd. > RTL-8139/8139C/8139C+ (rev 10) > > /etc/modprobe.conf:- > alias eth0 8139too > > Any suggestions welcomed..

1 0

bios information
by bruce 26 Aug '06

26 Aug '06

hi.. does centos give a way to read the bios for a given motherboard... thanks

2 1

Switching off color on console
by "Petr \"Qaxi\" Klíma" 25 Aug '06

25 Aug '06

Hello How do I switch off color mode on console (we have just BW monitor at the server) and not for all terminal connections? -- Petr Klíma e-mail: qaxi(a)seznam.cz

9 20

Looks like 3.8 is not ready to download
by Sam Trenholme 25 Aug '06

25 Aug '06

This is just a heads up that 3.8 does not look ready to download. There are 3.8 files at the CentOS mirrors, but the files (including the iso images) are constantly changing or disappearing. It looks like the hard-working diligent CentOS workers are making some last minute changes before getting CentOS 3.8 out the door. I presume that there will be a posting made to this list when 3.8 is ready--I hope this doesn't end up like 3.6, when the files are uploaded but not a peep on the mailing list nor webpage that a new 3.x release of CentOS has been made. I know most people are probably using 4.x, but I prefer 3.x because I know the software on this release is guaranteed to be present in any more modern Linux distro (maybe as an updated version); CentOS 3.x is the oldest codebase being currently maintained for any free Linux distro. - Sam

5 4

hdc lost interrupt
by Jamie Wilch 25 Aug '06

25 Aug '06

Hello After updating to the 2.6.9-42 kernel, one of my boxes stall during boot with hdc lost interrupt ide-cd:cmd 0x3 timed out The older 2.6.9-35 kernel boots fine. This is a Compaq Proliant PL360. The odd part is, I have another, identical Proliant that runs the new kernel just fine. Any idea what is happening? Thanks Jamie

2 2

SELinux targeted - named, portmap and syslogd errors
by Leonardo Vilela Pinheiro 25 Aug '06

25 Aug '06

Yesterday I activated SELinux in targeted mode, then I rebooted and started receiving some error messages in the system services initialization: ====================================================================== audit(1156518721.252:2): avc: denied { read } for pid=2223 comm="syslogd" name="libc-2.3.4.so" dev=dm-0 ino=50441 scontext=user_u:system_r:syslogd_t tcontext=system_u:object_r:file_t tclass=file audit(1156518721.280:5): avc: denied { append } for pid=2224 comm=" syslogd" name="messages" dev=dm-3 ino=38 scontext=user_u:system_r:syslogd_t tcontext=system_u:object_r:file_t tclass=file audit(1156518721.757:7): avc: denied { read } for pid=2246 comm="portmap" name="libnsl-2.3.4.so" dev=dm-0 ino=48836 scontext=user_u:system_r:portmap_t tcontext=system_u:object_r:file_t tclass=file audit(1156518728.009:10): avc: denied { read } for pid=2411 comm="named" name="liblwres.so.1.1.2" dev=dm-0 ino=462795 scontext=user_u:system_r:named_t tcontext=system_u:object_r:file_t tclass=file audit(1156518728.032:13): avc: denied { read } for pid=2411 comm="named" name="libgssapi_krb5.so.2" dev=dm-0 ino=459694 scontext=user_u:system_r:named_t tcontext=system_u:object_r:file_t tclass=lnk_file ====================================================================== The SELinux policies in use are the default from Centos packages (I haven't changed anything). Surely this bind, portmap and syslogd packages came from Centos base or update. bind-chroot is not installed. Bind seems to be working fine - as a cache and as a nameserver - even with those errors. Syslog also *seems* to be ok, as it keeps logging things on /var/log/, even in /var/log/messages. I don't use Portmap, but I have left it activated. Anyways, iptables blocks it. Any ideas on what is causing the problems and how to solve it ? Thanks -- Vilela

2 2

← Newer
1
...
7
8
9
10
11
12
13
...
34
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss August 2006