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 am trying to upgrade the Fedora 8 kernel from version 184.108.40.206-42.fc8.i686 to version 220.127.116.11-***. This is to apply patch for VMware Server. I have downloaded the kernel-18.104.22.168-34.fc8.i686.src.rpm and ran this command:
rpm -ivf kernel-22.214.171.124-34.fc8.i686.src.rpm and received the following warnings:
user mockbuild does not exist - using root
group mockbuild does not exist - using root
Do I need to create user and group named mockbuild? I also downloaded patch-126.96.36.199.bz2 from kernel.org, am I going to the right direction for this upgrade? Can I use yum install to upgrade the kernel automatically? Thanks!
Thanks for the advice. I have utilized yum to install kernel, kernel-devel, and kernel-headers from 188.8.131.52-4.fc8.i686 to 184.108.40.206-34.fc8.i686. However,I encountered this error:
Open: /tmp/initrd.mV4002/lib/modules/220.127.116.11-34.fc8: Permission denied
FATAL: Could not open /tmp/initrd.mV4002/lib/modules/18.104.22.168-34.fc8/modules.dep.temp for writing: Permission denied
Installed: kernel i6860:22.214.171.124-34.fc8
when using the following command:
yum -y install kernel-126.96.36.199-34.fc8
I didn't encountered any errors when installing kernel-devel and kernel-headers 188.8.131.52-34.fc8.i686. Using rpm -qa | grep kernel, kernel,kernel-devel, and kernel-headers for 184.108.40.206-34.fc8 are available together with the older version (220.127.116.11-4.fc8) During reboot with Grub, kerenl 18.104.22.168-34 has caused several directories not available and mount point failed. Any suggestion on this issue? Should I remove the older version of kernel and kernel-devel? Also I have trying to update several packages and there are dependencies errors to the following packages:
I have tried to yum install individual package with no success. Any suggestion?
Thank you for your contribution to cure my headache :-)
I just applied the update process based on warning on Gnome desktop and these are files that have dependency errors. There is one other file that has dependency error and I was able to yum install curl-devel-7.17.1-2.fc8.i386. I was puzzle to see the fc9 requirement on compiz-kde.0.6.2. Before this, when I was in the process to update kernel, I executed yum install kernel and not sure if this might have an effect to compiz-kde module. Thanks.
Dependency issues have not completely disappeared from Fedora although the situation is now much better than it used to be. And unlike other rpm based distros (that I won't bother to mention here - sigh) such issues shouldn't be a cause for concern. They will get stretched out in a day or two, maybe three. Apparently someone made an update available without realizing that some dependent package has not received an update yet. As soon as that other package becomes available, your dependency issue(s) will be solved. In the meantime, let it rest. There are workarounds but you shouldn't try them unless you have been using Fedora long enough to see the implications.
One reason you may have received a package for Fedora 9 is that you may have enabled the development repositories. This is generally not a good idea as it increases the risk of running into dependency issues (among other things). Check the development file in yum.repos.d. to find out whether it is enabled or not. Make sure to install yum-protect-base, a plug-in that will protect your base system from tricky updates. Be very careful when you decide to remove something through yum. Dependencies work both ways: not only do they pull in dependent packages, they also remove them. If you remove certain packages, you may find that they also remove other packages that are vital to keep your system functional. I advise against using the -y option when updating and especially when removing packages. Just use yum update or yum remove, that will give you a chance to back out if you find that things may go wrong if you accept the proposed installs/removals.
Compiz is indirectly linked with the kernel as video drivers are directly dependent on your kernel. Always be careful when updating your kernel if you use the livna video drivers: you generally need to check that a video driver update is available too when a newer kernel is out. Installing just the kernel often means you won't be able to start x anymore unless you switch to the open source drivers.