Re: [CentOS-docs] Correction to HowTos/InstallFromUSBkey

2012-05-07 Thread Phil Schaffner
Yves Bellefeuille wrote on 05/01/2012 10:07 PM:
 On Sunday 29 April 2012, Alan Bartletta...@elrepo.org  wrote:

 Thank you, Yves. I've taken care of both of those points. Would you
 like to check that it now reads correctly, please?
 There are a few more points that should be added. They should all appear
 after the end of the current list.

 During the installation process, the user is asked What type of media
 contains the installation image? The user should select the first
 partition on the USB key, which usually appears in the menu under Hard
 drive, then /dev/sdb1.

 After partitioning, the user is asked whether to install the Grub boot
 loader and where to install it. After booting from the USB key, the BIOS
 thinks that the USB key is the first drive. To install the Grub boot
 loader on the hard drive, which is the usual case, the user must change
 the order of the hard drives using the Grub installation options.

 After the Grub installation options, the following error message
 appears: Missing ISO 9660 image: The installer has tried to mount image
 #1, but cannot find it on the hard drive. The installation program is
 looking for the ISO file on the first partition of the USB key, but it's
 on the second partition. The user should go to a terminal (Ctrl-Alt-F2),
 unmount the first partition of the USB key (umount /mnt/isodir), mount
 the second partition (mount -t ext3 /dev/sdb2 /mnt/isodir), return to
 the installation program (Ctrl-Alt-F6) and choose Retry.

 (Unmounting /dev/sdb1 doesn't interfere with the installation process. I
 tried creating a link from /dev/sdb1 to the ISO image, but that didn't
 work, because /dev/sdb1 contains a VFAT or FAT32 flle system which
 doesn't support links.)


Thanks for the suggestions, and the help editing..  I will try to get to 
it soon.

Phil

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


Re: [CentOS-docs] CentOS Wiki - Editing Rights

2012-05-07 Thread Guillaume Rembert

 
 Date: Sun, 06 May 2012 23:43:23 +0200
 From: Ralph Angenendt ralph.angene...@gmail.com
 Subject: Re: [CentOS-docs] CentOS Wiki - Editing Rights
 To: centos-docs@centos.org
 Message-ID: 4fa6f07b.2040...@gmail.com
 Content-Type: text/plain; charset=ISO-8859-1
 
 On 30.04.2012 11:27, Guillaume Rembert wrote:
  Hello CentOS community,
  
  Would it be possible to become a CentOS Wiki contributor, please?
  
  My UserName is GuillaumeRembert.
  
  There are some commands which are not valid anymore on some articles,
  with CentOS 6.2 release, that I would like to correct.
 
 Can you tell me where you want to edit? We begin with a few editing
 rights, which then can be expanded.
 
 Cheers and thanks,
 
 Ralph
 
 

Hello Ralph,

The major part that I would like to edit is currently linked to this
article. I would like to update it for the CentOS 6 distribution:
http://wiki.centos.org/TipsAndTricks/MultimediaOnCentOS

I don't exactly know how are managed the wiki editing rights, but what
could be nice is to have a kind of intermediate editing profile, where
somebody wanting to contribute could make some corrections on any
article, but there would be a moderator that confirm the information can
be published, in order to keep control on the quality of the docs.

This would avoid that some information would be lost mainly due to this
hard procedure to edit/correct an article. I took some notes on what I
found out has changed on this article hopefully, but I will have to
perform again the steps to make sure that it is alright.

I am currently on servers installations. There will be some other
services and configurations that I am going through on CentOS 6, like
mails, web, etc (installation of them from the minimal setup with the
new IPA engine).

Is it possible? What do you think about it?

Guillaume

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


[CentOS-announce] CESA-2012:0546 Critical CentOS 5 php Update

2012-05-07 Thread Johnny Hughes

CentOS Errata and Security Advisory 2012:0546 Critical

Upstream details at : https://rhn.redhat.com/errata/RHSA-2012-0546.html

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

i386:
d8fcc11109c23da1f956cc2b46e66b78a252fd9d2f8280c985529f011521a88e  
php-5.1.6-34.el5_8.i386.rpm
ff64a2e54d3e53d0ee11361028576cb2ae5f5b5e9c07f570d8db5a4e4721  
php-bcmath-5.1.6-34.el5_8.i386.rpm
c35c2871e78ac300805571161ca444743508ac0b0bafba080bbc0093cb35021f  
php-cli-5.1.6-34.el5_8.i386.rpm
5140520f8448d1dbf84514ea8d570ae2026d9d44ca9ebb0264b219e6f4bd13c2  
php-common-5.1.6-34.el5_8.i386.rpm
076033ff5d1249d7b9be5f4588c072808048317d8339e110258d34cdddad1f85  
php-dba-5.1.6-34.el5_8.i386.rpm
e7496f62e6e53e4ab87b1f9a1f848f9bdd70ed442af1458450cf6259f419ab10  
php-devel-5.1.6-34.el5_8.i386.rpm
58fe6265fb8f753b0f15266b5e0cea956c2751e859033af9d4977687193e252a  
php-gd-5.1.6-34.el5_8.i386.rpm
17e266abab6653049e7edb47b5dbba538703f713db169d5e3a554acec8a3004a  
php-imap-5.1.6-34.el5_8.i386.rpm
18bd7bf4b1a7b38a8420c69d7326eeb22651500fb4520dd9b0421122948c8610  
php-ldap-5.1.6-34.el5_8.i386.rpm
b31bc233e35b62c7a453449f0db6b195f575b815743d8bc094064d9d2514410e  
php-mbstring-5.1.6-34.el5_8.i386.rpm
cef51f21e74da63fa53a59ac115f883620f6afdd3680c607cbf97380e6b8db6b  
php-mysql-5.1.6-34.el5_8.i386.rpm
ee42e70d440ec6cadcc89e2bc9d2340f75699fa74fd2b5668503bfb3e91a8b0f  
php-ncurses-5.1.6-34.el5_8.i386.rpm
ec25e5fc37829da2e5f0241a82714fe8fde19bf405dbd69b404c0806447fb38b  
php-odbc-5.1.6-34.el5_8.i386.rpm
18852ca2601521bbddb4f73b65bc97cd359ea2ff147c30780e344bf0948ad66a  
php-pdo-5.1.6-34.el5_8.i386.rpm
80e5aa10ca0bbc03ed3833a9537259e7372f8cfdf8637f7f3a6b497e2a41f1b1  
php-pgsql-5.1.6-34.el5_8.i386.rpm
62a237ecd2fb833971e72300d62dd43f633bac03927129ceeaed347dad00c686  
php-snmp-5.1.6-34.el5_8.i386.rpm
f74e7178d4b89dd7f7e19551f41d17b612ff56a37c6efdcd852cbf1337ba1af3  
php-soap-5.1.6-34.el5_8.i386.rpm
0ac1968e8860d7773c0fef19b76ba433c37a1540c7299a90d9617a26e08b1d07  
php-xml-5.1.6-34.el5_8.i386.rpm
1f0c060e33f06f6990de0ea9dc26968dfad026a3c773b0070e274d42a11cf8aa  
php-xmlrpc-5.1.6-34.el5_8.i386.rpm

x86_64:
391188b41ff82c2e4814bbca4a1a4344d05b8cdf387f7a7bcd408211a9a62a4a  
php-5.1.6-34.el5_8.x86_64.rpm
98b4d8c25116941c9e5454c3c67746c57c1a167a3d5e13cc52000d1091f2e0db  
php-bcmath-5.1.6-34.el5_8.x86_64.rpm
2f4bb9f595075596c023f8810a6331f6a0b8397fd4aa6848280df5f62632ad34  
php-cli-5.1.6-34.el5_8.x86_64.rpm
d464663d4b781850677db34db4c67a2d2bcf21a926504872f506163ece10b350  
php-common-5.1.6-34.el5_8.x86_64.rpm
e1c5a3b5955723b582df68142a9a14c2c82082b761c4d77a1215f321ae800716  
php-dba-5.1.6-34.el5_8.x86_64.rpm
8609c5314876cab5f78461f2c101f99921c6de998de95f67649e09913fd1d3ab  
php-devel-5.1.6-34.el5_8.x86_64.rpm
3f993b49f98b61e4879c7344fbc3d46c7d0e80b214e2ae9ec3b506d544914f51  
php-gd-5.1.6-34.el5_8.x86_64.rpm
83badf7518b2f96a380e131b1c98e94ff52b10766067dfe4f4170e6bedc2a03a  
php-imap-5.1.6-34.el5_8.x86_64.rpm
dbd700c32dc89278521ae8104b51bacfb587e2077fdf192e6cb885f9d43a7f71  
php-ldap-5.1.6-34.el5_8.x86_64.rpm
a4ab5df6b533b074a0f992d7ee0896233fe2f3d17847165035e8c2460ac507d8  
php-mbstring-5.1.6-34.el5_8.x86_64.rpm
5c0c4eceb738f4ab189150dca6e4cd71c20bc77462b13bf7cc9f115366375170  
php-mysql-5.1.6-34.el5_8.x86_64.rpm
6aa19a235446761b84facb55993f0945f2fdefb9b3da10199446b5acd7aff0b3  
php-ncurses-5.1.6-34.el5_8.x86_64.rpm
e0d5f058e048a0d1a666763aae365c55ab7e1e110f39cec7f631f4ab987ced12  
php-odbc-5.1.6-34.el5_8.x86_64.rpm
624151041fa3292ba02d344cfffb75f1b5bcfa18c70036f139ab0bd5a95fe80e  
php-pdo-5.1.6-34.el5_8.x86_64.rpm
50e6b4f6aaef148a7df1c6a9a1ceab42ab03b718eca47a9e8f17728156ce9fee  
php-pgsql-5.1.6-34.el5_8.x86_64.rpm
7b75336aa58ff5f6612bb2c6ba7b251c4a98b909b6e488371a05faf35f28b6ae  
php-snmp-5.1.6-34.el5_8.x86_64.rpm
080e38385214255037e7dcff4a044f16e3ff45613d9abe2aad2dfc15c7998025  
php-soap-5.1.6-34.el5_8.x86_64.rpm
cea1a71684992925b13a9d85de73cf955b68fe56378736be8f5e0f076b2a2edb  
php-xml-5.1.6-34.el5_8.x86_64.rpm
5d421b8d891e4605a4c877a71c98268f3e763b1c85e421b497b100a7ff09e36a  
php-xmlrpc-5.1.6-34.el5_8.x86_64.rpm

Source:
f6774aec5c18d6826d095825ef3f9d64b842160691d19d471bf51ecb495cf7ac  
php-5.1.6-34.el5_8.src.rpm



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

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


[CentOS-announce] CESA-2012:0546 Critical CentOS 6 php Update

2012-05-07 Thread Johnny Hughes

CentOS Errata and Security Advisory 2012:0546 Critical

Upstream details at : https://rhn.redhat.com/errata/RHSA-2012-0546.html

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


i386:
3cce64fa327be5f973b377241303f55c057df310197ba145892f128c58bf2f53  
php-5.3.3-3.el6_2.8.i686.rpm
ba811694992d8117d48f2caf464c3c41cfd4b54974f8cf89849e2aae2c42643b  
php-bcmath-5.3.3-3.el6_2.8.i686.rpm
55c9503ce195a86cf87939d918a1d142f5e980fcc2b24ffdb23076425be8408c  
php-cli-5.3.3-3.el6_2.8.i686.rpm
cce09830ca0afdd7b3a5447e29d5909ef3daf74a6ac180db7579351abe344452  
php-common-5.3.3-3.el6_2.8.i686.rpm
aff11ee676d596999dd83c85404a395b5de53c2ff0644bec4bf667e6fd2c5a1a  
php-dba-5.3.3-3.el6_2.8.i686.rpm
66f1de5f6e19c825e4bfda585d4f2f037d95b93ee56ee83452a4c20f2889356b  
php-devel-5.3.3-3.el6_2.8.i686.rpm
40954d90a41646dbb8435024b9a1e39032c3ea1103ae1fc1cc6f2372bab99a2d  
php-embedded-5.3.3-3.el6_2.8.i686.rpm
e78210d5e753381a45794d0ebf90ff4d14c8bd6fb854d8ce257939b23ec37943  
php-enchant-5.3.3-3.el6_2.8.i686.rpm
e099d4579b38a3931643fcd912d1a1c81fd629d02198e419542a7a421793430d  
php-gd-5.3.3-3.el6_2.8.i686.rpm
eb375482e3d61f5aa6b307774fad7f87474fd34f176937cbadba126c501c69f1  
php-imap-5.3.3-3.el6_2.8.i686.rpm
93d045af8da132fbea3367c5ac0621a14355146eaa634346134e1a35d7bbe575  
php-intl-5.3.3-3.el6_2.8.i686.rpm
aeff06b821e19933d194adc54cb36095352785edd5574f38ee7491f373601fd9  
php-ldap-5.3.3-3.el6_2.8.i686.rpm
0611356688accee9516fc94cc4538efa8741f64826dbcca0eb0a9116cba90726  
php-mbstring-5.3.3-3.el6_2.8.i686.rpm
09bf0c665bd30914dae7f48ca76ab40c34b3ed7bec610465d9b25638d981bd36  
php-mysql-5.3.3-3.el6_2.8.i686.rpm
3aa5ae54aa1fdf4ea1e6e9d2413513152d5ca8959171a7ff4a192dbef728c04f  
php-odbc-5.3.3-3.el6_2.8.i686.rpm
1c2591b693e25735e32e8618586edec7027e5d8c221afcb04301bded14a3dbbd  
php-pdo-5.3.3-3.el6_2.8.i686.rpm
e2ca871203837c3a308c138cf332e4a2768e5659ef39e6b0ddaaf0327cd39542  
php-pgsql-5.3.3-3.el6_2.8.i686.rpm
1806be4c9f7f49ac5cce6b0715ea44f162ea5bb48332a6125076f99a1426722b  
php-process-5.3.3-3.el6_2.8.i686.rpm
6556e322a5cc0842d5dca4a12a202ed7e8b806da18813326d10aa586c9b7f81b  
php-pspell-5.3.3-3.el6_2.8.i686.rpm
9130b0a7cf766699dd2263472ad9818965c88d5cfb692d2bdc95fa81eb2218c9  
php-recode-5.3.3-3.el6_2.8.i686.rpm
6f79a134f10f248f434054b03fa413c1e2a0ba2733708a330ffec4a4f2805a37  
php-snmp-5.3.3-3.el6_2.8.i686.rpm
295a1c906b40529bcb4d15e815e550371c7c4cdabf99e048faada3d0e81c0503  
php-soap-5.3.3-3.el6_2.8.i686.rpm
daffc31fc7eec6f056ff9dcb4ed0baf04e22c66a96976c57b95bb8baaa91a01f  
php-tidy-5.3.3-3.el6_2.8.i686.rpm
75b8c56631c18750043c9f199bd535730ef97412c1fb1c200653faf3bba60f16  
php-xml-5.3.3-3.el6_2.8.i686.rpm
67011bda6cda1576c8ebbea94d94074695ae813f51a31edfbf35fc8c7bc889d1  
php-xmlrpc-5.3.3-3.el6_2.8.i686.rpm
e9a50475ec560821bc4c44c70fdae05b00744fc71ae02346c3bfbec33d688e37  
php-zts-5.3.3-3.el6_2.8.i686.rpm

x86_64:
fee4d46743842d927a72a7d5499bf21ee28a758f124d0263d017f9f1db008427  
php-5.3.3-3.el6_2.8.x86_64.rpm
ebd49db48a8720dbb8485b87973b3fc3c1035dbd56226bff4e60d6b76373d9a9  
php-bcmath-5.3.3-3.el6_2.8.x86_64.rpm
c27d278a43c6ebf216ef5a8cf12d0b064a8627692688073e07a639a506c700e6  
php-cli-5.3.3-3.el6_2.8.x86_64.rpm
eaac2ad9357eba44f9634ccffd45e4a97c1e774b703adc002bb9f57bc624b5bb  
php-common-5.3.3-3.el6_2.8.x86_64.rpm
0684d63a3e60dea6f766764a043293e06a67c29eea69b251c5501e74dd5152a0  
php-dba-5.3.3-3.el6_2.8.x86_64.rpm
1a7d78a6823e2ffbdd93ace3d5a68d724c54d287403a948ec96aafb16898e618  
php-devel-5.3.3-3.el6_2.8.x86_64.rpm
8f54b289baf9068e511179c1576a865e250e5bdd3bd967b046fd27ac922f4912  
php-embedded-5.3.3-3.el6_2.8.x86_64.rpm
cea650a9d859fecc9e5d37361643669da2849107cffdb874abeee6082ebc4d0f  
php-enchant-5.3.3-3.el6_2.8.x86_64.rpm
d65de8336db734e7ebbfa8c9e5f19aeb5514a3abf2c250cc653ec0bd578c586c  
php-gd-5.3.3-3.el6_2.8.x86_64.rpm
8076902b2159564d24acb96f9dfd8718668aab49687386f825c951c5ebf58a09  
php-imap-5.3.3-3.el6_2.8.x86_64.rpm
be2c8a22fea6fd2dd7ede05e2b03ce03a7117e078450086f6937fab0e81d8e34  
php-intl-5.3.3-3.el6_2.8.x86_64.rpm
4dc2ca4e37abb5295f1d9be9ea92254132722051a8d7ae610e87b97c460fadcf  
php-ldap-5.3.3-3.el6_2.8.x86_64.rpm
f71778f5cd344c4adf31839c459e6d212f2de4f50cd7638015c75d5bd650cd13  
php-mbstring-5.3.3-3.el6_2.8.x86_64.rpm
4a8b44759e4b589961c338e4954213ac314208372289c16238cce8afdc15391a  
php-mysql-5.3.3-3.el6_2.8.x86_64.rpm
7bbb0f54f37e77b8fc067d75d1694670f1fdbb7997d7449dd84241ac6f70c778  
php-odbc-5.3.3-3.el6_2.8.x86_64.rpm
bb324ac3521ca299ad4daa08c58504945819123ed6faf7ddf7f6e5182fbbaaec  
php-pdo-5.3.3-3.el6_2.8.x86_64.rpm
e5eec3fe8f2d01fc30b68dd097e8eb80f9943ccc8b6a999a4e46c34df6bf7265  
php-pgsql-5.3.3-3.el6_2.8.x86_64.rpm
138078df93bf21ebf0084f5d7ff1462794b40214afb458c6a95124ed118be64c  
php-process-5.3.3-3.el6_2.8.x86_64.rpm
41628110fdb6595c5f327932b67c925a206cbeca82180331523db1c2e3552482  
php-pspell-5.3.3-3.el6_2.8.x86_64.rpm
603a549c920322ef71a888cd8e7c276d1f5e78f9d8745c23446dfcd611371a57  
php-recode-5.3.3-3.el6_2.8.x86_64.rpm

[CentOS-announce] CESA-2012:0544 Moderate CentOS 6 ImageMagick Update

2012-05-07 Thread Johnny Hughes

CentOS Errata and Security Advisory 2012:0544 Moderate

Upstream details at : https://rhn.redhat.com/errata/RHSA-2012-0544.html

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


i386:
78a4e26a4eeeda4e1876efef03142af49b59ceaa914c08f86278022ce2b3e272  
ImageMagick-6.5.4.7-6.el6_2.i686.rpm
aab146c090aabd92628c9ff9a1a59f1d27136047f892ef7acdfc12ab274e794b  
ImageMagick-c++-6.5.4.7-6.el6_2.i686.rpm
1cb787f39d2c150d8d6f149a7ada6ee545aaeeef05907c10d256be8c5837259f  
ImageMagick-c++-devel-6.5.4.7-6.el6_2.i686.rpm
a0b54e41b013a66dd498bbd97b03ae7d6796d3a12cca431a68e01dfa9dcf3a05  
ImageMagick-devel-6.5.4.7-6.el6_2.i686.rpm
23900280961f296c2fb373310c66b3970a5d28d5aaf8faf623cdaeb3ff0ccebf  
ImageMagick-doc-6.5.4.7-6.el6_2.i686.rpm
ce8b5d306effb6eaed95b67cacd44170d08b8bae9d2968855256869cb1041f3b  
ImageMagick-perl-6.5.4.7-6.el6_2.i686.rpm

x86_64:
78a4e26a4eeeda4e1876efef03142af49b59ceaa914c08f86278022ce2b3e272  
ImageMagick-6.5.4.7-6.el6_2.i686.rpm
5c67542ff27ece41671ff6cf344d531bdf7ffd1e4ba5b88bafbe6404c466319b  
ImageMagick-6.5.4.7-6.el6_2.x86_64.rpm
aab146c090aabd92628c9ff9a1a59f1d27136047f892ef7acdfc12ab274e794b  
ImageMagick-c++-6.5.4.7-6.el6_2.i686.rpm
41c75f3ae1ec1135a569f942a9d381b095f1b095648cee1ab68170294051c09b  
ImageMagick-c++-6.5.4.7-6.el6_2.x86_64.rpm
1cb787f39d2c150d8d6f149a7ada6ee545aaeeef05907c10d256be8c5837259f  
ImageMagick-c++-devel-6.5.4.7-6.el6_2.i686.rpm
08f389f03d2bd61cfc6860d88cb7630e2f3ced84de6792448ede2b7bb1ef0979  
ImageMagick-c++-devel-6.5.4.7-6.el6_2.x86_64.rpm
a0b54e41b013a66dd498bbd97b03ae7d6796d3a12cca431a68e01dfa9dcf3a05  
ImageMagick-devel-6.5.4.7-6.el6_2.i686.rpm
29545c97ff484416b2dc5fe0655201696b11a098e4d42c2833a9d6b48fb93dad  
ImageMagick-devel-6.5.4.7-6.el6_2.x86_64.rpm
e06e122354c0f427e8c76efb96582bb4b6a86d748e69e00b71f5f2d0a324cd8c  
ImageMagick-doc-6.5.4.7-6.el6_2.x86_64.rpm
86de3c7efc88a7849fb1022ca825f538d1d54beb4e726e94cf7778f979b78432  
ImageMagick-perl-6.5.4.7-6.el6_2.x86_64.rpm

Source:
62eb4d7f4a43ba20db069fa4fbe675415631dc123ea33c9dfc89f9cbb9bd151c  
ImageMagick-6.5.4.7-6.el6_2.src.rpm



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

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


[CentOS-announce] CEBA-2012:0548 CentOS 6 fence-agents Update

2012-05-07 Thread Johnny Hughes

CentOS Errata and Bugfix Advisory 2012:0548 

Upstream details at : https://rhn.redhat.com/errata/RHBA-2012-0548.html

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


i386:
0f64b0ade2c7a200ee0cdd6f3f6c74f8f3c175f713ad4f63ca4d8f04be9c1c60  
fence-agents-3.1.5-10.el6_2.3.i686.rpm

x86_64:
b0df09801b1a69b3fe17315bf36004f5327a09d9e0ec6ec6e71dfa4dc32d2647  
fence-agents-3.1.5-10.el6_2.3.x86_64.rpm

Source:
0eafc3ee5b2cb9ef38955a3c2967865a9e98d3ea9962e65c2b6f97b02c0cb804  
fence-agents-3.1.5-10.el6_2.3.src.rpm



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

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


[CentOS-announce] CESA-2012:0547 Critical CentOS 5 php53 Update

2012-05-07 Thread Johnny Hughes

CentOS Errata and Security Advisory 2012:0547 Critical

Upstream details at : https://rhn.redhat.com/errata/RHSA-2012-0547.html

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

i386:
87a469e5e39216019361e8e89c9174be5013e677b08b9083bb5dd58ea8442665  
php53-5.3.3-7.el5_8.i386.rpm
6aad57378e6d50670d446541b3b56b78b73a1b542741ae871bd16da7e64fde28  
php53-bcmath-5.3.3-7.el5_8.i386.rpm
2e7aecc21ead4d50ca8a46bf6caba951b78aae14e0b78c93eda699102b0e6289  
php53-cli-5.3.3-7.el5_8.i386.rpm
b5abc4559e1d21b34db757b1014eb518536f2c36ee96f5bf747045c3dc8ebbc8  
php53-common-5.3.3-7.el5_8.i386.rpm
428d1fcc3f05d678e5274812335359621d2f64c1e66ff4551a3596270d94bbf3  
php53-dba-5.3.3-7.el5_8.i386.rpm
058cc2f9616fafb6cc0baab90727368cd1952b6d297abab56c17c71c60e87a0c  
php53-devel-5.3.3-7.el5_8.i386.rpm
d81e5bd19349ff41f5781d699e536e72333e3905ef52bcd2078cf654b9e79512  
php53-gd-5.3.3-7.el5_8.i386.rpm
50637ec7784f099b5c9dee86129534818ad6605efb28f70503cea11187dbdc34  
php53-imap-5.3.3-7.el5_8.i386.rpm
b6cc90ce05fb595a6835b2d7e7ac26aa7b9f7e25dff62f3f4eb2b4e4d014ca5e  
php53-intl-5.3.3-7.el5_8.i386.rpm
0c086eed14371dcee9a64c82d7090dd757b8c693a95328919bd108e3fb472d3d  
php53-ldap-5.3.3-7.el5_8.i386.rpm
253c42e9762cd06b2db1ce144264fcc5e9d4820bb42464a107d6945df83d0b15  
php53-mbstring-5.3.3-7.el5_8.i386.rpm
af4ff943ef2c919cfbb54c33500340108fcca97d5bcd6f430d4a47780a360871  
php53-mysql-5.3.3-7.el5_8.i386.rpm
566336ef866cd9f57b85d9f4fe7230a4296c96e48739566b5b7cf3b6f7d4ee63  
php53-odbc-5.3.3-7.el5_8.i386.rpm
f11362c130ba642cdc0d7f47a13fd269ef5acb9a2f18b9c3f3f08b297d03f09a  
php53-pdo-5.3.3-7.el5_8.i386.rpm
b531d2029be532829a67c0e77416ca883353e3432e0994a59a8f79d6d1053b82  
php53-pgsql-5.3.3-7.el5_8.i386.rpm
4ac131a2a04d429355a068600dd8fcf5446a510eadb7a21208df0248aa3afe2d  
php53-process-5.3.3-7.el5_8.i386.rpm
02878820488dbbc790b4cf9b7a115976f30e7b884c4fd369ce49d760df5b57d2  
php53-pspell-5.3.3-7.el5_8.i386.rpm
2ab8efad64bb0515a648bee9a2cb6eb7f3f458e0fc3e68f44521953634471c46  
php53-snmp-5.3.3-7.el5_8.i386.rpm
6e1bae7866f34e22c48dd07436c392f3380c6ae77f37339da91985c009d7632f  
php53-soap-5.3.3-7.el5_8.i386.rpm
07bba3db12395c7dca30634c022382d744610a4d6f2778cd8df5f55fa8c4ffe8  
php53-xml-5.3.3-7.el5_8.i386.rpm
2e7c3ce6cfd5865225564f8f062e687683802f0b9ae6354dc92e7fc757495e4b  
php53-xmlrpc-5.3.3-7.el5_8.i386.rpm

x86_64:
14a23e26d36ac03696c746f53c4454e6b1c10de2a69c38355e8292539c8e4702  
php53-5.3.3-7.el5_8.x86_64.rpm
8a4d8ef363c2c4bb9847a9e2dbfdb20d09ef52a7f24ee3dd47a17fb9f664aa37  
php53-bcmath-5.3.3-7.el5_8.x86_64.rpm
7339b28801d014f7fae84563c4db9b0f68ed3dc399e63f3bca5933780611ac45  
php53-cli-5.3.3-7.el5_8.x86_64.rpm
badd2d9ad9e4cd2aa041243d3dec72335efe412faa7a066baed33c78fddf5482  
php53-common-5.3.3-7.el5_8.x86_64.rpm
a7be8b2929b9be601d76a653a62cf94d7b56b6babe839eba1009c615ff394806  
php53-dba-5.3.3-7.el5_8.x86_64.rpm
a8273c87a7b10e20c4ed3928c5316be8f682398ab4bd3b7c73160e4d05f87a3c  
php53-devel-5.3.3-7.el5_8.x86_64.rpm
9595c13bb9f1fb70e1e2fff00405923a2475ff273fe129c456cfd5cc8ba509c0  
php53-gd-5.3.3-7.el5_8.x86_64.rpm
2d3b563d2fd20c1c715d3f821b88c30fde77c24f1e2d81de9d6cd42dec79d4f3  
php53-imap-5.3.3-7.el5_8.x86_64.rpm
905bef4c98ded4502d22b3563686a2300a92c8d9ac625e3280534d9eee65fbde  
php53-intl-5.3.3-7.el5_8.x86_64.rpm
9d3df0378c19467f9c69b602398292f2bdd03694baab2b3362e84fca2ee7182f  
php53-ldap-5.3.3-7.el5_8.x86_64.rpm
9919184d657cf9f6681e4bc288a4a7438dadc529fc7208a1ee5789fd4980f040  
php53-mbstring-5.3.3-7.el5_8.x86_64.rpm
c732daf0bb01ad1bcc50ad919e60e31e8b4139b0f353e7978a421c14336fa3dd  
php53-mysql-5.3.3-7.el5_8.x86_64.rpm
2e7764f7bc7407cfbd11f4b3e26da465e803aa408e9d0856ef82e0082fce398e  
php53-odbc-5.3.3-7.el5_8.x86_64.rpm
f3e47896ccda56f2edc7bd1f262eefe177cde47cd8af512fd881c4c41e972cd7  
php53-pdo-5.3.3-7.el5_8.x86_64.rpm
eaf567ec90d5b8a962cdf90f0abd2335649b30aa4c59221339b706c6fedc4bec  
php53-pgsql-5.3.3-7.el5_8.x86_64.rpm
eed82be4caa18ff12456f5322dfa4c217045356c5afd236d65b4bb361b69c9cf  
php53-process-5.3.3-7.el5_8.x86_64.rpm
28c0344ebff096dc499c68c8b0485572813214f09ce8c65f3a3348bdccfa4855  
php53-pspell-5.3.3-7.el5_8.x86_64.rpm
ba6b0ed4fced29261c2b703b75a11552d00981d4660445a2c74c2a9c3f5acfcc  
php53-snmp-5.3.3-7.el5_8.x86_64.rpm
0647b2d5ad709cfcd689b9fd379f447d2bc2f86086ec4007fc8fc1072db7a5c0  
php53-soap-5.3.3-7.el5_8.x86_64.rpm
f315b70f3a5e160a76e35517bf592e2273f1ca26e09b901e0d523d2c3d306d5e  
php53-xml-5.3.3-7.el5_8.x86_64.rpm
d563cf1d60b539859ca4d2f0ff8c3745dbb1b099c96b49885592d1acb6c4f29d  
php53-xmlrpc-5.3.3-7.el5_8.x86_64.rpm

Source:
2e04b1aafed8459e0e7e885981c7c4b702a264e5a61360ff6138a3b5a610e6b7  
php53-5.3.3-7.el5_8.src.rpm



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

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


Re: [CentOS] loosing applications

2012-05-07 Thread Jesus del Valle

 Larry Martell seem's to have the right way.
 sys is not defined.

 Where should I pout it to get it permanent aund use pirut under X

Hi Michel. This is only to print a sys variable; you don't need to do
anything there. So your default python finds the libuser library, the error
you saw before with import libuser is not coming from this python, at least
as root. Does it make sense to remove pirut and re-install it? I don't use
it, I have absolutely no idea which consequences it may have removing and
reinstalling pirut for software that was already installed under pirut.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] [CentOS-docs] Updating the RAID1 HowTo to CentOS 6

