7. RPMs required:
Intel:
ftp://updates.redhat.com/6.1/en/os/i386/
sharutils-4.2.1-1.6.1.i386.rpm
Alpha:
ftp://updates.redhat.com/6.1/en/os/alpha
sharutils-4.2.1-1.6.1.alpha.rpm
SPARC:
ftp://updates.redhat.com/6.0/en/os/sparc
sharutils-4.2.1-1.6.1.sparc.rpm
Source:
ftp://updates.redhat.com/6.1/en/os/SRPMS
sharutils-4.2.1-1.6.1.src.rpm
8. Solution:
For each RPM for your particular architecture, run:
rpm -Uvh filename
where filename is the name of the RPM.
9. Verification:
MD5 sum Package Name
-------------------------------------------------------------------------
f950fe244105a350d77dc5e8df0f3fc8 i386/sharutils-4.2.1-1.6.1.i386.rpm
194e00e2961159398fa6fe2d80a39407 alpha/sharutils-4.2.1-1.6.1.alpha.rpm
6e7a0aff9a601cd983c2ca56842ef800 sparc/sharutils-4.2.1-1.6.1.sparc.rpm
c2ebe34ee1112979dae88ec4b222c51d SRPMS/sharutils-4.2.1-1.6.1.src.rpm
These packages are GPG signed by Red Hat, Inc. for security. Our key
is available at:
http://www.redhat.com/about/contact.html
You can verify each package with the following command:
rpm --checksig filename
If you only wish to verify that each package has not been corrupted or
tampered with, examine only the md5sum with the following command:
rpm --checksig --nogpg filename
Note that you need RPM >= 3.0 to check GnuPG keys.
10. References:
http://www.gnu.org/software/year2000-list.html