Re: [CentOS] skype not starting anymore, prelink issue?

2013-02-01 Thread wwp
Hello Yves,


On Thu, 31 Jan 2013 22:31:42 -0500 Yves Bellefeuille  wrote:

> On Wednesday 30 January 2013, wwp  wrote:
> 
> > I was running skype 4.1.0.20 on my 64-bit laptop for weeks (installed
> > in /opt, from an official skype binary archive, plus few 32-bit stuff
> > to get it working), when suddenly it stopped working, no way to start
> > it:
> 
> How did you get Skype 4.1 to work on CentOS 6 x64_64?

This point has already been answered on this mailing list (and
elsewhere). A bit of search in the archives and elsewhere would quickly
bring you this:
  http://wiki.centos.org/HowTos/Skype

Because Skype is 32-bit, the idea is to install it from the official
binary archive, and use yum to install few 32-bit libraries (yes, this
means that some libraries will be in 32-bit and 64-bit on your system,
not a problem). Sound and video work like a charm, skype+msn support.


Regards,

-- 
wwp


signature.asc
Description: PGP signature
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] ACL/permissions question

2013-02-01 Thread Ian Forde
You could always try 'chattr +i /home/joe' to make it immutable.  Check out
the man page for details...
On Jan 31, 2013 11:44 PM, "Boris Epstein"  wrote:

> Hello listmates,
>
> If I have a regular, ACL-capable filesystem on Linux (say, ext4 or xfs) is
> there a way for me to establish the following:
>
> 1) There is a directory, say, /home/joe . It is owned by user joe . No one
> but joe (and root, of course) can read or write anything in this directory.
>
> 2) No one can change permissions on that directory, not even joe. In other
> words, in joe all of a sudden joe decided to open his directory up to the
> world (or the group he is a member of) by doing something akin to:
>
> chmod 777 /home/joe
>
> he would not succeed.
>
> Thanks in advance for any help.
>
> Boris.
> ___
> 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


[CentOS] Centos as l2tp/ipsec-Client

2013-02-01 Thread sebastian
Hello,

i need to configure a centos 6.3 - server as an l2tp/ipsec-client. I 
have no idea how I there previous or if this is even possible.
Where one might find appropriate instructions? Google is not very 
helpful, without any idea.

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


Re: [CentOS] CentOS 6.3: libreport/abrt update problem

2013-02-01 Thread Johnny Hughes
On 02/01/2013 01:33 AM, Akemi Yagi wrote:
> On Thu, Jan 31, 2013 at 10:52 PM, Mogens Kjaer  wrote:
>> Hello,
>>
>> In updates, there are new packages of abrt and libreport.
>>
>> But yum update gives me:
>>
>> Error: Package: abrt-2.0.8-6.el6.centos.2.x86_64 (updates)
>> Requires: libreport >= 2.0.9-5.el6_3.2
>> Removing: libreport-2.0.9-5.el6.centos.x86_64 (@base)
>> libreport = 2.0.9-5.el6.centos
>> Updated By: libreport-2.0.9-5.el6.centos.2.x86_64 (updates)
>> libreport = 2.0.9-5.el6.centos.2
>>   You could try using --skip-broken to work around the problem
>>   You could try running: rpm -Va --nofiles --nodigest
>>
>> Is the new libreport incorrectly named
>>
>> libreport-2.0.9-5.el6.centos.2.x86_64
>>
>> instead of:
>>
>> libreport-2.0.9-5.el6.2.x86_64
>>
>> or is the dependency of abrt incorrect?
>>
>> Mogens
>
> abrt does requires libreport >= 2.0.9-5.el6_3.2.
>
> Problem seems to be that 2.0.9-5.el6.centos.2 is older than 2.0.9-5.el6_3.2 .
>

I am working this issue right now, should be fixed in about an hour.



signature.asc
Description: OpenPGP digital signature
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] Centos as l2tp/ipsec-Client

2013-02-01 Thread John R Pierce
On 2/1/2013 1:55 AM, sebastian wrote:
> i need to configure a centos 6.3 - server as an l2tp/ipsec-client. I
> have no idea how I there previous or if this is even possible.
> Where one might find appropriate instructions? Google is not very
> helpful, without any idea.

whats the server?   there's no single standard for how VPN's like that 
authenticate and get setup, even given that they are using l2tp over 
ipsec.   ipsec itself is an unholy mess.I prefer SSL based VPNs like 
OpenVPN.

openswan is the generic l2tp/ipsec client (and server) in linux, million 
configuration options via complex scripts, you need to know EXACTLY what 
the server is expecting to authenticate and setup a session, and what 
you're routing over it.




-- 
john r pierce  37N 122W
somewhere on the middle of the left coast

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


Re: [CentOS] Centos as l2tp/ipsec-Client

2013-02-01 Thread Patrick Lists
On 02/01/2013 10:55 AM, sebastian wrote:
> Hello,
>
> i need to configure a centos 6.3 - server as an l2tp/ipsec-client. I
> have no idea how I there previous or if this is even possible.
> Where one might find appropriate instructions? Google is not very
> helpful, without any idea.

CentOS 6.3 comes with Openswan which allows you to setup IPsec 
connections. More info on the Openswan website: 
https://www.openswan.org/projects/openswan/

There is also Libreswan which is a recent fork of Openswan. Current 
release is 3.0 and it has a long list of fixes over the latest Openswan 
release (2.6.38) so might be interesting to look at too:
http://www.libreswan.org

For L2TP there is xl2tpd: https://github.com/xelerance/xl2tpd which iirc 
is available from the EPEL repo.

Regards,
Patrick

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


Re: [CentOS] CentOS 6.3: libreport/abrt update problem

2013-02-01 Thread odusseas
Luigi Rosa  writes:

> 
> 
> Mogens Kjaer said the following on 01/02/2013 07:52:
> 
> > In updates, there are new packages of abrt and libreport. But yum update
> > gives me: Error: Package: abrt-2.0.8-6.el6.centos.2.x86_64 (updates)
> 
> Confirmed. Same issue here.
> 
> Ciao,
> luigi
> 


The same problem also for me!!
any help??
Cheers

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


Re: [CentOS] Centos as l2tp/ipsec-Client

2013-02-01 Thread sebastian

Am 01.02.2013 11:47, schrieb John R Pierce:
> On 2/1/2013 1:55 AM, sebastian wrote:
>> i need to configure a centos 6.3 - server as an l2tp/ipsec-client. I
>> have no idea how I there previous or if this is even possible.
>> Where one might find appropriate instructions? Google is not very
>> helpful, without any idea.
> whats the server?   there's no single standard for how VPN's like that
> authenticate and get setup, even given that they are using l2tp over
> ipsec.   ipsec itself is an unholy mess.I prefer SSL based VPNs like
> OpenVPN.
>
> openswan is the generic l2tp/ipsec client (and server) in linux, million
> configuration options via complex scripts, you need to know EXACTLY what
> the server is expecting to authenticate and setup a session, and what
> you're routing over it.
>
I have create a l2tp-vpn server on centos 6.3 like this how-to:
http://www.maxwhale.com/how-to-install-l2tp-vpn-on-centos/

The vpn-connection works with an Mac-client and an Iphone too.

I thinks thats a very simple config and exactly is the right to begin. 
My problem is now the client-configuration for an centos 6.3 (no GUI) 
--- client setup. How it works? xl2tpd as client?
I have no solution approach
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] Centos as l2tp/ipsec-Client

2013-02-01 Thread sebastian

Am 01.02.2013 11:47, schrieb John R Pierce:
> On 2/1/2013 1:55 AM, sebastian wrote:
>> i need to configure a centos 6.3 - server as an l2tp/ipsec-client. I
>> have no idea how I there previous or if this is even possible.
>> Where one might find appropriate instructions? Google is not very
>> helpful, without any idea.
> whats the server?   there's no single standard for how VPN's like that
> authenticate and get setup, even given that they are using l2tp over
> ipsec.   ipsec itself is an unholy mess.I prefer SSL based VPNs like
> OpenVPN.
>
> openswan is the generic l2tp/ipsec client (and server) in linux, million
> configuration options via complex scripts, you need to know EXACTLY what
> the server is expecting to authenticate and setup a session, and what
> you're routing over it.
>
I have create a l2tp-vpn server on centos 6.3 like this how-to:
http://www.maxwhale.com/how-to-install-l2tp-vpn-on-centos/

The vpn-connection works with an Mac-client and an Iphone too.

I thinks thats a very simple config and exactly is the right to begin. 
My problem is now the client-configuration for another centos 6.3 server 
(no GUI) --- the vpn-client setup. How it works? xl2tpd as client? I 
have no solution approach

my goal is one l2tp-server with xl2tpd and one vpn-client on centos 6.3
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] CentOS 6.3: libreport/abrt update problem

2013-02-01 Thread Fabien Archambault
2013/2/1 odusseas :
> Luigi Rosa  writes:
>
>>
>>
>> Mogens Kjaer said the following on 01/02/2013 07:52:
>>
>> > In updates, there are new packages of abrt and libreport. But yum update
>> > gives me: Error: Package: abrt-2.0.8-6.el6.centos.2.x86_64 (updates)
>>
>> Confirmed. Same issue here.
>>
>> Ciao,
>> luigi
>>
>
>
> The same problem also for me!!
> any help??
> Cheers
>
> ___
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos

You can just skip, temporarily the update of abrt with:
yum update --exclude=abrt\*


This should leave only abrt not updated (not a huge issue) or just
wait a couple of days until it is fixed.

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


[CentOS] CentOS-announce Digest, Vol 96, Issue 1

2013-02-01 Thread centos-announce-request
Send CentOS-announce mailing list submissions to
centos-annou...@centos.org

To subscribe or unsubscribe via the World Wide Web, visit
http://lists.centos.org/mailman/listinfo/centos-announce
or, via email, send a message with subject or body 'help' to
centos-announce-requ...@centos.org

You can reach the person managing the list at
centos-announce-ow...@centos.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of CentOS-announce digest..."


Today's Topics:

   1. CEBA-2013:0212  CentOS 6 glibc Update (Johnny Hughes)
   2. CESA-2013:0216 Important CentOS 5 freetype Update (Johnny Hughes)
   3. CESA-2013:0214 Important CentOS 5 nss Update (Johnny Hughes)
   4. CEBA-2013:0212  CentOS 6 glibc Update (Johnny Hughes)
   5. CESA-2013:0213 Important CentOS 6 nspr Update (Johnny Hughes)
   6. CESA-2013:0217 Important CentOS 6 mingw32-libxml2 Update
  (Johnny Hughes)
   7. CESA-2013:0218 Moderate CentOS 6 xorg-x11-drv-qxl Update
  (Johnny Hughes)
   8. CESA-2013:0219 Moderate CentOS 6 mysql Update (Johnny Hughes)
   9. CESA-2013:0216 Important CentOS 6 freetype Update (Johnny Hughes)
  10. CESA-2013:0215 Important CentOS 6 libreport Update (Johnny Hughes)
  11. CESA-2013:0215 Important CentOS 6 abrt Update (Johnny Hughes)


--

Message: 1
Date: Thu, 31 Jan 2013 15:49:35 +
From: Johnny Hughes 
Subject: [CentOS-announce] CEBA-2013:0212  CentOS 6 glibc Update
To: centos-annou...@centos.org
Message-ID: <20130131154935.ga10...@chakra.karan.org>
Content-Type: text/plain; charset=us-ascii


CentOS Errata and Bugfix Advisory 2013:0212 

Upstream details at : https://rhn.redhat.com/errata/RHBA-2013-0212.html

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 

i386:
49895c07e6438541f8fcee9de7e61f917bb1059f5ecefa8797d7c3a45f7a0542  
glibc-2.12-1.80.el6_3.7.i686.rpm
9ac3511106793afc32bf4db7fb6005352cc0f34b618fd84581361923529925dd  
glibc-common-2.12-1.80.el6_3.7.i686.rpm
941a2c8311e2c39d209eb8f4738c220b57bd8a1929c1d6cc64586ab2407db7c3  
glibc-devel-2.12-1.80.el6_3.7.i686.rpm
b1afc555f1f6b2e59b55a762d753edfa339b2de1a148905c341f0390013df35c  
glibc-headers-2.12-1.80.el6_3.7.i686.rpm
ebf30b405afbd8b7a24fbeb23c9fdbaae551157a3bb3861311965184f9705683  
glibc-static-2.12-1.80.el6_3.7.i686.rpm
140ec7848bceabc8188a7fe6778f6facab9d6fa762cd042cb180016b45a67375  
glibc-utils-2.12-1.80.el6_3.7.i686.rpm
6dc9fa51750e1d36e0e75cda872bd42aa68ac5cf91874da69075a88eb5083512  
nscd-2.12-1.80.el6_3.7.i686.rpm

