Hi All
I have some questions regarding Java upgrade on Red Hat 5.
I have Red Hat Enterprise Linux Server release 5 (Tikanga).
I Also have Source RPM: jdk-1.5.0_14-fcs.src.rpm installed under /usr/java/.
My questions are as follwo:
1.Is the latest Java rpm file name that I need to install is "jre-6u14-linux-i586-rpm.bin"
2.I would like to keep the java 1.5.0_14 in order to have the option to rollback how do I install the newest Java ? .
What are the steps for the installation ?
Hello All,
Want to share here an article for Whats app users that team whats app is requesting users to upgrade to its latest version since they have found a vulnerability; where Hacker could turn on a cell's camera, mic and scan messages and emails.
Here is an article from "THE VERGE" for... (1 Reply)
Hi, everytime I do "sudo apt-get " and install package or just upgrade I get the following error:
sha256sum mismatch jdk-7u3-linux-x64.tar.gz
Oracle JDK 7 is NOT installed.
dpkg: error processing oracle-java7-installer (--configure):
subprocess installed post-installation script returned... (1 Reply)
Hi Friends,
I am trying to upgrade my java version on solaris sparc machine. I have installed the o/s software from scratch and it came with some default java version. I want to install the newer version of java available on top of this machine.
I have already installed the latest version in... (7 Replies)
RPMKEYS(8) System Manager's Manual RPMKEYS(8)NAME
rpmkeys - RPM Keyring
SYNOPSIS
rpmkeys {--import|--checksig}
DESCRIPTION
The general forms of rpm digital signature commands are
rpmkeys --import PUBKEY ...
rpmkeys {-K|--checksig} PACKAGE_FILE ...
The --checksig option checks all the digests and signatures contained in PACKAGE_FILE to ensure the integrity and origin of the package.
Note that signatures are now verified whenever a package is read, and --checksig is useful to verify all of the digests and signatures
associated with a package.
Digital signatures cannot be verified without a public key. An ASCII armored public key can be added to the rpm database using --import.
An imported public key is carried in a header, and key ring management is performed exactly like package management. For example, all cur-
rently imported public keys can be displayed by:
rpm -qa gpg-pubkey*
Details about a specific public key, when imported, can be displayed by querying. Here's information about the Red Hat GPG/DSA key:
rpm -qi gpg-pubkey-db42a60e
Finally, public keys can be erased after importing just like packages. Here's how to remove the Red Hat GPG/DSA key
rpm -e gpg-pubkey-db42a60e
SEE ALSO popt(3),
rpm(8),
rpmdb(8),
rpmsign(8),
rpm2cpio(8),
rpmbuild(8),
rpmspec(8),
rpmkeys --help - as rpm supports customizing the options via popt aliases it's impossible to guarantee that what's described in the manual
matches what's available.
http://www.rpm.org/ <URL:http://www.rpm.org/>
AUTHORS
Marc Ewing <marc@redhat.com>
Jeff Johnson <jbj@redhat.com>
Erik Troan <ewt@redhat.com>
Panu Matilainen <pmatilai@redhat.com>
Red Hat, Inc 29 October 2010 RPMKEYS(8)