Hello list,
I'm a former Trustix User (were active in that community since the very first betas), and now that my dear distro is dead, I'm looking to make a switch..
Several people recommended CentOS, so I decided to give it a spin.. I installed one new server with 5.0 a few months back, and I do have a couple of questions..
- Why does the screen flicker on and off several times during boot and when logging in? - Why does floppy.so get loaded? I have no floppy, and having floppy.so loaded while installing certain packages is dreadfully slow. - When I chose a pure console environment, without any X11 stuff, why did a bunch of gnome packages get installed? - Is it possible to get a php-mssql package? -I need this if I'm going to use CentOS at work..
I think that's it for now..
Morten Nilsen wrote:
- Why does the screen flicker on and off several times during boot and
when logging in?
mine does not, so cant say what is going on with your setup, perhaps posting some more info about your setup might help make it easier to diagnose.
- Why does floppy.so get loaded? I have no floppy, and having floppy.so
loaded while installing certain packages is dreadfully slow.
nothing like that is loaded on my machine. I dont have a fdd either.
- When I chose a pure console environment, without any X11 stuff, why
did a bunch of gnome packages get installed?
CentOS comes with a package manager, yum. There is a man page for that, and lots of docs online. You can use that to remove anything you dont need.
- KB
Karanbir Singh wrote:
Morten Nilsen wrote:
- Why does the screen flicker on and off several times during boot and
when logging in?
mine does not, so cant say what is going on with your setup, perhaps posting some more info about your setup might help make it easier to diagnose.
Isn't much to say, really.. * ATI Radeon PCI * Intel 975 Chipset
The motherboard is an Asus "Wallstreet Quartet"..
- When I chose a pure console environment, without any X11 stuff, why
did a bunch of gnome packages get installed?
CentOS comes with a package manager, yum. There is a man page for that, and lots of docs online. You can use that to remove anything you dont need.
Yes, I know.. I didn't ask how to remove anything, just why it got installed to begin with.. The gnome stuff is long gone on this box.
Morten Nilsen wrote:
Karanbir Singh wrote:
Morten Nilsen wrote:
- Why does the screen flicker on and off several times during boot
and when logging in?
mine does not, so cant say what is going on with your setup, perhaps posting some more info about your setup might help make it easier to diagnose.
Isn't much to say, really..
- ATI Radeon PCI
- Intel 975 Chipset
The motherboard is an Asus "Wallstreet Quartet"..
- When I chose a pure console environment, without any X11 stuff,
why did a bunch of gnome packages get installed?
CentOS comes with a package manager, yum. There is a man page for that, and lots of docs online. You can use that to remove anything you dont need.
Yes, I know.. I didn't ask how to remove anything, just why it got installed to begin with.. The gnome stuff is long gone on this box.
Some stuff needs some of the Gnome libraries to function properly. I know Xen also installs 1 or 2 Gnome libs along the way. It might be worthwhile to check with rpm which Gnome stuff got installed, and which packages requires them :)
- Why does the screen flicker on and off several times during boot and
when logging in?
I presume you mean when logging in at the console, the fonts look a bit glitchy and flickery at times. I can't recall the exact details, but this is a known RHEL5 bug, caused by the system reloading the fonts every time a character or line of characters is displayed. There was one complicated workaround posted, but for now, this cannot be resolved. I don't see it now, in any case, since I login via ssh and dont need to be at the console.
- When I chose a pure console environment, without any X11 stuff, why
did a bunch of gnome packages get installed?
As strange as it may seem, some apps which are supposedly text-only, have dependencies based on the gnome libs. I can't remember the offending packages offhand, but I don't really care much since disk-space is so cheap.
- Is it possible to get a php-mssql package? -I need this if I'm going
to use CentOS at work..
There is no default rpm for centos5, but one exists for Fedora.
D Steward wrote:
- Why does the screen flicker on and off several times during boot and
when logging in?
I presume you mean when logging in at the console, the fonts look a bit glitchy and flickery at times.
no, that's not it.. the monitor goes into power off mode - the LED turns orange.
I don't see it now, in any case, since I login via ssh and dont need to be at the console.
Yes, I do that too.. but each time I actually need to use the console, this annoys me to no end..
- When I chose a pure console environment, without any X11 stuff, why
did a bunch of gnome packages get installed?
As strange as it may seem, some apps which are supposedly text-only, have dependencies based on the gnome libs. I can't remember the offending packages offhand, but I don't really care much since disk-space is so cheap.
Well, sure.. But on the other hand, it is nice to keep bloat down.
- Is it possible to get a php-mssql package? -I need this if I'm going
to use CentOS at work..
There is no default rpm for centos5, but one exists for Fedora.
I am aware of this fact, which is why I asked for CentOS to add a php-mssql package..
Morten Nilsen wrote:
D Steward wrote:
- Why does the screen flicker on and off several times during boot
and when logging in?
I presume you mean when logging in at the console, the fonts look a bit glitchy and flickery at times.
no, that's not it.. the monitor goes into power off mode - the LED turns orange.
Sounds like your monitor does not like switching modes between text / gui perhaps ?
This is not an issue I have ever seen myself before.
On 3/27/2008, "Karanbir Singh" mail-lists@karan.org wrote:
no, that's not it.. the monitor goes into power off mode - the LED turns orange.
Sounds like your monitor does not like switching modes between text / gui perhaps ?
Which GUI are you referring to? I removed all the X11 stuff..
Also, one time I booted, it had some problems starting some service, and that time the monitor stayed off.. had to ssh in to resolve it..That may indicate that someting in the sysinit shuts off the monitor at the start of a script, then turns it back on at the end..
-- Cheers, Morten :wq
Morten Nilsen wrote:
On 3/27/2008, "Karanbir Singh" mail-lists@karan.org wrote:
no, that's not it.. the monitor goes into power off mode - the LED turns orange.
Sounds like your monitor does not like switching modes between text / gui perhaps ?
Which GUI are you referring to? I removed all the X11 stuff..
Also, one time I booted, it had some problems starting some service, and that time the monitor stayed off.. had to ssh in to resolve it..That may indicate that someting in the sysinit shuts off the monitor at the start of a script, then turns it back on at the end..
Do these options exist in /boot/grub/grub.conf on the "Kernel" line:
quiet rhgb
If so, please remove them if you do not want X on the server. These 2 things try (during boot up) to take away the standard startup screen and replace it with a Blue background and picture. This uses X, which could cause something if it has been removed and the options are still listed.
Removing those options (if they are there) should fix that issue.
We do not seem to have php-mssql for CentOS extras as it requires freetds and we were concerned about potential patent issues with freetds. However, it seems Fedora is including freetds now in version 8 and version 9, so I will research this freetds issue again and if we think we can safely build and distribute freetds I will get it into our extras repo soon. If not, you should be able to easily build it ... but I think we will add it, so not to worry.
======================================================================
on a separate note:
Also ... some rpms do require certain things to be available, and the binaries are LINKED against the shared libraries. So, one can not just delete (for example) all xorg-x11 RPMS just because you don't want X. If you did use "rpm -e" (with a --force or --nodeps) then it should be OK since if a library is necessary, RPM will complain and not do the removal unless overridden.
Thanks, Johnny Hughes
On 3/27/2008, "Johnny Hughes" johnny@centos.org wrote:
that time the monitor stayed off.. had to ssh in to resolve it..That may indicate that someting in the sysinit shuts off the monitor at the start of a script, then turns it back on at the end..
Do these options exist in /boot/grub/grub.conf on the "Kernel" line:
quiet rhgb
If so, please remove them if you do not want X on the server. These 2 things try (during boot up) to take away the standard startup screen and replace it with a Blue background and picture. This uses X, which could cause something if it has been removed and the options are still listed.
Removing those options (if they are there) should fix that issue.
I'll look into it, thanks.
We do not seem to have php-mssql for CentOS extras as it requires freetds and we were concerned about potential patent issues with freetds. However, it seems Fedora is including freetds now in version 8 and version 9, so I will research this freetds issue again and if we think we can safely build and distribute freetds I will get it into our extras repo soon. If not, you should be able to easily build it ... but I think we will add it, so not to worry.
Good to hear :) I know I can easily build it, I supplied contrib rpms of freetds for Trustix a while back, which got adopted into official.. I just asked because I really like getting updates without having to rebuild php/freetds each time..
Also ... some rpms do require certain things to be available, and the binaries are LINKED against the shared libraries. So, one can not just delete (for example) all xorg-x11 RPMS just because you don't want X. If you did use "rpm -e" (with a --force or --nodeps) then it should be OK since if a library is necessary, RPM will complain and not do the removal unless overridden.
Yes, I am well aware of the dependency thing.. I used to maintain a large selection of packages in TSL contrib.. I did rpm -e libgnomesomething and added on packages until it stopped complaining about deps.. As far as X11 goes, I deselected that during install, don't remember having to remove any of those rpms by hand..
-- Cheers, Morten :wq
On Thu, 27 Mar 2008 at 3:24pm, Morten Nilsen wrote
Yes, I am well aware of the dependency thing.. I used to maintain a large selection of packages in TSL contrib.. I did rpm -e libgnomesomething and added on packages until it stopped complaining about deps..
'yum remove libgnomesomething' will do the depsolving for you (just like 'yum install').
Morten Nilsen a écrit :
I don't really mind doing it manually, it yields greater control..
Sorry, but this is an urban myth. Yum and RPM let you control things *equally*. I know, I use them both regularly, everyday, at home and at work. Refusing to use Yum in a situation like the one you describe is just asking for more work.
My short guide for RPM:
http://www.microlinux.fr/article.php3?id_article=7
My short guide for Yum:
http://www.microlinux.fr/article.php3?id_article=8
My advice: give Yum a try, you'll end up liking it :oD
Cheers from the sunny south of France,
Niki
Morten Nilsen wrote:
Joshua Baker-LePain wrote:
'yum remove libgnomesomething' will do the depsolving for you (just like 'yum install').
I don't really mind doing it manually, it yields greater control..
You are still in control - yum will figure out the right thing to do but will wait for your confirmation. The 'right thing' will always depend on the rpm contents anyway even if you do it the hard way.
on 3-27-2008 9:46 AM Morten Nilsen spake the following:
Joshua Baker-LePain wrote:
'yum remove libgnomesomething' will do the depsolving for you (just like 'yum install').
I don't really mind doing it manually, it yields greater control..
Yum gives you a list of what it wants to do and then asks your permission. How much more control do you need?
Morten Nilsen a écrit :
Johnny Hughes wrote:
Do these options exist in /boot/grub/grub.conf on the "Kernel" line:
quiet rhgb
Just got home - and no, they do not..
I remember having had a problem with the CentOS 5.0 kernel when adding 'vga=788' (or 'vga=791') to GRUB's kernel line. Seems like folks just forgot to compile some framebuffer modules into the kernel. This got corrected in 5.1.
The question may sound silly, but are you up-to-date?
Cheers,
Niki
Johnny Hughes wrote:
<snip>
We do not seem to have php-mssql for CentOS extras as it requires freetds and we were concerned about potential patent issues with freetds. However, it seems Fedora is including freetds now in version 8 and version 9, so I will research this freetds issue again and if we think we can safely build and distribute freetds I will get it into our extras repo soon. If not, you should be able to easily build it ... but I think we will add it, so not to worry.
<snip>
OK, for the record, freetds and php-mssql have been added to the CentOS-5 extras repo on the master server. Expect them to be on mirror.centos.org in the next hour and on the external public mirrors with a day.
BTW, Jim Perrin (one of our developers ... aka Evolution on freenode IRC) says that using the freetds and unixODBC driver is a better method to connect:
http://www.bofh-hunter.com/2008/03/27/chatting-with-mssql/
So now you have 2 CentOS repo options to talk to mssql :D
Thanks, Johnny Hughes
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf Of Morten Nilsen Sent: Wednesday, March 26, 2008 11:28 PM To: CentOS mailing list Subject: Re: [CentOS] A few questions regarding CentOS (5.0)
D Steward wrote:
- Why does the screen flicker on and off several times during boot
and when logging in?
I presume you mean when logging in at the console, the fonts look a bit glitchy and flickery at times.
no, that's not it.. the monitor goes into power off mode - the LED turns orange.
That sounds like the X server trying to start and failing. It did just as you describe about 8 times. I JUST experienced the same thing on a Fedora 8 install. Although, it finally failed and asked if I wanted to view the log and manually configure....
I had an un-identified monitor.....
It sounds like you might have removed X already too, so ignore this if it's not relevant... Dennis
Morten Nilsen wrote:
- Why does the screen flicker on and off several times during boot and
when logging in?
In the kernel distributed with RHEL5 / CentOS 5.0, a driver was accidentally omitted (CONFIG_FB_VESA). This makes the text mode display wonky on some common hardware. IIRC, this was not corrected until the 5.1 release. Once you upgrade to the current kernel, that problem should go away.
If you installed 5.0, you're missing a LOT of updates. The normal update mechanism should bring your machine up to 5.1 unless you've taken action to lock it to the 5.0 release.
Robert Nichols wrote:
If you installed 5.0, you're missing a LOT of updates. The normal update mechanism should bring your machine up to 5.1 unless you've taken action to lock it to the 5.0 release.
When I installed this box, 5.1 wasn't out yet.. And, no I haven't taken any kind of action to lock it to 5.0.
I have run "yum update" a few times, but I don't see any signs of it wanting to upgrade to 5.1..
On 27/03/2008, Morten Nilsen morten@runsafe.no wrote:
When I installed this box, 5.1 wasn't out yet.. And, no I haven't taken any kind of action to lock it to 5.0.
I have run "yum update" a few times, but I don't see any signs of it wanting to upgrade to 5.1..
If the command rpm -q centos-release returns centos-release-5-1.0.el5.centos.1 then you *are* running CentOS 5 update 1.
Alan.
Alan Bartlett wrote:
If the command rpm -q centos-release returns centos-release-5-1.0.el5.centos.1 then you *are* running CentOS 5 update 1.
I had previously looked at /etc/issue, which says "release 5 (Final)"..
# rpm -q centos-release centos-release-5-0.0.el5.centos.2 centos-release-5-1.0.el5.centos.1
hmm, that doesn't look right to me..?
on 3-27-2008 12:36 PM Morten Nilsen spake the following:
Alan Bartlett wrote:
If the command rpm -q centos-release returns centos-release-5-1.0.el5.centos.1 then you *are* running CentOS 5 update 1.
I had previously looked at /etc/issue, which says "release 5 (Final)"..
# rpm -q centos-release centos-release-5-0.0.el5.centos.2 centos-release-5-1.0.el5.centos.1
hmm, that doesn't look right to me..?
It looks like your system crashed in the middle of a yum update.
The attached script should fix it up, but check it first, don't just run it.
I would rather you see what it is doing, so you can follow the logic (if you can, it does a lot of pipes in and out of other commands). Maybe trim a copy to just after the first "grep" and look at the list it produces.
on 3-27-2008 1:05 PM Morten Nilsen spake the following:
Scott Silva wrote:
The attached script should fix it up, but check it first, don't just run it.
Your attachment got stripped, it seems..
Trying again...
I had previously looked at /etc/issue, which says "release 5 (Final)"..
As I'm sure you're aware from Johnny Hughes recent posting to this list, the contents of /etc/issue will stay that way for the entire life of CentOS 5.
# rpm -q centos-release
centos-release-5-0.0.el5.centos.2 centos-release-5-1.0.el5.centos.1
hmm, that doesn't look right to me..?
Nor me! I would be tempted to attempt to remove centos-release-5-1.0.el5.centos.1 (rpm -e --test centos-release-5-1.0.el5.centos.1; rpm -e centos-release-5.1.0.el5.centos.1if the test command was o.k.), then try a yum update.
It does look as if your rpm dbase is a bit scrambled. Perhaps a rm /var/lib/rpm/__db.??? would be an idea.
Alan.
On Thu, Mar 27, 2008 at 1:34 PM, Alan Bartlett ajb.stxsl@googlemail.com wrote:
I had previously looked at /etc/issue, which says "release 5 (Final)"..
As I'm sure you're aware from Johnny Hughes recent posting to this list, the contents of /etc/issue will stay that way for the entire life of CentOS 5.
# rpm -q centos-release centos-release-5-0.0.el5.centos.2 centos-release-5-1.0.el5.centos.1
hmm, that doesn't look right to me..?
Nor me! I would be tempted to attempt to remove centos-release-5-1.0.el5.centos.1 (rpm -e --test centos-release-5-1.0.el5.centos.1; rpm -e centos-release-5.1.0.el5.centos.1 if the test command was o.k.), then try a yum update.
rpm -e --justdb may be a good way to remove the newer version (only in the database) and do a yum update.
It does look as if your rpm dbase is a bit scrambled. Perhaps a rm /var/lib/rpm/__db.??? would be an idea.
Well, if it is suspected that there are more duplicates in the rpm database, you might want to follow the procedure detailed in this forum post:
http://www.centos.org/modules/newbb/viewtopic.php?viewmode=flat&topic_id...
Akemi
Alan.
Akemi Yagi wrote:
Well, if it is suspected that there are more duplicates in the rpm database, you might want to follow the procedure detailed in this forum post:
http://www.centos.org/modules/newbb/viewtopic.php?viewmode=flat&topic_id...
I've now gotten the dupes sorted out, and have run yum upgrade.. Next time I reboot the system, I'll report back on the state of the flashing..
Morten Nilsen wrote:
Next time I reboot the system, I'll report back on the state of the flashing..
Rebooted just now to test, and the flashing still happens..
[root@washu3 ~]# uname -a Linux washu3.4th-age.com 2.6.18-53.1.14.el5 #1 SMP Wed Mar 5 11:37:38 EST 2008 x86_64 x86_64 x86_64 GNU/Linux [root@washu3 ~]# rpm -q centos-release centos-release-5-1.0.el5.centos.1
I really do hope somebody have an idea, because this is real annoying.
Morten Nilsen wrote:
Morten Nilsen wrote:
Next time I reboot the system, I'll report back on the state of the flashing..
Rebooted just now to test, and the flashing still happens..
[root@washu3 ~]# uname -a Linux washu3.4th-age.com 2.6.18-53.1.14.el5 #1 SMP Wed Mar 5 11:37:38 EST 2008 x86_64 x86_64 x86_64 GNU/Linux [root@washu3 ~]# rpm -q centos-release centos-release-5-1.0.el5.centos.1
I really do hope somebody have an idea, because this is real annoying.
What happens when you reboot in "safe mode"? I know I have a Suse10.2 machine that does this, but on an old 14" CRT, so by rebooting in safe mode, it drops everything to a safe working mode
Please remember that there are also active CentOS fora. Perhaps this may be of interest:
http://www.centos.org/modules/newbb/viewtopic.php?topic_id=12678&forum=3...
Alan.
Alan Bartlett wrote:
Please remember that there are also active CentOS fora. Perhaps this may be of interest:
http://www.centos.org/modules/newbb/viewtopic.php?topic_id=12678&forum=3...
That does indeed look exactly like what is being described and they are not fixing it in RHEL ... though you might try their patch and see if it fixes it for you.
Johnny Hughes wrote:
Alan Bartlett wrote:
Please remember that there are also active CentOS fora. Perhaps this may be of interest:
http://www.centos.org/modules/newbb/viewtopic.php?topic_id=12678&forum=3...
That does indeed look exactly like what is being described and they are not fixing it in RHEL ... though you might try their patch and see if it fixes it for you.
I don't think that sounds like the same error at all, my screen switches off and depending on what is going on doesn't switch back on right away (like that one time when some process didn't start up and I had to ssh in to poke it)
Nevertheless, I tried applying the patch, and the result was identical..
On 29/03/2008, Morten Nilsen morten@runsafe.no wrote:
I don't think that sounds like the same error at all, my screen switches off and depending on what is going on doesn't switch back on right away (like that one time when some process didn't start up and I had to ssh in to poke it)
Nevertheless, I tried applying the patch, and the result was identical..
Then surely it comes down to an issue with either *your* video controller card or monitor. Please now try the obvious, follow scientific procedures and swap them out, one at a time. Clearly, it is a hardware problem and nothing to do with CentOS - unless you can convince me otherwise.
Alan.
Alan Bartlett wrote:
Then surely it comes down to an issue with either *your* video controller card or monitor. Please now try the obvious, follow scientific procedures and swap them out, one at a time. Clearly, it is a hardware problem and nothing to do with CentOS - unless you can convince me otherwise.
I will first have to find a new vga card to try that.. But I do know it isn't the monitor, as the three other boxes connected to it never show this sort of behaviour..
I have found a way to provoke the flashes, by the way; simply invoking ifup and ifdown triggers it.
On 30/03/2008, Morten Nilsen morten@runsafe.no wrote:
I will first have to find a new vga card to try that.. But I do know it isn't the monitor, as the three other boxes connected to it never show this sort of behaviour..
I have found a way to provoke the flashes, by the way; simply invoking ifup and ifdown triggers it.
Test #1. Original video card. Different monitor. Result #1? Test #2. Different video card. Original monitor. Result #2? Test #3. Different video card. Different monitor. Result #3?
Based on the three results, what can be deduced?
Alan.
Morten Nilsen wrote:
Robert Nichols wrote:
If you installed 5.0, you're missing a LOT of updates. The normal update mechanism should bring your machine up to 5.1 unless you've taken action to lock it to the 5.0 release.
When I installed this box, 5.1 wasn't out yet.. And, no I haven't taken any kind of action to lock it to 5.0.
I have run "yum update" a few times, but I don't see any signs of it wanting to upgrade to 5.1..
Unlike previous versions in 5.x the /etc/redhat-release doesn't change the value to track the minor release. If "yum update" says you are current, you are running 5.1.
Morten Nilsen wrote:
Robert Nichols wrote:
If you installed 5.0, you're missing a LOT of updates. The normal update mechanism should bring your machine up to 5.1 unless you've taken action to lock it to the 5.0 release.
When I installed this box, 5.1 wasn't out yet.. And, no I haven't taken any kind of action to lock it to 5.0.
I have run "yum update" a few times, but I don't see any signs of it wanting to upgrade to 5.1..
The upgrade to 5.1 is seamless. Your actual version (the replacement for "$releasever" in the URL in the yum config file) is "5", not "5.0", which will always track the latest release. Sounds like the kernel version (currently kernel-2.6.18-53.1.14.el5) is not what is causing your problem.
Robert Nichols wrote:
Morten Nilsen wrote:
Robert Nichols wrote:
If you installed 5.0, you're missing a LOT of updates. The normal update mechanism should bring your machine up to 5.1 unless you've taken action to lock it to the 5.0 release.
When I installed this box, 5.1 wasn't out yet.. And, no I haven't taken any kind of action to lock it to 5.0.
I have run "yum update" a few times, but I don't see any signs of it wanting to upgrade to 5.1..
The upgrade to 5.1 is seamless. Your actual version (the replacement for "$releasever" in the URL in the yum config file) is "5", not "5.0", which will always track the latest release. Sounds like the kernel version (currently kernel-2.6.18-53.1.14.el5) is not what is causing your problem.
I have only recently started using CentOS, and have an interesting query on this. If release 5 is always the latest release, does that mean when 5.6 comes out, it will still be v5? And how does the transition for major releases (from 4 to 5, 5 to 6) work?
on 3-27-2008 10:50 AM Rudi Ahlers spake the following:
Robert Nichols wrote:
Morten Nilsen wrote:
Robert Nichols wrote:
If you installed 5.0, you're missing a LOT of updates. The normal update mechanism should bring your machine up to 5.1 unless you've taken action to lock it to the 5.0 release.
When I installed this box, 5.1 wasn't out yet.. And, no I haven't taken any kind of action to lock it to 5.0.
I have run "yum update" a few times, but I don't see any signs of it wanting to upgrade to 5.1..
The upgrade to 5.1 is seamless. Your actual version (the replacement for "$releasever" in the URL in the yum config file) is "5", not "5.0", which will always track the latest release. Sounds like the kernel version (currently kernel-2.6.18-53.1.14.el5) is not what is causing your problem.
I have only recently started using CentOS, and have an interesting query on this. If release 5 is always the latest release, does that mean when 5.6 comes out, it will still be v5? And how does the transition for major releases (from 4 to 5, 5 to 6) work?
5 will always be 5 until it falls off of support. 5.6 is just version 5 at a set point in time with all the upgrades at the time the freeze was set. So you get CentOS 5, but with the current kernel and files at that time. The installer also gets any kernel revisions and patches that are at that point in time. That way a 5.6 install cd/dvd might install on hardware that was unsupported in an earlier point release.
A major release will get the next major number. I don't think any major release will ever automatically update to the next release, as upstream has always recommended a wipe and install over major version upgrades. And since upstream has usually set new releases at an 18-24 month release cycle, you can usually expect a new major release at about every 2 years or so.
Scott Silva wrote:
on 3-27-2008 10:50 AM Rudi Ahlers spake the following:
Robert Nichols wrote:
The upgrade to 5.1 is seamless. Your actual version (the replacement for "$releasever" in the URL in the yum config file) is "5", not "5.0", which will always track the latest release. Sounds like the kernel version (currently kernel-2.6.18-53.1.14.el5) is not what is causing your problem.
I have only recently started using CentOS, and have an interesting query on this. If release 5 is always the latest release, does that mean when 5.6 comes out, it will still be v5? And how does the transition for major releases (from 4 to 5, 5 to 6) work?
5 will always be 5 until it falls off of support. 5.6 is just version 5 at a set point in time with all the upgrades at the time the freeze was set. So you get CentOS 5, but with the current kernel and files at that time. The installer also gets any kernel revisions and patches that are at that point in time. That way a 5.6 install cd/dvd might install on hardware that was unsupported in an earlier point release.
A major release will get the next major number. I don't think any major release will ever automatically update to the next release, as upstream has always recommended a wipe and install over major version upgrades. And since upstream has usually set new releases at an 18-24 month release cycle, you can usually expect a new major release at about every 2 years or so.
Cool, thanx for the info :)
Rudi Ahlers wrote:
Robert Nichols wrote:
Morten Nilsen wrote:
Robert Nichols wrote:
If you installed 5.0, you're missing a LOT of updates. The normal update mechanism should bring your machine up to 5.1 unless you've taken action to lock it to the 5.0 release.
When I installed this box, 5.1 wasn't out yet.. And, no I haven't taken any kind of action to lock it to 5.0.
I have run "yum update" a few times, but I don't see any signs of it wanting to upgrade to 5.1..
The upgrade to 5.1 is seamless. Your actual version (the replacement for "$releasever" in the URL in the yum config file) is "5", not "5.0", which will always track the latest release. Sounds like the kernel version (currently kernel-2.6.18-53.1.14.el5) is not what is causing your problem.
I have only recently started using CentOS, and have an interesting query on this. If release 5 is always the latest release, does that mean when 5.6 comes out, it will still be v5? And how does the transition for major releases (from 4 to 5, 5 to 6) work?
Let me relate this to Windows :D
CentOS-5.1 and 5.2 and 5.3 are like XP, XP Service Pack 1, and XP Service Pack 2.
====================================================================
So you are always running CentOS-5 ... it is just a different state of being updated.
Neither the upstream provider nor CentOS recommends that you UPGRADE your install from one MAJOR version to another (ie CentOS-4.x to CentOS-5.x):
https://www.redhat.com/archives/rhelv5-beta-list/2008-March/msg00005.html
The upstream provider (and CentOS) recommend that you instead backup your data and reinstall your os as a new install, THEN restore your data and configure:
http://www.centos.org/docs/5/html/5.1/Installation_Guide/ch23s01.html
HOWEVER ...
if you do upgrade from 3.x (where $releasever is 3) to CentOS-4.x or CentOS-5.x then the $releasever will change to 4 or 5 as appropiate. In CentOS, $releasever is controlled by the VERSION (and not the RELEASE) of the centos-release package.
Thanks, Johnny Hughes
Johnny Hughes wrote:
Let me relate this to Windows :D
CentOS-5.1 and 5.2 and 5.3 are like XP, XP Service Pack 1, and XP Service Pack 2.
what is wrong with the world today ?
on 3-27-2008 11:36 AM Johnny Hughes spake the following:
Rudi Ahlers wrote:
Robert Nichols wrote:
Morten Nilsen wrote:
Robert Nichols wrote:
If you installed 5.0, you're missing a LOT of updates. The normal update mechanism should bring your machine up to 5.1 unless you've taken action to lock it to the 5.0 release.
When I installed this box, 5.1 wasn't out yet.. And, no I haven't taken any kind of action to lock it to 5.0.
I have run "yum update" a few times, but I don't see any signs of it wanting to upgrade to 5.1..
The upgrade to 5.1 is seamless. Your actual version (the replacement for "$releasever" in the URL in the yum config file) is "5", not "5.0", which will always track the latest release. Sounds like the kernel version (currently kernel-2.6.18-53.1.14.el5) is not what is causing your problem.
I have only recently started using CentOS, and have an interesting query on this. If release 5 is always the latest release, does that mean when 5.6 comes out, it will still be v5? And how does the transition for major releases (from 4 to 5, 5 to 6) work?
Let me relate this to Windows :D
CentOS-5.1 and 5.2 and 5.3 are like XP, XP Service Pack 1, and XP Service Pack 2.
Does that mean my systems will crash daily and I will need to buy a new version and a new computer to put it on every couple of years?
And please don't tell me that CentOS 6 will be like Vista, or I will be going back to my sliderule! ;-P
-
Akemi Yagi -
Alan Bartlett -
D Steward -
Dennis McLeod -
Johnny Hughes -
Joshua Baker-LePain -
Karanbir Singh -
Les Mikesell -
Morten Nilsen -
Niki Kovacs -
Robert Nichols -
Rudi Ahlers -
Scott Silva