Prediction of failures Post: 302342516

4 More Discussions You Might Find Interesting

1. HP-UX

Communication Failures

HI ALL, I have been trying to install a particular software using remote linux server. some thing like this: rsh <host ID> /usr/sbin/swinstall -x autoreboot=true -s /tmp/<software> <Product name>. The problem is whenever I try to install the product through a shell script the installation...

2. Post Here to Contact Site Administrators and Moderators

Event Prediction - New Sports Events

Hi, Some sports predictions suggestions. Although the Celtics are still playing the Heat. Just being optimistic that they will win. Otherwise, please change to Heat.

3. Post Here to Contact Site Administrators and Moderators

Event Prediction - Euro 2012

Please add this new "event".

4. Solaris

11.0 to 11.2 update failures

Attempting to update an 11.0 server with many non-global zones installed. pkg publisher is pkg.oracle.com/solaris/support. FMRI = pkg://solaris/entire@0.5.11,5.11-0.175.1.15.0.4.0:20131230T203500Z When we run pkg update --accept the server contacts oracle, checks packages, finds about 700...

LEARN ABOUT OPENSOLARIS

compver

compver(4)							   File Formats 							compver(4)

NAME

       compver - compatible versions file

DESCRIPTION

       compver	is an ASCII file used to specify previous versions of the associated package which are upward compatible. It is created by a pack-
       age developer.

       Each line of the file specifies a previous version of the associated package with which the current version is backward compatible.

       Since some packages may require installation of a specific version of another software package, compatibility information is extremely cru-
       cial.  Consider,  for  example, a package called "A" which requires version "1.0" of application "B" as a prerequisite for installation. If
       the customer installing "A" has a newer version of "B" (version 1.3), the compver file for "B" must indicate that "1.3" is compatible  with
       version "1.0" in order for the customer to install package "A".

EXAMPLES

       Example 1 Sample compver file.

       A sample compver file is shown below:

	 Version 1.3
	 Version 1.0

SEE ALSO

       pkginfo(4)

       Application Packaging Developer's Guide

NOTES

       The  comparison	of  the  version  string disregards white space and tabs. It is performed on a word-by-word basis. Thus, "Version 1.3" and
       "Version 1.3" would be considered the same.

       The entries in the compver file must match the values assigned to the VERSION parameter in the pkginfo(4) files.

SunOS 5.11							    4 Oct 1996								compver(4)