2012-05-07 Thread Adrian Sevcenco

On 05/02/12 18:47, Gianni Giardina wrote:

Hi.
The following HowTo on the CentOS Wiki:

http://wiki.centos.org/HowTos/Install_On_Partitionable_RAID1

valid for CentOS 5, has not been updated to CentOS 6, yet. I found it
very useful during the glorious CentOS 5 days and now that I've
successfully ported my RAID1 experience to CentOS 6, I'd like to share
it with the Community.


I have a question regarding partionable RAID :
why should the --metadata=0.90 be used?
in my man page (centos 6.2) i have this :
-e, --metadata=
Declare  the  style  of RAID metadata (superblock) to be used.  The 
default is 1.2 for --create, and to guess for other operations.  The 
default can be overridden by setting the metadata value for the CREATE 
keyword in mdadm.conf.


Options are:

0, 0.90	   Use the original 0.90 format superblock.  This format limits 
arrays to 28 component devices and limits component devices of levels 1 
and  greater  to  2  terabytes.   It  is  also possible for there to be 
confusion about whether the superblock applies to a whole device or just 
the last partition, if that partition starts on a 64K boundary.


1, 1.0, 1.1, 1.2 default   Use the new version-1 format superblock. 
This has fewer restrictions.  It can easily be moved between hosts with 
different endian-ness, and a recovery operation can be checkpointed and 
restarted.  The different sub-versions store the superblock at different 
locations on the device, either at the end (for 1.0), at the start (for 
1.1) or 4K from the start (for 1.2).  1 is equivalent to 1.2. 
default is equivalent to 1.2.


given the existence of 2+ tb hdd, metadata 0.9 is no go from the start 
... so, why 0.9 ?


Thanks,
Adrian

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


Re: [CentOS] [CentOS-docs] Updating the RAID1 HowTo to CentOS 6

2012-05-07 Thread Les Mikesell
On Mon, May 7, 2012 at 1:24 PM, Adrian Sevcenco adrian.sevce...@cern.ch wrote:
 On 05/02/12 18:47, Gianni Giardina wrote:

 Hi.
 The following HowTo on the CentOS Wiki:

 http://wiki.centos.org/HowTos/Install_On_Partitionable_RAID1

 valid for CentOS 5, has not been updated to CentOS 6, yet. I found it
 very useful during the glorious CentOS 5 days and now that I've
 successfully ported my RAID1 experience to CentOS 6, I'd like to share
 it with the Community.


 I have a question regarding partionable RAID :
 why should the --metadata=0.90 be used?
 in my man page (centos 6.2) i have this :
 -e, --metadata=
 Declare  the  style  of RAID metadata (superblock) to be used.  The default
 is 1.2 for --create, and to guess for other operations.  The default can be
 overridden by setting the metadata value for the CREATE keyword in
 mdadm.conf.

 Options are:

 0, 0.90    Use the original 0.90 format superblock.  This format limits
 arrays to 28 component devices and limits component devices of levels 1 and
  greater  to  2  terabytes.   It  is  also possible for there to be
 confusion about whether the superblock applies to a whole device or just the
 last partition, if that partition starts on a 64K boundary.

 1, 1.0, 1.1, 1.2 default   Use the new version-1 format superblock. This has
 fewer restrictions.  It can easily be moved between hosts with different
 endian-ness, and a recovery operation can be checkpointed and restarted.
  The different sub-versions store the superblock at different locations on
 the device, either at the end (for 1.0), at the start (for 1.1) or 4K from
 the start (for 1.2).  1 is equivalent to 1.2. default is equivalent to
 1.2.

 given the existence of 2+ tb hdd, metadata 0.9 is no go from the start ...
 so, why 0.9 ?

