Re: [CentOS] CentOS 6 is a bear

[Thomas Lange]

> On Fri, 07 Oct 2011 21:14:19 -0400, Bob Hoffman  
> said:

> Gotta say, centos has been tough to install and get working.
> The anaconda installer makes large drive setups horridly tedious 
> (especially if reinstalling a lot).

You can also install centos using FAI (http://fai-project.org) which
was announced in this mail:
http://lists.centos.org/pipermail/centos/2011-September/117878.html 

It has a pretty nice partitioning tool called setup-storage which uses
a configuration file similar to fstab. Here's one example.

disk_config disk1  fstabkey:uuid preserve_reinstall:7,8

primary  /  7G-15Gext4  rw,noatime,errors=remount-ro 
createopts="-m15"
logical  swap   2G-4G swap  rw   
logical  /tmp   3G-15Gext4  rw,noatime 
logical  /srv   20G-30G   ext4  rw,noatime 
logical  /home  1G-   ext4  rw,noatime,nosuid,nodev

IMO it's much more easier to do the hard disk setup this way,
especially if you do multiple installations.
-- 
regards Thomas
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] CentOS 5.7 Ethernet bonding - order of enslavement matters?

[whitivery]

Setting up bonding in active-backup mode 1 (using ARP monitoring)
on a server, it looked OK, but pulling the active link cable
didn't actually work, it didn't fail over.

Eventually with manual playing around with modprobe, ifconfig,
ifenslave, etc., a solution was stumbled upon: enslave the eth1
device before eth0, and all is good.

Why this should matter is a puzzle - I could not find anything in
bonding.txt or on the web about it.

I had to change ifup-eth to fix the problem.

Any ideas on why the enslavement order matters, or a better
solution to work around it?

The rest of this post is details.


To fix this, I had to patch
/etc/sysconfig/network-scripts/ifup-eth to reverse the order when
it is updating the sysfs slaves list.  A 1-line change, from:

for device in $(LANG=C egrep -l "^[[:space:]]*MASTER=\"?${DEVICE}\"?"
/etc/sysconfig/network-scripts/ifcfg-*) ; do

to:

for device in $(LANG=C egrep -l "^[[:space:]]*MASTER=\"?${DEVICE}\"?"
/etc/sysconfig/network-scripts/ifcfg-* | sort -r) ; do


With that change, everything works perfectly.

I don't like this solution (changing standard system files) but
it seems like the best one for now, and should not break
anything.


Maybe it's the particular network devices.  Platform is VIA M850
running CentOS5.7 64-bit, original content from DVD (no yum
update done).

Eth0 is the onboard device, using an updated VIA Velocity driver
(velocityget 1.42 instead of default via-velocity):

05:00.0 Ethernet controller: VIA Technologies, Inc. VT6120/VT6121/VT6122
Gigabit Ethernet Adapter (rev 82)

Eth1 is a Linksys (Cisco) USB300M USB-Ethernet dongle, using asix
driver:

Bus 001 Device 005: ID 0b95:7720 ASIX Electronics Corp. AX88772

Modprobe.conf:

alias eth0 velocityget

With the network service enabled (NetworkManager disabled), this
is my setup:

ifcfg-bond0:

DEVICE=bond0
BOOTPROTO=none
ONBOOT=yes
IPADDR=10.6.0.90
NETMASK=255.255.255.0
GATEWAY=10.6.0.1
BONDING_OPTS="mode=active-backup arp_interval=300 primary=eth0
arp_ip_target=+10.6.0.1 arp_ip_target=+10.6.0.2"

ifcfg-eth0:

DEVICE=eth0
BOOTPROTO=none
ONBOOT=yes
IPADDR=10.6.0.90
NETMASK=255.255.255.0
GATEWAY=10.6.0.1
HWADDR=00:1F:F2:03:FA:45
MASTER=bond0
SLAVE=yes

ifcfg-eth1:

DEVICE=eth1
BOOTPROTO=none
ONBOOT=yes
IPADDR=10.6.1.90
NETMASK=255.255.255.0
GATEWAY=10.6.0.1
MASTER=bond0
SLAVE=yes
HWADDR=58:6d:8f:3d:8d:4f


___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] CentOS 6 is a bear

[Andrew Dorozhkin]

On 08.10.2011 5:14, Bob Hoffman wrote:
> Gotta say, centos has been tough to install and get working.
>
> The anaconda installer makes large drive setups horridly tedious
> (especially if reinstalling a lot).
>
> Package selection seems a bit off...
>
> I did a virtualization package, no custom..did not install qemu,
> libvirt, and all attempts to do any virtualization failed due to
> non-installed packages.
>
> Then I decided to select all the virtualization packages in custom, but
> had selected 'web server' as the base package. I was never able to
> connect to the net here at home...apparently some things with 'modprobe'
> did not install and the eth devices 'does not exist' or something like that.
>
> Then I decided on the entire gnome package, with all the bells and
> whistles...everything worked, but who wants that? I removed some
> packages in gnome to see and reboot made machine dead.
> Did that 4 different times with very few package removals.
>
> Did a number of various tries with custom selections, but the
> dependencies seem to not be grabbing all it needs to work. Never got a
> non gnome setup to recognize eth devices (well, one time, but it never
> was able to get the net).
>
> I just installed a custom set up, all virtualization packages-
> virtualization selected as base. I added some gnome stuff and a few
> other doo dads.booted up..went right to the command line no virt
> software works, errors everywhere. Display will not come up (x, vnc, or
> gnome no matter what)..
>
> Every installation, in first boot up had major missing or odd problems.
> One time I booted up with a gnome set up and selinux was stopping 5
> differetn gdm programs..at boot...due to security risks... wtf?
>
> Any attempt to disable or make selinux permissive results in a dead
> machine, unable to ever boot again (left one up for 12 hours, never came
> back up, thought it was relabeling, but no message.)
>
> Removing packages with the gnome running only worked about 10% of the
> time, all others resulted in dead machine at reboot.
>
> I am considering, the only way to actually install and use this as a
> virtualized host is to go full desktop and hope the selinux enforcing
> will not break the system (with all the programs it will not let run on
> boot)...
>
> I have never, not once, been able to connect to the net in the command
> line setups...I know how to configure eths, network, dns, etc...not
> once, not even dhcp..config eth0 up, etc.. Gnome has not a single issue
> with the same exact file setups.. Many command line setups would not
> even see the eth devices, something about modprobe this or that not
> installed.wth?
>
> quite an interesting task. I have now taken the server out of the center
> and am just going to endlessly install until I get a system that is low
> resources and actually allows the virtualization to work.
>
> My last install, with all virt packages selected...?. cannot run
> virt-manager, libvirt, though some virt programs do work...why?
> something each needed to run was not installed as a
> dependency
>
> Reinstalling would not be so bad, but the anaconda installer does not
> quite set up the drives the same on a reinstall forcing a deletion of
> partitions and redoing the entire setup..quite annoying
>
> /rant off
> ___
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos


Would you summarize what problems with NIC(s) do you have? Its 
model/chip and kernel log (dmesg) would be nice as well.

In case this is Intel EXPI9301CTBLK NIC (according to your YT profile), 
which is seemed to be 82574L based, you should take into account known 
issues with stock e1000e module shipped with C6.0 [1] and that chip.

//br

1. http://lists.centos.org/pipermail/centos/2011-September/118027.html
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] Virtual RPM howto?

[Kenneth Porter]

Can someone point me to a howto or an example of a virtual package?

I'm building Diaspora (the open source competitor to Facebook) and I 
figured it would be handy to gather all the prereqs into a virtual package.

I'm working from these instructions, which seemed to go fine on CentOS 6:


___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] Installing Ruby gems on RPM-based systems

[Kenneth Porter]

