i have a problem that, my system boots up only in kernel 2.16.22 .,

And i have an application which requires 2.6.18 ....


It is not possible to use the 2.6.18 for my system, but how to make this application to see this 2.6.22 as 2.6.18.... Is it possible ??? ( that application is using this kernel for some internal purpose, how to make this 2.6.22 to show like 2.6.18 )

what application, pls, it's kind of important to know at least what kind of application it is. Is it a kernel module or have one as a part of it ?

If your application requires a particular kernel version ... rather unusual but not unheard-of ... then, by gawd, it requires that for some (good) reason, and nothing less will do.

yes, as you are saying it requires that kernel for good reason, but the reason which it requires the 2.6.18 is also present in 2.6.22.,

so am asking how to pretend this 2.6.22 as 2.6.18

It's not true, interfaces (internal / and or external) often change (that's one of the big linux problem in my point of view). That's why you have to know what is needed by your software or module in this kernel version.

Yes, I'll chime in -- in the most agreeable fashion -- that the people who stipulated this kernel version must have known what they are talking about. I do not predict that your present line of effort will be fruitful.

Well if you absolutely Must you could try editing the version string in the kernel binary. Might work, might not. But it's quick n easy, so worth a stab. Here's how:

- Make a copy of /boot/vmlinu* (whetever your kernel is called) to your home directory.
- Look at the copy using a hex editor. Search for the version string. Change it by value but NOT by length. If it was 10 chars before it shoule be 10 chars afterwards.
- Copy the kernel back to /boot/A_DIFFERENT_NAME
- If you use grub, look at the /boot/grub/menu.lst - this is the list of kernels that grub offers you at boot time. Add the new kernel. You should be able to copy one of the paragraphs defining another kernel and change the names.
- Within that same grub file there is a "timeout" which is the number of seconds grub waits before booting the default kernel. Set that to a good long time such as 20 seconds.
- Reboot, cross fingers.

To undo - Just change the grub/menu back to what it was before. Easiest if you make a backup before you start playing. You can also remove the customised Linux binary if you like, although if grub doesn't know about it anymore it's just ignored.

Have fun, have a knoppix boot disk to hand in case it all goes wrong - there are lots of ways this could happen - and have a bottle of champagne in case it goes right!

Regards, One who hasn't tried this before.

It might be better to take a hex editor to the application. If it dies then it's its own fault for making unreasonable and unjusified demands of the kernel. It is an open surce application, right? So you could change the application code so that it accepts your kernel version, no hex editor needed. That's the freedom we are fighting for, right?

Regards, Milchbein