I was trying this on the Kernel sources that comes with Redahat distribution(Default).Is that a problem?Should I download the new sources and try again?One thing I should tell you that I have only installed the Linux kernel and it's sources i.e.the minimum system.Will it give dependencies problem since there are no other packages and libraries? Mahesh Gharat
On Wed, 17 Oct 2001 Philip S Tellis wrote :
Just a thought, are you compiling the kernel sources that came with redhat or did you download the entire source? I was never able to compile the default redhat sources.
Philip
-- It does me no injury for my neighbor to say there are twenty gods or no God. It neither picks my pocket nor breaks my leg.
- Thomas Jefferson
Visit my webpage at http://www.ncst.ernet.in/~philip/ Read my writings at http://www.ncst.ernet.in/~philip/wri- tings/
MSN philiptellis Yahoo! philiptellis AIM philiptellis ICQ 129711328
--- Mahesh Gharat mahesh_gharat@rediffmail.com wrote:
I was trying this on the Kernel sources that comes with Redahat distribution(Default).Is that a problem?Should I download the new sources and try again?One thing I should tell you that I have only installed the Linux kernel and it's sources i.e.the minimum system.Will it give dependencies problem since there are no other packages and libraries? Mahesh Gharat
If you're using the RedHat sources, do a "make mrproper" before you do the "make <NULL|menu|x>config". For reasons best known to them, the RedHat kernel sources are supplied in an uncompilable state. The mrproper command executed before the make config sets them to a compilable state, so that you will be able to then compile witout problems.
Also, remember to do the mrproper stuff before *every* kernel compile.
HTH,
Rgds,
Krishnan
__________________________________________________ Do You Yahoo!? Make a great connection at Yahoo! Personals. http://personals.yahoo.com
On Thu, 18 Oct 2001, S. Krishnan wrote:
Also, remember to do the mrproper stuff before *every* kernel compile.
Not a good idea actually. If your hardware doesn't change, you'll probably want the same .config file to be used.
Philip
--- Philip S Tellis philip.tellis@iname.com wrote:
On Thu, 18 Oct 2001, S. Krishnan wrote:
Also, remember to do the mrproper stuff before
*every* kernel
compile.
Not a good idea actually. If your hardware doesn't change, you'll probably want the same .config file to be used.
Philip
It may not be a good idea, but things are not going to work if you don't - compiles will keep breaking. As for why, I guess Red Hat knows, but I don't - this is just something that I have observed practically.
Krishnan
__________________________________________________ Do You Yahoo!? Make a great connection at Yahoo! Personals. http://personals.yahoo.com
Sometime Today, S. Krishnan assembled some asciibets to say:
It may not be a good idea, but things are not going to work if you don't - compiles will keep breaking. As for why, I guess Red Hat knows, but I don't - this is just something that I have observed
Oh, ok. Redhat problem. Ya, the first thing I do when I install a new system is to uninstall the redhat kernel. You've got to remove the kernel sources, and headers, but leave the entry in the rpm database. Then install the latest kernel - after checking reviews of course.
Then, run up2date to upgrade everything.
Philip
Oh, ok. Redhat problem. Ya, the first thing I do when I install a new system is to uninstall the redhat kernel. You've got to remove the kernel sources, and headers, but leave the entry in the rpm database. Then install the latest kernel - after checking reviews of course.
Then, run up2date to upgrade everything.
Why leave the entry in the rpm db? I assume you are downloading the kernel as a tarball. In that case, would not the rpm entry break things w.r.t. versions etc? Is it because the up2date command will refresh the rpm db? I'm not very familiar with rpm databases, as you can make out.
Rgds,
Krishnan
__________________________________________________ Do You Yahoo!? Make a great connection at Yahoo! Personals. http://personals.yahoo.com
On Fri, 19 Oct 2001, S. Krishnan wrote:
Why leave the entry in the rpm db? I assume you are downloading the kernel as a tarball. In that case, would not the rpm entry break things w.r.t. versions etc? Is it because the up2date command will
if you don't leave the entry, then you won't be able to upgrade glibc, modutils or binutils. You may have to upgrade the database entry to 2.4.3 however, because some utils (util-linux for one) require that. Most are happy with simply 2.4
up2date will not touch the kernel unless you tell it to:
up2date --justdb --force kernel kernel-headers
Unfortunately, this will download quite a lot of stuff just to update the db.
Philip