When I first got involved with Red Hat (back with 5.2 in the early 90's) I 
learned the hard way not to use language-specific packaging systems like 
CPAN for Perl because they'd conflict with RPM's database and make it much 
harder to manage what was installed on my system. If I now need a package 
for which no RPM is available, I'll use a utility like cpanspec to 
repackage it into an RPM and install that.

Now I'm starting to work with Ruby and apparently it has its own packages 
called "gems". How do people deal with making Ruby and RPM get along?

I'm trying to build Diaspora, an open source alternative to Facebook, and 
it wants me to install a ton of gems. I'm working on a "disposable" machine 
that I can re-image at will, so I let it use Ruby's "bundle install" 
command to dump all the gems from the Ruby repositories into their system 
location. But in a "real" installation I'd want to do this with RPM, 
repackaging gems as needed. What's available to do this properly?


___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Installing Ruby gems on RPM-based systems

[Kenneth Porter]

--On Saturday, October 08, 2011 4:56 AM -0700 Kenneth Porter 
 wrote:

> How do people deal with making Ruby and RPM get along?

No sooner do I hit the send button than I realize how to frame the question 
to Google and find the answer. For the list archives:




___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] CentOS 6 is a bear [solved]

[Bob Hoffman]

I downloaded a brand new file, made a brand new dvd.
I then did an install selecting the virtualization package, then in 
custom I selected all the virt packages.
During install did the same thing as 100 times before, including making 
netmanager turn on eth auto.

it came up in command line, connected to the net, only error I can see 
so far in the dmesg is 2 things about
composite sync or something like that...

all other errors went away, installed the proper files to see my eths. I 
could even yum update from
command line.

I assume I must have had a bad dvd burn that corrupted a file somewhere.

Instead of taking 3-5 minutes to boot up, it boots quick now.
I was actually able to boot, play around, yum remove a few things, set 
selinux to enforce and permissive
on different boot ups and it actually booted up.

I gotta say the new dvd was 100% easy and no problems..the old dvd was 
giving me a unstable system.

the composite sync thing seems to be a bug that can be changed in grub, 
so they say.

Not even going to attempt to add x or graphics though, I guess you can 
install guests with text installer.
Just no fancy lvm stuff for the guests...

thanks ... it is up and running...finally...
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] CentOS-6.0 Continuous Release ( CR ) repository

[Timothy Murphy]

I don't really understand the function of this repository,
or rather why the RPMs in it are not in the standard repository?

I read the outline at
,
and added the repository on two CentOS machines.
On yum-updating some 450MB of updates were installed.
Both machines appear to be running perfectly well.

-- 
Timothy Murphy  
e-mail: gayleard /at/ eircom.net
tel: +353-86-2336090, +353-1-2842366
s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] [C6] Some typical apps missing?

[Ljubomir Ljubojevic]

I have recompiled many missing apps for Desktop use.

You can find packages at http://rpms.plnet.rs/plnet-centos6-i386/ i 
http://rpms.plnet.rs/plnet-centos6-x86_64/
Source RPMs are in http://rpms.plnet.rs/plnet-centos6-srpms/

That is not official repo, just my effort to have all desired 
packages/apps I want on my Desktop. Most(almost all) packages should be 
signed, and I am preparing release package for easy install, and some 
organizing is due.

Most noteworthy packages are (at the moment):
Firefox 7.0.1
Thunderbird 7.0.1
VLC 1.1.11 EPEL friendly (from Fuduntu) - not yet fully tested
MythTV 0.24
Wine 1.3.24
Banshee 2.0.1
Krusader 2.3.0
gnome-netstatus-2.28.1 (missing network Gnome applet)
Tomboy 1.2.2
LTSP 5.1.95
Gammu 1.26 /Wammu
OBEX and Blueman packages
For list of all downloaded packages please take a look for your self.


Notices:
- It is not wise to use these repositories on production servers!
- Do not use them if you are not comfortable with (some) unsigned packages.
- Some packages might be unstable. Use it on your own risk.
- Packages from plnet-downloaded are put there from other repositories
   or download sites, those who do not have their own repositories, for 
easy installing and avoiding search-download-
   install process. They are for now not regularly updated, but you are
   welcome to infor me if one of packages has newer version.
- plnet-replace packages are newer (non-critical only) packages then
   those in base repository.
- Almost all packages for now have "Packager" and other fields unchanged 
from original srpms. This is planed for later.

For now, you can use this for yum (watch for broken lines):

[plnet-compiled]
name=Spec CentOS-$releasever - plnet-compiled - $releasever - $basearch
baseurl=http://rpms.plnet.rs/plnet-centos6-$basearch/RPMS.plnet-compiled/
gpgcheck=0
enabled=1
priority=2

[plnet-downloaded]
name=Spec CentOS-$releasever - plnet-downloaded - $releasever - $basearch
baseurl=http://rpms.plnet.rs/plnet-centos6-$basearch/RPMS.plnet-downloaded/
gpgcheck=0
enabled=1
priority=2

[plnet-releases]
name=Spec CentOS-$releasever - plnet-releases - $releasever - $basearch
baseurl=http://rpms.plnet.rs/plnet-centos6-$basearch/RPMS.plnet-releases/
gpgcheck=0
enabled=1
priority=1

[plnet-replace]
name=Spec CentOS-$releasever - plnet-replace - $releasever - $basearch
baseurl=http://rpms.plnet.rs/plnet-centos6-$basearch/RPMS.plnet-replace/
gpgcheck=0
enabled=0
priority=1

[plnet-test]
name=Spec CentOS-$releasever - plnet-test - $releasever - $basearch
baseurl=http://rpms.plnet.rs/plnet-centos6-$basearch/RPMS.plnet-test/
gpgcheck=0
enabled=0
priority=4

-- 

Ljubomir Ljubojevic
(Love is in the Air)
PL Computers
Serbia, Europe

Google is the Mother, Google is the Father, and traceroute is your
trusty Spiderman...
StarOS, Mikrotik and CentOS/RHEL/Linux consultant
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Installing Ruby gems on RPM-based systems

[Craig White]

