Archive for 七月, 2009


Python IDE – Eclipse + PyDev

用 Eclipse + PyDev 開發 Google App Engine 的程式

http://blog.ericsk.org/archives/889

廣告

The PECL uploadprogress modules allows a user to see a upload progress bar.
This is a great UI that makes uploading in action and hence good user experience.

To intall uploadprogress module:

1. install php development, pecl, pear, and development tools if you not yet have them installed:

yum -y install php-devel php-pecl php-pear
yum -y groupinstall "Development Tools"

2. install the upload progress:

pecl install uploadprogress

This is what you should get:

[root@xxx]# pecl install uploadprogress
downloading uploadprogress-1.0.1.tgz ...
Starting to download uploadprogress-1.0.1.tgz (8,536 bytes)
.....done: 8,536 bytes
4 source files, building
running: phpize
Configuring for:
PHP Api Version: 20041225
Zend Module Api No: 20060613
Zend Extension Api No: 220060519
building in /var/tmp/pear-build-root/uploadprogress-1.0.1
running: /var/tmp/uploadprogress/configure
checking for egrep... grep -E
checking for a sed that does not truncate output... /bin/sed
checking for cc... cc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether cc accepts -g... yes
checking for cc option to accept ANSI C... none needed
checking how to run the C preprocessor... cc -E
checking for icc... no
checking for suncc... no
checking whether cc understands -c and -o together... yes
checking for system library directory... lib
checking if compiler supports -R... no
checking if compiler supports -Wl,-rpath,... yes
checking build system type... i686-redhat-linux-gnu
checking host system type... i686-redhat-linux-gnu
checking target system type... i686-redhat-linux-gnu
checking for PHP prefix... /usr
checking for PHP includes... -I/usr/include/php -I/usr/include/php/main -I/usr/include/php/TSRM -I/usr/include/php/Zend -I/usr/include/php/ext -I/usr/include/php/ext/date/lib
checking for PHP extension directory... /usr/lib/php/modules
checking for PHP installed headers prefix... /usr/include/php
checking if debug is enabled... no
checking if zts is enabled... no
checking for re2c... no
configure: WARNING: You will need re2c 0.13.4 or later if you want to regenerate PHP parsers.
checking for gawk... gawk
checking whether to enable uploadprogress functions... yes, shared
checking for ld used by cc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for /usr/bin/ld option to reload object files... -r
checking for BSD-compatible nm... /usr/bin/nm -B
checking whether ln -s works... yes
checking how to recognise dependent libraries... pass_all
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking for g77... no
checking for f77... no
checking for xlf... no
checking for frt... no
checking for pgf77... no
checking for fort77... no
checking for fl32... no
checking for af77... no
checking for f90... no
checking for xlf90... no
checking for pgf90... no
checking for epcf90... no
checking for f95... f95
checking whether we are using the GNU Fortran 77 compiler... yes
checking whether f95 accepts -g... yes
checking the maximum length of command line arguments... 32768
checking command to parse /usr/bin/nm -B output from cc object... ok
checking for objdir... .libs
checking for ar... ar
checking for ranlib... ranlib
checking for strip... strip
checking if cc supports -fno-rtti -fno-exceptions... no
checking for cc option to produce PIC... -fPIC
checking if cc PIC flag -fPIC works... yes
checking if cc static flag -static works... yes
checking if cc supports -c -o file.o... yes
checking whether the cc linker (/usr/bin/ld) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
configure: creating libtool
appending configuration tag "CXX" to libtool
appending configuration tag "F77" to libtool
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
checking for f95 option to produce PIC... -fPIC
checking if f95 PIC flag -fPIC works... yes
checking if f95 static flag -static works... yes
checking if f95 supports -c -o file.o... yes
checking whether the f95 linker (/usr/bin/ld) supports shared libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
configure: creating ./config.status
config.status: creating config.h
running: make
/bin/sh /var/tmp/pear-build-root/uploadprogress-1.0.1/libtool --mode=compile cc -I. -I/var/tmp/uploadprogress -DPHP_ATOM_INC -I/var/tmp/pear-build-root/uploadprogress-1.0.1/include -I/var/tmp/pear-build-root/uploadprogress-1.0.1/main -I/var/tmp/uploadprogress -I/usr/include/php -I/usr/include/php/main -I/usr/include/php/TSRM -I/usr/include/php/Zend -I/usr/include/php/ext -I/usr/include/php/ext/date/lib -DHAVE_CONFIG_H -g -O2 -c /var/tmp/uploadprogress/uploadprogress.c -o uploadprogress.lo
mkdir .libs
cc -I. -I/var/tmp/uploadprogress -DPHP_ATOM_INC -I/var/tmp/pear-build-root/uploadprogress-1.0.1/include -I/var/tmp/pear-build-root/uploadprogress-1.0.1/main -I/var/tmp/uploadprogress -I/usr/include/php -I/usr/include/php/main -I/usr/include/php/TSRM -I/usr/include/php/Zend -I/usr/include/php/ext -I/usr/include/php/ext/date/lib -DHAVE_CONFIG_H -g -O2 -c /var/tmp/uploadprogress/uploadprogress.c -fPIC -DPIC -o .libs/uploadprogress.o
/bin/sh /var/tmp/pear-build-root/uploadprogress-1.0.1/libtool --mode=link cc -DPHP_ATOM_INC -I/var/tmp/pear-build-root/uploadprogress-1.0.1/include -I/var/tmp/pear-build-root/uploadprogress-1.0.1/main -I/var/tmp/uploadprogress -I/usr/include/php -I/usr/include/php/main -I/usr/include/php/TSRM -I/usr/include/php/Zend -I/usr/include/php/ext -I/usr/include/php/ext/date/lib -DHAVE_CONFIG_H -g -O2 -o uploadprogress.la -export-dynamic -avoid-version -prefer-pic -module -rpath /var/tmp/pear-build-root/uploadprogress-1.0.1/modules uploadprogress.lo
cc -shared .libs/uploadprogress.o -Wl,-soname -Wl,uploadprogress.so -o .libs/uploadprogress.so
creating uploadprogress.la
(cd .libs && rm -f uploadprogress.la && ln -s ../uploadprogress.la uploadprogress.la)
/bin/sh /var/tmp/pear-build-root/uploadprogress-1.0.1/libtool --mode=install cp ./uploadprogress.la /var/tmp/pear-build-root/uploadprogress-1.0.1/modules
cp ./.libs/uploadprogress.so /var/tmp/pear-build-root/uploadprogress-1.0.1/modules/uploadprogress.so
cp ./.libs/uploadprogress.lai /var/tmp/pear-build-root/uploadprogress-1.0.1/modules/uploadprogress.la
PATH="$PATH:/sbin" ldconfig -n /var/tmp/pear-build-root/uploadprogress-1.0.1/modules
----------------------------------------------------------------------
Libraries have been installed in:
/var/tmp/pear-build-root/uploadprogress-1.0.1/modules