I always thought it was a huge advantage for software raid that the
kernel would autodetect and assemble the components.   Is there a way
to make that happen with 1.x metadata?

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


Re: [CentOS] [CentOS-docs] Updating the RAID1 HowTo to CentOS 6

2012-05-07 Thread Ljubomir Ljubojevic
On 05/07/2012 08:24 PM, Adrian Sevcenco wrote:
 On 05/02/12 18:47, Gianni Giardina wrote:
 Hi.
 The following HowTo on the CentOS Wiki:

 http://wiki.centos.org/HowTos/Install_On_Partitionable_RAID1

snip
 given the existence of 2+ tb hdd, metadata 0.9 is no go from the start
 ... so, why 0.9 ?


0.90 is needed so older GRUB can boot from that RAID1 partition.


-- 

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] hack / spam/ probe /attack

2012-05-07 Thread Scott Silva
on 5/3/2012 6:18 PM Bob Hoffman spake the following:
 On 5/3/2012 4:05 PM, m.r...@5-cent.us wrote:
 whois only lists a technical contact ofhostmas...@telepacific.com.
 However, from their website, I went to contact
 http://www.telepacific.com/support/corporate-contacts.asp, and see
 snip
 877-487-8349 Emergency Law Enforcement
 Option 2. Fraud and subpoena compliance
 866-839-8545 Non-Emergency Toll Fraud, Call Annoyance, Subpoena
 Compliance and non-emergency law enforcement
 877-702-2873 Internet Abuse Complaints
 snip
 Thanks for the ideas guys.
 I got home late and could only send a mail to abuse. Gonna try the calls
 tomorrow.
 It would be nice to know the way all these isps would like this stuff
 presented...
 And if I can get this yahoos name and address.

 bob