On Sat, 2011-10-08 at 03:56 -0700, Kenneth Porter wrote:
> When I first got involved with Red Hat (back with 5.2 in the early 90's) I 
> learned the hard way not to use language-specific packaging systems like 
> CPAN for Perl because they'd conflict with RPM's database and make it much 
> harder to manage what was installed on my system. If I now need a package 
> for which no RPM is available, I'll use a utility like cpanspec to 
> repackage it into an RPM and install that.
> 
> Now I'm starting to work with Ruby and apparently it has its own packages 
> called "gems". How do people deal with making Ruby and RPM get along?
> 
> I'm trying to build Diaspora, an open source alternative to Facebook, and 
> it wants me to install a ton of gems. I'm working on a "disposable" machine 
> that I can re-image at will, so I let it use Ruby's "bundle install" 
> command to dump all the gems from the Ruby repositories into their system 
> location. But in a "real" installation I'd want to do this with RPM, 
> repackaging gems as needed. What's available to do this properly?
> 
> 

CentOS 6 is new so there's little experience with running ruby packages
on it but there's really no problem with running 'gem install
$SOME_PACKAGE' on any system. Realistically, the available rpm packages
are never going to keep up with the gems so after you get the base ruby
rpm packages installed (ruby/ruby-irb/ruby-ri/ruby-rdoc/ruby-gems) you
should probably just quit there and use the built-in gem package
provider to do everything else. Also, if you are talking about something
like a Ruby on Rails solution, the more organized setups will use
'bundler' to get the application up to speed rather quickly.

Some people use RVM (ruby virtual manager which will allow you to have
multiple versions of ruby on the same computer). This pretty much steps
outside of the native rpm packaging completely.

CentOS 5.x however is a different beast and the ruby implementation is
1.8.5-X which is too old to do much of anything and I've found the
simplest thing to do is not use any CentOS ruby packages whatsoever and
simply use 'Enterprise ruby'

Craig


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Virtual RPM howto?

[Ned Slider]

On 08/10/11 11:46, Kenneth Porter wrote:
> Can someone point me to a howto or an example of a virtual package?
>

xorg-x11-drivers is an example of a virtual package in the distro. It 
pulls in all the xorg-x11-drv-* packages as dependencies. Take a look at 
the SRPM.

Hope that helps.

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Installing Ruby gems on RPM-based systems

[Kenneth Porter]

--On Saturday, October 08, 2011 6:29 AM -0700 Craig White 
 wrote:

> CentOS 6 is new so there's little experience with running ruby packages
> on it but there's really no problem with running 'gem install
> $SOME_PACKAGE' on any system. Realistically, the available rpm packages
> are never going to keep up with the gems so after you get the base ruby
> rpm packages installed (ruby/ruby-irb/ruby-ri/ruby-rdoc/ruby-gems) you
> should probably just quit there and use the built-in gem package
> provider to do everything else. Also, if you are talking about something
> like a Ruby on Rails solution, the more organized setups will use
> 'bundler' to get the application up to speed rather quickly.

That makes sense.

I played a little with gem2rpm but to really be useful there should be a 
yum repository of standard gems that tracks whatever ruby's normal upstream 
repositories hold (its CPAN equivalent).


___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Installing Ruby gems on RPM-based systems

[Craig White]

On Sat, 2011-10-08 at 05:46 -0700, Kenneth Porter wrote:
> --On Saturday, October 08, 2011 6:29 AM -0700 Craig White 
>  wrote:
> 
> > CentOS 6 is new so there's little experience with running ruby packages
> > on it but there's really no problem with running 'gem install
> > $SOME_PACKAGE' on any system. Realistically, the available rpm packages
> > are never going to keep up with the gems so after you get the base ruby
> > rpm packages installed (ruby/ruby-irb/ruby-ri/ruby-rdoc/ruby-gems) you
> > should probably just quit there and use the built-in gem package
> > provider to do everything else. Also, if you are talking about something
> > like a Ruby on Rails solution, the more organized setups will use
> > 'bundler' to get the application up to speed rather quickly.
> 
> That makes sense.
> 
> I played a little with gem2rpm but to really be useful there should be a 
> yum repository of standard gems that tracks whatever ruby's normal upstream 
> repositories hold (its CPAN equivalent).

gem development is too fast/furious for any type of distribution native
packaging to reasonably keep up. I've never actually looked at any
gem2rpm thing and the thought of doing so seems ridiculous to me.

I've been using ruby stuff since 2005 and I pretty much avoid the
distribution packages. FWIW, I don't use the native RPM ruby packages on
CentOS and likewise, don't use the native DPKG ruby packages on Ubuntu
and use Enterprise Ruby either.

Eventually it becomes obvious that to do anything serious with ruby, the
OS packages lag behind and become the problem. If you are doing
lightweight things, then you can probably get by. Certainly for
someone's first foray into ruby, CentOS 6 ruby packages are sufficient
and once you have the base installation, the gem packaging provider can
handle things quite well.

Craig


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] CentOS-6.0 Continuous Release ( CR ) repository

[nux]

Timothy Murphy writes:

> I don't really understand the function of this repository,
> or rather why the RPMs in it are not in the standard repository?


Because there is no "standard repository" yet. These RPMs are from the next 
version (6.1 as we write this) which has not been published yet. CR is just 
a way to keep up with updates while they work on publishing Centos 6.1.

--
Nux!
www.nux.ro

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] CentOS-6.0 Continuous Release ( CR ) repository

[Ljubomir Ljubojevic]

Vreme: 10/08/2011 02:34 PM, Timothy Murphy piše:
> I don't really understand the function of this repository,
> or rather why the RPMs in it are not in the standard repository?
>
> I read the outline at
> ,
> and added the repository on two CentOS machines.
> On yum-updating some 450MB of updates were installed.
> Both machines appear to be running perfectly well.
>

Every minor version is treated as upgrade, not update. If CR packages 
would be added to existing updates 6.0 repository, what would people who 
want ONLY 6.0 do? There are many other more compelling reasons, but even 
this one is enough.

-- 

Ljubomir Ljubojevic
(Love is in the Air)
PL Computers
Serbia, Europe

Google is the Mother, Google is the Father, and traceroute is your
trusty Spiderman...
StarOS, Mikrotik and CentOS/RHEL/Linux consultant
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] CentOS 6 is a bear [solved]

[Ljubomir Ljubojevic]

Vreme: 10/08/2011 02:27 PM, Bob Hoffman piše:
> Not even going to attempt to add x or graphics though, I guess you can
> install guests with text installer.
> Just no fancy lvm stuff for the guests...
>
> thanks ... it is up and running...finally...
You can use SystemRescueCD, or even Partition Editor selection from 
Hiren Boot CD (14?) to set fancy lvm/RAID partitioning.


-- 

Ljubomir Ljubojevic
(Love is in the Air)
PL Computers
Serbia, Europe

Google is the Mother, Google is the Father, and traceroute is your
trusty Spiderman...
StarOS, Mikrotik and CentOS/RHEL/Linux consultant
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Mock - Problems building Centos5 package on Centos6 - where can I ask for advice ?

[Trey Dockendorf]

On Oct 7, 2011 3:34 AM, "Morgan Cox"  wrote:
>
> Hi
>
> Thank you for your extremely quick (and faster than support from any
> company..) reply.
>
> Sorry, can you give more detail ?
>
> >From the look of the error the 'mock centos5' is missing these files :-
>
> /usr/share/aclocal/ltoptions.m4
> /usr/share/aclocal/ltsugar.m4
> /usr/share/aclocal/ltversion.m4
> /usr/share/aclocal/lt~obsolete.m4
>
> - which come from libtool2 (on centos6)
>
> Centos5 obviously doesn't have that version...
>
> I noticed in the .spec file it has
>
>
> ---
> %build
> # aclocal workaround - to be improved
> cat `aclocal
> --print-ac-dir`/{libtool,ltoptions,ltsugar,ltversion,lt~obsolete}.m4
> >>aclocal.m4
>
> # Force use of system libtool:
> libtoolize --force --copy
> cat `aclocal
> --print-ac-dir`/{libtool,ltoptions,ltsugar,ltversion,lt~obsolete}.m4
> >build/libtool.m4
> ---
>
> It also has - from the original .spec file I based it on:-
>
> BuildRequires: bzip2, perl, libtool >= 1.4.3, gcc-c++
>
> I have libtool installed in the mock enviroment ...
>
> Anyone know what i'm doing wrong ?
>
> Regards !
>
>
>
>
>
>
>
> On 6 October 2011 15:57, John Hodrien  wrote:
>
> > On Thu, 6 Oct 2011, Morgan Cox wrote:
> >
> > > Hi.
> > >
> > > I am trying to use Mock to rebuild a .src.rpm file I have made for PHP
> > 5.3.8
> > > (for Centos6)
> > >
> > > I have managed to install deps fine with mock.
> > >
> > > When I try to rebuild the package though I get.
> >
> > BuildRequires are wrong, since this SRPM requires files that aren't
being
> > pulled in.  Add BuildRequires to satisfy these missing requirements and
> > it'll
> > work.
> >
> > jh
> > ___
> > CentOS mailing list
> > CentOS@centos.org
> > http://lists.centos.org/mailman/listinfo/centos
> >
> ___
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos

If your wanting PHP-5.3 for CentOS5 you may want to look at the IUS repo.
They provide PHP 5.2 and 5.3 for CentOS5.

If you send me your SRPM offlist Ill try to build it on my Mock environment.

- Trey
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] CentOS-6.0 Continuous Release ( CR ) repository

[Nicolas Thierry-Mieg]

Ljubomir Ljubojevic wrote:
> Vreme: 10/08/2011 02:34 PM, Timothy Murphy piše:
>> I don't really understand the function of this repository,
>> or rather why the RPMs in it are not in the standard repository?
>>
>> I read the outline at
>> ,
>> and added the repository on two CentOS machines.
>> On yum-updating some 450MB of updates were installed.
>> Both machines appear to be running perfectly well.
>>
>
> Every minor version is treated as upgrade, not update. If CR packages
> would be added to existing updates 6.0 repository, what would people who
> want ONLY 6.0 do? There are many other more compelling reasons, but even
> this one is enough.
>

the vast majority of people who want "only 6.0" don't understand the 
centos release process.
I'ld say the main reason for CR is conformance to upstream.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] multiple ifcfg-x locations on CentOS-6

[Ljubomir Ljubojevic]

