opike
asked on
Question about upgrading linux kernel
I'm currently running kernel 2.6.24-27-generic but i need to install a driver that requires 2.6.27.7.11 (or greater). I have several programs already installed on my machine along with vmware server 2, which requires ubuntu 8.0.4.
What are the risks I run to my existing programs by upgrading the kernel?
How much is the kernel version associated with the linux instance version? i.e. if I upgrade the kernel to 2.6.27.7.11 am I now effectively no longer running ubuntu 8.0.4 and vmware is now running on an unsupported platform?
What are the risks I run to my existing programs by upgrading the kernel?
How much is the kernel version associated with the linux instance version? i.e. if I upgrade the kernel to 2.6.27.7.11 am I now effectively no longer running ubuntu 8.0.4 and vmware is now running on an unsupported platform?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks...this tells me what I needed to know. I will look into taking adavantage of a cloning system.
Yes SuperDave is right.
Thank you to remind me this option.
My approach is very radical many times. In fact there is a little chanche to mess it up badly in this way. Normally I do not like to loose something well working, so I prefer to not take any risk at all, expecially if it is a production machine I do not want to get angry with myself, it happened a few times in two decades and hate the idea to catch nervous dropdowns.
As I constantly work with IT systems and time is always less than necessary, my strategy is to use some little more time even if it looks not necessary in order to spare huge amounts in some occasions that will eat at once dozens of little bits previously spared.
Sorry for the game of words, I mean that 30-60 minutes for a clone meanwhile I do other things, will save me from a lot of problems if something goes wrong, for any reason, even reason that do not have absolutely nothing to do with the operation itself.
For example once I was just too tired and formatted not only the drive I was testing on but also the drive with the clone images which were recent and not double backed up as the whole matter was low budget and client did not want to pay for it but also did not double backed up by themselves ( I was doing the opposite in this case having at hand several cloned versions of the system on another drive). I felt lost in this low budget school project having 200 students coming up in a few hours and wanting to ravage their files on the server .
I was lucky enough to be able to restore an old working image from an old redundant backup, retrieve the new user list from another backup, and fast enough restore almost all in a decent way.
It was nothing difficult to setup, but again, why to loose hours to repeat a work? I lost just some time to find back this old redundant backups and updating them a little bit.
It happens, expecially when things are not done in a perfectly organized way, in a low budget mode, with few resources and when attention goes low for tireness or other disturbing reasons.
That is my experience, never take a risk if you do not want to have problems, if there can not be a problem anyway then is possible to do anything at wish.
Bye