Michael A. Peters wrote:
> Thomas Dukes wrote:
>> The error I got when I ran 'yum update' was:
>>
>> Error: Missing Dependency: nss = 3.12.2.0-2-el5.centos is needed by package
>> nss-devel
>>
>
> Yes, that will do it - devel packages do need to be the same EVR.
> Sounds like you figured it o
Michael A. Peters wrote:
> Mufit Eribol wrote:
>
>> Michael A. Peters wrote:
>>
>>> Thomas Dukes wrote:
>>>
>>>> The error I got when I ran 'yum update' was:
>>>>
>>>> Error: Missing
/kernels/2.6.18-128.1.1.el5-PAE-i686/include/linux/version.h
/usr/src/kernels/2.6.18-164.9.1.el5-PAE-i686/include/linux/version.h
/usr/src/kernels/2.6.18-92.1.18.el5-PAE-i686/include/linux/version.h
I would appreciate any help.
Thank you.
Mufit Eribol
Arturas Skauronas wrote:
> On Fri, Jan 8, 2010 at 2:24 PM, Mufit Eribol wrote:
>> Dear All,
>>
>> make KERNELDIR= /lib/modules/2.6.18-164.9.1.el5PAE/build
>> grep: /include/linux/version.h: No such file or directory
>> expr: syntax error
>> ../../../inc/lin
Karanbir Singh wrote:
> On 01/08/2010 12:24 PM, Mufit Eribol wrote:
>
>> I use a raid card on my Centos 5.4 server. Whenever I updated the
>> kernel, I used to compile drivers of the card for the new kernel. I have
>> done this many times in the past without any proble
Hello,
I have a CentOS 6 VM on a CentOS 6 host. This VM has two ethernet
interfaces, eth0 and eth1. It was working nice. All of a sudden eth1
stopped working as expected. Kernel started to give the message below:
kernel: udev: renamed network interface eth2 to eth2-eth1
There is no any eth2 or
On 05.11.2011 02:32, Ljubomir Ljubojevic wrote:
> Vreme: 11/05/2011 01:10 AM, Mufit Eribol piše:
>> Hello,
>>
>> I have a CentOS 6 VM on a CentOS 6 host. This VM has two ethernet
>> interfaces, eth0 and eth1. It was working nice. All of a sudden eth1
>> stopped wo
Kai Schaetzl wrote:
Priority for CentOS Extras repo: 1
double-check that! For instance, if this repo is not enabled, the priority
will not work!
Kai
Checked that, already enabled. Here is an excerpt from CentOS-Base.repo:
...
#additional packages that may be useful
[extras]
name=CentOS-
Scott Silva wrote:
Just to be thorough, run this;
rpm -qa | grep priorities
[EMAIL PROTECTED] ~]# rpm -qa | grep priorities
yum-priorities-1.1.10-9.el5.centos
[EMAIL PROTECTED] ~]#
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailm
Filipe Brandenburger wrote:
Hi,
The package names are different, so probably "geoip" (from RPMforge)
obsoletes "GeoIP" from CentOS.
In that case, for priorities to work and exclude the one that
obsoletes the other, you have to set this option in the [main] section
of /etc/yum/pluginconf.d/prior
Ralph Angenendt wrote:
Strange, because it works here:
[EMAIL PROTECTED] Documentation]# yum -v update | grep -i geoip
--> geoip-devel-1.4.0-1.el5.rf.x86_64 from rpmforge excluded (priority)
--> geoip-1.4.0-1.el5.rf.x86_64 from rpmforge excluded (priority)
--> geoip-1.4.4-1.el5.rf.x86_64 from
Hello,
I have a question about working principles of yum.
Here are the details:
Installed package: GeoIP.i386 1.4.4-1.el5.centos
Repo: CentOS Extras
Priority for CentOS Extras repo: 1
"yum update" wants to replace the above package with the following:
Package: geoip.i386 1.4.5-1.el5.rf
Repo:
Sorry bugging you for this simple command.
ls command displays question marks for the local characters (ones not
included in 8859-1 space) in filenames.
ie.
[EMAIL PROTECTED] aa]# touch çarp
[EMAIL PROTECTED] aa]# ls
??arp
[EMAIL PROTECTED] aa]# ls -b#for octal escapes
\303
Michael A. Peters wrote:
Mufit Eribol wrote:
Sorry bugging you for this simple command.
ls command displays question marks for the local characters (ones not
included in 8859-1 space) in filenames.
ie.
[EMAIL PROTECTED] aa]# touch çarp
[EMAIL PROTECTED] aa]# ls
??arp
[EMAIL PROTECTED] aa
Scott Silva wrote:
on 2/20/2008 3:14 PM Mufit Eribol spake the following:
Michael A. Peters wrote:
Mufit Eribol wrote:
Sorry bugging you for this simple command.
ls command displays question marks for the local characters (ones
not included in 8859-1 space) in filenames.
ie.
[EMAIL
Hello,
After a server crash, I re-installed postfix, cyrus-imapd, amavisd-new,
spamassassin on a Centos 5.1 box. But, now mail system behaves somewhat
different.
There is no problem with mail receiving/sending from/to internet.
Before the crash, mail system used to sent internal messages to
Brian wrote:
Mufit Eribol wrote:
Hello,
After a server crash, I re-installed postfix, cyrus-imapd,
amavisd-new, spamassassin on a Centos 5.1 box. But, now mail system
behaves somewhat different.
There is no problem with mail receiving/sending from/to internet.
Before the crash, mail
Hi,
My Centos 5.2 server (5.1 suffered the same problem as well) has a
logical volume on a RAID 10 array (4 SATA harddisks on a Highpoint
RR2310 controller). /etc/fstab has an entry for this array as below
/dev/raid_vg0/raid_lv0 /mnt/raid ext3defaults0 0
Normally it
Kai Schaetzl wrote:
Mufit Eribol wrote on Thu, 31 Jul 2008 10:08:48 +0300:
But, file system of "this volume" once in a while
goes "read only" mode.
there will be log entries about this. Do a *forced* fsck.
Kai
Kai, thank you very much for the hint.
I am not
William L. Maltby wrote:
On Thu, 2008-07-31 at 10:08 +0300, Mufit Eribol wrote:
Hi,
My Centos 5.2 server (5.1 suffered the same problem as well) has a
logical volume on a RAID 10 array (4 SATA harddisks on a Highpoint
RR2310 controller). /etc/fstab has an entry for this array as below
Kai Schaetzl wrote:
You have to unmount the filesystem in question. I think that's even
recommended for a "do not repair" run.
Kai
"shutdown -rF now" didn't fix the problem either.
There are problems with several inodes. Reboot fixes the problem for a
couple of hours.
I am thinking about re
Ralph Angenendt wrote:
touch /forcefsck
and reboot. This will cause all filesystems to be checked with fsck
after the reboot.
I did it several times. Unfortunately, it couldn't fix the problem. I
still get the following errors and the system goes "read only" after a
couple of minutes.
EXT3-f
Toby Bluhm wrote:
I did it several times. Unfortunately, it couldn't fix the problem.
Does it say the fsck is a success or fails?
How can I get this info? All I get dmesg and messages logs after the
boot. Is there a log somewhere? If not, I think I have to watch the
monitor on the server dur
Kai Schaetzl wrote:
You rebooted several times, you did not force a check I think. You have to
boot with the rescue CD and then do a thorough fsck on the filesystem.
Maybe on each one of the disks separately, don't know. The boot-up check
might not be sufficient. There's probably some bad block
I think I found the culprit albeit I still don't know how to fix.
1. During boot the screen prints the following errors
"no fstab.sys, mounting internal defaults
...
No devices found
Setting up Logical Volume Management: /var/lock: mkdir failed: No such
file or directory"
I have a LV on RAID m
Toby Bluhm wrote:
Mufit Eribol wrote:
I have a LV on RAID mounted as /mnt/raid. Then /mnt/raid/var is
symlinked to /var.
I was afraid you were going to say that.
Go back to single user mode.
mkdir /new_var
cd /mnt/raid/var
tar cf - . | ( cd /new_var ; tar xvf - )
Make sure both dirs
NiftyClusters Mitch wrote:
On Fri, Aug 1, 2008 at 1:43 PM, William L. Maltby
<[EMAIL PROTECTED]> wrote:
On Fri, 2008-08-01 at 16:13 -0400, Toby Bluhm wrote:
Mufit Eribol wrote:
.
. that you would correctly try to
fsck the *device*.
Toby Bluhm wrote:
Mufit Eribol wrote:
Toby Bluhm wrote:
Mufit Eribol wrote:
I have a LV on RAID mounted as /mnt/raid. Then /mnt/raid/var is
symlinked to /var.
I was afraid you were going to say that.
Go back to single user mode.
mkdir /new_var
cd /mnt/raid/var
tar cf - . | ( cd
28 matches
Mail list logo