Even the best abuse departments will probably not give you any info on the 
attacker... That might open them up to liability

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


[CentOS] Equivalent RHEL package for CentOS httpd package?

2012-05-07 Thread Mitch Patenaude
I'm trying to find out if a particular RedHat patch has been ported to
CentOS yet.

In particular, this vulnerability: CVE-2011-3607

According to this: https://rhn.redhat.com/errata/RHSA-2012-0323.html it
has been patched as of httpd-2.2.3-63.el5_8.1.x86_64.rpm

Now, in the latest CentOS repository, I find
httpd-2.2.3-63.el5.centos.1.x86_64.rpm

Is this the same (or later) release?  I suspect not, because the el5 !=
el5_8.1, but I'm not 100% sure I understand the mapping between the two
sets of RPM names.


Thanks,
   -- Mitch Patenaude mpatena...@shutterfly.com

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


Re: [CentOS] loosing applications

2012-05-07 Thread Michel Donais
 Hi Michel. This is only to print a sys variable; you don't need to do
 anything there. So your default python finds the libuser library, the 
 error
 you saw before with import libuser is not coming from this python, at 
 least
 as root. Does it make sense to remove pirut and re-install it? I don't use
 it, I have absolutely no idea which consequences it may have removing and
 reinstalling pirut for software that was already installed under pirut.