If you ever happen to want to link against installed libraries
in a given directory, LIBDIR, you must either use libtool, and
specify the full pathname of the library, or use the `-LLIBDIR'
flag during linking and do at least one of the following:
- add LIBDIR to the `LD_LIBRARY_PATH' environment variable
during execution
- add LIBDIR to the `LD_RUN_PATH' environment variable
during linking
- use the `-Wl,--rpath -Wl,LIBDIR' linker flag
- have your system administrator add LIBDIR to `/etc/ld.so.conf'

See any operating system documentation about shared libraries for
more information, such as the ld(1) and ld.so(8) manual pages.
----------------------------------------------------------------------

Build complete.
Don't forget to run 'make test'.

running: make INSTALL_ROOT="/var/tmp/pear-build-root/install-uploadprogress-1.0.1" install
Installing shared extensions: /var/tmp/pear-build-root/install-uploadprogress-1.0.1/usr/lib/php/modules/
running: find "/var/tmp/pear-build-root/install-uploadprogress-1.0.1" | xargs ls -dils
27529277 4 drwxr-xr-x 3 root root 4096 Jul 22 00:48 /var/tmp/pear-build-root/install-uploadprogress-1.0.1
27529298 4 drwxr-xr-x 3 root root 4096 Jul 22 00:48 /var/tmp/pear-build-root/install-uploadprogress-1.0.1/usr
27529299 4 drwxr-xr-x 3 root root 4096 Jul 22 00:48 /var/tmp/pear-build-root/install-uploadprogress-1.0.1/usr/lib
27529300 4 drwxr-xr-x 3 root root 4096 Jul 22 00:48 /var/tmp/pear-build-root/install-uploadprogress-1.0.1/usr/lib/php
27529301 4 drwxr-xr-x 2 root root 4096 Jul 22 00:48 /var/tmp/pear-build-root/install-uploadprogress-1.0.1/usr/lib/php/modules
27529297 44 -rwxr-xr-x 1 root root 43639 Jul 22 00:48 /var/tmp/pear-build-root/install-uploadprogress-1.0.1/usr/lib/php/modules/uploadprogress.so

Build process completed successfully
Installing '/usr/lib/php/modules/uploadprogress.so'
install ok: channel://pecl.php.net/uploadprogress-1.0.1
configuration option "php_ini" is not set to php.ini location
You should add "extension=uploadprogress.so" to php.ini

3. add the extension to php.ini:

extension=uploadprogress.so

4. restart apache for the changes to take effect.

service httpd restart

The PECL uploadprogress modules allows a user to see a upload progress bar.
This is a great UI that makes uploading in action and hence good user experience.

To intall uploadprogress module:

1. install php development, pecl, pear, and development tools if you not yet have them installed:

yum -y install php-devel php-pecl php-pear
yum -y groupinstall "Development Tools"

2. install the upload progress:

pecl install uploadprogress

This is what you should get:

[root@xxx]# pecl install uploadprogress
downloading uploadprogress-1.0.1.tgz ...
Starting to download uploadprogress-1.0.1.tgz (8,536 bytes)
.....done: 8,536 bytes
4 source files, building
running: phpize
Configuring for:
PHP Api Version: 20041225
Zend Module Api No: 20060613
Zend Extension Api No: 220060519
building in /var/tmp/pear-build-root/uploadprogress-1.0.1
running: /var/tmp/uploadprogress/configure
checking for egrep... grep -E
checking for a sed that does not truncate output... /bin/sed
checking for cc... cc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether cc accepts -g... yes
checking for cc option to accept ANSI C... none needed
checking how to run the C preprocessor... cc -E
checking for icc... no
checking for suncc... no
checking whether cc understands -c and -o together... yes
checking for system library directory... lib
checking if compiler supports -R... no
checking if compiler supports -Wl,-rpath,... yes
checking build system type... i686-redhat-linux-gnu
checking host system type... i686-redhat-linux-gnu
checking target system type... i686-redhat-linux-gnu
checking for PHP prefix... /usr
checking for PHP includes... -I/usr/include/php -I/usr/include/php/main -I/usr/include/php/TSRM -I/usr/include/php/Zend -I/usr/include/php/ext -I/usr/include/php/ext/date/lib
checking for PHP extension directory... /usr/lib/php/modules
checking for PHP installed headers prefix... /usr/include/php
checking if debug is enabled... no
checking if zts is enabled... no
checking for re2c... no
configure: WARNING: You will need re2c 0.13.4 or later if you want to regenerate PHP parsers.
checking for gawk... gawk
checking whether to enable uploadprogress functions... yes, shared
checking for ld used by cc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for /usr/bin/ld option to reload object files... -r
checking for BSD-compatible nm... /usr/bin/nm -B
checking whether ln -s works... yes
checking how to recognise dependent libraries... pass_all
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking for g77... no
checking for f77... no
checking for xlf... no
checking for frt... no
checking for pgf77... no
checking for fort77... no
checking for fl32... no
checking for af77... no
checking for f90... no
checking for xlf90... no
checking for pgf90... no
checking for epcf90... no
checking for f95... f95
checking whether we are using the GNU Fortran 77 compiler... yes
checking whether f95 accepts -g... yes
checking the maximum length of command line arguments... 32768
checking command to parse /usr/bin/nm -B output from cc object... ok
checking for objdir... .libs
checking for ar... ar
checking for ranlib... ranlib
checking for strip... strip
checking if cc supports -fno-rtti -fno-exceptions... no
checking for cc option to produce PIC... -fPIC
checking if cc PIC flag -fPIC works... yes
checking if cc static flag -static works... yes
checking if cc supports -c -o file.o... yes
checking whether the cc linker (/usr/bin/ld) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
configure: creating libtool
appending configuration tag "CXX" to libtool
appending configuration tag "F77" to libtool
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
checking for f95 option to produce PIC... -fPIC
checking if f95 PIC flag -fPIC works... yes
checking if f95 static flag -static works... yes
checking if f95 supports -c -o file.o... yes
checking whether the f95 linker (/usr/bin/ld) supports shared libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
configure: creating ./config.status
config.status: creating config.h
running: make
/bin/sh /var/tmp/pear-build-root/uploadprogress-1.0.1/libtool --mode=compile cc -I. -I/var/tmp/uploadprogress -DPHP_ATOM_INC -I/var/tmp/pear-build-root/uploadprogress-1.0.1/include -I/var/tmp/pear-build-root/uploadprogress-1.0.1/main -I/var/tmp/uploadprogress -I/usr/include/php -I/usr/include/php/main -I/usr/include/php/TSRM -I/usr/include/php/Zend -I/usr/include/php/ext -I/usr/include/php/ext/date/lib -DHAVE_CONFIG_H -g -O2 -c /var/tmp/uploadprogress/uploadprogress.c -o uploadprogress.lo
mkdir .libs
cc -I. -I/var/tmp/uploadprogress -DPHP_ATOM_INC -I/var/tmp/pear-build-root/uploadprogress-1.0.1/include -I/var/tmp/pear-build-root/uploadprogress-1.0.1/main -I/var/tmp/uploadprogress -I/usr/include/php -I/usr/include/php/main -I/usr/include/php/TSRM -I/usr/include/php/Zend -I/usr/include/php/ext -I/usr/include/php/ext/date/lib -DHAVE_CONFIG_H -g -O2 -c /var/tmp/uploadprogress/uploadprogress.c -fPIC -DPIC -o .libs/uploadprogress.o
/bin/sh /var/tmp/pear-build-root/uploadprogress-1.0.1/libtool --mode=link cc -DPHP_ATOM_INC -I/var/tmp/pear-build-root/uploadprogress-1.0.1/include -I/var/tmp/pear-build-root/uploadprogress-1.0.1/main -I/var/tmp/uploadprogress -I/usr/include/php -I/usr/include/php/main -I/usr/include/php/TSRM -I/usr/include/php/Zend -I/usr/include/php/ext -I/usr/include/php/ext/date/lib -DHAVE_CONFIG_H -g -O2 -o uploadprogress.la -export-dynamic -avoid-version -prefer-pic -module -rpath /var/tmp/pear-build-root/uploadprogress-1.0.1/modules uploadprogress.lo
cc -shared .libs/uploadprogress.o -Wl,-soname -Wl,uploadprogress.so -o .libs/uploadprogress.so
creating uploadprogress.la
(cd .libs && rm -f uploadprogress.la && ln -s ../uploadprogress.la uploadprogress.la)
/bin/sh /var/tmp/pear-build-root/uploadprogress-1.0.1/libtool --mode=install cp ./uploadprogress.la /var/tmp/pear-build-root/uploadprogress-1.0.1/modules
cp ./.libs/uploadprogress.so /var/tmp/pear-build-root/uploadprogress-1.0.1/modules/uploadprogress.so
cp ./.libs/uploadprogress.lai /var/tmp/pear-build-root/uploadprogress-1.0.1/modules/uploadprogress.la
PATH="$PATH:/sbin" ldconfig -n /var/tmp/pear-build-root/uploadprogress-1.0.1/modules
----------------------------------------------------------------------
Libraries have been installed in:
/var/tmp/pear-build-root/uploadprogress-1.0.1/modules

If you ever happen to want to link against installed libraries
in a given directory, LIBDIR, you must either use libtool, and
specify the full pathname of the library, or use the `-LLIBDIR'
flag during linking and do at least one of the following:
- add LIBDIR to the `LD_LIBRARY_PATH' environment variable
during execution
- add LIBDIR to the `LD_RUN_PATH' environment variable
during linking
- use the `-Wl,--rpath -Wl,LIBDIR' linker flag
- have your system administrator add LIBDIR to `/etc/ld.so.conf'

