Discuss October 2007

discuss@lists.centos.org

268 participants
322 discussions

Centos 5.0 Intel G33/P35 Chipset Support (Asus P5K-VM, P5KC)
by Michael Rock 22 Oct '07

22 Oct '07

I have 2 new boxes that I cannot use yet because of problems supporting these newer chipsets in 5.1. Does anyone know when the CD version of 5.0 x86-64 that has support for these chipsets be available on any on a Centos mirror? Has the support for these chipsets been added to yum yet? Here are my latest results with these chipsets and Centos 5.1 1. Asus P5K, E6850, P35 Chipset: Does not boot or install without "acpi=off all-generic-ide irqpoll nommconf" Also, when it does boot it does not recognize LAN and video hangs loading gnome. I tried install the Asus Linux driver for the mobo but 'make install' produces error that kernel sources cannot be found. 2. Asus P5K-VM, Q6600, G33 chipset: Installs and boots as long as "acpi=off" switch used. But I understand this disables multi-core support. LAN and video are working. thx -- Mike __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

2 1

freenx problem with the most recent updates
by Joachim Backes 22 Oct '07

22 Oct '07

When running "yum update" on monday, oct 22, I get the following conflicts: Transaction Check Error: file /etc/nxserver/node.conf.sample from install of freenx-0.7.1-1.el5.centos conflicts with file from package freenx-0.6.0-12.el5.centos file /usr/bin/nxkeygen from install of freenx-0.7.1-1.el5.centos conflicts with file from package freenx-0.6.0-12.el5.centos file /usr/bin/nxloadconfig from install of freenx-0.7.1-1.el5.centos conflicts with file from package freenx-0.6.0-12.el5.centos file /usr/bin/nxnode from install of freenx-0.7.1-1.el5.centos conflicts with file from package freenx-0.6.0-12.el5.centos file /usr/bin/nxprint from install of freenx-0.7.1-1.el5.centos conflicts with file from package freenx-0.6.0-12.el5.centos file /usr/bin/nxserver from install of freenx-0.7.1-1.el5.centos conflicts with file from package freenx-0.6.0-12.el5.centos file /usr/bin/nxsetup from install of freenx-0.7.1-1.el5.centos conflicts with file from package freenx-0.6.0-12.el5.centos Known? Regards -- Joachim Backes <joachim.backes(a)rhrk.uni-kl.de> University of Kaiserslautern,Computer Center [RHRK], Systems and Operations, High Performance Computing, D-67653 Kaiserslautern, PO Box 3049, Germany -------------------------------------------------- Phone: +49-631-205-2438, FAX: +49-631-205-3056 http://hlrwm.rhrk.uni-kl.de/home/staff/backes.html

5 12

Re: [CentOS] /etc/yum/pluginconf.d/prioriti es.conf file disappeared
by Lanny Marcus 22 Oct '07

22 Oct '07

>Message: 6 >On 21 October 2007, Johnny Hughes <johnny(a)centos.org> wrote: >That file does not change often from the default ... you can get the >default version by downloading the RPM in question and using this >command in the directory where you put it: >rpm2cpio yum-priorities-1.0.4-2.el5.centos.noarch.rpm | cpio -idv >After that, there will be a bunch of files in that same directory ... >which are the default files that get installed. >That file should be one of them, andat ><tempdir>/etc/yum/pluginconf.d/priorities.conf Johnny: THANK YOU for the above information. It's a minor problem, but, what bothers me is that I do *not* think that I deleted that file by accident. I think it disappeared by itself, which, if true, would be troubling. However, I'm open to the possibility that somehow, I deleted it, accidentally. And, a very special THANK YOU, for all of the time and work you put into CentOS! -- Lanny

1 0

new freenx and nx RPMS released, manual action for x86_64
by Johnny Hughes 22 Oct '07

22 Oct '07

