Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I have attempted to upgrade my kernel in Debian (wheezy), and can now see that in /lib/modules there are directories for the old and the new kernel.
But I am hesitant to delete the old kernel module directory. How do I 'point out' to my system which is the new kernel? It still tries to draw modules from the old kernel when I run certain network processes.
The next time you boot up you will see the Grub menu at that point you can specify which kernel you wish to use. For the distros I'm familiar with the default kernel used is the most recent one.
At any point you can run the following command and it will tell you what kernel is in use at that moment.
Are you saying that the system with two kernels installed cannot be rebooted by anyone? Once a new kernel is installed it will be used by the system the next time that system is rebooted. Normally you don't need "the option to select kernel at start-up". If you want the most recent kernel that will be the one selected the next time anyone reboots the system unless the older kernel is specifically selected by the one doing the rebooting.
The answer seems to be that when you rent a server on OpenVZ, or in my case here at least, the virtual machine was forced to inherit the kernel from the host. So all attempts to update failed. That's what I read somewhere, seems to make sense based on everything I've tried not being successful
I have 4 to 6 Linux versions on each of my machines, each with its own /lib/modules directory.
Linux 2.4 has it own partition, because that is more than a kernel difference. Multiple versions of Linux 2.6 occupy the same partition, with a subdirectory for each in /boot/.
The boot loader, such as LILO or GRUB must be informed of the choices.
They allow selecting which from a menu, and they have a default.
It sounds like the virtual machine does not include GRUB emulation.
However, virtual machines often will allow differing OS, even Linux and Windows.
So this is a question for your OpenVZ.
Even if you have root permissions on your machine, /lib/modules may be only an inactive copy.
It is hard to test that without adding a module file and watching for differences in the dmesg after reboot.
Running it as a virtual Linux under the Linux you have would work but would be inefficient.
You probably would have trouble installing the virtual Linux too.