Tuesday, August 05, 2008

Building a L.A.M.P. Server on OS X framework - PART 1


For my L.A.M.P. project, running on an older machine and acting as a test server I was going to use an old Macintosh G4 (the Original Graphite), but decided against it. Why? Seems that a 512MB - G4 running at 400MHz machine might not be enough to do the job. So, I selected an iBook G4 (1GHz with 1.2GB of RAM), 14.1” screen. This also gives me the ability of taking my test server with me if I want to work on the road.

I will be downloading and installing the following software, which are freeware for the most part. There are many sites that actually have step-by-step instruction and how-tos that cover every aspect of the operation. L.A.M.P. stands for Linux – Apache – MySQL and PHP. This L.A.M.P. in reality will be an O.A.M.P., since I replaced the Linux with OS X. So here is a list of server software that is needed to setup a functioning L.A.M.P. Server:

1. Operating system: I chose Apple Mac Server Tiger (10.4.11) as the operating system of my new L.A.M.P. machine. I was going to use the Leopard server (10.5.4), but then I decided against it. The tiger version already is a strain on this hardware

2. MySQL: I downloaded the MySQL server from their site directly. I chose the version 4.1 that is used very widely because of its stability and bug fixes. As it is with the most UNIX and Linux program that you download, you have to recompile the whole thing locally and it is highly suggested that you compile the whole thing on the same machine that you want to run it on. I was thinking to compile the whole thing under my newer and faster Mac. But no cigar – must be compiled on target machine. This will be an overnight job. So tonight before I go to bed, I will setup the little iBook to compile the whole big-bad-wolf MySQL (poor iBook, talk about torture!).

3. Apache 2.2: This is an adventure by itself. Apple ships OS X server with the Apache 1.3. I am planning to use Apache 2.2+ in my L.A.M.P. But this is more complicated than it seems, since they suggest that you remove the older version first and then download and recompile the newer one. I am looking forward to this, since I have never removed Apache server in its entirety.

Here was what has been done up to now. In part two, I will go thru the details of installing and configuring the MySQL server.

Monday, August 04, 2008

How to save iPhone battery

How to save iPhone battery and make iPhone less functional than a Razr:


1. Turn off Push Mail!

The most important selling pitch that Apple made to the IT community was the fact that the new iPhone 3G and the new version of iPhone Firmware will bring Push Mail to the table. Now they suggest switching it off to save battery? Makes no sense to me, since if you turn off that feature, then how would a Server push email to that device! Hmmm! Strike one…

2. Minimize the use of 3rd party Applications!

The second exciting feature in iPhone is the fact that Apple opened it up for the developers to build applications so we can easily download them via the AppStore, which in it’s own right is another exciting feature of the new iPhone 3G. Here they are now suggesting that we should not use this feature that we were so excited about was so exciting about. Hmmm! Strike two…

3. Turn Off 3G!

Another huge improvement over the original iPhone has been the addition of High-speed 3G systems. Faster Data – Video – and MMS (oops I forgot that iPhone has no video or MMS! LOL! Forgive me), suffice to say that 3G does all that much faster. Here they are now suggesting that the owners of the new iPhone 3G could turn this important function off to save battery? Hmmm! Strike three…

4. Minimize the use of Location services!

Yet another important functionality of iPhone is under attack for the sake of saving battery. GPS and Maps and location services are another important functionality that has been added to the new iPhone. To save battery we are suppose to turn this one off too? Hmmm! Strike four…

5. Turn off Bluetooth!

By Law, in most States and Provinces in North America, the use of hands free / Bluetooth is compulsory when driving! We know that this law has passed to minimize the loss attention from the actual driving that is brought about by a cell phone. Here we are again, being told not to use this Bluetooth, so we can save battery and quiet possibly cause accidents in our highways and byways! Hmmm! Strike five…

6. Turn off WiFi!

Another very useful feature of the iPhone is wireless 802.11G/N. This in it self is a very taxing feature on the battery. But if this service is available in the area, this could be the most useful feature of the phone. Since you have already turned off your Bluetooth, disabling this feature will totally deprive you of any type networking. Turning this feature of sometimes might be ok. But permanently – hmmmmm! Strike six…

7. Turn off that EQ!

This one truly takes the cake! EQ? How much battery could that use and how weak this batter is? I was under the impression that Nokia N95-8GB was bad with the battery. Seems it has direct and close competition, with one small difference; N95 has replaceable batteries!

When this phone was being designed and all these feature were included in to the design of this phone – wasn’t there even one hardware Eng. that could stand up to Mr. Jobs and state clearly that this battery won’t be able to handle all these features! Either provide a way to replacement batteries or come up with a more realistic design? And they say that software Engineers are kinda strange! One look at the hardware will tell you what we go thru to deal with it. I truly believe, if an iPhone owner follow all this advice – his/her iPhone will be functionally reduced to lower than a Motorola Razr.