Discuss

discuss@lists.centos.org

1 participants
34730 discussions

Change your default rpm query format on multi-lib archs (like x86_64)
by Johnny Hughes 12 Jan '05

12 Jan '05

All, I am now building rpms on, and using a multi-lib arch (x86_64) for the first time ... when using the standard command: rpm -qa | grep pkg_name The results might be pkg_name.i386 or pkg_name.x86_64 ... or both. But, the way it is shown by the default query format, looks the same ... like this: pkg_name pkg_name ---------------------------- example: [root@x86-64 ~]# rpm -qa | grep popt popt-1.9.1-21 popt-1.9.1-21 ---------------------------- To fix this problem on multi-lib machines (and change the default query format), you can change your .rpmmacros (or create a .rpmmacros) in your user home directory and add this line: %_query_all_fmt %%{name}-%%{version}-%%{release}.%%{arch} --------------------------- Now the result of the above example is: [root@x86-64 ~]# rpm -qa | grep popt popt-1.9.1-21.x86_64 popt-1.9.1-21.i386 --------------------------- So now you can easily tell which arch of a program is installed on multi-lib machines. Thanks, Johnny Hughes

4 4

vim update for CentOS-3.3 x86_64 rebuild :(
by Tru Huynh 12 Jan '05

12 Jan '05

Greatings, I am very sorry for having to misrebuild the vim update for x86_64 (CentOS-3.3): Wrong build host which was using a different libacl than the current CentOs-3.3... upon upgrading you might have got: ....Unable to satisfy dependencies Package vim-enhanced needs libacl.so.1(ACL_1.0)(64bit), this is not available. Package vim-minimal needs libacl.so.1(ACL_1.0)(64bit), this is not available. I have rebuild the new ones and replaced the wrong ones on the master mirror tonight Tue Jan 11 23:03:10 UTC 2005 ref: [RHSA-2005:010-01] Updated VIM packages fix security vulnerability https://rhn.redhat.com/errata/RHSA-2005-010.html ...centos-3/3.3/updates/x86_64/ RPMS/vim-common-6.3.046-0.30E.1.x86_64.rpm RPMS/vim-enhanced-6.3.046-0.30E.1.x86_64.rpm RPMS/vim-minimal-6.3.046-0.30E.1.x86_64.rpm RPMS/vim-X11-6.3.046-0.30E.1.x86_64.rpm SRPMS/vim-6.3.046-0.30E.1.src.rpm Best regards, Tru Huynh (deeply confused)

1 0

Open/Closed Ports
by Wayne Bastow 11 Jan '05

11 Jan '05

Hi, Just installed CentOS 3.3. I said to allow only http and ssh when I did the install. I can ssh to the machine and until I compiled apache 2 and installed it seperately I could connect to the default web server. I am running oracle on the box and have found that I can't connect remotely to oracle from another linux box (sql*net works fine on the CentOS box itself). I think it is because the port (oracle is on 1521) is blocked. Can anyone give me an idea of where to start? I've looked at hosts.deny/allow and they both contain no entries and I can't find anything in /etc that seems to be involved in the problem. Thanks, Wayne

4 5

Ok to update to 3.4
by cweisiger＠i-55.com 11 Jan '05

11 Jan '05

i get very little updates from yum, so i was wondering if it is ok to go ahead and update to 3.4, being im running 3.3.. i run a minimal system...minus a few packages removed after install. just didnt know about any possible security issues that would come down for 3.3 if i have updated to 3.4..how would or would i even need them....or will the upcoming security, bugs, etc.. be strictly for 3.4?...what im trying to say is would i miss any updates if i updated to 3.4, that are meant for 3.3?

2 1

Think someone has got into my server...
by WipeOut 11 Jan '05

11 Jan '05

I have just run chkrootkit on my server and have the following two suspicious entries.. Searching for suspicious files and dirs, it may take a while... /usr/lib/perl5/5.8.0/i386-linux-thread-multi/.packlist and further down.. Checking `bindshell'... INFECTED (PORTS: 465) Anyone have any advice for getting rid of it?? Later..

4 5

New public rsync/http/ftp mirror of CentOs Linux in Asia
by ftp-adm 11 Jan '05

11 Jan '05

Hi Following public mirror for CentOS Linux is available. Please add our URL's to the Download/Mirrors pages of CentOS. ftp://ftp.riken.jp/Linux/caos http://ftp.riken.jp/Linux/caos rsync://ftp.riken.jp/caos WAN Connectivity : 1 Gbps (Tire 1) rsync update : four times per day to mirror.caosity.org::cAos city/state/Country : Wako/Saitama/Japan Best Regards, Takashi Ichihara ( ftp-adm(a)alpha.riken.go.jp)

1 0

an RPM conundrum
by Barry L. Kline 11 Jan '05

11 Jan '05

I have an interesting chicken-and-egg problem that I hope someone can help me out of. I have a machine on which I originally loaded White Box. I subsequenty converted to CentOS using the instructions found numerous times in the group -- e.g. get the redhat-package RPM (thus changing /etc/redhat-release), then configuring yum and then yum -y upgrade. Everything has been going fine... that is until I tried installing the rpm-build package. Now I'm getting the message: [root@intranet root]# yum install rpm-build Gathering header information file(s) from server(s) Server: CentOS-3.3 - Addons Server: CentOS-3.3 - Base Server: CentOS-3.3 - Extras Server: CentOS-3.3 - Updates Finding updated packages Downloading needed headers Resolving dependencies ....Unable to satisfy dependencies Package rpm-build needs rpm = 4.2.3-10, this is not available. Which I assume is caused by my version of rpm: rpm-4.2.3-10.WB1 I can't seem to figure out how to convert RPM packages and, of course, I can't simly rpm -e rpm and then use the erased package to install itself. I've tried a simple yum --download-only ... but the dependency check still occurs. Any thoughts on what to try next? TIA, Barry

2 2

problem building the isos?
by security 11 Jan '05

11 Jan '05

Hello all, I am making my own distribution based on RHEL AS 3U4 (with additional rpms, like urpmi, webmin, nessus, Maildir format by default for Postfix, courier-IMAP etc.) and I would like to have information from the CentOS team. I am generating the isos of this distribution but during the launching of anaconda, the graphic interface failed to work, so the installation in text mode is the only one possible. I think i find the problem: pam. by using pam-0.75-51, all is ok (graphical install of anaconda) but with more recent versions, anaconda refuses to launch the graphical install. Question: had somebody similar problems?? Thank you in advance and good year to all :) -- jean-sébastien Hubert Service Informatique Air-Austral 0262 93 10 34 interne: 182 http://www.air-austral.com

2 3

CentOS 3.4 - i386 release
by Lance Davis 11 Jan '05

11 Jan '05

For Release: January 10, 2005 The CentOS Team is pleased to announce the official release of CentOS 3.4 for i386. This release includes all RHEL 3 updates (for U4) and errata up to January 5th, 2005. New ISO images are available as well as an installable DVD edition with source. In addition this release is available via BitTorrent. Downloading -- Bittorrent ------------------------- Bittorrents of a DVD image , binary iso's, and source iso's are available as follow: dvd iso http://mirror.centos.org/centos/3.4/isos/i386/CentOS-3.4-i386-dvd.iso.torre… 3 binary iso's http://mirror.centos.org/centos/3.4/isos/i386/CentOS-3.4-i386-discs1-3.torr… 3 source iso's http://mirror.centos.org/centos/3.4/isos/i386/CentOS-3.4-i386-src1-3.torrent Please use bittorrent and keep your downloader running for others to use even after the download completes. If you need to install bittorrent for CentOS, rpms are available from Dag's repository. http://dag.wieers.com/packages/bittorrent/bittorrent-3.4.2-1.1.el3.rf.noarc… An earlier version of bittorrent is also available in the CentOS 3.3 <contrib> repo - which may be installed using 'yum install bittorrent' - a gui version is also available - 'yum install bittorrent-gui' Then execute btdownloadcurses.py <url to .torrent file> in a shell. (or btdownloadgui.py for the gui) You may need to open ports 6881-6889 and 6969 if you have tight firewall restrictions. The .torrent files are also available on all caosity mirrors. Once again - please leave your downloader running after the download is complete (with ports 6881-6889 open) as your downloader will become part of the peer to peer bittorrent network and reduce the load on our mirror servers. Further information on bittorrent is available at http://bittorrent.com Downloading -- .iso images ------------------------- iso images are available from your favorite CentOS mirror as well. A current list of mirrors can be obtained from http://www.centos.org/mirrors Purchasing ---------- isos are available to purchse from www.cheeplinux.com (UK) and should also be available from a number of other online vendors. Upgrade Notes ------------- Initially CentOS 3.3 systems will not be automatically upgraded to CentOS 3.4. However in 72-96 hours from this announcment the centos-release rpm for 3.4 will be added to the 3.3 tree and that will force automatic upgrades when using yum. If you do NOT want to upgrade then exclude centos-release from updates in your yum.conf. We will try to maintain security updates for CentOS 3.3 for as long as there are no issues that mean they cant be used (eg 3.4 specific dependency issue) -- but as soon as that happens we will have to close the CentOS 3.3 tree. From this point forward $releasever will stay at 3. When 3.5 is released systems will automatically get updated. To prevent this you will need to hard code 3.4 in yum.conf in place of $releasever. To manually upgrade to CentOS-3.4 (now) --------------------------------------- first rpm -ivh http://mirror.centos.org/centos/3.4/os/i386/RedHat/RPMS/centos-yumcache-3.1… (to avoid the header downloads) (Note: If you had poreviously upgraded from CentOS 3.1 then you will already have a cento s-yumcache rpm installed and rpm will complain , in which case use rpm -Fvh) rpm -Fvh http://mirror.centos.org/centos/3.4/os/i386/RedHat/RPMS/centos-release-3-4.… (to get the new releasever) then yum update To automatically upgrade to CentOS 3.4 (from 72-96 hours time) ------------------------------------------------------ We recommend that you install centos-yumcache before updating as it will save all the header downloading. yum install centos-yumcache yum update centos-release yum update Otherwise yum will take two update cycles to perform the update, the first will update centos-release and the second will download all the headers and then update all the packages. CENTOSPLUS ---------- The new CentOSplus repo is designed to allow us to provide extended functionality to CentOS without compromising compatibility with Redhat Enterprise Linux. Packages that will live in CentOSplus - such as MySQL-4 - would update packages in the base distro, so it is only recommended that you enable CentOSplus in yum.conf when you are sure that is what you want. The difference between CentOSplus and 'extras' is that 'extras' are additional packages that are not already installed, so would not update existing packages beyond Rhel-3 , but provide extra functionality. It is hoped that there will be a wide range of CentOSplus packages provided in the future. RELEASE NOTES & CAVEATS ----------------------- -- YUM -- Your yum.conf should not get overwritten by the upgrade, but the new version may get written as yum.conf.rpmnew If your /etc/yum.conf file is a symlink to centos-yum.conf and you have manually edited centos-yum.conf, your centos-yum.conf file will be replaced by a new centos-yum.conf from the centos-yumconf rpm file in CentOS 3.4. Your existing centos-yum.conf file will be saved as yum.conf-SAVE. The following changes have been made tp the default centos-yum.conf :- Reference to the CentOSplus repository has been added (see below) but is not activated. The download path has changed from /centos-3/$releasever to /centos/$releasever to allow for update to CentOS-4 and later versions without having to change the configuration file. If you have edited yum.conf then neither of these changes will prevent it working but you would be advised to make them to avoid future problems. -- CENTOS-RELEASE RPM -- In order to accomodate compatibility with Dag's and other 3rd party repositories, the naming convention of centos-release has been changed. The version is now 3 (rather than 3.3) and will remain fixed $releasever used by yum) for the life of CentOS 3. The first number of the release will now carry the designation of the edition. For example, CentOS 3.4 ships with centos-release-3-4.2. The version is 3 and the release is 4.2. Compare this with the centos-release from the prior version: centos-release-3.3-1. yum detected $releasever as 3.3. Dag's excellent repository of Enterprise Linux RPMS. can be found at http://dag.wieers.com/home-made/apt/ -- RPM -- Due to an upstream bug that causes RPM to fail and requires manual elimination of the RPM database, CentOS 3.4 ships with the RPM used in CentOS 3.3. When the upstream providor releases a patched RPM the CentOS team will follow suit. CentOS 3.4 ships with rpm-4.2.3-10 as did CentOS 3.3 rather than rpm-4.3.3-13 provided with rhel3 U4. (https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=143532) -- MAILMAN -- CentOS 3.4 now ships with mailman as released by RedHat with quarterly Update 4 (U4). However the CentOS 3.4 verion is NOT compatible with the version available via CentOS 3.3 Extras. Since you can't read the Mailman upgrade documentation, we have made the upgrade notes available on the CentOS website. Read them here http://www.centos.org/mailman Databases will need to be manually updated per the instructions above. If want to avoid upgrading Mailman at this time, then temporarily exclude mailman from updates in your yum.conf until you are happy with the upgrade. No further updates to the 3.3 version of mailman will be released by the CentOS team. ------------ To stay up to date with CentOS join the CentOS mailing list at http://lists.caosity.org/mailman/listinfo/centos Join #centos at irc.freenode.net Or participate in the web forums at www.centos.org Please add any errors or bugs you encounter to buzilla on http://www.centos.org/bugs. Enjoy, The CentOS Team Lance Davis CentOS 3 i386 Release Manager

3 3

3.3 -> 3.4 transition
by Joe Pruett 11 Jan '05

11 Jan '05

maybe some of the 3.4 beta discussion has covered this, i wasn't watching it too closely. what is going to be the process to convert a system from 3.3 to 3.4? will a simple yum update work? or do we have to do something more intentional to make it happen? how does redhat handle u3->u4 updates? i assume that since u4 has been published that security patches from rh will only apply to u4? or do they also supply security patches for u3 for some period of time?

6 6

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