See any operating system documentation about shared libraries for
more information, such as the ld(1) and ld.so(8) manual pages.
----------------------------------------------------------------------

Build complete.
Don't forget to run 'make test'.

running: make INSTALL_ROOT="/var/tmp/pear-build-root/install-uploadprogress-1.0.1" install
Installing shared extensions: /var/tmp/pear-build-root/install-uploadprogress-1.0.1/usr/lib/php/modules/
running: find "/var/tmp/pear-build-root/install-uploadprogress-1.0.1" | xargs ls -dils
27529277 4 drwxr-xr-x 3 root root 4096 Jul 22 00:48 /var/tmp/pear-build-root/install-uploadprogress-1.0.1
27529298 4 drwxr-xr-x 3 root root 4096 Jul 22 00:48 /var/tmp/pear-build-root/install-uploadprogress-1.0.1/usr
27529299 4 drwxr-xr-x 3 root root 4096 Jul 22 00:48 /var/tmp/pear-build-root/install-uploadprogress-1.0.1/usr/lib
27529300 4 drwxr-xr-x 3 root root 4096 Jul 22 00:48 /var/tmp/pear-build-root/install-uploadprogress-1.0.1/usr/lib/php
27529301 4 drwxr-xr-x 2 root root 4096 Jul 22 00:48 /var/tmp/pear-build-root/install-uploadprogress-1.0.1/usr/lib/php/modules
27529297 44 -rwxr-xr-x 1 root root 43639 Jul 22 00:48 /var/tmp/pear-build-root/install-uploadprogress-1.0.1/usr/lib/php/modules/uploadprogress.so

Build process completed successfully
Installing '/usr/lib/php/modules/uploadprogress.so'
install ok: channel://pecl.php.net/uploadprogress-1.0.1
configuration option "php_ini" is not set to php.ini location
You should add "extension=uploadprogress.so" to php.ini

3. add the extension to php.ini:

extension=uploadprogress.so

4. restart apache for the changes to take effect.

service httpd restart

Verizon Getting Closer To Blending TV With Web

Verizon plans to open up its cable TV boxes to outside developers, just like Apple did with its iPhone. This is an image of the Twitter application as it will run on the Verizon FiOS cable TV system.

full story

Related: Analyst: Telecoms could learn from Verizon’s IPTV moves

‧聯合新聞網 2009/07/09
一個代表藝人與唱片業者的協會已和網路電台業者達成授權協議,這場長達兩年的版稅戰爭終於塵埃落定,並使原處灰色地帶的網路電台業撥雲見日。

網路廣播業者潘朵拉公司(Pandora)創辦人魏斯格林說:「相較於歌曲按首計費,這是大幅的減讓。」潘朵拉計劃今年要播放10億小時的歌曲,以往因為授權費談不攏,難以和其他業者討論合作。現在,魏斯格林說,「我們總算走過去了」。

但由於這項版稅協議,潘朵拉計劃對用戶收取額外費用。每月收聽逾40小時的「重度使用者」要繳交0.99美元,才能在該月繼續聽音樂。