Vreme: 10/08/2011 01:10 AM, Nicolas Thierry-Mieg piše:
> James B. Byrne wrote:
>> $ ll /sysconfig/networking/profiles/*
>> total 24
>> -rw-r--r--. 2 root root 158 Oct  7 15:19 hosts
>> -rw-r--r--. 2 root root 116 Oct  7 15:19 ifcfg-br0
>> -rw-r--r--. 2 root root 238 Oct  7 15:24 ifcfg-eth0
>> -rw-r--r--. 2 root root 117 Oct  7 15:19 ifcfg-eth1
>> -rw-r--r--. 2 root root  40 Oct  7 15:19 network
>> -rw-r--r--. 2 root root 120 Oct  7 15:25 resolv.conf
>>
>>
>> $ ll /etc/sysconfig/networking/devices
>> total 12
>> -rw-r--r--. 2 root root 116 Oct  7 15:19 ifcfg-br0
>> -rw-r--r--. 2 root root 238 Oct  7 15:24 ifcfg-eth0
>> -rw-r--r--. 2 root root 117 Oct  7 15:19 ifcfg-eth1
>
> ^
> look at that 2 there
>
>> My questions are:  What are these duplicate, and
>> identical, files doing in multiple places on my system;
>
> those are hard-linked, most likely the same file in both subdirs (not
> identical files, a single file hard-linked twice)
>
> the /etc/sysconfig/networking/* subdirs can exist on C5 as well, I think
> they're used by system-config-network
>
>
>> and why are they evidently interfering with the normal
>> processing of /etc/sysconfig/network-scripts through the
>> service utility?
>
> on a C6 machine I have those dirs are empty, as on your C5 system. I
> probably never used system-config-network on it. Networking through
> /etc/init.d/network functions fine without them.

Files in /sysconfig/networking/profiles/ are not hardlinks. As the last 
name suggests, those are files from Profiles. And using "ll" command is 
blinding you. If you use "ls -lR /etc/sysconfig/networking/profiles/* :

/etc/sysconfig/networking/profiles/default:
total 44
-rw-r--r--. 2 root root 271 Sep  3 22:00 hosts
-rw-r--r--. 3 root root 315 Jun 30 13:39 ifcfg-br0
-rw-r--r--. 3 root root 248 Jun 30 13:39 ifcfg-br0:1
-rw-r--r--. 3 root root 248 Jun 30 13:39 ifcfg-br0:2
-rw-r--r--. 3 root root 248 Jun 30 13:39 ifcfg-br0:3
-rw-r--r--. 3 root root 248 Jun 30 13:39 ifcfg-br0:4
-rw-r--r--. 3 root root 248 Jun 30 13:39 ifcfg-br0:5
-rw-r--r--. 3 root root 211 Jun 30 13:39 ifcfg-br0:6
-rw-r--r--. 3 root root 211 Jun 30 13:39 ifcfg-br0:7
-rw-r--r--. 3 root root 229 Sep  4 01:06 ifcfg-eth0
-rw-r--r--. 1 root root 286 Sep  4 00:56 resolv.conf

Both C5 and C6 have "network" service able to create and switch to 
multiple profiles. For example, switching to profile "WiFiKuca" is done 
with:

"system-config-network-cmd -p WiFiKuca -a"

In sub-directories of /etc/sysconfig/networking/profiles/ are stored 
originals of your configuration, and /etc/sysconfig/network-scripts/ has 
only files from current active profile.


-- 

Ljubomir Ljubojevic
(Love is in the Air)
PL Computers
Serbia, Europe

Google is the Mother, Google is the Father, and traceroute is your
trusty Spiderman...
StarOS, Mikrotik and CentOS/RHEL/Linux consultant
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] CentOS-6.0 Continuous Release ( CR ) repository

[Ljubomir Ljubojevic]

Vreme: 10/08/2011 03:22 PM, Nicolas Thierry-Mieg piše:
> Ljubomir Ljubojevic wrote:
>> Vreme: 10/08/2011 02:34 PM, Timothy Murphy piše:
>>> I don't really understand the function of this repository,
>>> or rather why the RPMs in it are not in the standard repository?
>>>
>>> I read the outline at
>>> ,
>>> and added the repository on two CentOS machines.
>>> On yum-updating some 450MB of updates were installed.
>>> Both machines appear to be running perfectly well.
>>>
>>
>> Every minor version is treated as upgrade, not update. If CR packages
>> would be added to existing updates 6.0 repository, what would people who
>> want ONLY 6.0 do? There are many other more compelling reasons, but even
>> this one is enough.
>>
>
> the vast majority of people who want "only 6.0" don't understand the
> centos release process.
> I'ld say the main reason for CR is conformance to upstream.

There are large systems that are obligated to use only packages from 
official releases/packages for security, etc.

Some people could advocate braking from "conformance to upstream", it's 
"political" reason, that is why I avoid it.  Separation of individual 
minor version is technical reason and enough as a show stopper, that is 
why I chose it.


-- 

Ljubomir Ljubojevic
(Love is in the Air)
PL Computers
Serbia, Europe

Google is the Mother, Google is the Father, and traceroute is your
trusty Spiderman...
StarOS, Mikrotik and CentOS/RHEL/Linux consultant
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Unable to run yum update

[Ljubomir Ljubojevic]

yaf-1.3.2-1.el6.rf.x86_64 did request older version of libfixbuf. And 
libfixbuf 1.0.1 was introduced Sept 28th.

There is yaf-2.1.1-2.el6.rf.x86_64.rpm as of yesterday. It should use 
newer libfixbuf.


-- 

Ljubomir Ljubojevic
(Love is in the Air)
PL Computers
Serbia, Europe

Google is the Mother, Google is the Father, and traceroute is your
trusty Spiderman...
StarOS, Mikrotik and CentOS/RHEL/Linux consultant
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] CentOS-6.0 Continuous Release ( CR ) repository

[Ned Slider]

On 08/10/11 14:22, Nicolas Thierry-Mieg wrote:
> Ljubomir Ljubojevic wrote:
>> Vreme: 10/08/2011 02:34 PM, Timothy Murphy piše:
>>> I don't really understand the function of this repository,
>>> or rather why the RPMs in it are not in the standard repository?
>>>
>>> I read the outline at
>>> ,
>>> and added the repository on two CentOS machines.
>>> On yum-updating some 450MB of updates were installed.
>>> Both machines appear to be running perfectly well.
>>>
>>
>> Every minor version is treated as upgrade, not update. If CR packages
>> would be added to existing updates 6.0 repository, what would people who
>> want ONLY 6.0 do? There are many other more compelling reasons, but even
>> this one is enough.
>>
>
> the vast majority of people who want "only 6.0" don't understand the
> centos release process.
> I'ld say the main reason for CR is conformance to upstream.

The CR repository was originally intended to be a fast track mechanism 
by which packages from the next point release could be released to the 
public once they had been built and passed QA without having to wait for 
ISO images to be built and sync'd to the mirrors.

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] CentOS-6.0 Continuous Release ( CR ) repository

[Timothy Murphy]

n...@li.nux.ro wrote:

>> I don't really understand the function of this repository,
>> or rather why the RPMs in it are not in the standard repository?

> Because there is no "standard repository" yet. These RPMs are from the
> next version (6.1 as we write this) which has not been published yet. CR
> is just a way to keep up with updates while they work on publishing Centos
> 6.1.

I've read the various responses, and am not really convinced.
It seems to me the developers are just making more work for themselves.
Of course that is their prerogative ...


-- 
Timothy Murphy  
e-mail: gayleard /at/ eircom.net
tel: +353-86-2336090, +353-1-2842366
s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] CentOS-6.0 Continuous Release ( CR ) repository

[Timothy Murphy]

Nicolas Thierry-Mieg wrote:

> the vast majority of people who want "only 6.0" don't understand the
> centos release process.

Are there such people?
I thought everyone was screaming for 6.1?

As far as I am concerned, a system either works or does not work;
and my system seems to work fine after CR update.

-- 
Timothy Murphy  
e-mail: gayleard /at/ eircom.net
tel: +353-86-2336090, +353-1-2842366
s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] CentOS-6.0 Continuous Release ( CR ) repository

[John Hodrien]

On Sat, 8 Oct 2011, Timothy Murphy wrote:

> n...@li.nux.ro wrote:
>
>>> I don't really understand the function of this repository,
>>> or rather why the RPMs in it are not in the standard repository?
>
>> Because there is no "standard repository" yet. These RPMs are from the
>> next version (6.1 as we write this) which has not been published yet. CR
>> is just a way to keep up with updates while they work on publishing Centos
>> 6.1.
>
> I've read the various responses, and am not really convinced.
> It seems to me the developers are just making more work for themselves.
> Of course that is their prerogative ...

Look at it differently then.  They're building packages for 6.1, and some pass
QA and some don't.  Equally getting anaconda happy is required.  Until you get
all of that done, you don't get 6.1.  Up that point, why not release packages
that pass QA?  That's CR, so it shouldn't involve an excessive amount of extra
work, but it does offer faster access to the updates.

jh
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] CentOS-6.0 Continuous Release ( CR ) repository

[John Hinton]

On 10/8/2011 10:30 AM, Timothy Murphy wrote:
> n...@li.nux.ro wrote:
>
>>> I don't really understand the function of this repository,
>>> or rather why the RPMs in it are not in the standard repository?
>> Because there is no "standard repository" yet. These RPMs are from the
>> next version (6.1 as we write this) which has not been published yet. CR
>> is just a way to keep up with updates while they work on publishing Centos
>> 6.1.
> I've read the various responses, and am not really convinced.
> It seems to me the developers are just making more work for themselves.
> Of course that is their prerogative ...
>
>
It is really quite simple. 6.1 is not out. Many of us absolutely must 
have 6.0 serving the public at this point. There are no more security 
updates for 6.0. So, why not provide updated packages as they are 
available, if they don't break other packages? It seems very sound 
reasoning to me. Extra work? Well, it is some, but not really that much.

To me, this is another case of the CentOS team trying hard to provide 
what the community needs as fast as they can. Choose to use the CR or 
not. For me and I'm certain many others, I'm very happy that it is 
there! And this provides an answer for now and perhaps again in the 
future when a minor release occurs just before a major security issue, 
leaving the ability to move forward with the new security packages 
before the minor release is ready.

As for passing security 'testing'. Well, CR might not provide the answer 
the 'testers' want, but do they ultimately want security or do they only 
want you to pass the test? Sometimes I think the latter... a question of 
'perceived' or 'actual'. I'll choose actual... and like it to be pretty 
quick... and CR provides an aid there.

John Hinton



-- 
John Hinton
877-777-1407 ext 502
http://www.ew3d.com
Comprehensive Online Solutions

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] CentOS 6.0 CR mdadm-3.2.2 breaks Intel BIOS RAID

[Trey Dockendorf]

I just upgraded my home KVM server to CentOS 6.0 CR to make use of the
latest libvirt and now my RAID array with my VM storage is missing.  It
seems that the upgrade to mdadm-3.2.2 is the culprit.

This is the output from mdadm when scanning that array,

# mdadm --detail --scan
ARRAY /dev/md0 metadata=imsm UUID=734f79cf:22200a5a:73be2b52:3388006b
ARRAY /dev/md126 metadata=imsm UUID=3d135942:f0fad0b0:33255f78:29c3f50a
mdadm(IMSM): Unsupported attributes : 4000
mdadm: IMSM metadata loading not allowed due to attributes incompatibility.
mdadm(IMSM): Unsupported attributes : 4000
mdadm: IMSM metadata loading not allowed due to attributes incompatibility.
ARRAY /dev/md127 container=/dev/md0 member=0
UUID=734f79cf:22200a5a:73be2b52:3388006b

The error about IMSM shows up on google as something that happened to Fedora
users during a FC14->FC15 upgrade.

The server itself isn't old, it's a Supermicro 2U with Dual Xeon 5400 family
of CPU.  There are two RAIDs on this one controller...a RAID1 which still
functions and a RAID5 which is the one that is unable to be seen.  I don't
know what IMSM is for, but the only thing strange about that array is it is
2.7TB so the BIOS configured it as two separate arrays, one as 2TB and one
as 700GB, but it was showing up to CentOS as a single volume.

I downgraded to 3.2.1 , ran mdadm again and bam...it works,

# mdadm --detail --scan
ARRAY /dev/md0 metadata=imsm UUID=734f79cf:22200a5a:73be2b52:3388006b
ARRAY /dev/md126 metadata=imsm UUID=3d135942:f0fad0b0:33255f78:29c3f50a
ARRAY /dev/md127 container=/dev/md0 member=0
UUID=691f975d:6beecfd8:67b39886:b7ee7f6e

Hopefully this can be fixed before this version makes it to 6.1, though it's
likely a problem for upstream RHEL as well.

- Trey
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] CentOS 6.0 CR mdadm-3.2.2 breaks Intel BIOS RAID

[Steve Brooks]

On Sat, 8 Oct 2011, Trey Dockendorf wrote:

> I just upgraded my home KVM server to CentOS 6.0 CR to make use of the
> latest libvirt and now my RAID array with my VM storage is missing.  It
> seems that the upgrade to mdadm-3.2.2 is the culprit.
>
> This is the output from mdadm when scanning that array,
>
> # mdadm --detail --scan
> ARRAY /dev/md0 metadata=imsm UUID=734f79cf:22200a5a:73be2b52:3388006b
> ARRAY /dev/md126 metadata=imsm UUID=3d135942:f0fad0b0:33255f78:29c3f50a
> mdadm(IMSM): Unsupported attributes : 4000
> mdadm: IMSM metadata loading not allowed due to attributes incompatibility.
> mdadm(IMSM): Unsupported attributes : 4000
> mdadm: IMSM metadata loading not allowed due to attributes incompatibility.
> ARRAY /dev/md127 container=/dev/md0 member=0
> UUID=734f79cf:22200a5a:73be2b52:3388006b
>
> The error about IMSM shows up on google as something that happened to Fedora
> users during a FC14->FC15 upgrade.
>
> The server itself isn't old, it's a Supermicro 2U with Dual Xeon 5400 family
> of CPU.  There are two RAIDs on this one controller...a RAID1 which still
> functions and a RAID5 which is the one that is unable to be seen.  I don't
> know what IMSM is for, but the only thing strange about that array is it is
> 2.7TB so the BIOS configured it as two separate arrays, one as 2TB and one
> as 700GB, but it was showing up to CentOS as a single volume.
>
> I downgraded to 3.2.1 , ran mdadm again and bam...it works,
>
> # mdadm --detail --scan
> ARRAY /dev/md0 metadata=imsm UUID=734f79cf:22200a5a:73be2b52:3388006b
> ARRAY /dev/md126 metadata=imsm UUID=3d135942:f0fad0b0:33255f78:29c3f50a
> ARRAY /dev/md127 container=/dev/md0 member=0
> UUID=691f975d:6beecfd8:67b39886:b7ee7f6e
>
> Hopefully this can be fixed before this version makes it to 6.1, though it's
> likely a problem for upstream RHEL as well.
>
> - Trey
> ___
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos



Hmm I recall seeing something like this on an "sl6" box. I think it needed 
a "/etc/mdadm.conf" with som metadata id code.. I am pretty sure I fixed 
it with

mdadm --detail --scan >> /etc/mdadm.conf

and a reboot.

Steve
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] CentOS 6.0 CR mdadm-3.2.2 breaks Intel BIOS RAID

[Trey Dockendorf]

On Sat, Oct 8, 2011 at 2:04 PM, Steve Brooks wrote:

> On Sat, 8 Oct 2011, Trey Dockendorf wrote:
>
> > I just upgraded my home KVM server to CentOS 6.0 CR to make use of the
> > latest libvirt and now my RAID array with my VM storage is missing.  It
> > seems that the upgrade to mdadm-3.2.2 is the culprit.
> >
> > This is the output from mdadm when scanning that array,
> >
> > # mdadm --detail --scan
> > ARRAY /dev/md0 metadata=imsm UUID=734f79cf:22200a5a:73be2b52:3388006b
> > ARRAY /dev/md126 metadata=imsm UUID=3d135942:f0fad0b0:33255f78:29c3f50a
> > mdadm(IMSM): Unsupported attributes : 4000
> > mdadm: IMSM metadata loading not allowed due to attributes
> incompatibility.
> > mdadm(IMSM): Unsupported attributes : 4000
> > mdadm: IMSM metadata loading not allowed due to attributes
> incompatibility.
> > ARRAY /dev/md127 container=/dev/md0 member=0
> > UUID=734f79cf:22200a5a:73be2b52:3388006b
> >
> > The error about IMSM shows up on google as something that happened to
> Fedora
> > users during a FC14->FC15 upgrade.
> >
> > The server itself isn't old, it's a Supermicro 2U with Dual Xeon 5400
> family
> > of CPU.  There are two RAIDs on this one controller...a RAID1 which still
> > functions and a RAID5 which is the one that is unable to be seen.  I
> don't
> > know what IMSM is for, but the only thing strange about that array is it
> is
> > 2.7TB so the BIOS configured it as two separate arrays, one as 2TB and
> one
> > as 700GB, but it was showing up to CentOS as a single volume.
> >
> > I downgraded to 3.2.1 , ran mdadm again and bam...it works,
> >
> > # mdadm --detail --scan
> > ARRAY /dev/md0 metadata=imsm UUID=734f79cf:22200a5a:73be2b52:3388006b
> > ARRAY /dev/md126 metadata=imsm UUID=3d135942:f0fad0b0:33255f78:29c3f50a
> > ARRAY /dev/md127 container=/dev/md0 member=0
> > UUID=691f975d:6beecfd8:67b39886:b7ee7f6e
> >
> > Hopefully this can be fixed before this version makes it to 6.1, though
> it's
> > likely a problem for upstream RHEL as well.
> >
> > - Trey
> > ___
> > CentOS mailing list
> > CentOS@centos.org
> > http://lists.centos.org/mailman/listinfo/centos
>
>
>
> Hmm I recall seeing something like this on an "sl6" box. I think it needed
> a "/etc/mdadm.conf" with som metadata id code.. I am pretty sure I fixed
> it with
>
> mdadm --detail --scan >> /etc/mdadm.conf
>
> and a reboot.
>
> Steve
> ___
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos
>

That's the problem, mdadm --detail --scan throws errors.  After updating to
mdadm-3.2.2 , and rebooting, the entry /dev/md126 was removed, likely
because when I run it and don't pipe the output, it shows this...

# mdadm --detail --scan
ARRAY /dev/md0 metadata=imsm UUID=734f79cf:22200a5a:73be2b52:3388006b
ARRAY /dev/md126 metadata=imsm UUID=3d135942:f0fad0b0:33255f78:29c3f50a
mdadm(IMSM): Unsupported attributes : 4000
mdadm: IMSM metadata loading not allowed due to attributes incompatibility.
mdadm(IMSM): Unsupported attributes : 4000
mdadm: IMSM metadata loading not allowed due to attributes incompatibility.
ARRAY /dev/md127 container=/dev/md0 member=0
UUID=734f79cf:22200a5a:73be2b52:3388006b
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] CentOS 6.0 CR mdadm-3.2.2 breaks Intel BIOS RAID

[Ljubomir Ljubojevic]

Vreme: 10/08/2011 09:14 PM, Trey Dockendorf piše:
> That's the problem, mdadm --detail --scan throws errors.  After updating to
> mdadm-3.2.2 , and rebooting, the entry /dev/md126 was removed, likely
> because when I run it and don't pipe the output, it shows this...

Have you tried "yum downgrade mdadm" ? and rebooting?
-- 

Ljubomir Ljubojevic
(Love is in the Air)
PL Computers
Serbia, Europe

Google is the Mother, Google is the Father, and traceroute is your
trusty Spiderman...
StarOS, Mikrotik and CentOS/RHEL/Linux consultant
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] CentOS-6.0 Continuous Release ( CR ) repository

[Craig White]

On Sat, 2011-10-08 at 15:30 +0100, Timothy Murphy wrote:
> n...@li.nux.ro wrote:
> 
> >> I don't really understand the function of this repository,
> >> or rather why the RPMs in it are not in the standard repository?
> 
> > Because there is no "standard repository" yet. These RPMs are from the
> > next version (6.1 as we write this) which has not been published yet. CR
> > is just a way to keep up with updates while they work on publishing Centos
> > 6.1.
> 
> I've read the various responses, and am not really convinced.
> It seems to me the developers are just making more work for themselves.
> Of course that is their prerogative ...

the various responses seemed to cloud the reasoning more than clarified
it and I guess it would be more reasonable to point you to the official
CentOS reasoning...

http://wiki.centos.org/AdditionalResources/Repositories/CR

Upstream has their 'fast track' and I gather that this mirrors (or at
least attempts to mirror) the upstream methods (with some good
reasoning).

Craig


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] CentOS 6.0 CR mdadm-3.2.2 breaks Intel BIOS RAID

[William Warren]

On 10/8/2011 3:14 PM, Trey Dockendorf wrote:
> On Sat, Oct 8, 2011 at 2:04 PM, Steve Brookswrote:
>
>> On Sat, 8 Oct 2011, Trey Dockendorf wrote:
>>
>>> I just upgraded my home KVM server to CentOS 6.0 CR to make use of the
>>> latest libvirt and now my RAID array with my VM storage is missing.  It
>>> seems that the upgrade to mdadm-3.2.2 is the culprit.
>>>
>>> This is the output from mdadm when scanning that array,
>>>
>>> # mdadm --detail --scan
>>> ARRAY /dev/md0 metadata=imsm UUID=734f79cf:22200a5a:73be2b52:3388006b
>>> ARRAY /dev/md126 metadata=imsm UUID=3d135942:f0fad0b0:33255f78:29c3f50a
>>> mdadm(IMSM): Unsupported attributes : 4000
>>> mdadm: IMSM metadata loading not allowed due to attributes
>> incompatibility.
>>> mdadm(IMSM): Unsupported attributes : 4000
>>> mdadm: IMSM metadata loading not allowed due to attributes
>> incompatibility.
>>> ARRAY /dev/md127 container=/dev/md0 member=0
>>> UUID=734f79cf:22200a5a:73be2b52:3388006b
>>>
>>> The error about IMSM shows up on google as something that happened to
>> Fedora
>>> users during a FC14->FC15 upgrade.
>>>
>>> The server itself isn't old, it's a Supermicro 2U with Dual Xeon 5400
>> family
>>> of CPU.  There are two RAIDs on this one controller...a RAID1 which still
>>> functions and a RAID5 which is the one that is unable to be seen.  I
>> don't
>>> know what IMSM is for, but the only thing strange about that array is it
>> is
>>> 2.7TB so the BIOS configured it as two separate arrays, one as 2TB and
>> one
>>> as 700GB, but it was showing up to CentOS as a single volume.
>>>
>>> I downgraded to 3.2.1 , ran mdadm again and bam...it works,
>>>
>>> # mdadm --detail --scan
>>> ARRAY /dev/md0 metadata=imsm UUID=734f79cf:22200a5a:73be2b52:3388006b
>>> ARRAY /dev/md126 metadata=imsm UUID=3d135942:f0fad0b0:33255f78:29c3f50a
>>> ARRAY /dev/md127 container=/dev/md0 member=0
>>> UUID=691f975d:6beecfd8:67b39886:b7ee7f6e
>>>
>>> Hopefully this can be fixed before this version makes it to 6.1, though
>> it's
>>> likely a problem for upstream RHEL as well.
>>>
>>> - Trey
>>> ___
>>> CentOS mailing list
>>> CentOS@centos.org
>>> http://lists.centos.org/mailman/listinfo/centos
>>
>>
>> Hmm I recall seeing something like this on an "sl6" box. I think it needed
>> a "/etc/mdadm.conf" with som metadata id code.. I am pretty sure I fixed
>> it with
>>
>> mdadm --detail --scan>>  /etc/mdadm.conf
>>
>> and a reboot.
>>
>> Steve
>> ___
>> CentOS mailing list
>> CentOS@centos.org
>> http://lists.centos.org/mailman/listinfo/centos
>>
> That's the problem, mdadm --detail --scan throws errors.  After updating to
> mdadm-3.2.2 , and rebooting, the entry /dev/md126 was removed, likely
> because when I run it and don't pipe the output, it shows this...
>
> # mdadm --detail --scan
> ARRAY /dev/md0 metadata=imsm UUID=734f79cf:22200a5a:73be2b52:3388006b
> ARRAY /dev/md126 metadata=imsm UUID=3d135942:f0fad0b0:33255f78:29c3f50a
> mdadm(IMSM): Unsupported attributes : 4000
> mdadm: IMSM metadata loading not allowed due to attributes incompatibility.
> mdadm(IMSM): Unsupported attributes : 4000
> mdadm: IMSM metadata loading not allowed due to attributes incompatibility.
> ARRAY /dev/md127 container=/dev/md0 member=0
> UUID=734f79cf:22200a5a:73be2b52:3388006b
> ___
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos
why bother with bios FAKERAID using PIO mode(effectively).  Make a 
backup and redo using MD raid and turn off the bios raid. Then things 
will work correctly.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] CentOS 6.0 CR mdadm-3.2.2 breaks Intel BIOS RAID

[Trey Dockendorf]

On Sat, Oct 8, 2011 at 4:31 PM, William Warren <
hescomins...@emmanuelcomputerconsulting.com> wrote:

> On 10/8/2011 3:14 PM, Trey Dockendorf wrote:
> > On Sat, Oct 8, 2011 at 2:04 PM, Steve Brooks >wrote:
> >
> >> On Sat, 8 Oct 2011, Trey Dockendorf wrote:
> >>
> >>> I just upgraded my home KVM server to CentOS 6.0 CR to make use of the
> >>> latest libvirt and now my RAID array with my VM storage is missing.  It
> >>> seems that the upgrade to mdadm-3.2.2 is the culprit.
> >>>
> >>> This is the output from mdadm when scanning that array,
> >>>
> >>> # mdadm --detail --scan
> >>> ARRAY /dev/md0 metadata=imsm UUID=734f79cf:22200a5a:73be2b52:3388006b
> >>> ARRAY /dev/md126 metadata=imsm UUID=3d135942:f0fad0b0:33255f78:29c3f50a
> >>> mdadm(IMSM): Unsupported attributes : 4000
> >>> mdadm: IMSM metadata loading not allowed due to attributes
> >> incompatibility.
> >>> mdadm(IMSM): Unsupported attributes : 4000
> >>> mdadm: IMSM metadata loading not allowed due to attributes
> >> incompatibility.
> >>> ARRAY /dev/md127 container=/dev/md0 member=0
> >>> UUID=734f79cf:22200a5a:73be2b52:3388006b
> >>>
> >>> The error about IMSM shows up on google as something that happened to
> >> Fedora
> >>> users during a FC14->FC15 upgrade.
> >>>
> >>> The server itself isn't old, it's a Supermicro 2U with Dual Xeon 5400
> >> family
> >>> of CPU.  There are two RAIDs on this one controller...a RAID1 which
> still
> >>> functions and a RAID5 which is the one that is unable to be seen.  I
> >> don't
> >>> know what IMSM is for, but the only thing strange about that array is
> it
> >> is
> >>> 2.7TB so the BIOS configured it as two separate arrays, one as 2TB and
> >> one
> >>> as 700GB, but it was showing up to CentOS as a single volume.
> >>>
> >>> I downgraded to 3.2.1 , ran mdadm again and bam...it works,
> >>>
> >>> # mdadm --detail --scan
> >>> ARRAY /dev/md0 metadata=imsm UUID=734f79cf:22200a5a:73be2b52:3388006b
> >>> ARRAY /dev/md126 metadata=imsm UUID=3d135942:f0fad0b0:33255f78:29c3f50a
> >>> ARRAY /dev/md127 container=/dev/md0 member=0
> >>> UUID=691f975d:6beecfd8:67b39886:b7ee7f6e
> >>>
> >>> Hopefully this can be fixed before this version makes it to 6.1, though
> >> it's
> >>> likely a problem for upstream RHEL as well.
> >>>
> >>> - Trey
> >>> ___
> >>> CentOS mailing list
> >>> CentOS@centos.org
> >>> http://lists.centos.org/mailman/listinfo/centos
> >>
> >>
> >> Hmm I recall seeing something like this on an "sl6" box. I think it
> needed
> >> a "/etc/mdadm.conf" with som metadata id code.. I am pretty sure I fixed
> >> it with
> >>
> >> mdadm --detail --scan>>  /etc/mdadm.conf
> >>
> >> and a reboot.
> >>
> >> Steve
> >> ___
> >> CentOS mailing list
> >> CentOS@centos.org
> >> http://lists.centos.org/mailman/listinfo/centos
> >>
> > That's the problem, mdadm --detail --scan throws errors.  After updating
> to
> > mdadm-3.2.2 , and rebooting, the entry /dev/md126 was removed, likely
> > because when I run it and don't pipe the output, it shows this...
> >
> > # mdadm --detail --scan
> > ARRAY /dev/md0 metadata=imsm UUID=734f79cf:22200a5a:73be2b52:3388006b
> > ARRAY /dev/md126 metadata=imsm UUID=3d135942:f0fad0b0:33255f78:29c3f50a
> > mdadm(IMSM): Unsupported attributes : 4000
> > mdadm: IMSM metadata loading not allowed due to attributes
> incompatibility.
> > mdadm(IMSM): Unsupported attributes : 4000
> > mdadm: IMSM metadata loading not allowed due to attributes
> incompatibility.
> > ARRAY /dev/md127 container=/dev/md0 member=0
> > UUID=734f79cf:22200a5a:73be2b52:3388006b
> > ___
> > CentOS mailing list
> > CentOS@centos.org
> > http://lists.centos.org/mailman/listinfo/centos
> why bother with bios FAKERAID using PIO mode(effectively).  Make a
> backup and redo using MD raid and turn off the bios raid. Then things
> will work correctly.
> ___
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos
>


I did the downgrade it it worked fine after.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] CentOS CVE "database"?

[Nate Duehr]

Appears it's back up, just as a follow-up.

On Oct 8, 2011, at 12:01 AM, Nate Duehr wrote:

> Was working on a project tonight to document CVE fixes applied to servers, 
> and noted that RedHat has completely jacked up their website.
> 
> In the past, I've usually just used their website for links to their CVE 
> list, as well as links to their Errata to look up specifics for CentOS 
> machines.
> 
> It sure looks like these links are either permanently gone from the public 
> pages to be hidden internally only available to Subscribers, or... 
> 
> RedHat's Marketing folks have completely destroyed what was once a valuable 
> information-filled website.
> 
> Either way... the question now becomes...
> 
> Is there something similar to RedHat's CVE listings by year and number hosted 
> by anyone in the CentOS community or by CentOS itself for CentOS?  I haven't 
> had much luck with my GoogleFu tonight.
> 
> Thanks, 
> Nate
> ___
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] CentOS 6.0 CR mdadm-3.2.2 breaks Intel BIOS RAID

[Ljubomir Ljubojevic]

Vreme: 10/09/2011 12:16 AM, Trey Dockendorf piše:
> On Sat, Oct 8, 2011 at 4:31 PM, William Warren<
> hescomins...@emmanuelcomputerconsulting.com>  wrote:

>> why bother with bios FAKERAID using PIO mode(effectively).  Make a
>> backup and redo using MD raid and turn off the bios raid. Then things
>> will work correctly.

> I did the downgrade it it worked fine after.

I just now realized that you have fakeraid (dmraid). That is very 
dangerous, because if MB dies, you might need to find another one with 
same chipset to make it work. On the other hand, Linux software RAID 
(mdadm). That way your RAID will work on any MB.

So I also recommend William Warren's suggestion to convert as soon as 
possible. You can even use "RAID 10 - far" to gain 2 x read and 1 x 
write speed of normal disk while mirroring.


-- 

Ljubomir Ljubojevic
(Love is in the Air)
PL Computers
Serbia, Europe

Google is the Mother, Google is the Father, and traceroute is your
trusty Spiderman...
StarOS, Mikrotik and CentOS/RHEL/Linux consultant
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] ganglia failing dependency

[Tim Dunphy]

hello list,

 I'm trying to install ganglia-gmetad on centos 5.6. rrdtool is already 
installed and librrd is there. But for some reason when I go to install this 
package it doesn't see that it is.
[root@VIRTCENT11:/usr/local/src/ganglia-3.2.0] #yum install ganglia-gmetad
Loaded plugins: fastestmirror, security
Loading mirror speeds from cached hostfile
 * base: mirrors.lga7.us.voxel.net
 * epel: serverbeach1.fedoraproject.org
 * extras: mirror.umoss.org
 * rpmforge: fr2.rpmfind.net
 * updates: mirror.atlanticmetro.net
Excluding Packages in global exclude list
Finished
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package ganglia-gmetad.i386 0:3.0.7-1.el5 set to be updated
--> Processing Dependency: librrd.so.2 for package: ganglia-gmetad
--> Finished Dependency Resolution
ganglia-gmetad-3.0.7-1.el5.i386 from epel has depsolving problems
  --> Missing Dependency: librrd.so.2 is needed by package 
ganglia-gmetad-3.0.7-1.el5.i386 (epel)
Error: Missing Dependency: librrd.so.2 is needed by package 
ganglia-gmetad-3.0.7-1.el5.i386 (epel)
 You could try using --skip-broken to work around the problem
 You could try running: package-cleanup --problems
package-cleanup --dupes
rpm -Va --nofiles --nodigest



But here are the required libraries:


[root@VIRTCENT11:/usr/local/src/ganglia-3.2.0] #locate librrd.so.2
/usr/lib/librrd.so.2
/usr/lib/librrd.so.2.0.13

Does anyone have any ideas on how to get past this point?

thanks!

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] ganglia failing dependency

[John R Pierce]

On 10/08/11 5:47 PM, Tim Dunphy wrote:
> [root@VIRTCENT11:/usr/local/src/ganglia-3.2.0] #locate librrd.so.2
> /usr/lib/librrd.so.2
> /usr/lib/librrd.so.2.0.13
>
> Does anyone have any ideas on how to get past this point?

it appears there are rrdtool's in both rpmforge and epel.  odds are, 
these aren't packaged in a compatible manner.  anyways, your ganglia 
stuff is from epel, so you probably should ask them.





-- 
john r pierceN 37, W 122
santa cruz ca mid-left coast

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] ganglia failing dependency

[Ljubomir Ljubojevic]

Vreme: 10/09/2011 02:56 AM, John R Pierce piše:
> On 10/08/11 5:47 PM, Tim Dunphy wrote:
>> [root@VIRTCENT11:/usr/local/src/ganglia-3.2.0] #locate librrd.so.2
>> /usr/lib/librrd.so.2
>> /usr/lib/librrd.so.2.0.13
>>
>> Does anyone have any ideas on how to get past this point?
>
> it appears there are rrdtool's in both rpmforge and epel.  odds are,
> these aren't packaged in a compatible manner.  anyways, your ganglia
> stuff is from epel, so you probably should ask them.
>
>
>
>
>

Tim, remove rrdtool (you installed it from repoforge/rpmforge) and rum 
install for ganglia-gmetad. rrdtool will be automaticaly installed:

[root@kancelarija yum.repos.d]# yum install ganglia-gmetad
Loaded plugins: downloadonly, fastestmirror, priorities, refresh-packagekit
Loading mirror speeds from cached hostfile
1032 packages excluded due to repository priority protections
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package ganglia-gmetad.x86_64 0:3.1.7-3.el6 will be installed
--> Processing Dependency: ganglia = 3.1.7-3.el6 for package: 
ganglia-gmetad-3.1.7-3.el6.x86_64
--> Processing Dependency: librrd.so.4()(64bit) for package: 
ganglia-gmetad-3.1.7-3.el6.x86_64
--> Processing Dependency: libganglia-3.1.7.so.0()(64bit) for package: 
ganglia-gmetad-3.1.7-3.el6.x86_64
--> Processing Dependency: libconfuse.so.0()(64bit) for package: 
ganglia-gmetad-3.1.7-3.el6.x86_64
--> Running transaction check
---> Package ganglia.x86_64 0:3.1.7-3.el6 will be installed
---> Package libconfuse.x86_64 0:2.6-3.el6 will be installed
---> Package rrdtool.x86_64 0:1.3.8-6.el6 will be installed
--> Processing Dependency: dejavu-lgc-sans-mono-fonts for package: 
rrdtool-1.3.8-6.el6.x86_64
--> Running transaction check
---> Package dejavu-lgc-sans-mono-fonts.noarch 0:2.30-2.el6 will be 
installed
--> Finished Dependency Resolution

Dependencies Resolved

==
  Package  Arch Version 
Repository  Size
==
Installing:
  ganglia-gmetad   x86_64   3.1.7-3.el6 
plc-epel34 k
Installing for dependencies:
  dejavu-lgc-sans-mono-fonts   noarch   2.30-2.el6plc-os 
 393 k
  ganglia  x86_64   3.1.7-3.el6 
plc-epel   150 k
  libconfuse   x86_64   2.6-3.el6 
plc-epel76 k
  rrdtool  x86_64   1.3.8-6.el6   plc-os 
 293 k

Transaction Summary
==
Install   5 Package(s)

Total download size: 945 k
Installed size: 3.1 M
Is this ok [y/N]:


Also, install yum-plugin-priorities and setup priorites for all repos. I 
would use priority=1 for all main repos, priority=2 for EPEL, and 
priority=3 for Repoforge, ...

-- 

Ljubomir Ljubojevic
(Love is in the Air)
PL Computers
Serbia, Europe

Google is the Mother, Google is the Father, and traceroute is your
trusty Spiderman...
StarOS, Mikrotik and CentOS/RHEL/Linux consultant
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] CentOS 6.0 CR mdadm-3.2.2 breaks Intel BIOS RAID

[Trey Dockendorf]

On Oct 8, 2011 7:23 PM, "Ljubomir Ljubojevic"  wrote:
>
> Vreme: 10/09/2011 12:16 AM, Trey Dockendorf piše:
> > On Sat, Oct 8, 2011 at 4:31 PM, William Warren<
> > hescomins...@emmanuelcomputerconsulting.com>  wrote:
>
> >> why bother with bios FAKERAID using PIO mode(effectively).  Make a
> >> backup and redo using MD raid and turn off the bios raid. Then things
> >> will work correctly.
>
> > I did the downgrade it it worked fine after.
>
> I just now realized that you have fakeraid (dmraid). That is very
> dangerous, because if MB dies, you might need to find another one with
> same chipset to make it work. On the other hand, Linux software RAID
> (mdadm). That way your RAID will work on any MB.
>
> So I also recommend William Warren's suggestion to convert as soon as
> possible. You can even use "RAID 10 - far" to gain 2 x read and 1 x
> write speed of normal disk while mirroring.
>
>
> --
>
> Ljubomir Ljubojevic
> (Love is in the Air)
> PL Computers
> Serbia, Europe
>
> Google is the Mother, Google is the Father, and traceroute is your
> trusty Spiderman...
> StarOS, Mikrotik and CentOS/RHEL/Linux consultant
> ___
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos

Can anyone confirm or advise how to do partionable raid with mdadm in Centos
6?  I made a few attempts using methods from centos 5 with no success.
Everytime I created md_d0 it did not contain any partions from the member
disks.

- Trey
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] CentOS 6.0 CR mdadm-3.2.2 breaks Intel BIOS RAID

[Lucian]

On Sun, Oct 9, 2011 at 5:21 AM, Trey Dockendorf  wrote:
> Can anyone confirm or advise how to do partionable raid with mdadm in Centos
> 6?  I made a few attempts using methods from centos 5 with no success.
> Everytime I created md_d0 it did not contain any partions from the member
> disks.

I can advise not to do that, it always looked like an ugly hack to me.
Just stick with the standard way. What I do is just create a small md
raid for /boot (this needs to be raid1) and make everything else one
big md raid with lvm on top. Works great for me and it's very flexible
due to lvm and ext4 (that means on the fly filesystem resize among
other things).
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos