Installing PHP 5.2.10 on CentOS 5.5 in 6 steps

Recently I ran into the problem to update PHP on a CentOS 5.5 server from version 5.1.6 to 5.2 or higher. The reason was that I wanted to test Drupal 7 on a virtual machine the first time.

As a fact for Drupal, Drupal 7 needs PHP 5.2.5 or higher as a requirement. But a simple "php -version" revealed that CentOS only comes with version 5.1.6. Understandably, because CentOS is a server operating system an only provides stable packages in their repositories.

Anyway, a simple "yum update php" only says "nothing to do", so here is the hack to get a more recent PHP on the server:

1. Get root.
2. Make sure that you are only using standard PHP packages, remove the other ones (for now). You can get a list of installed php packages using the commands "rpm -qa |grep php".
3. Add the deployment repositories through (editing) creating the file "/etc/yum.repos.d/CentOS-Testing.repo". Insert the following lines (without spaces at the start):
   [c5-testing]
   name=CentOS-5 Testing
   baseurl=http://dev.centos.org/centos/$releasever/testing/$basearch/
   enabled=1
   gpgcheck=1
   gpgkey=http://dev.centos.org/centos/RPM-GPG-KEY-CentOS-testing
   includepkgs=php*
4. Update PHP through the command "yum update".
5. Resart the Apache web server (or any webserver you use) through "service httpd restart" or "apachectl restart".
6. Test the version of PHP:
   [root]# php -version
   PHP 5.2.10 (cli) (built: Nov 13 2009 11:44:05) Copyright (c) 1997-2009 The PHP Group Zend Engine v2.2.0,
   Copyright (c) 1998-2009 Zend Technologies
   

That pretty was it. If you had non-standard-packages, reinstall them now.

Video: Opera response to Google Chrome's speed test video

Remember the Google Chrome speed / performance test video? Well, Opera responded with an own performance test video as a reply to Google.

As known, the Opera browser and Google's Chrome are fighting for the fastest-browser-in-the-world crown and Opera is catching up right now with a faster Javascript engine in Opera 10.50. Time do do a little performance testing:

But though both tests do compare the respective performance using the all-known-potato-method, you cannot be exactly sure if a comparison can be done really accurately. Judge yourself.

Chrome performance better than lightning (or a potato canon)

Well, everyone already had the idea that Google's Chrome browser is one of the fastest browser out there. Be it rendering (by using the WebKit) or JavaScript (with the V8 engine), even giving every tab an own process seems to help.

But, until today, I did not know that Chrome is faster than sound or a flash (thunder and lightning). Or even... an ordinary potato gun.

Evidence needed? Watch this video, it explains how that is possible (scientifically).

Who would have thought that a browser outranges a potato canon? Well, now we know.

Five reasons why Apple can/should/could create a tablet-PC (and five why not)

So there are many rumours (or should we say "reasons"?) why Apple will release a kind of tablet PC on Jan 26th. No one knows, everyone speculates, but let us be honest: Technically, they could. And for me to look into the glass ball: At Jan, 26th, Steve will introduce a device pretty the same like the iPod Touch with a 7" display, having wireless and a OS X. But that is just the beginning.

Marketing and the name will be important

Most rumours go for the name. May it be iSlate, or iGuide (here too), no one knows (despite the fact that both seem to be aquired / protected by Apple's employe "Regina Porter" and Apple's commissioned lawyers). I, personally, go for something else. "iSlate" or "iGuide" does not sound like Apple for me. Better would be "iTouch" or "iBook Touch", something like that. But here, iThink, we will have to wait for Apple's last call.

Apart from the good kind of selection depending on names, Apple's congeniality is not ultimately found in technical reasons. It is founded in design and pretty useable products. And their placement in the market.

Other markets emerge, existing markets got complex

Having the netbook market exploding these days and (for a newbee at the phonie-thingies) some drawbacks at the mobile market which might, on the long tail, get serious for production costs and/or customer revenues, Apple is smart enough to engage new markets. So let us have a look on why Apple should expand their market introducing a complete new device to the market.