依照2007年原定的版稅收費法,網路廣播業要在每個人收聽每首歌時繳交0.08美分,到2010年時漲至每人每首0.19美分。這種收費法讓網路廣播業者大嘆付不起,更曾組織過「寂靜之日」,全體停播一天,以示抗議。

現在,網路廣播業者和代表版權人的SoundExchange達成協議,年營收125萬美元以上的網路廣播台必須付至少25%的營收取得授權,或是也可用每人每首0.093美分付費,2015年時漲價至每人每首0.14美分。

營收125萬美元以下的網路廣播業者,則須支付7%的費用、或10%至14%的銷售,以取得使用授權。向聽戶收取月費的網路廣播電台,則要為每首歌每位訂戶付0.15美分,2015年時增至0.25美分。

這些付費方式僅限於「純網路」的廣播業者,那些把AM、FM無線廣播內容放到網路上的廣播公司,不適用這個付費方式。今年稍早,代表傳統無線電台的美國全國廣播協會(NAB)已和SoundExchange達成付費方式的協議。

美國人使用網路廣播的人數呈現爆炸性成長,根據Arbitron與Edison研究公司調查,目前每周有4,200萬美國人開機收聽網路廣播,比2004年的1,900萬人大幅增多。

代表參與談判的網路廣播業者包括AccuRadio、Digitally Imported與RadioIO。網路廣播業者可以在30天內決定是否要接受這項協議,或者逕用2007年的收費標準,或者直接向各歌曲的版權商談授權費。

經濟日報╱編譯陳家齊/綜合外電

‧聯合新聞網 2009/07/16
中華電信與台灣大哥大的網際網路互連費用爭議,國家通訊傳播委員會(NCC)昨(15)日表示,公告新牌價為每Mbps1,480元,且用愈多愈便宜,將有大量使用折扣表,若以業者平均1,800元來說,將便宜三成左右。