x86_64:
49895c07e6438541f8fcee9de7e61f917bb1059f5ecefa8797d7c3a45f7a0542  
glibc-2.12-1.80.el6_3.7.i686.rpm
4466b6bfda35951eec957e925debd47af2f2ee7fa5fe62fc8f9a96a08f9f12b5  
glibc-2.12-1.80.el6_3.7.x86_64.rpm
b4e89bc58a60659a885be0713eb99e2425c1a58e22d30d3f229f6de33440202e  
glibc-common-2.12-1.80.el6_3.7.x86_64.rpm
941a2c8311e2c39d209eb8f4738c220b57bd8a1929c1d6cc64586ab2407db7c3  
glibc-devel-2.12-1.80.el6_3.7.i686.rpm
2ebcd18ce2b7e05a57667b2b588d804c733e109ca25c748c5bdcecfa7502e121  
glibc-devel-2.12-1.80.el6_3.7.x86_64.rpm
74ee89ddb7df516f06fe18e8fed848090769ff2a74f8a1adcdd343e9851c6e0e  
glibc-headers-2.12-1.80.el6_3.7.x86_64.rpm
ebf30b405afbd8b7a24fbeb23c9fdbaae551157a3bb3861311965184f9705683  
glibc-static-2.12-1.80.el6_3.7.i686.rpm
f4febf76728c35459376fbd3622507f698805de1bf9b8649ba9b339c5e48d3a4  
glibc-static-2.12-1.80.el6_3.7.x86_64.rpm
4195f0e0b661341bb06bc05055a389d605859bfe3683ceb3a8034f6d154bdc47  
glibc-utils-2.12-1.80.el6_3.7.x86_64.rpm
e31d1ecfcfcca92106095e72ba1d535aa87f4d841d02576f32cedf6a71534a0a  
nscd-2.12-1.80.el6_3.7.x86_64.rpm

Source:
00a4acd908f62bef4b9b67942e1fc347a62aa19b9db0c7b677daa96160c217b7  
glibc-2.12-1.80.el6_3.7.src.rpm



-- 
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net



--

Message: 2
Date: Thu, 31 Jan 2013 21:55:44 +
From: Johnny Hughes 
Subject: [CentOS-announce] CESA-2013:0216 Important CentOS 5 freetype
Update
To: centos-annou...@centos.org
Message-ID: <20130131215544.ga31...@chakra.karan.org>
Content-Type: text/plain; charset=us-ascii


CentOS Errata and Security Advisory 2013:0216 Important

Upstream details at : https://rhn.redhat.com/errata/RHSA-2013-0216.html

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 

i386:
cacc70568addbfa074947de9177b38da49f5a45361640dd4360e45252650bb81  
freetype-2.2.1-32.el5_9.1.i386.rpm
0406d616a5c8fc7fccd343d6226a52fde050c8ae7a5ccc71a42eddece6621028  
freetype-demos-2.2.1-32.el5_9.1.i386.rpm
ca10d7bc4e1dc5dceac26529add39f6ca1660b086d6fd81b475185ed7a6ac3a1  
freetype-devel-2.2.1-32.el5_9.1.i386.rpm

x86_64:
cacc70568addbfa074947de9177b38da49f5a45361640dd4360e45252650bb81  
freetype-2.2.1-32.el5_9.1.i386.rpm
1fffcbb350ebb38bfcaa5a18cfc2ea6bbe42461d11cf0c642e88032f292651f0  
freetype-2.2.1-32.el5_9.1

[CentOS] Network stopped just out of the blue leaving this backtrace:

2013-02-01 Thread Eliezer Croitoru
Network stopped just out of the blue leaving this backtrace
After this or during this my network switch just stopped working ang got
stuck.
Maybe the switch made the problem?

Thanks,
Eliezer

Feb  1 04:07:15 localhost kernel: [ cut here ]
Feb  1 04:07:15 localhost kernel: WARNING: at
net/sched/sch_generic.c:261 dev_watchdog+0x26d/0x280() (Not tainted)
Feb  1 04:07:15 localhost kernel: Hardware name:
Feb  1 04:07:15 localhost kernel: NETDEV WATCHDOG: eth0 (r8169):
transmit queue 0 timed out
Feb  1 04:07:15 localhost kernel: Modules linked in: tcp_diag inet_diag
bluetooth rfkill bnx2fc fcoe libfcoe libfc 8021q scsi_transport_fc garp
scsi_tgt stp llc sunrpc xt_recent xt_state xt_multiport iptable_filter
ipt_REDIRECT ipt_MASQUERADE iptable_nat nf_nat nf_conntrack_ipv4
iptable_raw xt_MARK xt_socket nf_conntrack nf_defrag_ipv4 ip6_tables
nf_defrag_ipv6 iptable_mangle ip_tables ext2 ppdev parport_pc parport
serio_raw sg i2c_i801 snd_hda_codec_realtek snd_hda_intel snd_hda_codec
snd_hwdep snd_seq snd_seq_device snd_pcm snd_timer snd soundcore
snd_page_alloc ext3 jbd mbcache sd_mod crc_t10dif pata_acpi ata_generic
ata_piix r8169 mii i915 drm_kms_helper drm i2c_algo_bit i2c_core video
output dm_mirror dm_region_hash dm_log dm_mod be2iscsi bnx2i cnic uio
ipv6 cxgb4i cxgb4 cxgb3i libcxgbi cxgb3 mdio libiscsi_tcp qla4xxx
iscsi_boot_sysfs libiscsi scsi_transport_iscsi [last unloaded:
scsi_wait_scan]
Feb  1 04:07:15 localhost kernel: Pid: 0, comm: swapper Not tainted
2.6.32-279.19.1.el6.centos.plus.x86_64 #1
Feb  1 04:07:15 localhost kernel: Call Trace:
Feb  1 04:07:15 localhost kernel:   [] ?
warn_slowpath_common+0x87/0xc0
Feb  1 04:07:15 localhost kernel: [] ?
intel_pmu_enable_all+0xba/0x160
Feb  1 04:07:15 localhost kernel: [] ?
warn_slowpath_fmt+0x46/0x50
Feb  1 04:07:15 localhost kernel: [] ?
dev_watchdog+0x26d/0x280
Feb  1 04:07:15 localhost kernel: [] ?
internal_add_timer+0x9b/0x110
Feb  1 04:07:15 localhost kernel: [] ?
dev_watchdog+0x0/0x280
Feb  1 04:07:15 localhost kernel: [] ?
run_timer_softirq+0x197/0x340
Feb  1 04:07:15 localhost kernel: [] ?
tick_sched_timer+0x0/0xc0
Feb  1 04:07:15 localhost kernel: [] ?
lapic_next_event+0x1d/0x30
Feb  1 04:07:15 localhost kernel: [] ?
__do_softirq+0xc1/0x1e0
Feb  1 04:07:15 localhost kernel: [] ?
hrtimer_interrupt+0x140/0x250
Feb  1 04:07:15 localhost kernel: [] ?
call_softirq+0x1c/0x30
Feb  1 04:07:15 localhost kernel: [] ?
do_softirq+0x65/0xa0
Feb  1 04:07:15 localhost kernel: [] ? irq_exit+0x85/0x90
Feb  1 04:07:15 localhost kernel: [] ?
smp_apic_timer_interrupt+0x70/0x9b
Feb  1 04:07:15 localhost kernel: [] ?
apic_timer_interrupt+0x13/0x20
Feb  1 04:07:15 localhost kernel:   [] ?
intel_idle+0xde/0x170
Feb  1 04:07:15 localhost kernel: [] ?
intel_idle+0xc1/0x170
Feb  1 04:07:15 localhost kernel: [] ?
cpuidle_idle_call+0xa7/0x140
Feb  1 04:07:15 localhost kernel: [] ? cpu_idle+0xb6/0x110
Feb  1 04:07:15 localhost kernel: [] ? rest_init+0x7a/0x80
Feb  1 04:07:15 localhost kernel: [] ?
start_kernel+0x424/0x430
Feb  1 04:07:15 localhost kernel: [] ?
x86_64_start_reservations+0x125/0x129
Feb  1 04:07:15 localhost kernel: [] ?
x86_64_start_kernel+0xfa/0x109
Feb  1 04:07:15 localhost kernel: ---[ end trace 0bd7c853b258ec62 ]---
Feb  1 04:07:15 localhost kernel: r8169 :01:00.0: eth0: link up

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


[CentOS] Dell unofficial community repository - what do you think?

2013-02-01 Thread Rafał Radecki
Hi all.

I am currently gathering information about firmware update on Dell
PowerEdge machines.
I've found
http://linux.dell.com/wiki/index.php/Firmware-tools_announcement
and
https://linux.dell.com/repo/community/
It is an unofficial, community supported repository.

What are your experiences: should I perform firmware updates the
traditional way by downloading *.bin packages from Dell and run them
manually or should I use this repo? Is this repo "safe" and releases
stable packages?

Best regards,
Rafal Radecki.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] skype not starting anymore, prelink issue?

2013-02-01 Thread Yves Bellefeuille
On Friday 01 February 2013, wwp  wrote:

> This point has already been answered on this mailing list (and
> elsewhere). A bit of search in the archives and elsewhere would
> quickly bring you this:
> http://wiki.centos.org/HowTos/Skype

I'm very familiar with that document. :-) And many users, including 
myself, couldn't get Skype 4.1 to work on CentOS 64 bits using those 
instructions.

If Skype 4.1 did work on your 64-bit system, I'm very interested in 
knowing the details; you can contact me directly if you wish.

(Skype 4.0 does work; in your initial post, you said that 4.1.0.20 used 
to work on your system, but no longer does.)

Yves

-- 
Yves Bellefeuille 
"Simply put, E=mc^2 is liberal claptrap." -- Conservapedia.com

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


Re: [CentOS] Dell unofficial community repository - what do you think?

2013-02-01 Thread lhecking
 
> What are your experiences: should I perform firmware updates the
> traditional way by downloading *.bin packages from Dell and run them
> manually or should I use this repo? Is this repo "safe" and releases
> stable packages?
 
 This is a good resource: 
https://lists.us.dell.com/mailman/listinfo/linux-poweredge.

 Personally, I prefer the repo over both .bin packages and Lifecycle controller
 updates. However, there are sometimes problems with the repo, in particular
 after new releases. The mailing list is the canonical place for reporting,
 and it is monitored by Dell employees.

 The best possible scenario is a local mirror of the repository, but I haven't
 yet figured out how to configure machines to use it; not sure whether yum or
 httpd config is the problem.

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


Re: [CentOS] Dell unofficial community repository - what do you think?

2013-02-01 Thread Mikael Fridh
On Fri, Feb 1, 2013 at 1:57 PM, Rafał Radecki  wrote:
> Hi all.
>
> I am currently gathering information about firmware update on Dell
> PowerEdge machines.
> I've found
> http://linux.dell.com/wiki/index.php/Firmware-tools_announcement
> and
> https://linux.dell.com/repo/community/
> It is an unofficial, community supported repository.

Depending on your hardware you will have support here:
http://linux.dell.com/repo/hardware
http://linux.dell.com/wiki/index.php/Repository/hardware

I create a local mirror via rsync and use for all the Dell servers.

> What are your experiences: should I perform firmware updates the
> traditional way by downloading *.bin packages from Dell and run them
> manually or should I use this repo? Is this repo "safe" and releases
> stable packages?

I'm usually fine with the hardware repo above unless I need something
really new (some versions that's not yet released in the firmware repo
as rpms).

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


Re: [CentOS] skype not starting anymore, prelink issue?

2013-02-01 Thread wwp
Hello Yves,


On Fri, 1 Feb 2013 08:08:20 -0500 Yves Bellefeuille  wrote:

> On Friday 01 February 2013, wwp  wrote:
> 
> > This point has already been answered on this mailing list (and
> > elsewhere). A bit of search in the archives and elsewhere would
> > quickly bring you this:
> > http://wiki.centos.org/HowTos/Skype
> 
> I'm very familiar with that document. :-) And many users, including 
> myself, couldn't get Skype 4.1 to work on CentOS 64 bits using those 
> instructions.
> 
> If Skype 4.1 did work on your 64-bit system, I'm very interested in 
> knowing the details; you can contact me directly if you wish.
> 
> (Skype 4.0 does work; in your initial post, you said that 4.1.0.20 used 
> to work on your system, but no longer does.)

Yep, well I think I also followed a blog post somewhere on the
internet, which was more detailed. Anyway nothing was different from
using ldd to know what 32-bit deps the skype binary has and install the
appropriate lib. I didn't do any magic or setup in the system config
files. That simply worked by installing 32-bit stuff.


Regards,

-- 
wwp


signature.asc
Description: PGP signature
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


[CentOS] OT: Antwort: Re: Dell unofficial community repository - what do you think?

2013-02-01 Thread Andreas Reschke
centos-boun...@centos.org wrote on 01.02.2013 14:27:19:

> Mikael Fridh  
> Gesendet von: centos-boun...@centos.org
> 
> 01.02.2013 14:27
> 
> Bitte antworten an
> CentOS mailing list 
> 
> An
> 
> CentOS mailing list 
> 
> Kopie
> 
> Thema
> 
> Re: [CentOS] Dell unofficial community repository - what do you think?
> 
> On Fri, Feb 1, 2013 at 1:57 PM, Rafał Radecki  
wrote:
> > Hi all.
> >
> > I am currently gathering information about firmware update on Dell
> > PowerEdge machines.
> > I've found
> > http://linux.dell.com/wiki/index.php/Firmware-tools_announcement
> > and
> > https://linux.dell.com/repo/community/
> > It is an unofficial, community supported repository.
> 
> Depending on your hardware you will have support here:
> http://linux.dell.com/repo/hardware
> http://linux.dell.com/wiki/index.php/Repository/hardware
> 
> I create a local mirror via rsync and use for all the Dell servers.
> 
> > What are your experiences: should I perform firmware updates the
> > traditional way by downloading *.bin packages from Dell and run them
> > manually or should I use this repo? Is this repo "safe" and releases
> > stable packages?
> 
> I'm usually fine with the hardware repo above unless I need something
> really new (some versions that's not yet released in the firmware repo
> as rpms).
> 
> --
> Mikael
> ___
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos

Does anybody know if there is the same repo from HP?
 
 
Mit freundlichen Grüßen
Andreas Reschke


Unix/Linux-Administration
andreas.resc...@behrgroup.com
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] OT: Antwort: Re: Dell unofficial community repository - what do you think?