It's already been done, uninstall and re-install pirut without success. The 
version removed end the re-installed one were at the same level

For Centos-5.8 I've a test machine both are at the same level of update.
If I do print (sys.path) on the production machine, I get

 import sys
 print (sys.path)
['', '/usr/lib/python24.zip', '/usr/lib/python2.4', 
'/usr/lib/python2.4/plat-linux2', '/usr/lib/python2.4/lib-tk', 
'/usr/lib/python2.4/lib-dynload', '/usr/lib/python2.4/site-packages']

And on the test machine I get

 import sys
 print (sys.path)
['', '/usr/lib/python24.zip', '/usr/lib/python2.4', 
'/usr/lib/python2.4/plat-linux2', '/usr/lib/python2.4/lib-tk', 
'/usr/lib/python2.4/lib-dynload', '/usr/lib/python2.4/site-packages', 
'/usr/lib/python2.4/site-packages/Numeric', 
'/usr/lib/python2.4/site-packages/gtk-2.0']

If I refer at Larry Martell message, he pointed that the problem was with 
sys.path

If I look in ?usr/lib/python2.4/site-packages/
numeric in there on the test machine but absent on the production one

I tried to re-install  python-numeric.i386 0:23.7-2.2.2.el5_6.1 and nothig 
change; numeric is still not there

