pegasus/ReleaseNotes.htm - diff

Return to ReleaseNotes.htm CVS log

Up to [Pegasus] / pegasus

Diff for /pegasus/ReleaseNotes.htm between version 1.11 and 1.17

version 1.11, 2007/08/08 21:20:13

version 1.17, 2010/03/26 13:20:35

Line 1

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">

<head>

<style>

st1\:*{behavior:url(#ieooui) }

</style>

Line 962

Line 961

font-size:10.0pt;

font-family:"Times New Roman"}

</style>

href="http://www.openpegasus.org/pp/uploads/40/6165/PEP_150_ReleaseNotesPegasus2.3.2V1_1_files/editdata.mso">

<o:smarttagtype

<o:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="place"></o:smarttagtype><o:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="date"></o:smarttagtype><!--[if gte mso 9]><xml>

namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="City"></o:smarttagtype>

<o:smarttagtype

namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="place"></o:smarttagtype><o:smarttagtype

namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="date"></o:smarttagtype><!--[if gte mso 9]><xml>

<o:DocumentProperties>

<o:Author>IBM_User</o:Author>

<o:LastAuthor> </o:LastAuthor>

Line 995

Line 990

</w:Compatibility>

<w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel>

</w:WordDocument>

</xml><![endif]-->

</xml><![endif]--></head>

</head>

<div class="MsoNormal" style="text-align: center;" align="center"><span

style="color: black;">

<hr align="center" color="#009900" noshade="noshade" size="2"

Pegasus

width="100%"></div>

<p class="MsoNormal" style="margin-bottom: 12pt; text-align: center;"

align="center">Pegasus

Enhancement Proposal (PEP)<o:p></o:p>

<span

style="color: black;">

PEP #: 305

PEP #: 355

Title: Release

Notes for OpenPegasus 2.6.1

Notes for OpenPegasus version 2.10.0

Created: <st1:date

year="2004" day="23" month="3">3 August 2007

</st1:date>

Created: 21 January 2010

Authors: Dave

Sudlik

Authors: Karl Schopmeyer

Status:  approved

Status:  draft

Version History:

<table class="MsoNormalTable" style="width: 868px; height: 54px;"

border="1" cellpadding="0" cellspacing="1">

<tbody>

<td

style="padding: 0.75pt; background: rgb(202, 230, 202) none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;"

height="27">

<span

<o:p> </o:p>

style="font-family: Arial; color: black;"><o:p>Version </o:p>

</td>

<td

style="padding: 0.75pt; background: rgb(202, 230, 202) none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;"

height="27">

<span

<o:p> </o:p>

style="font-family: Arial; color: black;"><o:p>Date </o:p>

</td>

<td

style="padding: 0.75pt; background: rgb(202, 230, 202) none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;"

height="27">

<span

<o:p> </o:p>

style="font-family: Arial; color: black;"><o:p> Author</o:p>

</td>

<td

style="padding: 0.75pt; background: rgb(202, 230, 202) none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;"

height="27">

<span

style="font-family: Arial; color: black;"><o:p> Change Description

</o:p>

</td>

<o:p> </o:p>

</td>

</tr>

<span

style="font-family: Arial; color: black;"> 1.0<o:p></o:p>

1.0<o:p></o:p>

</td>

<span

style="font-family: Arial; color: black;"><o:p>  3

August 2007

21 January 2010

</o:p>

</td>

<span

style="font-family: Arial;">Dave Sudlik

Karl Schopmeyer

</td>

<span

style="font-family: Arial; color: black;">Initial

Initial

Submission. Updates for 2.6.1 (from 2.6) are highlighted <span

Submission <o:p>

style="color: rgb(255, 0, 0);">in

</o:p>

this color. <o:p><font

size="2"> </o:p>

</td>

</tr>

<tr>

<td style="vertical-align: top; text-align: center;">1.1

</td>

<td style="vertical-align: top; text-align: center;">8 August 2007

</td>

<td style="vertical-align: top; text-align: center;">Dave Sudlik

</td>

<td style="padding: 0.75pt;" align="center" height="21">Karl Schopmeyer</td>

<td style="vertical-align: top;">Updates from review <span

style="color: rgb(255, 0, 0);">

<td style="padding: 0.75pt;" height="21"> Remove PEP 353 and 354 from

</td>

list and point to repository.Clean up PEP list</td>

</tr>

<td style="padding: 0.75pt;" align="center" height="21">Karl Schopmeyer</td>

</tr>

<tr>

<td style="padding: 0.75pt;" align="center" height="21">25 March 2010</td>

<td style="padding: 0.75pt;" align="center" height="21">Karl Schopmeyer</td>

<td style="padding: 0.75pt;" height="21">Incorporate comments from Vote on

this PEP - This version approved</td>

</tr>

</tr>

</tbody>

</table>

<o:p> </o:p>

<div class="MsoNormal" style="text-align: center;" align="center"><span

style="color: black;">

<hr align="center" color="#009900" noshade="noshade" size="2"

width="100%"></div>

Abstract: This document defines the release notes for the

2.6.1 release of the OpenPegasus CIM Server. The purpose of this PEP is

2.10.0 release of the OpenPegasus CIM Server. The purpose of this PEP is

simply to summarize the characteristics of this release, point to other

to summarize the characteristics of this release, point to other

documentation that defines the release in more detail, and provide

additional information about this release that is not available in the

other Pegasus documentation. <span

other Pegasus documentation.

style="font-size: 9pt;"><a

href="http://www.openpegasus.org/pp/protected/doc_edit.tpl?grid=632&file=Pegasus2_3_1ReleaseNotes.html&tag=35"

target="_self">

</a>

<h2 style="margin-bottom: 1px;"><o:p> Contents</o:p></h2>

<div class="MsoNormal" style="text-align: center;" align="center"><span

style="color: black;">

<hr align="center" color="#009900" noshade="noshade" size="2"

width="100%"></div>

<h2 style="margin-bottom: 1px;"><o:p> Contents

</o:p></h2>

<ol>

<li><a href="#Availability_of_this_Release_">Availability of this

Release</a></li>

<li><a href="#Functionality_of_This_Release">OpenPegasus

Functionality of This Release</a></li>

<li><a href="#Compatibility_Considerations_">Compatibility Considerations</a></li>

<li><a href="#Relationship_to_CIMWBEM_Standards">Relationship

to CIM/WBEM Standards</a></li>

<li><a href="#Supported%20Platforms">OpenPegasus Supported Platforms</a></li>

<li><a href="#Conformance%20with%20DMTF%20Specifications">Conformance

with DMTF Specifications</a></li>

<li><a href="#PEGASUS%20Bugs">OpenPegasus Bugs</a></li>

<li> <a

<li> <a href="#Pegasus%20Release%20Control%20and%20Version%20Definition%20Documentation">OpenPegasus

href="#Pegasus%20Release%20Control%20and%20Version%20Definition%20Documentation">OpenPegasus

Release Control and Version Definition Documentation</a></li>

<li><a href="#General%20Documentation">General

Documentation</a></li>

Line 1134

Line 1175

<li>Source release in both ZIP (and ZIP EXE) and TAR formats.

These can be

downloaded from the OpenPegasus Web

site at <a

site at <a href="http://www.openpegasus.org/page.tpl?CALLER=index.tpl&ggid=392">www.openpegasus.org.</a> </li>

href="http://www.openpegasus.org/page.tpl?CALLER=index.tpl&ggid=392">www.openpegasus.org.</a> </li>

<li>OpenPegasus source RPMs on the OpenPegasus web site.. A source RPM is  available on the

<li>OpenPegasus  binary and source RPMs on the

OpenPegasus web site that can be used to build binaries for most LSB-compliant RPM-based Linux distributions and versions.</li>

OpenPegasus web site.. The source RPM is  available on the

OpenPegasus web site that can be used to build binaries for most

LSB-compliant RPM-based Linux distributions and versions.</li>

<li>The Pegasus CVS repository. The CVS tags representing this

release and

subsequent snapshots that are made available in the Pegasus CVS are

defined on the OpenPegasus CVS repository web page (see the <a

defined on the OpenPegasus CVS repository web page (see the <a href="http://cvs.opengroup.org/cgi-bin/viewcvs.cgi/">OpenPegasus

href="http://cvs.opengroup.org/cgi-bin/viewcvs.cgi/">OpenPegasus

CVS page</a> for information) using the tags defined on the <a href="http://www.openpegasus.org/page.tpl?CALLER=cvs.tpl&ggid=392">release

CVS page</a> for information) using the tags defined on the <a

href="http://www.openpegasus.org/page.tpl?CALLER=cvs.tpl&ggid=392">release

snapshots page</a>.</li>

</ul>

The instructions for acquiring the released code are on the <a

The instructions for acquiring the released code are on the <a href="http://www.openpegasus.org/page.tpl?CALLER=index.tpl&ggid=392">Pegasus

href="http://www.openpegasus.org/page.tpl?CALLER=index.tpl&ggid=392">Pegasus

WEB site</a>.

Installation instructions are part of the README in the root of the

Pegasus source

tree.

</div>

<h2>OpenPegasus Functionality for This

<h2>OpenPegasus Functionality for This Release</h2>

Release</h2>

Pegasus overall status by release is defined by  a <a

Pegasus overall status by release is defined by  a

href="http://www.openpegasus.org/page.tpl?ggid=799">Feature Status WEB

<a href="http://www.openpegasus.org/page.tpl?ggid=799">Feature Status WEB Page</a>

Page</a> that is available on the OpenPegasus web site .  That web

that is available on the OpenPegasus web site .  That web page shows the

page shows the Pegasus users and developers the status of the various

Pegasus users and developers the status of the various features found in Pegasus

features found in Pegasus using a simple color coded key (white, red,

using a simple color coded key (white, red, yellow, green) and a description of

yellow, green) and a description of each feature.

each feature.Pegasus 2.10.0

Pegasus 2.6.1 is a "point"

is a major release, extending the previous Pegasus release in selected

release, extending Pegasus 2.6 in

areas as described in the Pegasus  PEP defining this release

selected areas. Normally an OpenPegasus "point" release does not

.

contain major new pieces of functionality, but in this case one new PEP

was added for IPv6 support, the description of which has been added to

The major areas of development for this release  were as follows. For

these Release Notes.

more information access the PEP for each change defined:

The major areas of development for this release  were as

Table of Major Changes for this Release

follows. For more information access the documented PEP:

Table of Major Changes for this Release

<table style="font-family: Arial;" bordercolordark="#666666"

bordercolorlight="#cccccc" border="1" cellspacing="1">

<tbody>

<th bgcolor="#e0e8ef">Description</th>

<th bgcolor="#00ffff">Description of Change</th>

<th bgcolor="#e0e8ef">Posted PEP

<th bgcolor="#00ffff" width="128">Posted PEP Version</th>

Version</th>

</tr>

<td style="color: rgb(153, 51, 153);" align="left">OpenPegasus

<td align="left" width="75%">WS-Management Support in CIM Server - Phase II.

Support for IPv6: Stage 1

NOTE: This is an update of the same PEP number that incorporated

</td>

WS_Management changes to Pegasus 2.9.0 to incorporate more WS_Management

<td style="color: rgb(0, 153, 0);"> <a

functionality.</td>

href="http://www.openpegasus.org/pp/uploads/40/14222/PEP_291_IPv6.html">1.2</a>

</td>

2.2</a> </td>

</tr>

<tr>

<td align="left" width="75%">Extend CIMCLI to create/modify instances with other features</td>

</tr>

<td align="left" width="75%">Single-Memory-Object for CMPI structure</td>

</tr>

<td align="left" width="75%">Separate Internal Modules from Common Library</td>

1.1</a></td>

</tr>

<tr><td style="text-align: center;">PEP 350</td><td>Multi CIMOM support on

same OS </td><td style="text-align: center;">

1.0</a></td></tr><tr><td style="text-align: center;">

<a name="comtag_90">repupgrade utility enhancement to

update SystemName property in indication filter/handler and

ObjectManager instances</a> </td><td style="text-align: center;"> </td></tr><tr align="center">

<a name="comtag_95">Indication service can be

disabled/enabled dynamically</a> </td>

</tr>

</tr>

</tbody>

</table>

The status of several components of Pegasus functionality change

The status of several components of Pegasus functionality change status

status between Pegasus versions. <a

between Pegasus versions. <a name="comtag_116">Features that

name="comtag_116">Features that have changed status can be identified

have changed status can be identified by a change in color from the previous

by a change in color from the previous release to this release</a>

release to this release</a> on the

on the <a href="http://www.openpegasus.org/page.tpl?ggid=799">Feature

<a href="http://www.openpegasus.org/page.tpl?ggid=799">Feature Status WEB Page</a>.

Status WEB Page</a>.

Finally, a significant number of internal changes and corrections

Finally, a significant number of internal changes and corrections were made

were made under the control of the Pegasus bugzilla bug system. See the

under the control of the Pegasus bugzilla bug system. See the bug section below

bug section below for more information.

for more information.

<h3 style="color: rgb(153, 51, 153);">IPv6 Support

<h3>Information on  IPv6 Support (PEP 291)</h3>

</h3>

NOTE: This functionality was incorporated in OpenPegasus 2.7.0 but it

IPv6 is short for "Internet

was felt that the information below was worth repeating in subsequent Release

Notes

IPv6 is short for "Internet

Protocol

Version 6". IPv6 is the "next generation" protocol designed by the IETF

to replace the current version Internet Protocol, IP Version 4

("IPv4"). IPv6 Support for OpenPegasus is documented in <a

("IPv4"). IPv6 Support for OpenPegasus is documented in <a href="http://www.openpegasus.org/pp/uploads/40/14222/PEP_291_IPv6.html">

href="http://www.openpegasus.org/pp/uploads/40/14222/PEP_291_IPv6.html">PEP

PEP

291</a>.

291</a>.

The IPv6 support in OpenPegasus is

The IPv6 support in OpenPegasus is

controlled by the PEGASUS_ENABLE_IPV6 build variable. The default for this

controlled by the PEGASUS_ENABLE_IPV6 build variable. Setting this to

variable is "true"; setting this to

'true' before building OpenPegasus will enable the IPv6 support. In

'false' before building OpenPegasus will disable the IPv6 support.

2.6.1 this variable will default to 'false' to omit the IPv6 support.

The following subsections provide

The following subsections provide

some information on IPv6 support for the Linux and Windows platforms.

Note that in the 2.6.1 release there is no automatic run-time detection

of IPv6 support on a platform by OpenPegasus. If you build with

Line 1231

Line 1304

Listener components. For more information on IPv6 support for your

specific platform, refer to the documentation for that platform.

All OpenPegasus externals that

All OpenPegasus externals that

support either a hostname or an IP address as input have been updated

to allow an IPv6 address to be specified. If the required input is just

an IP address (eg. no optional or required port number), then the IPv6

Line 1241

Line 1314

case a host with an IPv6-configured network interface would be

specified as:

<div style="margin-left: 40px; color: rgb(153, 51, 153);">osinfo -h

<div style="margin-left: 40px; color: rgb(153, 51, 153); font-family: monospace;"><big>osinfo -h

3ffe:1:2:1 -p 5988

3ffe:1:2:1 -p 5988</big></div>

</div>

But the cimcli command, which

But the cimcli command, which

takes

an optional "location" option including an optional port number,

requires the IPv6 address to be delimited with brackets, for example:

<div style="margin-left: 40px; color: rgb(153, 51, 153);">cimcli ns -l

<div style="margin-left: 40px; font-family: monospace;"><big>cimcli ns -l [3ffe:1:2:1]</big></div>

[3ffe:1:2:1]</div>

or

or

<div style="margin-left: 40px;"><big>cimcli ns -l [3ffe:1:2:1]:5989</big>

<div style="margin-left: 40px; color: rgb(153, 51, 153);">cimcli ns -l

[3ffe:1:2:1]:5989

</div>

For more information on

For more information on

specifying

IPv6 addresses, refer to <a style="color: rgb(153, 51, 153);"

IPv6 addresses, refer to <a href="http://www.ietf.org/rfc/rfc2373.txt">IETF RFC 2373 - IP Version

href="http://www.ietf.org/rfc/rfc2373.txt">IETF RFC 2373 - IP Version

6 Addressing Architecture</a>

6 Addressing Architecture</a>

and <a href="http://www.ietf.org/rfc/rfc2732.txt">IETF RFC 2732 - Format for

and <a style="color: rgb(153, 51, 153);"

Literal IPv6 Addresses in URL's</a>.

href="http://www.ietf.org/rfc/rfc2732.txt">IETF RFC 2732 - Format for

<h4>IPv6 on Linux</h4>

Literal IPv6 Addresses in URL's</a><span

Modern Linux distributions already

style="color: rgb(153, 51, 153);">.<br

style="color: rgb(153, 51, 153);">

<h4 style="color: rgb(153, 51, 153);">IPv6 on Linux

</h4>

Modern Linux distributions already

contain IPv6-ready kernels, the

IPv6 capability is generally compiled as a module, but it's possible

that this module is not loaded automatically on startup.

Note:

Note:

you shouldn't anymore use kernel series 2.2.x, because it's not

you shouldn't use kernel series 2.2.x, because it's not

IPv6-up-to-date anymore. Also the IPv6 support in series 2.4.x is no

longer improved according to definitions in latest RFCs. It's recommend

to use series 2.6.x now.

To check whether your current

To check whether your current

running

kernel supports IPv6, take a look into your /proc filesystem. The entry

/proc/net/if_inet6 must exist. A short automated test looks like:

<div style="margin-left: 40px; color: rgb(153, 51, 153);">test -f

<div style="margin-left: 40px; color: rgb(153, 51, 153); font-family: monospace;"><big>test -f

/proc/net/if_inet6 && echo "Running kernel is IPv6 ready"

/proc/net/if_inet6 && echo "Running kernel is IPv6 ready"</big></div>

</div>

For more information on

For more information on

enabling

IPv6 in the Linux kernel and configuring network interfaces, refer to <a

IPv6 in the Linux kernel and configuring network interfaces, refer to

style="color: rgb(153, 51, 153);"

<a href="http://tldp.org/HOWTO/html_single/Linux+IPv6-HOWTO/">The Linux

href="http://tldp.org/HOWTO/html_single/Linux+IPv6-HOWTO/">The Linux

Documentation Project's IPv6 HOWTO</a>.

Documentation Project's IPv6 HOWTO</a><span

style="color: rgb(153, 51, 153);">.

Warning:

Warning:

There is currently an open issue with RedHat to address a problem that

is seen intermittently on RHEL5 and SLES10 systems. This problem is

described in <a style="color: rgb(153, 51, 153);"

described in

href="http://cvs.opengroup.org/bugzilla/show_bug.cgi?id=6586">Pegasus

<a href="http://cvs.opengroup.org/bugzilla/show_bug.cgi?id=6586">Pegasus

bug 6586</a> and <a

bug 6586</a>

style="color: rgb(153, 51, 153);"

href="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=248052">RedHat

and

bug 248052</a>, and manifests

<a href="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=248052">RedHat

itself as an intermittent IPv6 socket failure. You should be aware that

bug 248052</a>,

OpenPegasus with IPv6 enabled may be

significantly impacted in these environments.<br

style="color: rgb(153, 51, 153);">

<h4 style="color: rgb(153, 51, 153);">IPv6 on Windows</h4>

and manifests itself as an intermittent IPv6 socket failure. You should be aware

Microsoft provides supported IPv6

that OpenPegasus with IPv6 enabled may be significantly impacted in these

environments.

<h4>IPv6 on Windows</h4>

Microsoft provides supported IPv6

implementations for Windows Server

2003, Windows XP with Service Pack 1 (SP1), Windows XP with Service

Pack 2 (SP2), and Windows CE .NET 4.1 and later.

On Windows XP, you can use the <span

On Windows XP, you can use the ipv6.exe tool to install, uninstall, and

style="font-weight: bold; color: rgb(153, 51, 153);">ipv6.exe<span

style="color: rgb(153, 51, 153);"> tool to install, uninstall, and

query

your IPv6 configuration. For example:<br

your IPv6 configuration. For example:

style="color: rgb(153, 51, 153);">

<div style="margin-left: 40px; color: rgb(153, 51, 153); font-family: monospace;"><big>ipv6 install

<div style="margin-left: 40px; color: rgb(153, 51, 153);">ipv6 install

ipv6 if</big></div>

ipv6 if

Windows Vista

</div>

Windows Vista

and Windows Server 2008 support an integrated

IPv4 and IPv6 implementation known as the Next Generation TCP/IP stack.

Note that the OpenPegasus IPv6 support in 2.6.1 has not yet been tested

Note that the OpenPegasus IPv6 support has not yet been tested

on Windows Vista or Windows Server 2008.<br

on Windows Vista or Windows Server 2008.

style="color: rgb(153, 51, 153);">

For more information on

For more information on

installing, configuring, and using IPv6 on Windows platforms, refer to

the document <a style="color: rgb(153, 51, 153);"

the document

href="https://www.microsoft.com/technet/network/ipv6/ipv6faq.mspx">IPv6

for Microsoft Windows: Frequently Asked Questions</a><span

IPv6

style="color: rgb(153, 51, 153);">.<br

for Microsoft Windows: Frequently Asked Questions</a>.

style="color: rgb(153, 51, 153);">

<h4 style="color: rgb(153, 51, 153);">Testing your OpenPegasus IPv6

<h4>Testing your OpenPegasus IPv6

support</h4>

support</h4>

As part of the OpenPegasus

As part of the OpenPegasus

automated tests, the TestClient, g11ntest, and IndicationStressTest

test clients were modified to run tests using the IPv6 loopback address

(::1) if PEGASUS_ENABLE_IPV6=true.<br

(::1) if PEGASUS_ENABLE_IPV6=true.

style="color: rgb(153, 51, 153);">

You can also perform manual

You can also perform manual

tests

using the IPv6 loopback or a real IPv6-configured network interface.

For example, using the IPv6 loopback on a system with OpenPegasus

running on the wbem standard http port of 5988:<br

running on the WBEM standard http port of 5988:

style="color: rgb(153, 51, 153);">

osinfo -h ::1</big></div>

osinfo -h ::1

<h2><a name="Compatibility_Considerations_">Compatibility Considerations</a></h2>

</div>

Support for forward-compatibility is a fundamental design principle for the

OpenPegasus project. As a Community, our goal is for well-behaved OpenPegasus

<ol>

Providers or Clients, using only the externally defined OpenPegasus interface,

</ol>

to continue to work with a minor version upgrade of OpenPegasus. However, there

are certain classes of errors (e.g., non-compliance with a standard that

significantly affects interoperability) that may require the Community to make

potentially incompatible changes. The following table contains a list of defect

fixes that MAY impact, even well-behaved, OpenPegasus Providers or Clients when

upgrading to this OpenPegasus release.

<tbody>

<th bgcolor="#00ffff" width="10%">Bugzilla #</th>

<th bgcolor="#00ffff">Description</th>

</tr>

</tr>

</tr>

</tr>

</tr>

</tr>

</tbody>

</table>

<h2>OpenPegasus Relationship to

CIM/WBEM Standards</h2>

Pegasus was designed and implemented to comply with the DMTF

CIM/WBEM specifications The following table defines the level of the

DMTF specifications to which this version of Pegasus aims to conform

today.

<tbody>

<tr>

<td bgcolor="#00ffff" width="33%">DMTF Specification</td>

Line 1378

Line 1464

</tr>

<tr>

<td width="33%">DSP 0200 - CIM Operations over HTTP</td>

<td width="33%">1.2.0, preliminary, 9 December 2004</td>

<td width="33%">Version 1.2, Final, January 09, 2007</td>

</tr>

<tr>

<td width="33%">DSP 0201 - Representation of CIM in XML</td>

<td width="33%">2.2.0, preliminary, December 2004</td>

<td width="33%">Version 2.2 Final, January 09, 2007</td>

</tr>

<tr>

<td width="33%">DSP 0202 - CIM Query Language Specification</td>

Line 1398

Line 1484

</tr>

<tr>

<td width="33%">CIM Schema </td>

<td width="33%">2.9 Final, Jan. 2005 ( default) 2.13.1 (available

<td width="33%">2.22.1 Final,  22 Oct 2009( default) </td>

in pegasus CVS)</td>

</tr>

</tbody>

</table>

Line 1419

Line 1504

provider registration.  This is not a deviation from the

specifications but is a different method of registration than many CIM

Servers and means that the the provider qualifier is unused in Pegasus.</li>

<li> Indications -Today Pegasus supports process

<li>Indications -Today Pegasus supports process

indications and lifecycle indications when defined specifically by

providers. Pegasus does not support lifecycle indications if they are

not defined by the provider or for changes to CIM Classes.<font

not defined by the provider or for changes to CIM Classes.  For

color="#ff0000">  For

more information see the Pegasus CVS file:<a name="comtag_137">

more information see the Pegasus CVS file  <a name="comtag_137"> <font

pegasus/src/Unsupported/LifecycleIndicationProvider/README.LifecycleIndications.htm</a>.</li>

face="Courier New">pegasus/src/Unsupported/LifecycleIndicationProvider/README.LifecycleIndications.htm</a>.</li>

<li>

<font

IncludeQualifiers

style="color: rgb(0, 0, 0); font-weight: bold;">IncludeQualifiers

option on Instance Operations

The DMTF specifications have deprecated the use of qualifiers on

instance operations with the 1.2 CIM Operations Specification. 

instance operations with the 1.2 CIM Operations Specification and

stated specifically that the client should NOT depend on the

includeQualifiers parameter of the CIM/XML instance operations

returning qualifiers. 

Some CIM Client implementations expect instances

returned

from the CIM Server to include the qualifiers defined in the class

Line 1445

Line 1531

should NOT depend on Pegasus accurately honoring the includeQualifier

parameter for instance operations.  In the future it is expected

that Pegasus will deprecate the use of qualifiers on instance

operations completely.

operations completely.  When Pegasus uses object normalization,

</li>

the normalizer does apply qualifiers to returned instances if the

<li>LocalOnly option on instance

includeQualifiers operation parameter is set.</li><li>LocalOnly option on instance

Operations - With the 1.1 version of Specification for CIM

Operations over HTTP, the definition of the LocalOnly parameter for the

GetInstance and EnumerateInstances operations was modified. This change

Line 1458

Line 1544

filter the set of set of properties returned. See Appendix C of this

specification for more information.</li>

<li>

MultiRequest Oprations - Pegasus

MultiRequest Operations - Pegasus

does not support the DMTF defined MultiRequest Operation option.

</li>

<li>

MOFCompiler namespace pragma - The

Pegasus compiler does not support the namespace pragma.

</li>

<li>Pegasus implements

<li>CIMOperation Trailer - Pegasus implements

chunking

based on the DSP0200 1.2.0 preliminary spec. Refer to bug <a

based on the DSP0200 1.2.0 preliminary spec. including the operation trailer

style="color: rgb(153, 51, 153);"

defined in that specification Refer to bug

href="http://cvs.opengroup.org/bugzilla/show_bug.cgi?id=6760">6760</a><span

<a href="http://cvs.opengroup.org/bugzilla/show_bug.cgi?id=6760">6760</a> for more details.

style="color: rgb(153, 51, 153);"> for more details.

This trailer was completely removed from the DSP0200 1.2 final specification

as a non-compatible change so that if chunking is used Pegasus is returning

a noncompliant response to enumerate type requests.

</li>

</ol>

<h2>OpenPegasus <a

<h2>OpenPegasus <a name="Supported Platforms">Supported

name="Supported Platforms">Supported

Platforms</a></h2>

Each OpenPegasus release lists as 'active' platforms those

Each OpenPegasus release lists as 'active' platforms those

hardware/software platforms that have recognized ports for the Pegasus

hardware/software platforms that have recognized ports for the Pegasus code base

code

including a maintainer for the platform that will be willing to regularly

base including a maintainer for the platform that will be willing to

document issues and/or fix defects as the Pegasus code base is changed. 

regularly document issues and/or fix defects as the Pegasus

Pegasus may be operable on other platforms (ex. Windows 98) but without a group

code base is changed. 

to provide the role of test and maintenance, correct operation of  Pegasus

Pegasus may be operable on other platforms (ex. Windows 98) but without

cannot be assured.  In all cases, including the active platforms, it is the

a group

responsibility of the entity that packages and/or compiles OpenPegasus for

to provide the role of test and maintenance, correct operation of 

shipment or deployment, to read, and actively monitor the Pegasus bugzilla

Pegasus cannot be

database for a list of relevant defects that affect their platform.  

assured.  In all cases, including the active platforms, it is the

The platforms that are considered ported are shown in the two tables below. 

responsibility of the entity that packages and/or compiles OpenPegasus

The first table represents platform sofr which testing is done on a regular

for shipment or deployment, to read, and actively monitor the Pegasus

basis and reported to the Pegasus Nightly Build Test WEB Page. Those platforms

bugzilla database for a list of relevant defects that affect their

which have been ported but do not have test results that are current at the time

platform.   The platforms that are considered 'active' for this

of the release are reported in the second table.Actively Supported Platforms (Nightly Tests Reported for this release)

Pegasus release are:

<table class="MsoNormalTable" style="width: 302.25pt;" border="1"

cellpadding="0" cellspacing="1" height="409" width="504">

<tbody>

<td

style="padding: 0.75pt; background: rgb(153, 255, 153) none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial; width: 126.75pt;"

height="26" width="211">

Platform and

OS<o:p></o:p>

</td>

<td

Compilers<o:p></o:p>

height="26" width="289">

Compilers<span

style="color: black;"><o:p></o:p>

</td>

</tr>

<td style="padding: 0.75pt; width: 126.75pt;" height="25"

width="211">

HP-UX<o:p> PA_RISC and

HP-UX<o:p></o:p>

Itanium</o:p>

</td>

<td style="padding: 0.75pt; width: 173.25pt;" height="25"

width="289">

HP aC++ B3910B<o:p></o:p>

HP <span

class="SpellE">aC++ B3910B<o:p></o:p>

</td>

</tr>

<td style="padding: 0.75pt; width: 126.75pt;" height="25"

width="211">

Linux on Power<o:p></o:p>

<span

</td>

style="color: black;">Linux on Power<span

style="color: black;"><o:p></o:p>

gcc<o:p></o:p>

</td>

<td style="padding: 0.75pt; width: 173.25pt;" height="25"

width="289">

<span

style="color: black;">gcc<o:p></o:p>

</td>

</tr>

<td style="padding: 0.75pt; width: 126.75pt;" height="25"

width="211">

zLinux<o:p></o:p>

<span

</td>

style="color: black;">zLinux<o:p></o:p>

</td>

gcc<o:p></o:p>

<td style="padding: 0.75pt; width: 173.25pt;" height="25"

width="289">

<span

style="color: black;">gcc<o:p></o:p>

</td>

</tr>

<td style="padding: 0.75pt; width: 126.75pt;" height="25"

width="211">

Linux Itanium<o:p></o:p>

</td>

<td style="padding: 0.75pt; width: 173.25pt;" height="25"

width="289">

gcc<o:p></o:p>

<span

style="color: black;">gcc<o:p></o:p>

</td>

</tr>

<td style="padding: 0.75pt; width: 126.75pt;" height="25"

width="211">

Linux IA-32</td>

Linux IA-32, <span

style="color: rgb(153, 51, 153);">X86_64<o:p></o:p>

gcc

</td>

(versions 3.xx, 4.xx)<o:p></o:p></td>

<td style="padding: 0.75pt; width: 173.25pt;" height="25"

width="289">

<span

style="color: black;">gcc

(versions 2.9x, 3.xx, 4.xx)<o:p></o:p>

</td>

</tr>

<td style="padding: 0.75pt; width: 126.75pt;" height="91"

width="211">

Linux X86_64<o:p></o:p>

Windows 2000<o:p></o:p>

</td>

<td style="padding: 0.75pt; width: 173.25pt;" height="91"

gcc

width="289">

(versions 3.xx, 4.xx)

Microsoft

Visual C++ Ver 6 and Microsoft .Net compiler Version.   <span

style="color: black;">Works on VC .NET 2003 (aka

v7.1)<o:p></o:p>

</td>

</tr>

<tr>

<td style="padding: 0.75pt; width: 126.75pt;" height="69"

width="211">

<td style="vertical-align: top;">XL C/C++ from z/OS Version

Windows XP<o:p>,

1.7 and up</td>

Windows 2003</o:p>

</td>

<td style="padding: 0.75pt; width: 173.25pt;" height="69"

width="289">

Microsoft

Visual C++ Ver. 6 and Microsoft .Net compiler Version 7.1<span

style="color: black;" lang="NL"><o:p></o:p>

</td>

</tr>

</tbody>

</table>

Platforms not Actively supported for this release (No

current Nightly Build Test Results

<tbody>

<td style="padding: 0.75pt; width: 126.75pt;" height="43"

width="211"> MacOS version 10.2 and higher</td>

Platform and

<td style="padding: 0.75pt; width: 173.25pt;" height="43"

OS<o:p></o:p>

width="289"> gcc 3.3, gcc 4.01</td>

</td>

Compilers<o:p></o:p>

</td>

</tr>

<tr>

<td style="vertical-align: top;"><big>HP OpenVMS Alpha

<td style="padding: 0.75pt;"> Windows XP

</big></td>

</td>

<td style="vertical-align: top;"> <big><font

style="color: rgb(0, 0, 0);" color="RED">HP C++ V<span

Microsoft Visual C++ Ver. 6 and Microsoft .Net compiler Version 7.1.

style="color: rgb(153, 51, 153);">7.3-009 for OpenVMS

Note: Visual C++ Ver. 6 no longer being regular tested.

Alpha and above</big> </td>

</td>

</tr>

<tr>

<td style="vertical-align: top;"><big><font

<td style="padding: 0.75pt;"> MacOS version 10.3 and higher</td>

style="color: rgb(0, 0, 0);"> HP OpenVMS IA64</big></td>

<td style="vertical-align: top;"><big><font

style="color: rgb(0, 0, 0);">HP C++ V7.<span

style="color: rgb(153, 51, 153);">2-021 on OpenVMS IA64 and

above</big> </td>

</tr>

<tr>

<td style="vertical-align: top;"><big><span

<td style="vertical-align: top;"><big>Solaris 8</big></td>

style="color: rgb(0, 0, 0);">Solaris 8

</big></td>

<td style="vertical-align: top;"><big>GNU  2.95.3,  Sun

CC compiler V 5.8. Note that the latest thread patch (108993) may be

required. (see Pegasus bug 4632)</big>

</td>

</tr>

<tr>

<td style="vertical-align: top;"><big><font

<td style="vertical-align: top;"><big>Solaris 9</big></td>

color="RED">Solaris 9

</big></td>

<td style="vertical-align: top;"><big>GNU  2.95.3, Sun

WorkShop 6 update 2 C++ 5.3, patch 111685-22 2005/04/09</big>

</td>

</tr><tr><td><big>HP OpenVMS 8.3 or later Alpha</big></td><td><big>HP C++ V7.3-009 or later required for OpenVMS

Alpha</big></td></tr>

<tr><td><big> HP OpenVMS 8.3 or later IA64</big></td><td><big>HP C++ V7.3-023 or

later required on OpenVMS IA64</big></td></tr>

<tr>

Windows 2000

</td>

Microsoft Visual C++ Ver.  6 and Microsoft .Net compiler version. Works on VC .NET 2003 v7.1).

NOTE: Visual C++ Ver. 6 no longer being regularly tested.</td>

</tr>

<tr>

<td style="padding: 0.75pt;"> Windows 2003

</td>

Microsoft Visual C++ Ver. 6 and Microsoft .Net compiler Version 7.1.

Note: Visual C++ Ver. 6 no longer being regular tested.

</td>

</tr>

<tr><td><big>OpenSolaris 11 (Nevada) Community Edition (Sparc and IX86)</big></td><td><big>CC Compiler Sun Studio 5.11</big></td></tr>

</tbody>

</table>

Platform patches

Platform patches

<font

style="color: rgb(0, 0, 0);">The following is a list of platform

patches Pegasus requires.

The following is a list known of platform

patches Pegasus requires.

<font

<ol>

style="color: rgb(0, 0, 0);">RHAS

<li>

2.1 needs the update to fix Red Hat Bugzilla 98815.

RHAS

2.1 needs the update to fix Red Hat Bugzilla 98815.</li>

<li>

RHEL 4.4 multithreading bug in

getpwuid-r could cause a CIM Server failure (Bugzilla 6232). This is fixed in

RHEL 4.5</li>

<li>

Red Hat and SUSE Linux

multiple versions -

multithreaded client intermittently fails connecting to IPv6 (Pegasus Bugzilla

6586) (Red Hat bug 248052) </li>

</ol>

</div>

Further information regarding Pegasus support on IBM platforms can

found at: <a

found at: <a href="http://publib.boulder.ibm.com/infocenter/eserver/v1r1/en_US/index.htm?info/icmain.htm">http://publib.boulder.ibm.com/infocenter/eserver/v1r1/en_US/index.htm?info/icmain.htm</a>

href="http://publib.boulder.ibm.com/infocenter/eserver/v1r1/en_US/index.htm?info/icmain.htm"><span

style="text-decoration: underline; color: rgb(51, 51, 255);">http://publib.boulder.ibm.com/infocenter/eserver/v1r1/en_US/index.htm?info/icmain.htm</a>

Further information regarding Pegasus support on HP platforms can

Line 1662

Line 1738

<a href="http://www.hp.com/go/wbem">http://www.hp.com/go/wbem</a>.

<h2><a name="PEGASUS Bugs">Pegasus Defects</a></h2>

The Pegasus bugzilla database documents any defects found in Pegasus

and  is available through the following link:  <a

and  is available through the following link:  <a href="http://cvs.rdg.opengroup.org/bugzilla/">OpenPegasus bugzilla

href="http://cvs.rdg.opengroup.org/bugzilla/">OpenPegasus bugzilla

database</a>.

database</a>.  Note that all changes  committed for this

Effective with the start of the Pegasus 2.6 work, all changes to the

release have been marked with the keyword 2.6.<span

CVS tree are documented through bugs.  Bugs reports are filed not

style="color: rgb(153, 51, 153);">1_APPROVED

only for bugs and

so that all changes for this release can be found with the following

their corresponding fixes but also as part of the process of committing

bug search. Effective with the start of the Pegasus 2.6 work, all

new code

changes to the CVS tree were documented through bugs.  Thus bugs

representing the work on PEPs done for Pegasus 2.6 and all subsequent

were filed not only for bugs and their corresponding fixes but also as

versions.  Therefore, a search of

part of the process of committing new code representing the work on

the Open Pegasus bugzilla base for bugs with the tag for a particular

PEPs done for Pegasus 2.6.  Therefore, a search of the bugzilla

version

base for bugs with the tag 2.6.<span

(ex. 

style="color: rgb(153, 51, 153);">1_APPROVED will

yield

2.6.0_APPROVED</a>,

all changes to the

Pegasus RELEASE_2_6-branch

2.6.1_APPROVED</a>,

CVS branch since

<a href="http://cvs.rdg.opengroup.org/bugzilla/buglist.cgi?keywords=2.7.0_APPROVED">2.7.0_APPROVED</a>, etc) will yield all changes to

Pegasus 2.6.0.

the Pegasus CVS tree for that Pegasus release.

- Changes for Pegasus 2.6.<span

     - Changes for this release (bugs Tagged

style="color: rgb(153, 51, 153);">1 point release (bugs Tagged <font

2.10.0_APPROVED). The link is <a href="http://cvs.rdg.opengroup.org/bugzilla/buglist.cgi?keywords=2.10.0_APPROVED">

face="Courier New">2.6.1_APPROVED)

Pegasus 2.10.0_APPROVED bug list.</a>

href="http://cvs.rdg.opengroup.org/bugzilla/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=2.6.1_APPROVED&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0=">Pegasus

<h2><a name="Pegasus Release Control and Version Definition Documentation">Release Control and Version Definition Documentation</a></h2>

2.6.1_APPROVED bug list</a>

The Pegasus project is controlled largely through the CVS repository and a set of documents

<h4>2.6.1 bugs of special interest:

(PEPs) that serve both as the definition and review mechanism for new and

</h4>

<ul>

<li><a style="color: rgb(153, 51, 153);"

href="http://cvs.opengroup.org/bugzilla/show_bug.cgi?id=6643">Bug 6643</a><span

style="color: rgb(153, 51, 153);"> changed the way OpenPegasus loads

libraries (such as providers) in a POSIX environment. The dlopen() call

was changed to include the RTLD_GLOBAL option for all POSIX platforms

except VMS.

</li>

</ul>

<h2><a

name="Pegasus Release Control and Version Definition Documentation">Pegasus

Release Control and Version Definition Documentation</a></h2>

The Pegasus project is controlled largely through a set of documents

(PEPs) that serve as the definition and review mechanism for new and

modified Pegasus functionality and for the definition and documentation

of releases.

of releases.The following documentation defines the characteristics of this

Specifically the following PEPs define the characteristics of the

Pegasus release. The PEPs are available at

Pegasus 2.6 release. These PEPs are available as

OpenPegasus Approved PEPs.</a><ol>

href="http://www.openpegasus.org/pp/protected/documents.tpl?CALLER=index.tpl&gdc_docage=0&S=gdc_title&R=desc">OpenPegasus

Approved PEPs.</a>

<li>

For this 2.6.1 point release,

OpenPegasus Release Definition/Status -  </li>No PEP (See Wiki Section <a href="http://wiki.opengroup.org/pegasus-wiki/doku.php?id=dev:release:2_9_x">OpenPegasus 2.10.x Release Status</a>) - A

only

section in the Pegasus wiki is used

this document, the 2.6.1 Release Notes, was updated. All other

references should be back to the 2.6 release PEPs.

<ol>

<li> PEP 218 - OpenPegasus 2.6 Release Definition - This PEP

used

throughout the development of this version as the control point for

functionality that will go into the release and points to all of the

functionality that will go into the release and points to all of the PEPs that

PEPs that represent the Pegasus  functionality changes for this

represent the Pegasus  functionality changes for this version of Pegasus.

version of Pegasus.</li>

<li> PEP 277 -  OpenPegasus 2.6 Build and Configuration

Options  for Selected

OpenPegasus  Build and Configuration

Platforms</li>

Options  for Selected

<li> PEP 278 OpenPegaus 2.6 External Interfaces - Lists the

Platforms -

public interfaces for clients and providers that are considered

<a href="http://cvs.opengroup.org/cgi-bin/viewcvs.cgi/*checkout*/pegasus/doc/BuildAndReleaseOptions.html?rev=1.18">CVS Respository Build And Release Options Document</a> -

external and therefore "frozen".

In previous versions of Pegasus this

</li>

information was  releases as a Pegasus PEP. Starting with Pegasus 2.9.0

<li> PEP 279 - OpenPegasus 2.6 SDK Packaging Definition - Defines

the information is located in the OpenPegasus CVS repository as <big>

the recommended set of files for inclusion in the OpenPegasus SDK</li>

pegasus/doc/BuildAndReleaseOptions.html</big>.</li>

<li>PEP 280 - Pegasus  2.6 Runtime Packaging Definition -

Defines the recommended set of files for inclusion in this OpenPegasus

<li>

release.</li>

OpenPegasus External Interfaces -

<li>PEP 305 - Pegasus 2.6.1

Release

CVS Repository External Interfaces Document</a>- THE list of the

Notes (This document located in

OpenPegasus interfaces that are considered external and therefore "frozen".

the approved PEP repository and the OpenPegasus source tree root

Unless an exception is explicitly approved by the Steering Committee all

directory)

subsequent releases of Pegasus MUST continue to support these interfaces.

Interfaces not explicitly listed in this document, should be considered as

internal and subject to change.

In previous Pegasus releases this information was available as a separate

PEP. Starting with Pegasus 2.9.0 this information is integrated into the

Pegasus repository as  pegasus/doc/EnternalInterface.html.

<li>

OpenPegasus  SDK Packaging Definition - </li>

PEP 352</a> - Defines the

recommended set of files for inclusion in the OpenPegasus SDK

<li>

Pegasus  Runtime Packaging Definition -

PEP 351</a> - </li>Defines the

recommended set of files for inclusion in this OpenPegasus release.

<li>Pegasus Release Notes -  PEP 355

- (This document is located in the

approved PEP

repository and the OpenPegasus source tree root directory (<big>pegasus/ReleaseNotes.htm</big>)

</li>

<li>PEP 289  - Pegasus 2.6 readme.txt (Located in PEP

repository and also in the OpenPegasus

</ol>

source

tree root directory).</li>

<h2><a name="General Documentation">General Documentation</a></h2>

</ol>

The following documentation is available for the this Pegasus

<h2><a name="General Documentation">General Documentation</a></h2>

release:

The following documentation is available for the this Pegasus

release:

<li class="MsoNormal" style="color: black;">Utilities - A

<li class="MsoNormal" style="color: black;">Utilities - </li>A

combination of help generally available with the -h option for each

combination of help generally available with the --help option for each

command and HTML documentation for most of the tools.<o:p></o:p></li>

command and HTML documentation for most of the tools.<o:p></o:p>

<li class="MsoNormal" style="color: black;">API and  usage

documentation - See the header files and the HTML  API

documentation - </li>See the header files and the HTML  API

documentation that is on the web site. The best API usage documentation

is the existing utilities and test programs and the examples in the API

documentation.  In particular the Common/tests unit tests contain

extensive examples of the use of the Common APIs.</li>

extensive examples of the use of the Common APIs.

<li class="MsoNormal" style="color: black;">Building and Debugging

Providers - Readme.html in the Pegasus Root Directory, API

Providers - </li>Readme.html in the Pegasus source tree Root Directory, API

documentation, and documentation from the Pegasus Technical Workshop

which is available on the Pegasus web site.</li>

which is available on the Pegasus web site.

<li class="MsoNormal" style="color: black;">Building and Debugging

Clients - API documentation and the documentation on the Pegasus

Clients - </li>API documentation and the documentation on the Pegasus

Technical Workshop which is available on the Pegasus web site.</li>

Technical Workshop which is available on the Pegasus web site.

<li class="MsoNormal" style="color: black;">Compiler operation and

commands - compiler help (cimmofl -h)</li>

<li class="MsoNormal" style="color: black;">PEPs - The

<li class="MsoNormal" style="color: black;">PEPs - </li>The

features of Pegasus that have been installed in this and the previous

few versions are defined by Pegasus PEPs that are available on the

OpenPegasus web site.  While these are the original design

documents largely and use in the process of defining and approving the

overall characteristics of new functionality, they serve as a guide to

the design and implementation of these features.</li>

the design and implementation of these features.

</ul>

<span

<hr>Licensed to The Open Group (TOG) under one or more contributor license

style="color: black;">  <o:p></o:p>

agreements. Refer to the OpenPegasusNOTICE.txt file distributed with

<div class="MsoNormal" style="text-align: center;" align="center"><span

this work for additional information regarding copyright ownership.

style="color: black;">

Each contributor licenses this file to you under the OpenPegasus Open

<hr align="center" color="#009900" noshade="noshade" size="2"

Source License; you may not use this file except in compliance with the

width="100%">

License.

Permission is hereby granted, free of charge, to any person obtaining a

Corporation; Hewlett-Packard Development Company, L.P.; IBM Corp.; The

copy of this software and associated documentation files (the "Software"),

Open Group; VERITAS Software Corporation; Intel Corp.

to deal in the Software without restriction, including without limitation

the rights to use, copy, modify, merge, publish, distribute, sublicense,

Permission is hereby granted, free of charge, to any

and/or sell copies of the Software, and to permit persons to whom the

person obtaining a copy  of this software and associated

Software is furnished to do so, subject to the following conditions:

documentation files (the "Software"), to deal in the Software without

The above copyright notice and this permission notice shall be included

restriction, including without limitation the rights to use, copy,

in all copies or substantial portions of the Software.

modify, merge, publish, distribute, sublicense, and/or sell copies of

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS

the Software, and to permit persons to whom the Software is furnished

OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF

to do so, subject to the following conditions:

MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.

IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY

THE ABOVE COPYRIGHT NOTICE AND THIS PERMISSION

CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,

NOTICE SHALL BE INCLUDED IN ALL COPIES OR SUBSTANTIAL PORTIONS OF THE

TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE

SOFTWARE. THE SOFTWARE IS PROVIDED  "AS IS", WITHOUT WARRANTY OF

SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE

WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND

NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE

LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION

OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION

WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

</div>

</div>

</body>

</body></html>

</html>

Legend:

Removed from v.1.11
changed lines
	Added in v.1.17

No CVS admin address has been configured