2013-02-01 Thread Phil Gardner
They provide an official repo for the proliant support pack (PSP), but I
don't think they offer firmware updates via yum. I honestly haven't
needed it, unlike Dell, whose support techs insist that I update
firmware as the first step to troubleshooting a failed hard drive or bad
memory modules...

http://downloads.linux.hp.com/SDR/downloads/ServicePackforProLiant/rhel/6/x86_64/current/

repoview -
http://downloads.linux.hp.com/SDR/downloads/ServicePackforProLiant/rhel/6/x86_64/current/repoview/

On 02/01/2013 08:31 AM, Andreas Reschke wrote:
> centos-boun...@centos.org wrote on 01.02.2013 14:27:19:
> 
>> Mikael Fridh  
>> Gesendet von: centos-boun...@centos.org
>>
>> 01.02.2013 14:27
>>
>> Bitte antworten an
>> CentOS mailing list 
>>
>> An
>>
>> CentOS mailing list 
>>
>> Kopie
>>
>> Thema
>>
>> Re: [CentOS] Dell unofficial community repository - what do you think?
>>
>> On Fri, Feb 1, 2013 at 1:57 PM, Rafał Radecki  
> wrote:
>>> Hi all.
>>>
>>> I am currently gathering information about firmware update on Dell
>>> PowerEdge machines.
>>> I've found
>>> http://linux.dell.com/wiki/index.php/Firmware-tools_announcement
>>> and
>>> https://linux.dell.com/repo/community/
>>> It is an unofficial, community supported repository.
>>
>> Depending on your hardware you will have support here:
>> http://linux.dell.com/repo/hardware
>> http://linux.dell.com/wiki/index.php/Repository/hardware
>>
>> I create a local mirror via rsync and use for all the Dell servers.
>>
>>> What are your experiences: should I perform firmware updates the
>>> traditional way by downloading *.bin packages from Dell and run them
>>> manually or should I use this repo? Is this repo "safe" and releases
>>> stable packages?
>>
>> I'm usually fine with the hardware repo above unless I need something
>> really new (some versions that's not yet released in the firmware repo
>> as rpms).
>>
>> --
>> Mikael
>> ___
>> CentOS mailing list
>> CentOS@centos.org
>> http://lists.centos.org/mailman/listinfo/centos
> 
> Does anybody know if there is the same repo from HP?
>  
>  
> Mit freundlichen Grüßen
> Andreas Reschke
> 
> 
> Unix/Linux-Administration
> andreas.resc...@behrgroup.com
> ___
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos
> 

-- 
_
Phil Gardner
PGP Key ID 0xFECC890C
OTR Fingerprint 6707E9B8 BD6062D3 5010FE8B 36D614E3 D2F80538


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


Re: [CentOS] Dell unofficial community repository - what do you think?

2013-02-01 Thread Phil Gardner
This is correct, the latest firmware updates take a little bit to get
packaged and tested before they get pushed to the repo.

I also haven't figured out how to only update firmware for specific
devices. With the inventory_firmware and update_firmware commands, it
looks for updates and applies all updates at once.

As for creating a local mirror, a simple rsync grabs it (I exclude
everything I don't need)

rsync --progress  --delete -avHz  --exclude=rh30 --exclude=rh30_64
--exclude=rh40 --exclude=rh40_64 --exclude='SLES_*' --exclude='SLE_*'
--exclude='suse*' --exclude='sles*'
linux.dell.com::repo/hardware/OMSA_7.1/
/yumrepo/repos/dell/hardware/OMSA_7.1/

I also don't use the community repo...I haven't found anything I need in
there.

I'll attach the yum repo file I use for my local repo. A 'yum install
srvadmin-all dell_ft_install' will grab what you need for firmware tools
and OpenManage, and then a 'yum install $(bootstrap_firmware)' will grab
all your hardware specific firmware.



On 02/01/2013 08:27 AM, Mikael Fridh wrote:
> On Fri, Feb 1, 2013 at 1:57 PM, Rafał Radecki  wrote:
>> Hi all.
>>
>> I am currently gathering information about firmware update on Dell
>> PowerEdge machines.
>> I've found
>> http://linux.dell.com/wiki/index.php/Firmware-tools_announcement
>> and
>> https://linux.dell.com/repo/community/
>> It is an unofficial, community supported repository.
> 
> Depending on your hardware you will have support here:
> http://linux.dell.com/repo/hardware
> http://linux.dell.com/wiki/index.php/Repository/hardware
> 
> I create a local mirror via rsync and use for all the Dell servers.
> 
>> What are your experiences: should I perform firmware updates the
>> traditional way by downloading *.bin packages from Dell and run them
>> manually or should I use this repo? Is this repo "safe" and releases
>> stable packages?
> 
> I'm usually fine with the hardware repo above unless I need something
> really new (some versions that's not yet released in the firmware repo
> as rpms).
> 
> --
> Mikael
> ___
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos
> 

-- 
_
Phil Gardner
PGP Key ID 0xFECC890C
OTR Fingerprint 6707E9B8 BD6062D3 5010FE8B 36D614E3 D2F80538


[dell-omsa-indep]
name=Dell OMSA repository - Hardware independent
type=rpm-md
mirrorlist=http://localrepo/repos/dell/hardware/latest/mirrors.cgi?osname=el$releasever&basearch=$basearch&native=1&dellsysidpluginver=$dellsysidpluginver
gpgcheck=1
gpgkey=http://localrepo/repos/dell/hardware/latest/RPM-GPG-KEY-dell
http://localrepo/repos/dell/hardware/latest/RPM-GPG-KEY-libsmbios
enabled=1
failover=priority
bootstrapurl=http://localrepo/repos/dell/hardware/latest/bootstrap.cgi


[dell-omsa-specific]
name=Dell OMSA repository - Hardware specific
type=rpm-md
mirrorlist=http://localrepo/repos/dell/hardware/latest/mirrors.cgi?osname=el$releasever&basearch=$basearch&native=1&sys_ven_id=$sys_ven_id&sys_dev_id=$sys_dev_id&dellsysidpluginver=$dellsysidpluginver
gpgcheck=1
gpgkey=http://localrepo/repos/dell/hardware/latest/RPM-GPG-KEY-dell
http://localrepo/repos/dell/hardware/latest/RPM-GPG-KEY-libsmbios
enabled=1
failover=priority
bootstrapurl=http://localrepo/repos/dell/hardware/latest/bootstrap.cgi
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] Dell unofficial community repository - what do you think?

2013-02-01 Thread lhecking

> I also haven't figured out how to only update firmware for specific
> devices. With the inventory_firmware and update_firmware commands, it
> looks for updates and applies all updates at once.
 
 inventory_firmware_gui lets you select. I'm not aware of how to achieve
 this with command line only.

> As for creating a local mirror, a simple rsync grabs it (I exclude
> everything I don't need)
 
 Yes, I have something pretty similar :)

