Example
df
/dev/sda34 124427 12078 105925 11% /boot

Is this case I am only using 11% of my boot after cleaning up the unused kernel images.

The Fedora Community has released a Open Source script under the GNU Licensing called Kernel-prune . you can download this script using the following command via ssh

curl -O ‘http://skvidal.fedorapeople.org/misc/kernel-prune.py’

You will then need to make the python script executable by issuing
chmod a+x kernel-prune.py

Then running it using ./kernel-prune.py
The return value will give you a list of unused kernel images which can be safely removed from your system.

To remove the kernels I created a file called cleanboot and added the following content
PKGS=`./kernel-prune.py`
echo $PKGS
yum remove $PKGS

Again making this new file executable using
chmod a+x cleanboot

Then running the file as ./cleanboot

The script will ask you if you would like to remove the unused kernel packages , hit Y for yes and give it a few moments. Perform a reboot and you should be all set.

This script may work on centos and other distros , but i have not tested this solution on those systems. Please make a backup of your data before proceeding with this process.

Thanks,

When trying to enable imagemagick within Gallery2 by Menalto

Check your php,ini file for a directive open_basedir

add the root path that contains the convert binary , so for example if convert is at /usr/bin/convert
set the basedir to
open_basedir = /your/home:/usr/bin

without this settings you will not have access to the /usr/bin folder.

This occurred when using a live cd in a virtual player under bridge mode. The app loads after a virtual player reboot, but restarting the service within ssh returned the error. So I did a hard reboot on the host machine which resolve the issue.

You will also need to make sure the host name is correct in the ejabberd cfg file.

JAuthentication::__construct: Could not load authentication libraries.

solution..

Make sure the authentication plugin is enabled ..
in the Joomla database, and changed it’s published status to 1 in the “jos_plugins” table.

error:
Software error: Can’t locate Calendar/CalciumStart.pm in @INC (@INC contains: CalciumDir40/upgrades CalciumDir40/redist …

Solution:
A message like this means that Calcium can’t find its installation directory. The location of the Calcium source code files and data directory are specified in the main Calcium script; some installations will require the full path to the Calcium installation directory here, instead of a relative path. To fix this, edit the main script (Calcium40.pl), and change the line near the top that looks like this:
BEGIN {$Defines::calendar_root = ‘CalciumDir40′}
Replace CalciumDir40 with the full filesystem path to that directory. For example, something like:
BEGIN {$Defines::calendar_root = ‘C:\public\html\cgi-bin\CalciumDir40′}
or maybe
BEGIN {$Defines::calendar_root = ‘/usr/local/apache/cgi-bin/CalciumDir40′}
should help.

Run
yum install vim-enhanced

or within vi
:syntax on

ssh-keygen -t rsa

It will ask you for a password but you can leave it blank.

Note you could also pick -t dsa if you prefer.

Ensure that the remote server has a .ssh directory

Make sure the server your connecting to has a .ssh directory in your home
directory. If it doesn’t exist you can run the ssh-keygen command above, and
it will create one with the correct permissions.

Copy your local public key to the remote server

If your remote server doesn’t have a file called ~/.ssh/authorized_keys2
then we can create it. If that file already exists, you need to append to it
instead of overwriting it, which the command below would do:
scp ~/.ssh/id_rsa.pub remote.server.com:.ssh/authorized_keys2

Now ssh to the remote server

Now you can ssh to the remote server without entering your password.

background: tried to add a custom error page caused a 500 internal server error to be displayed.

The error was cleared by making some changes to my htaccess file which included some rewrite directive. Another option may be to add the custom error directive to the .htaccess file.

You will need to make sure the /cache/theme folder has the proper permissions.

Solution: this issue was resolve in version ImageMagick 6.4.4-9
you will need to upgrade to the latest version

Test script to see if you need to upgrade

#!/usr/bin/perl -w

print "<h1>$is_Magick</h1>";

Reference