Checking For and Updating Packages
To see which installed packages on your system have updates available, use the following command:
Updating Packages
You can choose to update a single package, multiple packages, or all packages at once. If any dependencies of the package (or packages) you update have updates available themselves, then they are updated too.
Updating a Single Package
To update a single package, run the following command as root:
Updating All Packages and Their Dependencies
To update all packages and their dependencies, simply enter yum update (without any arguments):
Necessary packages for ffmpeg and ffmpeg-php Install
First run the command uname to find the arch
Then download rpmforge-release
rpm -Uhv http://packages.sw.be/rpmforge-release/rpmforge-release-0.5.1-1.el5.rf.x86_64.rpm
yum clean all
yum update
yum install ffmpeg ffmpeg-devel
yum install mplayer mencoder
yum install gcc gmake make libcpp libgcc libstdc++ gcc4 gcc4-c++ gcc4-gfortran
yum install subversion ruby ncurses-devel ruby-libs
yum install flvtool2*
Run svn checkout:
svn checkout svn://svn.mplayerhq.hu/ffmpeg/trunk ffmpeg
svn checkout svn://svn.mplayerhq.hu/mplayer/trunk mplayer
cd /usr/local/src/mplayer
svn update
cd /usr/local/src
Copy codecs for mplayer:
mv /usr/local/src/essential-20061022/* /usr/local/lib/codecs/
chmod -R 755 /usr/local/lib/codecs/
If you are using secure tmp:
mkdir /usr/local/src/tmp
chmod 777 /usr/local/src/tmp
export TMPDIR=/usr/local/src/tmp
For ffmpeg-php
wget http://downloads.sourceforge.net/project/ffmpeg-php/ffmpeg-php/0.6.0/ffmpeg-php-0.6.0.tbz2?use_mirror=nchc
tar -xjf ffmpeg-0.5.2.1.tbz2
phpize
./configure
make
make install
How to protect one Yum repo’s packages from being replaced by packages from another source?
If we use two different repositories, each holding a different version of the same package, only the latest of the two will be installed if you use yum to update that package. This can lead to problems if the third party repository contains a newer version of a core system package than the Red Hat repository.
The yum-protectbase plugin will protect files of the base repository from being replaced by packages from a third party repository.
To install the plugin, use this command:
yum install yum-protectbase
This will install the plugin and its basic configuration file, /etc/yum/pluginconf.d/protectbase.conf
Setting are stored under /etc/yum/pluginconf.d/rhnplugin.conf with a section name matching the repo.id of the channel. You need to add :
To protect a different repository, go to its configuration file in /etc/yum.repos.d/repository.repo and add this line to its configuration
/etc/yum.repos.d/repository.repo
Add
[repository]
…
protect = 1
You will need to add this for each repository which needs to be protected.
List of packages that should not be upgraded on an Ensim Pro for Linux server.
Ensim RPMs you should leave alone: Some of these application RPMs have an tag in the build number (”ensimized RPMs”). This denotes that Parallels Pro Control Panel for Linux has made modifications to the RPM for various reasons such as fixing bugs, adding additional security, or improving performance for hosting domains. The detailed list of these RPMs is shown below.
Package Name
apache-mod_fastcgi
ensim-perl
frontpage
tomcat-connectors
analog
chartdirector-python
imap
majordomo
Miva-empresa
Mivamerchant
Mivamerchant-5.00
miva-empresa-5.02
phpMyAdmin
poprelay
squirrelmail
vacation
webdav
tomcat4
Zope
Reference :http://www.parallels.com/products/pro/
Verifying Installed Packages
Over the course of a system’s normal usage, files get changed. This could be as innocent as simply changing a configuration file in the /etc directory or as problematic as a file being corrupted by a power failure. To assist in the detection of these changes, RPM allows users and administrators to verify the integrity of an installed package.
The command
or
Will verify all installed packages. RPM then computes the MD5 checksum of all files on the disk and compares them to the stored MD5 sums from the original RPMs. The output of the command is a line indicating any files that differ from the versions that were originally installed and a code indicating how the file has changed.