> I'll attach the yum repo file I use for my local repo. A 'yum install
> srvadmin-all dell_ft_install' will grab what you need for firmware tools
> and OpenManage, and then a 'yum install $(bootstrap_firmware)' will grab
> all your hardware specific firmware.
 
 Thanks, I'll compare it with my own to see what's wrong.

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


[CentOS] error during yum update 6.3

2013-02-01 Thread Steve Clark
Hello,

Anybody else running into this. I am seeing it on two different
CentOS boxes I have.

yum --disablerepo=* --enablerepo=base,updates update
...
---> Package abrt.i686 0:2.0.8-6.el6.centos will be updated
---> Package abrt.i686 0:2.0.8-6.el6.centos.2 will be an update
--> Processing Dependency: libreport >= 2.0.9-5.el6_3.2 for package: 
abrt-2.0.8-6.el6.centos.2.i686
...
---> Package libreport.i686 0:2.0.9-5.el6.centos will be updated
---> Package libreport.i686 0:2.0.9-5.el6.centos.2 will be an update
...

Error: Package: abrt-2.0.8-6.el6.centos.2.i686 (updates)
Requires: libreport >= 2.0.9-5.el6_3.2
Removing: libreport-2.0.9-5.el6.centos.i686 (@base)
libreport = 2.0.9-5.el6.centos
Updated By: libreport-2.0.9-5.el6.centos.2.i686 (updates)
libreport = 2.0.9-5.el6.centos.2

-- 
Stephen Clark
*NetWolves*
Director of Technology
Phone: 813-579-3200
Fax: 813-882-0209
Email: steve.cl...@netwolves.com
http://www.netwolves.com
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] error during yum update 6.3

2013-02-01 Thread Phil Savoie
Yep, me too,

Yum remove abrt then carry on.  I imagine this will get fixed later.

Phil

On 02/01/2013 09:37 AM, Steve Clark wrote:
> Hello,
>
> Anybody else running into this. I am seeing it on two different
> CentOS boxes I have.
>
> yum --disablerepo=* --enablerepo=base,updates update
> ...
> --->  Package abrt.i686 0:2.0.8-6.el6.centos will be updated
> --->  Package abrt.i686 0:2.0.8-6.el6.centos.2 will be an update
> -->  Processing Dependency: libreport>= 2.0.9-5.el6_3.2 for package: 
> abrt-2.0.8-6.el6.centos.2.i686
> ...
> --->  Package libreport.i686 0:2.0.9-5.el6.centos will be updated
> --->  Package libreport.i686 0:2.0.9-5.el6.centos.2 will be an update
> ...
>
> Error: Package: abrt-2.0.8-6.el6.centos.2.i686 (updates)
>  Requires: libreport>= 2.0.9-5.el6_3.2
>  Removing: libreport-2.0.9-5.el6.centos.i686 (@base)
>  libreport = 2.0.9-5.el6.centos
>  Updated By: libreport-2.0.9-5.el6.centos.2.i686 (updates)
>  libreport = 2.0.9-5.el6.centos.2
>
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] Centos 6.3 - which repos to use?

2013-02-01 Thread Timothy Murphy
Les Mikesell wrote:

> Using any single 3rd party repo is likely to work at least until the
> next update because the contents will have been tested against the
> base distro - as long as the packages are intended for use with
> RHEL/Centos.

I have a slightly different question.
I had kbsingh-CentOS-Extras.repo enabled until recently.
Is disabling a repo that has been in use likely to cause any problems?


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


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


[CentOS] Opening a jar file from the desktop

2013-02-01 Thread James B. Byrne
I have java-1.7.0-openjdk installed on a CentOS-6.3 x86_64 system.  On
my desktop I have a jar file containing a calculator program which
runs fine on CentOS-5 and on MS-Windows machines.

On the CentOS-6 system when I right-click on the jar file and say open
with java nothing apparently happens.  When I double-click on it then
I see a file browser window offering to extract the contents but there
are no contents visible, only an empty / directory.  If I go to the
desktop in a terminal session and type java superbcalc.jar then I see
this message:  "Could not find or load main class superbcalc.jar"

There is no CLASSPATH environment variable set by the system.  If I
provide one and include the current directory '.' I get the same
error.

CLASSPATH=. java superbcalc.jar
Error: Could not find or load main class superbcalc.jar

What has changed in CentOS-6 to stop this from working and how do I
get jar files to open and run using Java both from the command line
and from the desktop?



-- 
***  E-Mail is NOT a SECURE channel  ***
James B. Byrnemailto:byrn...@harte-lyne.ca
Harte & Lyne Limited  http://www.harte-lyne.ca
9 Brockley Drive  vox: +1 905 561 1241
Hamilton, Ontario fax: +1 905 561 0757
Canada  L8E 3C3

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


Re: [CentOS] Centos 6.3 - which repos to use?

2013-02-01 Thread Les Mikesell
On Fri, Feb 1, 2013 at 9:38 AM, Timothy Murphy  wrote:
> Les Mikesell wrote:
>
>> Using any single 3rd party repo is likely to work at least until the
>> next update because the contents will have been tested against the
>> base distro - as long as the packages are intended for use with
>> RHEL/Centos.
>
> I have a slightly different question.
> I had kbsingh-CentOS-Extras.repo enabled until recently.
> Is disabling a repo that has been in use likely to cause any problems?

Generally not.  It just means that you won't get any updates on
packages that only exist in that repo.  However there is some chance
that a same-named package will appear with a higher version number in
a different, enabled repo - and if it doesn't have the same origin
there is some chance of it being incompatible in some way.   This is
more likely to result in a single broken app than yum conflicts,
though.

-- 
   Les Mikesell
  lesmikes...@gmail.com
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] OT: Antwort: Re: Dell unofficial community repository - what do you think?

2013-02-01 Thread John Doe
From: Andreas Reschke 
> Does anybody know if there is the same repo from HP?

http://downloads.linux.hp.com/SDR/index.html

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


Re: [CentOS] error during yum update 6.3

2013-02-01 Thread Akemi Yagi
On Fri, Feb 1, 2013 at 6:37 AM, Steve Clark  wrote:
> Hello,
>
> Anybody else running into this. I am seeing it on two different
> CentOS boxes I have.
>
> yum --disablerepo=* --enablerepo=base,updates update
> ...
> ---> Package abrt.i686 0:2.0.8-6.el6.centos will be updated
> ---> Package abrt.i686 0:2.0.8-6.el6.centos.2 will be an update
> --> Processing Dependency: libreport >= 2.0.9-5.el6_3.2 for package: 
> abrt-2.0.8-6.el6.centos.2.i686
> ...
> ---> Package libreport.i686 0:2.0.9-5.el6.centos will be updated
> ---> Package libreport.i686 0:2.0.9-5.el6.centos.2 will be an update
> ...
>
> Error: Package: abrt-2.0.8-6.el6.centos.2.i686 (updates)
> Requires: libreport >= 2.0.9-5.el6_3.2
> Removing: libreport-2.0.9-5.el6.centos.i686 (@base)
> libreport = 2.0.9-5.el6.centos
> Updated By: libreport-2.0.9-5.el6.centos.2.i686 (updates)
> libreport = 2.0.9-5.el6.centos.2


Please follow this thread:

http://lists.centos.org/pipermail/centos/2013-February/131818.html

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


Re: [CentOS] Opening a jar file from the desktop

2013-02-01 Thread Frank Cox
On Fri, 1 Feb 2013 10:42:23 -0500
James B. Byrne wrote:

> how do I
> get jar files to open and run using Java both from the command line
> and from the desktop?

Create a small script or a launcher (right-click on desktop, Create Launcher)
containing the following: java -jar nameofjar.jar

-- 
MELVILLE THEATRE ~ Real D 3D Digital Cinema ~ www.melvilletheatre.com
www.creekfm.com - FIFTY THOUSAND WATTS of POW WOW POWER!
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] Opening a jar file from the desktop

2013-02-01 Thread James B. Byrne

On Fri, February 1, 2013 10:59, Reindl Harald wrote:

> java -jar superbcalc.jar

Thank you.
-- 
***  E-Mail is NOT a SECURE channel  ***
James B. Byrnemailto:byrn...@harte-lyne.ca
Harte & Lyne Limited  http://www.harte-lyne.ca
9 Brockley Drive  vox: +1 905 561 1241
Hamilton, Ontario fax: +1 905 561 0757
Canada  L8E 3C3

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


Re: [CentOS] How to extract one file from rpm using yum?

2013-02-01 Thread Ali Corbin
> >> The command line way of getting 1 file out of a rpm is to rpm2cpio.
> >>
> >>  rpm2cpio  > 
> >>
> >> Now you have a cpio archive which you can use to get files out of.
> > Or:
> >
> > rpm2cpio  | cpio -idv
> >

And one more:

To extract a single file from a package

 rpm2cpio gnupg-1.2.6-6.src.rpm | cpio -ivd gnupg.spec
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] How to extract one file from rpm using yum?

2013-02-01 Thread Todd Rinaldo

On Feb 1, 2013, at 11:56 AM, Ali Corbin  wrote:

 The command line way of getting 1 file out of a rpm is to rpm2cpio.
 
 rpm2cpio  > 
 
 Now you have a cpio archive which you can use to get files out of.
>>> Or:
>>> 
>>> rpm2cpio  | cpio -idv
>>> 
> 
> And one more:
> 
> To extract a single file from a package
> 
> rpm2cpio gnupg-1.2.6-6.src.rpm | cpio -ivd gnupg.spec

I know it's petty, but every time I realize I need to use cpio to do this, it 
really annoys me. This is the only present day use of cpio I'm aware of.

Todd

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


Re: [CentOS] CentOS 6.3: libreport/abrt update problem

2013-02-01 Thread Luigi Rosa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Johnny Hughes said the following on 01/02/2013 11:29:

> I am working this issue right now, should be fixed in about an hour.

It is, thanks.




Ciao,
luigi

- -- 
/
+--[Luigi Rosa]--
\

Mathematicians do it in theory.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with undefined - http://www.enigmail.net/

iEYEARECAAYFAlEMDG8ACgkQ3kWu7Tfl6ZSoqgCeK2cH4HhnQblsLfSsAMLxy8BM
uuYAoLHRVVAktPZcEr7l2Z/Si13WCcAm
=l4Ru
-END PGP SIGNATURE-
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] CentOS 6.3: libreport/abrt update problem

2013-02-01 Thread Johnny Hughes
On 02/01/2013 05:41 AM, Fabien Archambault wrote:
> 2013/2/1 odusseas :
>> Luigi Rosa  writes:
>>
>>>
>>> Mogens Kjaer said the following on 01/02/2013 07:52:
>>>
 In updates, there are new packages of abrt and libreport. But yum update
 gives me: Error: Package: abrt-2.0.8-6.el6.centos.2.x86_64 (updates)
>>> Confirmed. Same issue here.
>>>
>>> Ciao,
>>> luigi
>>>
>>
>> The same problem also for me!!
>> any help??
>> Cheers
>>
>> ___
>> CentOS mailing list
>> CentOS@centos.org
>> http://lists.centos.org/mailman/listinfo/centos
> You can just skip, temporarily the update of abrt with:
> yum update --exclude=abrt\*
>
>
> This should leave only abrt not updated (not a huge issue) or just
> wait a couple of days until it is fixed.

For the record, the fix is pushed, however some of our external mirrors
only sync a couple of times per day .. so it may take a day for them to
get fixed.

If you absolutely need that package updated, you can point the updates
repo to mirror.centos.org and "yum clean all" then "yum update".



signature.asc
Description: OpenPGP digital signature
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


[CentOS] weird issue with qemu-kvm network...

2013-02-01 Thread skull
Hello CentOS mailinglist
I am running CentOS 6.3 with qemu-kvm and libvirt.
I was experimenting with bridged VM networking. Usually the VMs run over 
the network device virbr0.
So i created a new bridge with brctl and added my eth0 to that bridge. 
Not touching virbr0 or it's configuration at all.
Then i edited the configuration xml from my VM with 'virsh edit vmname'.
After that i decided to restart my server, basically just to 'reset' my 
network. I know, that's not necessary. But it's easier than risking 
connection loss and having to get physical access to the server ;)

After the restart my virbr0 network device was gone!
cat /var/log/dmesg | grep virbr0 returned nothing.
cat /var/log/messages | grep virbr0 brought up nothing aswell.

I tried to reinstall all relevant packages with
yum reinstall qemu-kvm python-virtinst virt-top virt-viewer libvirt 
libvirt-client libvirt-python qemu-kvm-tools

But with no success :(

Does anyone have an idea how to recreate the default virbr0?
Is it doable via virsh? I don't have a DE installed on this server, so 
no virtual-manager. I am willing to go that far if it's worth it though.

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


Re: [CentOS] weird issue with qemu-kvm network...

2013-02-01 Thread James Hogarth
>
> Does anyone have an idea how to recreate the default virbr0?
> Is it doable via virsh? I don't have a DE installed on this server, so
> no virtual-manager. I am willing to go that far if it's worth it though.
>

You don't need a DE for that just yum install xauth virt-manager and ssh -X
to forward it to your local X server.

Although I do a fair amount from virsh and editing XML if you don't use a
cluster manager/tool/IaaS like ovirt, openstack, archipel etc virt-manager
is too useful not to have - especially to get console access to VMs nicely.

I'm home now but if you're struggling on the bridge part come Monday send
me a mail and I'll send you my server network configs to give you a start
on this.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] weird issue with qemu-kvm network...

