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.
Omg, I never even thought about those dependencies, you're absolutely right. Then again, I performed this routine shortly after FC6 was released so that wasn't an issue back then. And with my hardware getting better and better support, I tend to get out of touch with the whole tweaking business, getting sooo lazy. If anyone knows an unsupported motherboard or something, please recommend
One thing you could do is have a look at the baseurls you can find in the files fedora-core.repo, fedora-extras.repo and fedora-updates.repo. They are under /etc/yum.repos.d.
You need to make sure that either:
the first baseurl is uncommented (i.e. no # in front of it)
that you put some alternative mirror(s) in there. The default baseurl figures pretty much in everyone's files so they tend to get a lot of traffic, which may result in them being unaccessible at times. If you want to add one or more alternative mirrors, have a look at this: http://rhold.fedoraproject.org/Download/mirrors.html
Select one or more mirrors near you and put them under baseurl; make sure you adjust where necessary: the mirror list specifies only the top level mirror directories but you need to specify Fedora version and architecture as well (x86, x86_64, etc). Unfortunately, some mirrors are organized a bit differently from others or at least from the default baseurl so you need to paste the mirror address(es) in your browser and go to the site to explore in which subdirectories your packages are stored. Just have a look at the default baseurls in order determine which subdirectories are needed. Here's an example for the fedora-core.repo: http://mirror.linux.duke.edu/pub/fed...e/6/x86_64/os/
and from the same mirror, for the updates-repo: http://mirror.linux.duke.edu/pub/fed...ates/6/x86_64/
Note that both are for 64 bit Fedora; there is a 32 bit subdirectory at the same levels.
Here is a thread where someone had similar problems with repos, also, there are apparently bugs in the yum package that came with original discs, not the re-spins, for some people, updating the yum package got things happening. You can compare your Fedora repo files to the ones I posted here from /etc/yum.repos.d.
i tried the yum after removing the hash '#' from the repo files and this time i got another prob...
actually i have internet via a 100 Mbps LAN connection which requires authentication(user id. and passwd.) for opening any site....so yum just gave the message about the authentication not given....but i don't no where to provide the network password as yum did not ask for it....how can i make yum ask for user-id and passwd for internet....
Huh? Do you have to provide id for each and every site you visit? That seems awfully inconvenient, to say the least. Or is it rather like you have to identify yourself just once at the beginning of each internet session?
Erm... you were supposed to download and install, that's what you usually do. If you do
yum update packagename(s)
yum fetches the package(s) and then it asks if it should install them (y/n); at that point you need to type y(es) or (n)o and then it installs whatever it fetched (or it doesn't if you said no).
If you did that and chose yes, then the packages are already installed. If not, you need to redo the yum but this time it will look for them on your hard disk first; if you didn't clean your var cache, they should still be there - if you did clean the cache (or did something wrong) it will have to download from the internet again.
If you type
it will return the currently installed kernel; if it says 2.6.19 something, you can be sure that at least the kernel packages were updated.
If you downloaded the packages manually (I'm not quite clear what you did exactly) you need to cd to the place where the rpms are stored, e.g. if they are on you desktop
cd /home/your username/Desktop
and install them manually
rpm -ivh kernel*
Please bear in mind: this procedure is by all means the worst choice you could make! You can try it if you have absolutely no other choice but else, don't. The thing is that packages do not exist independently from one another; often one package needs another one (or more) to function (that's what is known as "dependencies") and if you install them manually, you won't get told so ! so you'll install your stuff, then find that certain things don't work anymore because certain "dependencies" were not installed - worst of all, you may never find out what is missing so you can only reinstall!!! - but most often, rpm will refuse to install anything until you download and install the dependencies first... And that can be a LOT of work, trust me. If you use yum as I described, it will take care of all the dependencies and download those along with whatever you told it to fetch.
As I said in a previous post, I recommend doing a FULL update, which means
yum -y update
because this is the best way of avoiding dependency issues (the -y, btw, means yes - if you do that, yum will download and install everything without asking any further questions). You can manually install kernel packages alone, to begin with, but then you need to get kernel kernel-headers nash and makeinitrd (and make sure they match - one version of a certain package requires a specific version of the other ones - another reason to use yum...).
If you go to http://rpm.pbone.net/ and put --> kernel-2.6.18-1.2869.fc6.i686.rpm , in the search field you will find the kernel and kernel-src, I could not find the devel or headers packages, but the source should have all headers that you can use for compiling and by rights should be installed in /lib/modules/2.6.18-1.2869/build. Because you already have a kernel installed, you cannot install another one over top, you have to upgrade the kernel and all the other packages except for the kernel-src package which you probably do not have one installed, therefore you do not upgrade that package, you install it. Example:
rpm -Uvh kernel-2.6.18-1.2869.fc6.i686.rpm <--(for upgrading packages already installed to a newer package)
rpm -ivh kernel-2.6.18-1.2869.fc6.src.rpm <--(for installing a package where an older version is not installed)
The kudzu-devel is not required, just kudzu (dependency hell for the devel package). If you want to try upgrading to the 2.6.19 kernel packages you will also need nash package, but when trying to upgrade it you will find a list of dependencies that need to be satisfied first and it becomes a tangled mess because other packages not related to the kernel upgrade will be tied to dependencies for nash and mkinitrd. If you did not select "development libraries & tools" as package groups to install during the initial installation, you will have to satisfy dependencies for installing the kernel source, (gcc, gcc++, gcc-fortran, make, etc.), install them using rpm install command from off the install discs. There is a list called "install.log" in /root of all installed packages during installation.
Last edited by Junior Hacker; 04-03-2007 at 09:18 PM.
You can install the kernel and not upgrade to keep a copy of the last kernel if required. All other packages need to be upgraded other than kernel source of course. You will need to re-boot to use the newer kernel.