There are new RPMS released for nx and freenx in the CentOS-4 and CentOS-5 Extras repository. I normally do not announce that here, as those can easily be obtained on a normal "yum upgrade/update", however in this case there are special actions required *_IF_* you have the x86_64 architecture for either CentOS-4 or CentOS-5 with the current versions of nx and freenx installed. The freenx and nx in the x86_64 tree were i386 versions prior to this release because the nomachine code would not compile on x86_64. This release fixes that and the new versions are x86_64 RPMS and no longer i386. This means that YUM will not update the currently installed i386 RPMS that are installed on x86_64 machines. ============= *_ATTENTION_* ============= If you are running nx and freenx on x86_64, to get these upgraded you *_MUST_*: 1. Manually download the x86_64 RPMS from these location: CentOS-5: <http://mirror.centos.org/centos/5/extras/x86_64/RPMS/freenx-0.7.1-1.el5.cen…> <http://mirror.centos.org/centos/5/extras/x86_64/RPMS/nx-3.0.0-4.el5.centos.…> CentOS-4: <http://mirror.centos.org/centos/4/extras/x86_64/RPMS/freenx-0.7.1-1.el4.cen…> <http://mirror.centos.org/centos/4/extras/x86_64/RPMS/nx-3.0.0-4.el4.centos.…> 2. Manually install these two RPMS with this command (as root from within the directory where you downloaded them): rpm -Uvh freenx-0.7.1-1.el5.centos.x86_64.rpm nx-3.0.0-4.el5.centos.x86_64.rpm (that command is all one line if it wraps on your e-mail) ============= I apologize for the manual update requirement, however yum will not update i386 packages with x86_64 ones. Again ... this is *_ONLY_* required if you have the prior released i386 versions of nx and freenx installed on the X86_64 arch of either CentOS-4.x or CentOS-5.x. If you are using the i386 architecture of CentOS-4.x or CentOS-5.x then you can just upgrade via yum normally. Thanks, Johnny Hughes

2 3

CentOS upgrade in Xen domU?
by Mike Edwards 22 Oct '07

22 Oct '07

