Discuss

discuss@lists.centos.org

1 participants
34753 discussions

Raidcore SATA support
by Mark Weaver 21 Jun '05

21 Jun '05

Hi all, I was wondering if anyone has tried and succeeded to use this controller. Its the bc4852 SATA controller. There's supposed to be support for it, but so far we've not been able to get the driver to load during the install and thus we've got no "valid drive" on which to load the OS. thanks, -- Mark

1 0

Re: [CentOS] CentOS 4.0 -> 4.1 update failing
by Bryan J. Smith <b.j.smith＠ieee.org> 21 Jun '05

21 Jun '05

From: Johnny Hughes <mailing-lists(a)hughesjr.com> > All of that is probably true ... but the optimizations are already set > by default by the config.guess and autoconf and automake for almost all > RedHat SRPMS ... and CentOS doesn't change those, unless absolutely > necessary. Which is what I agree is most preferrable. > Therefore, for almost all packages on CentOS-3 they are --march=i386 > --mtune=i686 ... Maybe I need to look a bit deeper then. I could have swore I've seen many packages with Makefiles (after any autoconf) that clearly send to stdout a "gcc ... --march=i486". Maybe I'm thinking too much of just the kernel itself. > and for most CentOS-4 packages they are --march=i386 -- > mtune=pentium4 ... being that the default target is i386. Yep, I guess the --mtune=pentium4 was introduced with FC2+. I would recommend Intel backtrack though, because it's not the most ideal for other i686 architectures (only true P4 or Athlon). Although the performance hit is not that much. -- Bryan J. Smith mailto:b.j.smith@ieee.org

1 0

Re: [CentOS] CentOS 4.0 -> 4.1 update failing
by Bryan J. Smith <b.j.smith＠ieee.org> 21 Jun '05

21 Jun '05

From: Johnny Hughes <mailing-lists(a)hughesjr.com> > Right ... but in a software capacity we are also talking about pentium, > pentium mmx, cyrix i686, amd k6, via c3 that use i586 packages. No! You _never_ want anything but a _true_ Pentium or Pentium MMX using i586. i586 ISA and/or optimization are _not_ good for anything but those 2 chips. You want to use i686 for AMD K6, Cyrix M2 and Via C3. You want to use i486 for AMD K5 and Cyrix 6x86/M1. This is one of the most misunderstood details in the user world. > CentOS is trying to provide limited support for them. This support > doesn't in any way affect other packages like glibc.i686 or the i686 > kernels ... In case someone might be concerned about a CentOS / RHEL > divergence. The i586 packages are only installed on machines that have > i586 processors ... I understand that. But the point you are missing is that there are _only_2_ "i586 ISA" processors: Pentium and Pentium MMX Do not confuse "i586 class" with "i586 ISA." I appreciate that CentOS offers these added processors, since Red Hat does not consider it their bother -- whether they only ship i486 and i686, or just i686 now (since all designs of the mid-to-late '90s are i686 ISA). > if you have i686 then that is what is installed on your machine. I understand. > Red Hat did seem open to at least reviewing a patch to the glibc > package that provides i586 support if we get it working. And that's great. But I'm sure the marketshare is why they didn't do it themselves. Right now, the market is: i686 ISA compatible > i486 ISA compatible > i586 ISA compatible And it's been like that for awhile. But even before then, it's _always_ been: i486 ISA compatible > i586 ISA compatible i586 is not recommended, even if i686 ISA compatible typically means i586 is supported. It's just rather poor performing, and you can occassionally run into a serious instruction issue (especially with early i686 clones that did i686 fine, but not always i586). There is _no_ "i586 clone" -- no one would purposely clone the Pentium's instruction set because it was quickly superceded by i686 for good reasons. Unfortunately, Intel took forever to get past its Pentium Pro offering, which was never designed for consumers, and finally offer an i686 for consumers in the Pentium II. Hence why i686 clones like the AMD K6 actually pre-date much of the widespread consumer adoption of an i686 from Intel itself because the consumer chip didn't hit for years after its first ISA. idSoftware always had excellent commentary on i586 v. i686, largely because they found some of the best hacks for i586 to get around many of its ALU design flaws. -- Bryan J. Smith mailto:b.j.smith@ieee.org

7 10

question about updates with centos 3.x / Upgrade to 3.5 for the updates or reinstall all servers with centos 3 ?
by Cesar Lagarrigue 21 Jun '05

21 Jun '05

Hello i have a doubt, if i installed 3.3 , 3.4 or 3.5, i see the mirrors removed the 3.1-3.4 i have a 3.3 running ....but i thinked the rhel flavors are supposed to long life (3~5 years) but not understand, i to upgrade to 3.5 for have the lastest updates? Reinstall servers to centos 3.5 are big job... or then i have to install centos 3 with no revision for have long life s.o for get the updates? Thanks a lot. -- Cesar Lagarrigue V. Ingeniero de sistemas BEE Consultorías y Sistemas Fono : (562) 231-7131 Fax: (562) 231-7136 Carmencita 25 Of.62 Las Condes Santiago de Chile www.bee.cl

4 3

MySQL 5
by Marco Bascietto 21 Jun '05

21 Jun '05

Hello List, has anyone installed MySQL 5 on a CentOS box from the RHEL 4 rpms found in [1]? Any tips to perform the installation in the SElinux environment? Best regards, Marco [1] http://dev.mysql.com/downloads/mysql/5.0.html

1 0

Dell PE 6850 with CentOS-3
by Morten Tørmoen 21 Jun '05

21 Jun '05

Hi list, I'm seeing problems when probing cdrom and floppy devices on a Dell PowerEdge 6850 (4x3.16GHz, 16GB RAM) with CentOS-3.4 using 2.4.21-27.0.4.ELhugemem. When I run snmpwalk the system hangs with 100% wait on all 8 cpu's (in HyperThreading mode) for approx 20s before it goes back to idle state. Same thing if I open/probe any of the cdrom/floppy devices in other ways also. If I BIOS-disable cdrom and floppy and prevents loading of these modules, the symptoms are gone and snmpwalk runs fine. ...but the problem still exits. :-) Has anyone encountered similar problems? Best regards, Morten -- morten tørmoen, morten(a)basefarm.no, +47 97 77 47 77 basefarm as, http://www.basefarm.no, +47 40 00 41 00

1 0

Re: [CentOS] Yum repository info
by Rohan Walsh 21 Jun '05

21 Jun '05

>> Would like to know where I could find repo info to be able to install >> frozen-bubble and/or supertux please. > >If I'm correct (but you should check the buildlogs on the website), >the >problem is building perl-SDL and SDL on RHEL3 and RHEL4, and that's >required for frozen-bubble. > >I think it even requires replacing something that belongs to base in >order >to get it done. But if you investigate and report back I will >re-evaluate my decision :) >PS You can also try the RH9 build for RHEL3, and the FC3 build for >RHEL4 >if you feel lazy. using Dags and Dries repos for Centos 4, and FC3 source repo (as below) using apt, apt-get -b source {package} will work for everything that isn't in binary for FC4 to get supertux and frozen-bubble. No doubt yum would work fine too. rpm-src http://ayo.freshrpms.net/ fedora/linux/3/i386 core rpm-src http://ayo.freshrpms.net/ fedora/linux/3/i386 os rpm-src http://ayo.freshrpms.net/ fedora/linux/3/i386 extras rpm-src http://ayo.freshrpms.net/ fedora/linux/3/i386 updates

1 0

OT: question on setting up an email server
by Jimmy Bradley 21 Jun '05

21 Jun '05

Hi guys, I realize that this might be considered to be off topic, but the machine I want to use is running Cent OS. Ok, this is what I'm thinking about trying, and mainly just to see if I can do it. I've got a total of 3 linux machines here, and I was thinking about setting one of them up as an email server. Now, I'm not talking about setting the machine up so that all I run on it is an email client like thunderbird, or evolution and retrieve email from my email account at bellsouth. What I want to try and do is set the machine up so that my machine is the email server, and I retrieve my email from it. Is what I'm thinking about even possible, or am I just simply having a case of too much oxygen on the brain? If what I'm thinking about is possible, how would I go about doing it? Thanks Jimmy

12 22

RE: [CentOS] script to make a CentOS 4.0 respository updates server...
by Mark A. Lewis 21 Jun '05

21 Jun '05