但這個價格對於新進固網業者要求的每M為300元至500元的理想價格,實在是差很大。新進固網業者說,只能「含淚接受」,希望主管機關-NCC能從長遠的產業政策來看,進一步修改不合時宜的法令,建立業者間的合理互連機制。

業者間的牌價將降低,NCC昨日並指出,ADSL電路費實施價格管制方案,三年降價期限將在明年4月截止,NCC正檢討費率中,據NCC高層指出,明年「應該會再調降」,且NCC將實施最低保證頻寬,保障消費者權益。

經濟日報╱記者余麗姿/台北報導

A few app requires PHP 5.2.x but major repositories is yet support anything higher than 5.1.6 at this time. Recompile PHP is a pain also.

Remi maintains a repository that can save your 1 day or 2 if you have such need.

cd /etc/yum.repos.d/
wget http://download.fedora.redhat.com/pub/epel/5/i386/epel-release-5-3.noarch.rpm
wget http://rpms.famillecollet.com/enterprise/remi-release-5.rpm
rpm -Uvh remi-release-5*.rpm epel-release-5*.rpm

You now have Remi repository on your system. It’s disabled by default, and I recommend you leave it as is. To install from remi, run the following:

yum --enablerepo=remi update php

I use remi to install php and its related stuff like GD, mcrypt, etc. As well as MySQL. The repository rocks!

A few app requires PHP 5.2.x but major repositories is yet support anything higher than 5.1.6 at this time. Recompile PHP is a pain also.

Remi maintains a repository that can save your 1 day or 2 if you have such need.

cd /etc/yum.repos.d/
wget http://download.fedora.redhat.com/pub/epel/5/i386/epel-release-5-3.noarch.rpm
wget http://rpms.famillecollet.com/enterprise/remi-release-5.rpm
rpm -Uvh remi-release-5*.rpm epel-release-5*.rpm

You now have Remi repository on your system. It’s disabled by default, and I recommend you leave it as is. To install from remi, run the following:

yum --enablerepo=remi update php

I use remi to install php and its related stuff like GD, mcrypt, etc. As well as MySQL. The repository rocks!

I’ve put together old hardware pieces at home for a download & file sharing box. It got 4 old disks (30G, 250G, 500G, 80G) together. Knowing that disks will out of its life sooner or later, I rsync important stuff to the mac next to it. Couple weeks ago, shit finally happen.

The broken disk is the 30G, so most of stuff are still in the other disks. To recover, I put into a new disk, re-install CentOS, so the box is bootable again. Now I need to re-activate and mount the old disks.

Re-install CentOS
1.Put in the new disk, go to Bios and make sure CD-ROM is having first boot priority, and the new disk is the boot disk in Hard Disk boot priority setting.
2.Put in the CentOS DVD, boot from it. In the install process, make sure you don’t re-partition the old disks.
3.If you are not sure what to do, you can un-plug the power cores of all old disks, install on the new disk first. Once the installation is finished, plug back the power of old disks, boot from DVD again, and reset the boot loader.
4.Now you’ve got a bootable box with all the disks in place.

RHEL systems like Red Hat, CentOS or Fedora, partition the disks automatically at install time. By default, it sets up the partitions using LVM for the root device.
By default, the OS set up a volume group called VolGroup00, with two logical volumes, LogVol00 and LogVol01, the first for the root directory and the second for swap.

Since the new disk is big enough, I set up the new disk (not using the volume). As you can see in the partition layout of physical disks below (/dev/sda is the new disk):
[root@xxx]# sfdisk -l

Disk /dev/hda: 19457 cylinders, 255 heads, 63 sectors/track
Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0

Device Boot Start End #cyls #blocks Id System
/dev/hda1 * 0+ 19456 19457- 156288321 8e Linux LVM
/dev/hda2 0 - 0 0 0 Empty
/dev/hda3 0 - 0 0 0 Empty
/dev/hda4 0 - 0 0 0 Empty

Disk /dev/hdc: 24792 cylinders, 255 heads, 63 sectors/track
Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0

Device Boot Start End #cyls #blocks Id System
/dev/hdc1 * 0+ 24791 24792- 199141708+ 8e Linux LVM
/dev/hdc2 0 - 0 0 0 Empty
/dev/hdc3 0 - 0 0 0 Empty
/dev/hdc4 0 - 0 0 0 Empty

Disk /dev/sda: 38913 cylinders, 255 heads, 63 sectors/track
Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0

Device Boot Start End #cyls #blocks Id System
/dev/sda1 * 0+ 12 13- 104391 83 Linux
/dev/sda2 267 38912 38646 310423995 83 Linux
/dev/sda3 13 266 254 2040255 82 Linux swap / Solaris
/dev/sda4 0 - 0 0 0 Empty

Disk /dev/sdb: 60801 cylinders, 255 heads, 63 sectors/track
Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0

Device Boot Start End #cyls #blocks Id System
/dev/sdb1 * 0+ 60800 60801- 488384001 8e Linux LVM
/dev/sdb2 0 - 0 0 0 Empty
/dev/sdb3 0 - 0 0 0 Empty
/dev/sdb4 0 - 0 0 0 Empty

To re-activate and re-mount
vgchange is the utility to update/change your volume group attribute. Since one of the disk in previous volume is missing, I need to vgchange –ay –partial to activate the volume.

[root@xxx]# vgchange –ay –partial
Couldn't find device with uuid 'AiegxE-NfQy-AA5E-OUcn-bvpY-UG3o-5oT1gY'.
/dev/mapper/VolGroup00-LogVol00-missing_3_0: read failed after 0 of 4096 at 0: Input/output error
/dev/mapper/VolGroup00-LogVol01-missing_0_0: read failed after 0 of 4096 at 0: Input/output error
/dev/VolGroup00/LogVol01: read failed after 0 of 4096 at 0: Input/output error
Couldn't find device with uuid 'AiegxE-NfQy-AA5E-OUcn-bvpY-UG3o-5oT1gY'.
2 logical volume(s) in volume group "VolGroup00" now active

Well, a lot of error due to the missing disk, but the volume is active now. You can verify by:

[root@xxx]# lvscan
/dev/VolGroup00/LogVol00: read failed after 0 of 4096 at 892413607936: Input/output error
/dev/VolGroup00/LogVol00: read failed after 0 of 4096 at 892413665280: Input/output error
/dev/mapper/VolGroup00-LogVol01-missing_0_0: read failed after 0 of 4096 at 2080309248: Input/output error
/dev/mapper/VolGroup00-LogVol01-missing_0_0: read failed after 0 of 4096 at 4096: Input/output error
/dev/mapper/VolGroup00-LogVol01-missing_0_0: read failed after 0 of 4096 at 0: Input/output error
/dev/VolGroup00/LogVol01: read failed after 0 of 4096 at 2080309248: Input/output error
/dev/VolGroup00/LogVol01: read failed after 0 of 4096 at 2080366592: Input/output error
Couldn't find device with uuid 'AiegxE-NfQy-AA5E-OUcn-bvpY-UG3o-5oT1gY'.
/dev/mapper/VolGroup00-LogVol00-missing_3_0: read failed after 0 of 4096 at 0: Input/output error
/dev/VolGroup00/LogVol01: read failed after 0 of 4096 at 0: Input/output error
Couldn't find device with uuid 'AiegxE-NfQy-AA5E-OUcn-bvpY-UG3o-5oT1gY'.
/dev/mapper/VolGroup00-LogVol00-missing_3_0: read failed after 0 of 4096 at 0: Input/output error
/dev/VolGroup00/LogVol01: read failed after 0 of 4096 at 0: Input/output error
Couldn't find device with uuid 'AiegxE-NfQy-AA5E-OUcn-bvpY-UG3o-5oT1gY'.
ACTIVE '/dev/VolGroup00/LogVol00' [831.12 GB] inherit
ACTIVE '/dev/VolGroup00/LogVol01' [1.94 GB] inherit

Now you can mount the active volume by:
[root@xxx]# mount /dev/VolGroup00/LogVol00 /mnt

The old volume is now accessible at /mnt
[root@xxx]# ls –al /mnt

What Next
I copy the stuff I want to recover. What to do with the old drives? I need to think about…Having a old box on all time is actually costly (in term of electric bill). But having a box on is handy in many occurrences..

Ref:
http://www.linuxjournal.com/article/8874
http://fedoraforum.org/forum/archive/index.php/t-64964.html