Five reasons why Apple can/should/could create a tablet-PC (and five why not):

1. Technically they have OS X for iPhone and therefore "Cocoa Touch" which is needed to run a successful tablet PC nowadays (fast enough multitouch applications).

2. Rumours say that Apple worked four years on something like a touch-PC, if they are not ready yet with their experience on Cocoa Touch, they never will be.

3. Rumours say that Apple is asking software deliverers to not only work for the resolution of iPhone/iPod Touch but to modify their software to work on bigger screen resolutions.

4. Having 100.000 "Apps" in their market place that might be easily modified would help a lot to implement a new platform.

5. After the success of the iPhone everyone will listen to a new device, even if it is "yet another touch PC" - marketing is on their side.

Where there is much light, there is shadow, too. Five reasons against:

1. A tablet PC needs to cope with all functionalities of a normal PC. Can Cocoa Touch be married with OS X at a glance? Windows 7 has it built in.

2. You never can copy a success story in IT-world. After the success of the iPhone, the Apple touch-PC should be a burner, having much more functionality than the iPhone (else it would only fill an niche).

3. Apple is (at the moment) forced to get functionalities to the iPhone other mobile companies have, should they open a second front at tablet-PC's or concentrate to what they have/need to do?

4. Pricing will be critical. Selling an iPhone at $199 which then is partly payed by a telecommunication partner is cheaper than selling a new kind of device at Apple's own [risk] (rumours say it should be well under $1000)

5. January 26th is a date the media knows (now). Steve Jobs has to deliver (something - read the link tot he end). Hopefully he is not taking his mouth too full (or didn't at the past without saying something... ).

Words from the editor (please only read if you want to):

Well, I would not call it "words from the editor" here at the end of this blog. I'd call it: Rumours. I researched a lot depending the Apple-tablet-thingie going on. My opinion is that Apple will - at best - deliver a gizmo working with a 7" touch display on Jan, 26.

On the other hand I read that they will only get new gadgets 'n gizmos for the iPhone on this date. No one can tell, but one thing is clear: Apple does, let's says since mid 2007, not always move fast enough. Nowadays they have to move. Kind of fast. Others do.

So my guess for the future is: On Jan, 26th, Steve introduces iPhone 4.0 :) or something like a "iBook Touch". Starting at 7", getting to 10.1" (promised middle of 2010).

Quotes for large software projects

Again it is time to talk about larger software projects. This time not only about the "how's" and "where's", let us take a more... humorous approach. Let us have some famous qoutes you could use to get some brains straight back to line.

If someone shows off a very complicated software design to you, consider to quote the following:

"There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult."

C.A.R. Hoare

Let's say everything in a huge project is clear - theoretically. Why should implementing it be difficult? Because...

"In theory, theory and practice are the same. In practice, they're not."

Yogi Berra

Long-year-experience and wisdom from my friends:

"Frameworks like Ruby on Rails exist to make simple things even more simple and complex things impossible."

A colleague of mine

A deadline bites. But again, time - while developing in a large project - is somewhat relative:

"The first 90% of the code accounts for the first 90% of the development time. The remaining 10% of the code accounts for the other 90% of the development time."

Tom Cargill

Cutting the development time by throwing more developers into a project? Reply this:

"Nine people can't make a baby in a month."

Fred Brooks

Not exactly valueable for large projects, but, alas, said by a great man:

"Whereas Europeans generally pronounce my name the right way ('Nick-louse Veert'), Americans invariably mangle it into 'Nickel's Worth.' This is to say that Europeans call me by name, but Americans call me by value."

Niklaus Wirth

Something every programmer of a large project at least said once in his life:

"It works on my machine."

Anonymous Programmer

And, one of my favourites, not exactly from a programmer (but a wise man):

"Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away."

Antoine de Saint Exupéry

Look out for some more quotes at "Quotes: 5 different views on computers and programs".