2013-02-01 Thread skull
Am 01.02.2013 23:39, schrieb James Hogarth:
>> Does anyone have an idea how to recreate the default virbr0?
>> Is it doable via virsh? I don't have a DE installed on this server, so
>> no virtual-manager. I am willing to go that far if it's worth it though.
>>
> You don't need a DE for that just yum install xauth virt-manager and ssh -X
> to forward it to your local X server.
>
> Although I do a fair amount from virsh and editing XML if you don't use a
> cluster manager/tool/IaaS like ovirt, openstack, archipel etc virt-manager
> is too useful not to have - especially to get console access to VMs nicely.
>
> I'm home now but if you're struggling on the bridge part come Monday send
> me a mail and I'll send you my server network configs to give you a start
> on this.
> ___
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos
>
I guess it's better to communicating this over the list, in case someone 
runs in the same problem :)

What i did in terms of network changes was the following script. It's an 
old one i used when i didn't work with virsh, because i followed an old 
tutorial for kvm-qemu on CentOS 5.
It basically creates a new bridge called bg0, creates a tap0 interface, 
and connects eth0 and tap0 to the bridge.
(comments ommited)

  22 chown root:kvm /dev/net/tun
  23 chmod 0660 /dev/net/tun
  24
  25 service libvirtd stop
  26 service httpd stop
  27 service vsftpd stop
  28 service named stop
  32 brctl addbr br0
  35 ifconfig eth0 0.0.0.0
  38 brctl addif br0 eth0
  41 ifconfig br0 192.168.2.253 netmask 255.255.255.0 up
  44 route add -net 192.168.2.0 netmask 255.255.255.0 br0
  47 route add default gw 192.168.2.1 br0
  50 tunctl -u root -g kvm -t tap0
  58 ifconfig tap0 up


so i ran this script and tried to use the tap0 the xml from the vm.
it didn't work (yeah i am not that smart in terms of bridges, i know i 
am not getting it 100 percent ;) )
but i didn't touch virbr0 at all.
it even showed up as usual when i did a "brctl show all"
and either eth0 or tap0 were connected in any way with it.

after the restart virbr0 was gone.

If you want to have more logs etc just ask away.


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


Re: [CentOS] Dell unofficial community repository - what do you think?

2013-02-01 Thread SilverTip257
On Fri, Feb 1, 2013 at 9:22 AM,  wrote:

>
> > I also haven't figured out how to only update firmware for specific
> > devices. With the inventory_firmware and update_firmware commands, it
> > looks for updates and applies all updates at once.
>
>  inventory_firmware_gui lets you select. I'm not aware of how to achieve
>  this with command line only.
>

update_firmware


>
> > As for creating a local mirror, a simple rsync grabs it (I exclude
> > everything I don't need)
>
>  Yes, I have something pretty similar :)
>
>
I use their repo directly, but I should mirror it now that I have more
machines that make use of those packages.

It looks like srvadmin-omcommon is broken for one reason or another. [0] [1]

[0]
http://lists.us.dell.com/pipermail/linux-poweredge/2013-January/047660.html
[1]
http://lists.us.dell.com/pipermail/linux-poweredge/2013-January/047677.html

>
> > I'll attach the yum repo file I use for my local repo. A 'yum install
> > srvadmin-all dell_ft_install' will grab what you need for firmware tools
> > and OpenManage, and then a 'yum install $(bootstrap_firmware)' will grab
> > all your hardware specific firmware.
>
>  Thanks, I'll compare it with my own to see what's wrong.
>
>
The amount of software installed depends on whether one is running the full
OpenManage administration interface or not.


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

-- 
---~~.~~---
Mike
//  SilverTip257  //
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] weird issue with qemu-kvm network...

2013-02-01 Thread skull
Am 01.02.2013 23:56, schrieb skull:
> Am 01.02.2013 23:39, schrieb James Hogarth:
>>> Does anyone have an idea how to recreate the default virbr0?
>>> Is it doable via virsh? I don't have a DE installed on this server, so
>>> no virtual-manager. I am willing to go that far if it's worth it though.
>>>
>> You don't need a DE for that just yum install xauth virt-manager and ssh -X
>> to forward it to your local X server.
>>
>> Although I do a fair amount from virsh and editing XML if you don't use a
>> cluster manager/tool/IaaS like ovirt, openstack, archipel etc virt-manager
>> is too useful not to have - especially to get console access to VMs nicely.
>>
>> I'm home now but if you're struggling on the bridge part come Monday send
>> me a mail and I'll send you my server network configs to give you a start
>> on this.
>> ___
>> CentOS mailing list
>> CentOS@centos.org
>> http://lists.centos.org/mailman/listinfo/centos
>>
> I guess it's better to communicating this over the list, in case someone
> runs in the same problem :)
>
> What i did in terms of network changes was the following script. It's an
> old one i used when i didn't work with virsh, because i followed an old
> tutorial for kvm-qemu on CentOS 5.
> It basically creates a new bridge called bg0, creates a tap0 interface,
> and connects eth0 and tap0 to the bridge.
> (comments ommited)
>
>22 chown root:kvm /dev/net/tun
>23 chmod 0660 /dev/net/tun
>24
>25 service libvirtd stop
>26 service httpd stop
>27 service vsftpd stop
>28 service named stop
>32 brctl addbr br0
>35 ifconfig eth0 0.0.0.0
>38 brctl addif br0 eth0
>41 ifconfig br0 192.168.2.253 netmask 255.255.255.0 up
>44 route add -net 192.168.2.0 netmask 255.255.255.0 br0
>47 route add default gw 192.168.2.1 br0
>50 tunctl -u root -g kvm -t tap0
>58 ifconfig tap0 up
>
>
> so i ran this script and tried to use the tap0 the xml from the vm.
> it didn't work (yeah i am not that smart in terms of bridges, i know i
> am not getting it 100 percent ;) )
> but i didn't touch virbr0 at all.
> it even showed up as usual when i did a "brctl show all"
> and either eth0 or tap0 were connected in any way with it.
>
> after the restart virbr0 was gone.
>
> If you want to have more logs etc just ask away.
>
>
> ___
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos
>

I fixed it.
I had to yum remove everything
and then yum install everything

apparently yum reinstall doesnt do the same.

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


Re: [CentOS] weird issue with qemu-kvm network...

2013-02-01 Thread James Hogarth
>
> What i did in terms of network changes was the following script. It's an
> old one i used when i didn't work with virsh, because i followed an old
> tutorial for kvm-qemu on CentOS 5.
> It basically creates a new bridge called bg0, creates a tap0 interface,
> and connects eth0 and tap0 to the bridge.

Err no... That's a terrible way to go about this.

It's very not rhel and pretty flakey at best.

You can do everything you need to in /etc/sysconfig/network-scripts/ifcfg-*

Specifically you need ifcfg-br0 (or something similar) with type=Bridge
(the capital B is important) this is where you should configure the network
fit you physical host too.

Then in your ifcfg-eth0 you link that to the bridge.

For VMs you can then see this in virt-manager when building hosts and
libvirt will automatically create appropriate vnetX virtual interfaces to
bind to the bridge.

This is off the top of my head whilst suffering insomnia so double check
with the upstream documentation ;-)

If you need bonding or vlans it becomes more complicated ;-)
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos