Discuss

discuss@lists.centos.org

8 participants
34745 discussions

How do point releases work?
by Steve Snyder 22 Apr '05

22 Apr '05

I'm new to RHEL-like distros. When, say, CentOS 4.1 is released, will it simply be CentOS 4.0 + released updates in new ISO images? Or is it more than just the updated packages integrated into the full distribution? Put another way, if my 4.0 installation is kept up to date with YUM, will I basically have a 4.1 installation? Thanks.

4 3

How to record a data CD ?
by Mário Gamito 22 Apr '05

22 Apr '05

Hi, For years that i've been recording CDs and DVDs and all well. Now, i can't in CentOS-4 First i run: # mkisofs -r -J -o cd_backup cd/ Then # cdrecord -scanbus Output is: cdrecord: Warning: controller returns wrong size for CD capabilities page. 1,0,0 100) 'SAMSUNG ' 'CD-ROM SC-148F ' 'F008' Removable CD-ROM 1,1,0 101) 'HP ' 'CD-Writer+ 9500 ' '1.0e' Removable CD-ROM 1,2,0 102) * 1,3,0 103) * 1,4,0 104) * 1,5,0 105) * 1,6,0 106) * 1,7,0 107) * [root@tux gamito]# So, i used to record using: # cdrecord -v speed=16 dev=1,1,0 -data cd_backup But i get this error: "[root@tux gamito]# cdrecord -v speed=4 dev=1,1,0 -data cd_backup cdrecord: No write mode specified. cdrecord: Asuming -tao mode. cdrecord: Future versions of cdrecord may have different drive dependent defaults. cdrecord: Continuing in 5 seconds... Cdrecord-Clone 2.01-dvd (i686-pc-linux-gnu) Copyright (C) 1995-2004 JÃ¶rg Schilling Note: This version is an unofficial (modified) version with DVD support Note: and therefore may have bugs that are not present in the original. Note: Please send bug reports or support requests to http://bugzilla.redhat.com/bugzilla Note: The author of cdrecord should not be bothered with problems in this version. TOC Type: 1 = CD-ROM scsidev: '1,1,0' scsibus: 1 target: 1 lun: 0 cdrecord: Success. Cannot open SCSI driver. cdrecord: For possible targets try 'cdrecord -scanbus'. cdrecord: For possible transport specifiers try 'cdrecord dev=help'." Any ideas ? Thanks in advance Warm Regards, Mário Gamito

4 5

CentOS-announce Digest, Vol 2, Issue 11
by centos-announce-request＠centos.org 22 Apr '05

22 Apr '05

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-2005:383 Critical CentOS 4 i386 and x86_64 Firefox - security update (Johnny Hughes) 2. firefox 1.0.3 for CentOS-3/ia64 (Pasi Pirhonen) ---------------------------------------------------------------------- Message: 1 Date: Thu, 21 Apr 2005 07:22:18 -0500 From: Johnny Hughes <johnny(a)centos.org> Subject: [CentOS-announce] CESA-2005:383 Critical CentOS 4 i386 and x86_64 Firefox - security update To: centos-announce(a)centos.org Message-ID: <1114086138.3236.16.camel(a)myth.home.local> Content-Type: text/plain; charset="us-ascii" CentOS Errata and Security Advisory CESA-2005:383 for i386 and x86_64 http://rhn.redhat.com/errata/RHSA-2005-383.html refers The following updated files have been uploaded and are currently syncing to the mirrors: i386: firefox-1.0.3-1.4.1.centos4.i386.rpm x86_64: firefox-1.0.3-1.4.1.centos4.x86_64.rpm src: firefox-1.0.3-1.4.1.centos4.src.rpm Get with the command: yum update firefox Thanks, Johnny Hughes

1 0

Centos EOL changes
by Michael Rock 22 Apr '05

22 Apr '05

Hi, has the end of life and yum update process changed for Centos? I want to stick with a release, but receive security updates to maintain stability on my critical servers. Last year I remember the plan being that if you picked 3.1, 3.3 or 3.4 you could stick with it and automatically receive yum updates without changing anything. Then when 3.4 came out the Centos readme said if you were on 3.3 you would automatically be updated to 3.4 through yum. That never happened and I remember reading some where here it would not. Which was fine by me since I assume that was due to sticking to the original plan. But now it seems I have a 3.3-1 server that all of sudden looks like it wants to update to 3.4. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

3 2

centos 4 apt repository
by Mark Quitoriano 22 Apr '05

22 Apr '05

any repository for centos 4?

2 4

Dovecot .99.11 build fails; libiconv
by Karl S. Katzke 22 Apr '05

22 Apr '05

Well, it seems this just isn't my day. Using the source RPM from a centos mirror, I tried to rebuild (and, after that fails) build manually a dovecot RPM. I get several errors about automake's iconv macro, AM_ICONV, missing, and then the install fails while looking for libiconv. I tested by first trying to rebuild the RPM, and when that failed, building the RPM manually by installing in sources and building, and when THAT failed, by unpacking the tarball and manually ./configure and make. Thanks to some googling around, I found that libiconv is a GNU package that's available in source, but that should generally be satisfied in glibc according to postings on the redhat mailing list. However... well, it seems that it isn't. Either that, or it's settled by a specific version of glibc, which I don't have in my glibc-2.3.4-2 ... and yes, I do have -common, -devel, -headers, -kernheaders, etc. installed for i686. I do have iconv.h on my system, but dovecot is specifically looking for libiconv. Anyone seen this before? Thanks, Karl Katzke

1 0

RE: [CentOS] X330 Keyboard/box dies on install 4.0, not on 3.4
by Graham Johnston 21 Apr '05

21 Apr '05

> -----Original Message----- > From: centos-bounces(a)centos.org > [mailto:centos-bounces@centos.org] On Behalf Of Karl S. Katzke > Sent: Thursday, April 21, 2005 5:57 PM > To: centos(a)centos.org > Subject: [CentOS] X330 Keyboard/box dies on install 4.0, not on 3.4 > > I've got a handful of IBM X330's at my colo and another couple at the > office for testing purposes. Currently, they're running > CentOS 3.4 and > are very happy doing so. The 3.4 install was perfectly seamless. > > When I tried to upgrade one of my test machines to 4.0, the keyboard > died once I got into the install every single time once I boot to > anaconda from the CD. It dies as soon as the blue-background screen > appears, and it dies no matter which selection I choose at isolinux. > (I'm sure the system isn't locked because the keyboard is > dead while the > SCSI driver is loading, and the system keeps chugging along happily > until it needs input.) > The CD passes all of the tests I can apply to it, from > checksum to media > check, and has been used to install a half dozen machines > both before or > since. I also downloaded a new ISO from a different mirror > and reburnt > another one; it's most certainly the install package. The box itself > runs 3.4 quite happily. Note that x330s use IBM's cable-chaining > technology, which is great if you've got a tiny colo rack > with a lot of > servers in it like I do, since I don't have to have a KVM. > > So what changed in the install process? How can I get this > resolved well > enough to be able to use the CentOS 4 CDs? both the 3.4 and > 4.0 install > I realize that I could reaim my repository and upgrade to 4 > via yum, but > that's a pain if I'm having to bring a whole box back up from > scratch... > not to mention a nice hit to my bandwidth bill at my colo. > > Suggestions? Ideas? > > Thanks in advance, > -Karl Katzke Karl, I am not sure that it is the x330. We also have half a dozen x330s and although I don't have centos 4 on all of them I am confident that we have successfully installed centos 4 at least three times on this server. We are also using the dvi like breakout cable, and it attaches to an HP cat5 kvm. Graham

1 0

X330 Keyboard/box dies on install 4.0, not on 3.4
by Karl S. Katzke 21 Apr '05

21 Apr '05

I've got a handful of IBM X330's at my colo and another couple at the office for testing purposes. Currently, they're running CentOS 3.4 and are very happy doing so. The 3.4 install was perfectly seamless. When I tried to upgrade one of my test machines to 4.0, the keyboard died once I got into the install every single time once I boot to anaconda from the CD. It dies as soon as the blue-background screen appears, and it dies no matter which selection I choose at isolinux. (I'm sure the system isn't locked because the keyboard is dead while the SCSI driver is loading, and the system keeps chugging along happily until it needs input.) The CD passes all of the tests I can apply to it, from checksum to media check, and has been used to install a half dozen machines both before or since. I also downloaded a new ISO from a different mirror and reburnt another one; it's most certainly the install package. The box itself runs 3.4 quite happily. Note that x330s use IBM's cable-chaining technology, which is great if you've got a tiny colo rack with a lot of servers in it like I do, since I don't have to have a KVM. So what changed in the install process? How can I get this resolved well enough to be able to use the CentOS 4 CDs? both the 3.4 and 4.0 install I realize that I could reaim my repository and upgrade to 4 via yum, but that's a pain if I'm having to bring a whole box back up from scratch... not to mention a nice hit to my bandwidth bill at my colo. Suggestions? Ideas? Thanks in advance, -Karl Katzke

1 0

Re: [CentOS] Centos EOL changes
by Michael Rock 21 Apr '05

21 Apr '05

I went ahead with the yum update, now 'rpm -q centos-release' shows: centos-release-3.3-1 centos-release-3-4.2 I had walked away from a vnc session as it was yum updating and came back to a closed vnc sessions. So I thought maybe it did not finish. However a server reboot and a subsequent 'yum clean' and 'yum update' did not yield any new additions. So it looks like it got everything but not sure if it should show both versions in 'rpm -q centos-release'? thx again -- Mike --- Matt Hyclak <hyclak(a)math.ohiou.edu> wrote: > On Thu, Apr 21, 2005 at 02:14:07PM -0700, Michael > Rock enlightened us: > > I was getting security updates from yum centos > > mirrors regularly on the 3.3-1 servers and checked > the > > Centos errata. So I assumed the default unchanged > > centos yum.conf was giving me everything I needed. > Now > > it seems yum will jump me from 3.3-1 to 3.4. > > > > Does this all sound about right? > > > > (I figured after seeing this I must be doing > something > > wrong or the process changed somewhere. I do not > > remember seeing an announcement other than the one > > back in January but later someone mentioned the > > automatic update to 3.4 would not happen). > > > > If my memory serves me, there was a problem with > bind breaking during an > upgrade from 3.3 to 3.4, so until the problem was > fixed (within the last > week or two), both the 3.3 and 3.4 trees were > maintained separately. Now > that the problem has been resolved, the maintainers > have combined it all > back into a single tree. > > Matt > > -- > Matt Hyclak > Department of Mathematics > Department of Social Work > Ohio University > (740) 593-1263 > > _______________________________________________ > CentOS mailing list > CentOS(a)centos.org > http://lists.centos.org/mailman/listinfo/centos > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

2 1

RE: [CentOS] Apache, MySQL, and PHP
by Mark A. Lewis 21 Apr '05

21 Apr '05

> -----Original Message----- > From: centos-bounces(a)centos.org > [mailto:centos-bounces@centos.org] On Behalf Of Olaf Greve > Sent: Wednesday, April 20, 2005 3:17 AM > To: CentOS mailing list > Subject: Re: [CentOS] Apache, MySQL, and PHP > > Hi, > > I have set up this combination on various platforms, > including Windows, FreeBSD, RHEL and CentOS and I must say > that by far the easiest was CentOS. Now, how is this any different than what you would do on RHEL? Seeing as Cent is based on it, it would be identical. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.

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