apeto2104 at gmail.com
Thu Aug 12 20:15:26 UTC 2010
Kevin, I'm using a server from a company in spain that rents dedicated
At first, the server was setup with Fedora 13. Clean, no other stuff in it.
I started the process of installing Asterisk the same way I did with another
server that we have
but with Fedora 12. This other server was already 'prepered' by someone
else. They let
me the server after using it for a while and I successfully installed
Asterisk on it with no problems at all.
yum install kernel-devel and everything else worked fine.
So, when I started to have problems on the new server with Fedora 13, I
decided to downgrade to Fedora 12.
The problem is that the company that rents me the server, don't support
Fedora 12 anymore.
They have Fedora 11 or 13. So I choose Fedora 11x64. And here I'm.
With fedora 13 I couldn't install gcc either. Some dependencies were looking
for kernel > 2.2.1 or
something like it. So I decided to downgrade to 12.( that became 11 becouse
the didn't have 12 )
Someone here told me Fedora 11 is no longer supported. Is that true ? No
more repos available ?
So far the only thing that I can not do is to install kernel-devel.
Can I install some other version of kernel-devel and compile anyway ? Can I
trick it by changing the dir name ?
Asterisk needs this headers to 'make' it so ...
Here you have the /etc/grub.conf
[root at ns310181 etc]# more grub.conf
title linux fedora11_64
kernel /boot/bzImage-220.127.116.11-xxxx-grs-ipv4-64 root=/dev/md1 ro
Looks like a "special" Fedora version ( some xxxx there ), not a free one
you can download from internet.
May be the guys that let me the other server, installed a new kernel. Can I
do that ?
Can you give me some tips ( tips, guides, urls ) on how to do it ? I see
that you are kind of an expert on linux.
Obviously I'm not. But not afraid to try new things.
u'r d man !!!
2010/8/12 Kevin J. Cummings <cummings at kjchome.homeip.net>
> On 08/12/2010 03:10 PM, Albert Bonomo wrote:
> > Kevin, my man, you know what you r talking about !!!
> > here you have the command output:
> > [root at ns310181 include]# rpm -qa kernel\*
> > kernel-headers-18.104.22.168-167.fc11.x86_64
> > or the other one ( shorter )
> > [root at ns310181 include]# rpm -qa | grep 2.6
> > *kernel-headers-22.214.171.124-167.fc11.x86_64*
> > tar-1.22-6.fc11.x86_64
> > python-2.6-12.fc11.x86_64
> > nss-tools-3.12.6-1.2.fc11.x86_64
> > psmisc-22.6-9.fc11.x86_64
> > udev-extras-20090226-0.5.20090302git.fc11.x86_64
> > nss-3.12.6-1.2.fc11.x86_64
> > gnutls-2.6.6-3.fc11.x86_64
> > sudo-1.7.2p6-2.fc11.x86_64
> > gnutls-devel-2.6.6-3.fc11.x86_64
> > grep-2.6.3-1.fc11.x86_64
> > patch-2.6.1-1.fc11.x86_64
> > libtool-ltdl-2.2.6-11.fc11.3.x86_64
> > python-libs-2.6-12.fc11.x86_64
> > ssmtp-2.61-14.fc11.x86_64
> > iproute-2.6.29-2.fc11.x86_64
> > nss-softokn-freebl-3.12.6-1.2.fc11.x86_64
> > Now I see the real kernel. I'm running on 126.96.36.199-167.fc11.x86_64
> Ah, no, you are not. if uname says you are running on 188.8.131.52, you
> have booted a 184.108.40.206 kernel. The question now becomes, where is it,
> and where did it come from? If you have no kernel RPM installed, then
> where did your kernel come from. I have both a kernel and a
> kernel-headers package installed (in fact, I have a couple of kernels
> installed) on most of my systems.
> On my 1 F11 system, I have:
> > # rpm -q -a kernel\*
> > kernel-headers-220.127.116.11-105.2.23.fc11.i586
> > kernel-devel-18.104.22.168-105.2.23.fc11.i586
> > kernel-doc-22.214.171.124-105.2.23.fc11.noarch
> > kernel-firmware-126.96.36.199-105.2.23.fc11.noarch
> > kernel-188.8.131.52-105.2.23.fc11.i586
> > kernel-184.108.40.206-167.fc11.i586
> and I'm running:
> > # uname -r
> > 220.127.116.11-105.2.23.fc11.i586
> As you can see, I also have kernel-18.104.22.168-167 installed, but I'm not
> booting it.
> You need to look at your /etc/grub.conf file (or where it really lives
> in /boot/grub/grub.conf) and see what kernels you system can boot from.
> Perhaps that will shed some light on where your 22.214.171.124 kernel has come
> from. You haven't installed anything from another non-RPM source have you?
> BTW, the following are current F13 kernels:
> > rpm -q kernel
> > kernel-126.96.36.199-124.fc13.i686
> > kernel-188.8.131.52-147.fc13.i686
> > kernel-184.108.40.206-147.2.4.fc13.i686
> You, obviously, are running on x86_64 hardware.
> > I can also see that I have header installed:
> > *kernel-headers-220.127.116.11-167.fc11.x86_64
> > *The question would be, where ?*
> > *So, I wonder why 'uname -r' gives me this crap:
> > 18.104.22.168-xxxx-grs-ipv4-64 ????
> > And why 'yum install kernel-devel' doesn't work ?
> I can't answer that without seeing more of your yum output (where is it
> looking for kernels, etc). But, if you are running a non-rpm kernel,
> building/installing other software is going to give you miles and miles
> of grief. And finding/installing RPMs is going to be next to impossible
> in cases like this.
> > Thanks for the answer.
> > you'r the man
> > Albert
> Kevin J. Cummings
> kjchome at rcn.com
> cummings at kjchome.homeip.net
> cummings at kjc386.framingham.ma.us
> Registered Linux User #1232 (http://counter.li.org)
@apetob at Tweeter
There are only 10 types of people in the world:
Those who understand binary and those who don't
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the users