Thanks ,

I will try to use kernel that comes in centos website, I think that would be safer.

my server is in remote location, and I don't see any grub screen, so I was wondering if there is an option that I can specify the kernel that Linux to be booted at the reboot time, some thing like shutdown -g0 -i6 which_kernel-options

am I able to see console screen with KVM ? I wish we had it, so I could see whats happening on console, or is there any way to redirect the console to remote terminal ?

Lukasz wrote:

User centos wrote:

...

Is kernel depends on Centos version, I mean I have installed Centos 4.3 and its kernel version is 2.6.9, but I want to upgrade the kernel to the latest available in kernel.org.

you can use any 2.6.x kernel version, but then you have to run it yourself

I suggest to use kernel source RPM package from Fedora 6 or 7 and try to rebuild it; even if you will have to modify spec file, it's less work and more safe and you have huge number of patches; and you will have RPM packages, so you can build and test kernel on other machine with no risk

-- Opole - Miasto Bez Granic. http://www.opole.pl - tu znajdziesz nowe miejsca, nowe mozliwosci, nowe inspiracje...

---

CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos

my server is in remote location, and I don't see any grub screen, so I was wondering if there is an option that I can specify the kernel that Linux to be booted at the reboot time, some thing like shutdown -g0 -i6 which_kernel-options

This is handled by your bootloader, which is grub. In your /etc/grub.conf file, there is a line that says "default=x" where x is the number of the section from the top of the file, starting with 0. You can also use the "fallback=x" statement to boot a different kernel in case the default kernel is unable to boot.

If you really want to be able to specify which kernel will be booted on the next boot (and only the next boot) you can install the lilo boot loader and use "lilo -R <image title>" and the next time the system is booted, it will use that kernel, but all other times it will use the default kernel. If you are not familiar with lilo, I strongly recommend that you install it on a machine locally and use it there until you are comfortable with it before deploying it to a machine at a remote data center.

Hope this helps, Barry

Centos 4 kernel's base version is 2.6.9 and Centos 5 kernel's base version is 2.6.18. and I couldn't find anything in Centos mirror sites and repository ( I really need kernel version 2.6.18. )

Downloaded and installed kernel 2.16.18 for version 5, and installed it on Centos 4, it is ok but while I am installing another software I am getting pointer exception fault.

couldn't compile 2.6.18 SROM on Centos 4, I am getting "unifdef is needed" when I am running

rpmbuild -bb kernel-2.6.18

now I guess I have only two choices: 1- upgrading Centos 4 to Centos 5, which I need your opinion for the best way of accomplishing it, considering my server is in remote location and I don't have access to console. ( is kick start works for remote installation with not access to console ? )

2- Downloading kernel from kernel.org, which I want to know if the same version in kernel.org is identical to same version in Centos repository. I want to make sure I will have the same thing, to prevent weird problem in future.

Thanks

Barry Brimer wrote:

...

my server is in remote location, and I don't see any grub screen, so I was wondering if there is an option that I can specify the kernel that Linux to be booted at the reboot time, some thing like shutdown -g0 -i6 which_kernel-options

This is handled by your bootloader, which is grub. In your /etc/grub.conf file, there is a line that says "default=x" where x is the number of the section from the top of the file, starting with 0. You can also use the "fallback=x" statement to boot a different kernel in case the default kernel is unable to boot.

If you really want to be able to specify which kernel will be booted on the next boot (and only the next boot) you can install the lilo boot loader and use "lilo -R <image title>" and the next time the system is booted, it will use that kernel, but all other times it will use the default kernel. If you are not familiar with lilo, I strongly recommend that you install it on a machine locally and use it there until you are comfortable with it before deploying it to a machine at a remote data center.

Hope this helps, Barry _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos

Thanks every one for all your help,

using VNC seems to be a good option for those who has no access to console and want to install Centos remotely, however just to test , I tried to upgrade Centos 4.5 to Centos 5, but it progressed almost to the end and then stoped with some error. nothing upgraded.

I think I should first upgrade it locally and then start doing it remotely.

fresh install will leave a lot of files from previous version, so it should not be considered at all.

is there any log file that shows why upgrade failed ?

Cheers

Scott Silva wrote:

centos spake the following on 8/20/2007 4:10 AM:

...

Centos 4 kernel's base version is 2.6.9 and Centos 5 kernel's base version is 2.6.18. and I couldn't find anything in Centos mirror sites and repository ( I really need kernel version 2.6.18. )

Downloaded and installed kernel 2.16.18 for version 5, and installed it on Centos 4, it is ok but while I am installing another software I am getting pointer exception fault.

couldn't compile 2.6.18 SROM on Centos 4, I am getting "unifdef is needed" when I am running

rpmbuild -bb kernel-2.6.18

now I guess I have only two choices: 1- upgrading Centos 4 to Centos 5, which I need your opinion for the best way of accomplishing it, considering my server is in remote location and I don't have access to console. ( is kick start works for remote installation with not access to console ? )

2- Downloading kernel from kernel.org, which I want to know if the same version in kernel.org is identical to same version in Centos repository. I want to make sure I will have the same thing, to prevent weird problem in future.

Thanks

Building a kernel from source on an enterprise system will almost surely break something. A remote upgrade is possible, but you will need to test it thoroughly on something like a vmware image or another piece of hardware that you can access easily. You had the option to use vnc and do remote installs in 4.0, but I haven't tried it in 5. Here is a link that will take a little testing and adjusting as it is for an upgrade to 4. http://www.karan.org/blog/index.php/2005/06/15/upgrading_to_centos4_over_a_r...