On these facts, can somebody point me a solution?

---
Michel Donais


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


Re: [CentOS] Equivalent RHEL package for CentOS httpd package?

2012-05-07 Thread Johnny Hughes
On 05/07/2012 07:16 PM, Mitch Patenaude wrote:
 I'm trying to find out if a particular RedHat patch has been ported to
 CentOS yet.

 In particular, this vulnerability: CVE-2011-3607

 According to this: https://rhn.redhat.com/errata/RHSA-2012-0323.html it
 has been patched as of httpd-2.2.3-63.el5_8.1.x86_64.rpm

 Now, in the latest CentOS repository, I find
 httpd-2.2.3-63.el5.centos.1.x86_64.rpm

 Is this the same (or later) release?  I suspect not, because the el5 !=
 el5_8.1, but I'm not 100% sure I understand the mapping between the two
 sets of RPM names.

You suspect wrong :)

We keep the dist tags the same for packages that we do not modify for
branding ... so if that was an unmodified package, it would have a
.el5_8 dist tag, just like upstream.

BUT ... for packages that we modify ... we always use a .el5.centos
dist tag unless forced to use something else for some reason.

So, since httpd is a modified package,
httpd-2.2.3-63.el5.centos.1.x86_64.rpm ==
httpd-2.2.3-63.el5_8.1.x86_64.rpm





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


[CentOS] Is EXT4 filesystem production ready in CenTOS 5.x series?

2012-05-07 Thread Mail List
Hi Guys,

We run CENTOS 5.8 in some of our servers. We would like to know whether EXT4 
filesystem is ready for production use in CENTOS 5.8 OS?

We couldn't find ext4 utility mkfs.ext4 in our CENTOS 5.8 servers.

Can anyone help us?

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


Re: [CentOS] Is EXT4 filesystem production ready in CenTOS 5.x series?

2012-05-07 Thread John R Pierce
On 05/07/12 9:44 PM, Mail List wrote:
 We run CENTOS 5.8 in some of our servers. We would like to know whether EXT4 
 filesystem is ready for production use in CENTOS 5.8 OS?

 We couldn't find ext4 utility mkfs.ext4 in our CENTOS 5.8 servers.


I would only use ext4 with CentOS 6.  the kernel in 5.x is just too old. 
   I've already migrated to using XFS for my larger file systems with 
EL6, and just use ext4 for the system itself.


-- 
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