Archive for April, 2007

PHP 5.2 on fresh HD installation

tom on April 13th, 2007

I was installing PHP 5.2 with GD support on a brand spanking new HD.

With a ./configure like:

./configure –enable-fastcgi –enable-discard-path –enable-force-redirect –with-gd –with-jpeg-dir=/usr/local/lib –with-png-dir=/usr/local/lib

You will definitely need some dependencies. Here is how I solved them Read the rest of this entry »

Post a comment | Comments Off

Error when installing Lighttpd 1.5 – gthread-2.0 requirements

tom on April 13th, 2007

I was installing lighttpd 1.5 the other day when I received this error:

configure: error: Package requirements (gthread-2.0 >= 2.4.0) were not met:

The new lighttpd 1.5 requires glib2-2.4.0 or greater. Thus, to install the necessary files, simply type:

# yum install glib2-devel

And you are all set.

Post a comment | Comments Off

How to change the linux login banner/message

tom on April 12th, 2007

The login banner is essential to legal actions taken against people who misuse and illegally hack into your box. There have been cases where the hackers got off because the server they hacked into actually “Welcomed” them into the system!

To change the login banner/welcome message, simply edit the /etc/issue file.

#vi /etc/issue

Should do the trick!

Post a comment | Comments Off

Device: /dev/hda, 3 Offline uncorrectable sectors

tom on April 9th, 2007

If you are finding this in your /var/log/messages file, it most likely means your Harddrive is failing or going to fail very soon.

I tried fscking it

# fsck /dev/hda

However that returned:
Couldn’t find ext2 superblock, trying backup blocks…
fsck.ext2: Bad magic number in super-block while trying to open /dev/hda

The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>

Which means it definitely is the harddrive failing. Time to replace it!