|
|
Sponsored Content
Operating Systems
Linux
Red Hat
How to upgrade kernel form 2.4 to 2.6
Post 302090847 by Corona688 on Wednesday 27th of September 2006 04:43:34 PM
09-27-2006
According to this, RHEL3 does not officially support the 2.6 kernels. You can drop one in, but the module-loader etc. won't work with it, meaning you'll have to compile in all the drivers you want instead of making them modules.
If this is a production system, I'm not sure it's a good idea, at least if you ever want Redhat to speak you you again.
I know I totally ****** up Mandrake by installing a custom kernel. RPM threw a hissy fit and stopped working.
The steps would be:
1) Download the source/patches you want.
2) Configure your kernel with 'make menuconfig'.
3) Build your kernel with 'make'.
4) Copy the bzImage file into wherever you keep your boot images.
5) Update lilo or grub to add an entry for the new kernel. (keep the old kernel in case the new one doesn't work!!)
6) Reboot. If it doesn't work, goto 2.
More details depend on boot manager, system layout, etc.
If this is a production system, I'm not sure it's a good idea, at least if you ever want Redhat to speak you you again.
I know I totally ****** up Mandrake by installing a custom kernel. RPM threw a hissy fit and stopped working.The steps would be:
1) Download the source/patches you want.
2) Configure your kernel with 'make menuconfig'.
3) Build your kernel with 'make'.
4) Copy the bzImage file into wherever you keep your boot images.
5) Update lilo or grub to add an entry for the new kernel. (keep the old kernel in case the new one doesn't work!!)
6) Reboot. If it doesn't work, goto 2.
More details depend on boot manager, system layout, etc.
Last edited by reborg; 09-27-2006 at 07:52 PM.. Reason: watch the language
|
|
8 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Please someone I need information on how to change a Unix form/document into a microsoft word document in order to be emailed to another company. Please help ASAP. Thankyou :confused: (8 Replies)
Discussion started by: Cheraunm
8 Replies
2. UNIX for Dummies Questions & Answers
Hi everyone,
I am trying to have a second kernel in my Red hat 2.4.18.
I downloaded the 2.4.9 version and did all the extract and stuff. when I run the command make bzImage I get the following error:
devlist.h:6931: __devices_b1b3 causes a section type conflict
> devlist.h:6934:... (1 Reply)
Discussion started by: bashirpopal
1 Replies
3. Red Hat
Hello, everyone.
I am using Fedora 15, and want to upgrade to version 16. I follow the official link Upgrading Fedora using yum - FedoraProject to upgrade my OS by the following command:
yum update kernel* --releasever=16
yum groupupdate Base --releasever=16
reboot
After reboot, OS... (2 Replies)
Discussion started by: 915086731
2 Replies
4. Hardware
Hi,
I would like to ask related to video graphics driver specifically the AMD (radeon HD 7000 series) or had someone with the same experience or problem that im currently experiencing and willing to share some info. I understand that the kernel is self contain it will not affect the installed... (3 Replies)
Discussion started by: jao_madn
3 Replies
5. Shell Programming and Scripting
HI Guys,
I have data in File A.txt
RL03 RL03_A_1 RL03_B_1 RL03_C_1
RL03 -119.8 -119.5 -119.5
RL07 RL07_A_1 RL07_B_1 RL07_C_1
RL07 -119.3 -119.5 -119.5
RL15 RL15_A_1 RL15_C_1
RL15 -120.5 -119.4
RL16... (2 Replies)
Discussion started by: asavaliya
2 Replies
6. Shell Programming and Scripting
How to remove x lines form top and y lines form bottom.
This works, but like awk only cat file | head -n-y | awk 'NR>(x-1)'
so remove last 3 lines and 5 firstcat file | head -n-3 | awk 'NR>4' (5 Replies)
Discussion started by: Jotne
5 Replies
7. Solaris
Hi Guys,
I am getting into patching activity now a days.
I had already done kernel upgrade through LU.
My doubt is if i had to install 3 patches to get my system to current available patch level, can i directly patch one by one on an inactive LU and once done i can activate it later on
or... (3 Replies)
Discussion started by: Rockyc3400
3 Replies
8. Red Hat
Dear All ,
I want upgrade my kernel version from kernel-2.6.18-164.el5 to kernel-2.6.18-199.el5.
We have RED HAT Linux Server Red Hat Enterprise Linux Server release 5.4 (Tikanga).
Kindly let me know where we can download this particular RPM.
if we want to download from RHN , pl let... (0 Replies)
Discussion started by: jegaraman
0 Replies
LEARN ABOUT CENTOS
dh_systemd_start
DH_SYSTEMD_START(1) Debhelper DH_SYSTEMD_START(1) NAME
dh_systemd_start - start/stop/restart systemd unit files SYNOPSIS
dh_systemd_start [debhelperoptions] [--restart-after-upgrade] [--no-stop-on-upgrade] [unitfile...] DESCRIPTION
dh_systemd_start is a debhelper program that is responsible for starting/stopping or restarting systemd unit files in case no corresponding sysv init script is available. As with dh_installinit, the unit file is stopped before upgrades and started afterwards (unless --restart-after-upgrade is specified, in which case it will only be restarted after the upgrade). This logic is not used when there is a corresponding SysV init script because invoke-rc.d performs the stop/start/restart in that case. OPTIONS
--restart-after-upgrade Do not stop the unit file until after the package upgrade has been completed. This is the default behaviour in compat 10. In earlier compat levels the default was to stop the unit file in the prerm, and start it again in the postinst. This can be useful for daemons that should not have a possibly long downtime during upgrade. But you should make sure that the daemon will not get confused by the package being upgraded while it's running before using this option. --no-restart-after-upgrade Undo a previous --restart-after-upgrade (or the default of compat 10). If no other options are given, this will cause the service to be stopped in the prerm script and started again in the postinst script. -r, --no-stop-on-upgrade, --no-restart-on-upgrade Do not stop service on upgrade. --no-start Do not start the unit file after upgrades and after initial installation (the latter is only relevant for services without a corresponding init script). NOTES
Note that this command is not idempotent. dh_prep(1) should be called between invocations of this command (with the same arguments). Otherwise, it may cause multiple instances of the same text to be added to maintainer scripts. Note that dh_systemd_start should be run after dh_installinit so that it can detect corresponding SysV init scripts. The default sequence in dh does the right thing, this note is only relevant when you are calling dh_systemd_start manually. SEE ALSO
debhelper(7) AUTHORS
pkg-systemd-maintainers@lists.alioth.debian.org 11.1.6ubuntu2 2018-05-10 DH_SYSTEMD_START(1)