I'm running into a slight problem trying to upgrade a CentOS 4.4 install to 5.0. The configuration: CentOS 4.4 is an old install that used to boot natively. That has since been backed up and restored to two seperate LVs (as the original install had two partitions). The host system now runs Debian, and I've been able to successfully boot the old CentOS 4.4 install under Xen (with a Debian domU kernel, but that's besides the point). I've decided to upgrade the CentOS domU to CentOS 5. After determining that the recommended upgrade path is to do so via the installer, I grabbed the CentOS installer kernel/ramdisk and configured my domU to boot from those. The installer comes up without a problem. Things get hairy when the installer takes a look at the 'disks'. I receive the following message: /dev/xvda currently has a loop partition layout. To use this disk for the installation of CentOS, it must be re-initialized, causing the loss of ALL DATA on this drive. It looks like the installer doesn't like the fact that there are no partitions (which is correct, as the 'disk' is actually a logical volume under lvm). As I'm trying to do an upgrade, and not blow away my existing setup, this isn't going to work. My question, therefore, is - how do I tell the CentOS 5 installer to ignore the fact that there are no partitions, and to simply do the install? As mentioned previously, the CentOS domU does boot perfectly fine, and given the prevalence of volume groups, logical volumes and virtual machines these days, it seems rather silly to have an installer absolutely rely on the existence of partitions before it'll let one do an upgrade or install. -- Mike Edwards | If this email address disappears, Unsolicited advertisments to | assume it was spammed to death. To this address are not welcome. | reach me in that case, s/-.*@/@/ "Our progress as a nation can be no swifter than our progress in education. The human mind is our fundamental resource." -- John F. Kennedy

3 3

CentOS 64bit to support ICH9
by David Hrbáč 22 Oct '07

22 Oct '07

Hi, Well, ICH9 support for CentOS as announced on Oct 16th by me http://lists.centos.org/pipermail/centos/2007-October/088104.html has been extended. Today I have published x86_64 install DVD. You can find it here: http://fs12.vsb.cz/hrb33/pub/ich9/ Regards, David Hrbáč

1 1

CentOS-announce Digest, Vol 32, Issue 14
by centos-announce-request＠centos.org 22 Oct '07

22 Oct '07

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. CESA-2007:0979 Critical CentOS 4 ia64 firefox - security update (Pasi Pirhonen) 2. CESA-2007:0980 Critical CentOS 4 ia64 seamonkey - security update (Pasi Pirhonen) 3. CESA-2007:0981 Moderate CentOS 4 ia64 thunderbird - security update (Pasi Pirhonen) 4. CESA-2007:0979 Critical CentOS 4 s390(x) firefox - security update (Pasi Pirhonen) 5. CESA-2007:0980-01: Critical CentOS 2 i386 seamonkey security update (John Newbigin) ---------------------------------------------------------------------- Message: 1 Date: Sun, 21 Oct 2007 18:58:17 +0300 From: Pasi Pirhonen <upi(a)centos.fi> Subject: [CentOS-announce] CESA-2007:0979 Critical CentOS 4 ia64 firefox - security update To: centos-announce(a)centos.org Message-ID: <20071021155817.GH9935(a)centos.fi> Content-Type: text/plain; charset="us-ascii" CentOS Errata and Security Advisory 2007:0979 https://rhn.redhat.com/errata/RHSA-2007-0979.html The following updated files have been uploaded and are currently syncing to the mirrors: ia64: updates/ia64/RPMS/firefox-1.5.0.12-0.7.el4.centos.ia64.rpm -- Pasi Pirhonen - upi(a)iki.fi - http://pasi.pirhonen.eu/ Top-postings silently ignored

1 0

Postfix dropping settings CentOS4.5
by Johnny Massengill 22 Oct '07

22 Oct '07

My company is using Trend Micro InterScan Messaging Security Suite 7.0 for linux. This setup uses Postfix as a mail gateway for MS Exchange. The problem I'm having is ever so often Postfix 2.2.11 will lose the Transport mapping lookup tables setting. When this happens, mail into our domain will stop being relayed to our Exchange server. FYI: please remember, I'm ok with understanding how Linux works, but I'm a Postfix noob! Thanks in advance for the help -- Johnny Massengill

4 3

bind-9.3.3-9.0.1 RPM BUILD error
by Indunil Jayasooriya 22 Oct '07

22 Oct '07

Hi, Centos 4.4 comes with bind 9.2.x. I want to upgrade it to bind bind-9.3.3-9.x as bind 9.2.x had a security hole. So I downloaded bind-9.3.3-9.0.1.el5.src.rpm from Centos5 repo and tried to built RPM out of it. But, I failed to do it. I got bellow errors. ./dbus_service.c: In function `dbus_svc_send_va': ./dbus_service.c:296: warning: implicit declaration of function `dbus_message_iter_init_append' ./dbus_service.c:298: warning: implicit declaration of function `dbus_message_iter_append_basic' ./dbus_service.c: In function `dbus_svc_message_iterator_new': ./dbus_service.c:497: warning: wrong type argument to increment ./dbus_service.c: In function `dbus_svc_message_next_arg_type': ./dbus_service.c:513: warning: wrong type argument to increment ./dbus_service.c: In function `dbus_svc_message_next_arg': ./dbus_service.c:521: warning: wrong type argument to increment ./dbus_service.c:522: warning: implicit declaration of function `dbus_message_iter_get_basic' ./dbus_service.c: In function `dbus_svc_message_element_type': ./dbus_service.c:530: warning: wrong type argument to increment ./dbus_service.c:531: warning: implicit declaration of function `dbus_message_iter_get_element_type' ./dbus_service.c: In function `dbus_svc_message_get_elements': ./dbus_service.c:538: warning: wrong type argument to increment ./dbus_service.c:539: warning: implicit declaration of function `dbus_message_iter_get_fixed_array' ./dbus_service.c: In function `dbus_svc_message_iterator_free': ./dbus_service.c:545: warning: wrong type argument to increment ./dbus_service.c: In function `dbus_svc_init': ./dbus_service.c:1015: warning: implicit declaration of function `dbus_connection_open_private' ./dbus_service.c:1015: warning: assignment makes pointer from integer without a cast ./dbus_service.c:1024: warning: implicit declaration of function `dbus_connection_close' ./dbus_service.c:1039: warning: assignment makes pointer from integer without a cast ./dbus_service.c:1080: warning: implicit declaration of function `dbus_bus_get_unique_name' ./dbus_service.c:1080: warning: assignment makes pointer from integer without a cast ./dbus_service.c:1084: warning: implicit declaration of function `dbus_bus_request_name' ./dbus_service.c:1094: error: `DBUS_REQUEST_NAME_REPLY_PRIMARY_OWNER' undeclared (first use in this function) ./dbus_service.c:1094: error: (Each undeclared identifier is reported only once ./dbus_service.c:1094: error: for each function it appears in.) ./dbus_service.c:1096: error: `DBUS_REQUEST_NAME_REPLY_EXISTS' undeclared (first use in this function) ./dbus_service.c:1097: error: `DBUS_REQUEST_NAME_REPLY_IN_QUEUE' undeclared (first use in this function) ./dbus_service.c:1098: error: `DBUS_REQUEST_NAME_REPLY_ALREADY_OWNER' undeclared (first use in this function) make[2]: *** [dbus_service.o] Error 1 make[2]: Leaving directory `/usr/src/redhat/BUILD/bind-9.3.3rc2/bin/named' make[1]: *** [subdirs] Error 1 make[1]: Leaving directory `/usr/src/redhat/BUILD/bind-9.3.3rc2/bin' make: *** [subdirs] Error 1 error: Bad exit status from /var/tmp/rpm-tmp.78789 (%build) RPM build errors: Bad exit status from /var/tmp/rpm-tmp.78789 (%build) ANY IDEAS? Has anybody built ? -- Thank you Indunil Jayasooriya

4 10

arp corrupted
by Bobby 22 Oct '07

22 Oct '07

Hi, I've been trying to get a couple of routers up after h/w failure. The border router is an OpenBSD firewall running NAT between the Internet and a DMZ like subnet, and in that a Linux antivirus server is running NAT to the LAN. When the client does a DNS query it reaches to the f/w where dns is running and is returned into the A/V server but never hits the 0.254 interface. (Shown by running tcpdump on each interface.) (Internet) | OpenBSD Firewall NAT 192.168.1.254 | 192.168.1.253 eth0 Anti-Virus in "DMZ" 192.168.0.254 eth1 | 192.168.0.11 Client on LAN The routing table on the A/V server is: 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 192.168.0.0 192.168.0.254 255.255.255.0 UG 0 0 0 eth1 192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth1 0.0.0.0 192.168.1.254 0.0.0.0 UG 0 0 0 eth0 Sitting on the A/V server one can reach the client without problem. Arp shows: Address HWtype HWaddress Flags Mask Iface 192.168.1.254 ether 00:20:78:0F:AC:31 C eth0 Unless I try to reach the client web server from the A/Vserver, then it fails and arp says: Address HWtype HWaddress Flags Mask Iface corp.domain.com (incomplete) eth0 dell11.domain.com ether 00:06:29:AF:A3:67 C eth1 192.168.1.254 ether 00:20:78:0F:AC:31 C eth0 One can also see the arp requests go out on eth 0 rather than eth1: arp who-has 192.168.0.10 tell 192.168.0.254 Pinging works well: PING 192.168.0.11 (192.168.0.11) 56(84) bytes of data. 64 bytes from 192.168.0.11: icmp_seq=0 ttl=64 time=0.277 ms Iptables on the A/V server says: *nat :PREROUTING ACCEPT [0:0] :POSTROUTING ACCEPT [0:0] :OUTPUT ACCEPT [0:0] -A PREROUTING -i eth1 -p tcp -m tcp --dport 80 -j REDIRECT --to-port 9080 -A PREROUTING -i eth1 -p tcp -m tcp --dport 110 -j REDIRECT --to-port 9110 -A PREROUTING -i eth1 -p tcp -m tcp --dport 25 -j REDIRECT --to-port 9025 -A PREROUTING -i eth1 -p tcp -m tcp --dport 21 -j REDIRECT --to-port 9021 COMMIT *filter :INPUT ACCEPT [0:0] :FORWARD ACCEPT [0:0] :Firewall-INPUT - [0:0] -A INPUT -i lo -j ACCEPT -A INPUT -i eth0 -j ACCEPT COMMIT It is supposed to route all outbound traffic through the various ports where the A/V s/w is listening. ifconfig shows: eth0 Link encap:Ethernet HWaddr 00:0D:88:39:6A:F1 inet addr:192.168.1.253 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::20d:88ff:fe39:6af1/64 Scope:Link UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1 RX packets:77670 errors:0 dropped:0 overruns:0 frame:0 TX packets:97635 errors:0 dropped:0 overruns:0 carrier:0 collisions:523 txqueuelen:1000 RX bytes:22858238 (21.7 MiB) TX bytes:21513745 (20.5 MiB) Interrupt:11 Base address:0x2400 eth1 Link encap:Ethernet HWaddr 00:50:FC:AC:52:4B inet addr:192.168.0.254 Bcast:192.168.0.255 Mask:255.255.255.0 inet6 addr: fe80::250:fcff:feac:524b/64 Scope:Link UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1 RX packets:26676 errors:0 dropped:0 overruns:0 frame:0 TX packets:20424 errors:0 dropped:0 overruns:1 carrier:0 collisions:0 txqueuelen:1000 RX bytes:2747567 (2.6 MiB) TX bytes:26324006 (25.1 MiB) Interrupt:7 Base address:0x2800 If NAT did not work I could see it having a problem. It appears to be happy routing icmp but not tcp. cat /proc/sys/net/ipv4/ip_forward shows 1 which it would have to anyway since the request goes out from the LAN. -- Bobby

2 5

← Newer
1
...
10
11
12
13
14
15
16
...
33
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 October 2007