My bad. Did not read the original post. > -----Original Message----- > From: centos-bounces(a)centos.org > [mailto:centos-bounces@centos.org] On Behalf Of Mark A. Lewis > Sent: Monday, June 20, 2005 8:42 PM > To: CentOS mailing list > Subject: RE: [CentOS] script to make a CentOS 4.0 respository > updates server... > > Shouldn't we be using rsync instead of wget? > > > -----Original Message----- > > From: centos-bounces(a)centos.org > > [mailto:centos-bounces@centos.org] On Behalf Of Paul > > Sent: Monday, June 20, 2005 8:37 PM > > To: CentOS mailing list > > Subject: Re: [CentOS] script to make a CentOS 4.0 > respository updates > > server... > > > > On Mon, 2005-06-20 at 14:14 -0500, israel.garcia(a)cimex.com.cu wrote: > > > List, I have a CentOS 4.0 server in my intranet which will > > serves as a > > > CentOS repository updates, so I need a script to do that > job, I can > > > not use RSYNC. I just want to download CentOS 4.0 updates > > every night. > > > > > > Can you help me? > > > > > > Regards, > > > Israel > > > > > > > The following script is one I use ... though it could be > optimized to > > just download the RPMs and use createrepo to recreate the metadata. > > > > The script I use is as follows: > > #!/bin/sh > > # > > # mirror-centos.sh - Mirror CentOS Linux Updates # > > > > # Variables > > MIRROR="mirror.cs.wisc.edu" > > WBDIR="pub/mirrors/linux/caosity.org/centos" > > VERSIONS="4" > > ARCHS="SRPMS i386 x86_64" > > WBUPDATES="/home/ftp/pub/centos" > > PROXY="http://firewall.company.com:8080/" > > > > # Limit Transfer Rate to 10K bytes per second MAXRATE="10k" > > > > # Do the mirror > > for d in $VERSIONS; do > > for y in $ARCHS; do > > cd $WBUPDATES > > ## env http_proxy=$PROXY \ > > wget --non-verbose --no-host-directories --cut-dirs=8 --mirror \ > > --passive-ftp --limit-rate=$MAXRATE \ > > --directory-prefix=$WBUPDATES/$d/updates/$y \ > > ftp://$MIRROR/$WBDIR/$d/updates/$y > > ##--output-file=/tmp/mirror-centos.log > > > > # the RPMS should be checked for valid sigs, not ready for that > > yet > > ##rpm --checksig $WBUPDATES/$d/updates/$y/*.rpm | grep 'NOT OK' > > done > > done > > > > > > # Done > > exit > > > > _______________________________________________ > > CentOS mailing list > > CentOS(a)centos.org > > http://lists.centos.org/mailman/listinfo/centos > > > > -- > > This message has been scanned for viruses and dangerous content by > > MailScanner, and is believed to be clean. > > > > > > -- > This message has been scanned for viruses and dangerous > content by MailScanner, and is believed to be clean. > > _______________________________________________ > CentOS mailing list > CentOS(a)centos.org > http://lists.centos.org/mailman/listinfo/centos > -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.

2 1

CentOS 4.0 -> 4.1 update failing
by Aleksandar Milivojevic 21 Jun '05

21 Jun '05

I've updated CentOS 4.0 to 4.1 on several machines (some desktops, some servers). However on my laptop, update is failing with following error just after headers are downloaded: --> Running transaction check --> Processing Dependency: glibc-common = 2.3.4-2 for package: glibc --> Finished Dependency Resolution Error: Missing Dependency: glibc-common = 2.3.4-2 is needed by package glibc My CentOS.repo is a standard one, as distributed with CentOS. I don't have any additional repos defined on my laptop. I attempted to clear yum cache (rm -rf /var/cache/yum/*). Rerun yum update, and got the same error again. Looking at the /var/cache/yum/base/headers, I see that yum downloaded headers for gblic-common, glibc-devel, and glibc-headers, but not for glibc. Seems as if yum did not considered base glibc package to be due for update. Running rpm -q glibc, shows that currently installed version of glibc is 2.3.4-2 (and all the other currently installed glibc packages are at the same version level). I don't remember doing anything fancy on that laptop that could have triggered this problem. Basically, it was normal install (desktop+devel packages mostly), and after that it was regulary updated from cron. Of course, as a workaround I could download glibc and related packages and update it by hand, and than rerun yum update to get all other updates from 4.1. But, I though it would be more fun if anybody could give me hint or two why yum failed to update this particular system.

4 9

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