similar to: up2date changing source

I get these two errors when I upgrade to the current 5 base. centos-release-5-0.0.el5.centos.2 CentOS release 5 (Final) file /etc/yum.repos.d/CentOS-Base.repo from install of centos-release-5 -1.0.el5.centos.1 conflicts with file from package centos-yumconf-4-4.5 file /etc/sysconfig/rhn/sources from install of centos-release-5- 1.0.el5.centos.1 conflicts with file from package

I am searching for a crm solution for small business and private use. Can't find anything within the CentOS 4.2. Most important for me are: address book, comments and document organization. Any comments or recommendations appreciated. kai

Well I just tried up2date -u Testing package set / solving RPM inter-dependencies... Downloading headers to solve dependencies... ####################################### Downloading headers to solve dependencies... There was a package dependency problem. The message was: Unresolvable chain of dependencies: libibverbs 1.0.3-1 requires kernel-ib libmthca 1.0.2-1

CentOS3.9 Users: After applying all Updates to Upgrade from CentOS 3.8 CentOS 3.9 I find up2date no longer works "correctly" (or shall I say NOT as before)... Missing is the "sources" File!!! Is this how V 4.5.5-7 is supposed to be or is the "sources" File omission an "error"??? Lawrence Houston -- (centos at greenfield.dyndns.org)

CentOS Errata and Bugfix Advisory 2006:0901-001 The up2date released with CentOS-4.4 did not specifically require the new centos-release, however the new centos-release provides the /etc/sysconfig/rhn/sources file for up2date. This update changes up2date to require centos-release >= 4-4.2 which will allow up2date to be used to upgrade of CentOS from 4.3 (or older versions) to 4.4. The

CentOS Errata and Bugfix Advisory 2006:0901-001 The up2date released with CentOS-4.4 did not specifically require the new centos-release, however the new centos-release provides the /etc/sysconfig/rhn/sources file for up2date. This update changes up2date to require centos-release >= 4-4.2 which will allow up2date to be used to upgrade of CentOS from 4.3 (or older versions) to 4.4. The

Hi, I installed 3.1 from CD and ran up2date without changing /etc/sysconfig/rhn/rhn-source. Checking some of the files it appears I have all the updates including the updates from the last few weeks. However up2date for some reason shows that I still need to update and lists old and current files in the list of available updates. Any idea why this is so and how to fix it?

What is the correct command using up2date and yum to install the kernel source package. Thanks, jerry

I installed postgrey from rpmforge and wanted to use sysconfig to change options instead of overwriting the init file. However, I get a weird warning from postgrey. I'm not sure if this is a postgrey quirk or I use sysconfig the wrong way. /etc/sysconfig/postgrey: OPTIONS="--unix=/var/spool/postfix/postgrey/socket --delay=660" /etc/rc.d/init.d/postgrey:

i updated to the latest up2date rpm.... then when updating to the latest kernel this is what happened after i ran up2date -fu for the kernel/kernel-source updates Testing package set / solving RPM inter-dependencies... Traceback (most recent call last): File "/usr/sbin/up2date", line 1174, in ? sys.exit(main() or 0) File "/usr/sbin/up2date", line 772, in main

Is it possible to exclude one package from a repo whilst using the up2date icon please? If so, how do I do it? Sharon. -- 13:34:23 up 2 days, 3:23, 3 users, load average: 2.70, 1.92, 1.67 A taste of linux http://www.sharons.org.uk/taste/index.html efever http://www.efever.blogspot.com/ Centos 4.2, KDE 3.4.3-1.0, OpenOffice 2.0 Registered Linux user 334501

I run CentOS 4.1 on a remote server and did a minimal installation. My problem is that I can not login using the HOSTNAME, must use the IP. 1. edited the - /etc/sysconfig/network 2. changed - HOSTNAME=a266 3. restarted the network Looks ok, hostname appears when logged on via IP, but can't use the HOSTNAME to log on from client. --- [kai at localhost ~]$ ssh a266 ssh: a266: Name or

Is there a program on CentOS which will sort my passwd/group etc. files by username or uid/gid? On Suse I can do this with a sysconfig switch and Suseconfig, is there something similar on RH-based systems? Kai -- Kai Sch?tzl, Berlin, Germany Get your web at Conactive Internet Services: http://www.conactive.com

I want to add the following route command route add -net 192.168.2.0/27 gw 192.168.2.3 via the normal network setup. The result should be the following routing table (the first line): 192.168.2.0/27 via 192.168.2.3 dev xenbr1 scope link 192.168.2.0/27 dev eth2 proto kernel scope link src 192.168.2.4 192.168.2.0/27 dev xenbr1 proto kernel scope link src 192.168.2.3 192.168.1.0/24 dev xenbr0

If so, how do you configure the up2date client that comes with CentOS to look at the local yum mirror? Conversely, how do you disable the CentOS Network Alert Notification Tool so that users won't see the "throbbing red circle" and be tempted to launch the up2date client? Thanks, Alfred

Hi all, i have a problem with centos's up2date tool. I have setup a central update server with yam (http://dag.wieers.com/home-made/yam/) under CentOS-4. When yam calls t up2date to download updates, up2date returns this error: Traceback (most recent call last): File "/usr/bin/yam", line 1099, in ? main() File "/usr/bin/yam", line 983, in main

Just updated another machine to 5.3, everything fine, but grub.conf wasn't updated to the 128 kernel. It got a new modified date and the kernel is there, but the content wasn't changed. /etc/sysconfig/kernel contains the correct UPDATEDEFAULT=yes No errors in logs or during the update. No problem to boot with this kernel once added. This is the first time I ever see this happen. Any

My first notebook upgrade: I repaired my old HP nc4010 (bought a new hinge on ebay) and realized this was the perfect way to test out the upgrade to 5.2 before doing it on my production notebook. First I updated to 'current' 5.1 (by current I mean I have not synced my 5.1 local repo since building my 5.2 repo). I had not used my nc4010 for a while and the kernel was at

I'm getting a SELinux warning when trying to start a perl daemon (bigsister) that I installed on a fresh CentOS 4.2 system and the start fails (there is nothing else logged, I cannot be sure that this is the fail reason but I assume it). However, SELinux is set to permissive mode, isn't permissive mode meant to only issue warnings and not block anything? So, as a first workaround I

There have been some complaints recently concerning this, so I thought an explanation of the setup AND recommendations are in order. First, I want to say that we need more donated servers with fast (at least 100mbit) internet connections. If you are making lots of money using CentOS and are a hosting provider, please consider providing us a donated server so we can better distribute CentOS. Now