1 a.arora 1.21
2 OpenPegasus - A Manageability Services Broker for the DMTF CIM/WBEM Standards
3
4 Author: Mike Brasher, Karl Schopmeyer
5
6 Tagline: OpenPegasus is an object manager for DMTF CIM objects written in C++
7 and supported by The Open Group
8
9 STATUS: Revised March 10 to match Pegasus release 2.3
10
11 NOTE: Obsolete. See readme.html
12 Contents:
13 =========
14
15 1. Overview
16 2. Availability of Pegasus
17 3. Pegasus major components
18 4. Pegasus Dependencies
19 5. The Pegasus Directory Structure
20 6. Installation
21 7. Building Pegasus
22 a.arora 1.21 8. Populate the Repository
23 9. The MU Utility
24 10. Notes about Building Pegasus on Linux
25 11. Notes about Building Pegasus on Mac OS X/Darwin
26 12. Notes on building Pegasus with SSL
27 13. Building Pegasus on Windows 2000 or Windows XP With Microsoft Visual C++
28 14. Installing the Pegasus HTML Test Client
29 15. Development with Pegasus and Pegasus Tools
30 16. Commands
31 17. Creating SSL certifications.
32 18. Configuring Pegasus to use SSL
33 19. Configuring Pegasus to use PAM
34 20. Testing with ICU enabled
35 21. Documentation
36 22. Participate
37
38
39
40
41 1. Overview:
42 ============
43 a.arora 1.21
44 OpenPegasus (also refered to as Pegasus):
45
46 Pegasus is an open-source object manager for DMTF CIM objects. It is written
47 in C++ and includes the Object manager, a set of defined interfaces, and SDKs
48 for both client, providers, and services extensions. It is maintained
49 consistent with the DMTF CIM and WBEM specifications except for any exceptions
50 noted in the documentation.
51
52 This distribution represents a work in progress towards building a Pegasus
53 release. Pegasus is open source and is covered under the following license.
54 This version is incomplete and is directed towards evaluators and developers
55 of the Pegasus Architecture.
56
57 Pegasus is being developed and maintained under the auspices of The Open
58 Group. Pegasus is maintained under the license defined in the doc directory
59 (LICENSE) of this release. This licensing is intended to support as wide a
60 distribution as possible with minimal demands on the users.
61
62 This distribution represents a snapshot of the current work. Currently Pegasus
63 is in phase 1 of a multiphase development project. This snapshot is primarily
64 a.arora 1.21 for developers and for evaluation of the project.
65
66 More information on this project, access to the CVS, and documentation on
67 Pegasus are available from the OpenGroup WEB site.
68
69 There are separate files in the release for
70
71 History of releases - HISTORY
72 What's new for this release - WHATSNEW
73 What's Broken - BUGS
74
75 In addition, the roadmap for Pegasus and further information on the project is
76 available on The Opengroup Pegasus WEB Site.
77
78 http://www.openpegasus.org
79
80
81 2. Availability of Pegasus:
82 ============================
83
84 Pegasus is distributed as open source. The distribution is available via
85 a.arora 1.21 CVS and snapshot images in tar and zip file formats.
86
87 The source code from CVS can be found at the following Open Group CVS server;
88
89 cvs.opengroup.org:/cvs/MSB
90
91 using the password authenticating server option (pserve).
92
93 Anonymous access for read is with the name and password "anon" as follows:
94
95 %export CVSROOT=:pserver:anon@cvs.opengroup.org:/cvs/MSB
96 %cvs login
97
98 When requested, enter the password "anon"
99
100 The source tree is in the directory pegasus. To check out the complete Pegasus
101 source tree just type:
102
103 cvs co pegasus
104
105 A Pegasus directory will be created under the current directory and populated
106 a.arora 1.21 with the complete source tree and documentation. To get the latest updates
107 after a checkout just type this from Pegasus root:
108
109 cvs update -d
110
111
112 Active contributors to Pegasus have write access to the CVS repository.
113 If you are interested in contributing back to the Pegasus project,
114 (i.e. write (checkin) access to CVS) please request access from either
115 Martin Kirk (m.kirk@opengroup.org) or Karl Schopmeyer (k.schopmeyer@opengroup.org).
116
117
118 3. Pegasus Major Components:
119 =============================
120
121 The major components of Pegasus are:
122
123 Pegasus Server - WBEM/CIM Server with interfaces for providers and clients
124
125 Pegasus Repositories - Today Pegasus provides a defined class repository
126 interface and a simple file based class repository. It also includes
127 a.arora 1.21 an instance repository. Note that these repository were created for
128 functionality, not efficieny. It is expected that they will be replaced
129 with other implementations of the respository function as the need arises.
130
131 Pegasus Client SDK - Tools for building Pegasus clients based on the Pegasus
132 C++ interfaces and using the WBEM HTTP/XML protocols or directly
133 interfacing with Pegasus.
134
135 Pegasus Test Clients - Simple test clients being developed as part of the
136 Pegasus development process
137
138 Pegasus HTML Test Client - To aid in testing we created a test client for
139 Pegasus that uses a WEB server (ex. Apache) with a set of CGI modules and
140 HTML to allow the entry of Pegasus operations from a WEB browser as forms
141 and the receipt of the response as WEB pages. This has proven useful as a
142 test tool and can be used for a wide variety of demonstrations.
143
144 Pegasus Provider SDK - Tools for building Pegasus providers using the Pegasus
145 C++ interfaces.
146
147 Pegasus Providers - Providers to illustrate the use of Pegasus services including
148 a.arora 1.21 providers for test and demonstration.
149
150 Pegasus Service Extensions - Common services for use by other Pegasus
151 components to extend Pegasus capabilites.
152
153 Pegasus MOF Compiler - FA standalone compiler for MOF files that can be used
154 to install MOF into the Pegasus schema repository and also to check syntax.
155 There is also a tool to extract the MOF from the repository.
156
157
158 4. Pegasus Dependencies:
159 =========================
160
161 We have worked to minimize the dependence of Pegasus on other software
162 packages and tools. Currently Pegasus has the following dependencies:
163
164 1. GNUMAKE - To simplify the building of Pegasus across multiple platforms we
165 have standardized on a set of build tools including: GNUMAKE. We are using
166 GNUMAKE 3.79.1 successfully both in Windows and Linux environments.
167
168 GNUMAKE is available from
169 a.arora 1.21
170 http://www.gnu.org
171
172
173 2. MU.EXE - To minimize the difference between Linux and Windows for GNUMAKE,
174 we have created a utility called MU.exe. This utility is required for
175 Pegasus make with ONLY Windows environment. It is provided as an alternative to
176 requiring a number of UNIX utilities (SH, RM, etc.) on the windows platform
177 and effectively provides the functions of these utilities that GNUMAKE
178 needs. MU is not required on UNIX or LINUX platforms.
179
180 NOTE: The binary for MU.EXE is not distributed in the Pegasus bin directory.
181 You must build it separately. MU source code is part of the distribution
182 in the directory src/utils/MU with its own make file. You must compile MU
183 before you initiate the Pegausu make.
184
185 NOTE: A copy of the binary is made available as a zip file on the Pegasus
186 WEB site.
187
188 Again, MU is used ONLY if you are using Windows.
189
190 a.arora 1.21
191 3. FLEX and BISON - These tools were used to develop the MOF compiler and WQL
192 parser. Anybody intending to recompile the compiler or parser from scratch
193 will be required to have these tools. They are only required if changes need
194 to be made to the files for parsing and compiling.
195
196
197 4. DLCOMPAT - dlcompat is a dlopen(3) et.al. compatibility library for
198 Mac OS X/Darwin.
199
200 NOTE: The dlcompat is not distributed with pegasus source.
201
202 dlcomapt is available from
203
204 http://www.opendarwin.org/projects/dlcompat/
205
206 Again, dlcomapt needs to be installed ONLY if you are using Mac OS X/Darwin.
207
208
209 5. DOC++ - The Pegasus documentation is taken from a combination of text files
210 and the Pegasus header files themselves. This documentation is formatted
211 a.arora 1.21 with DOC++ and GAWK. These tools are required if the documentation is to
212 be recreated but we expect that only the core team will be recreating
213 documentaiton.
214
215
216 5. The Pegasus Directory Structure
217 ===================================
218
219 Pegasus is distributed as a complete directory structure that should be
220 installed either from one of the snapshots or from CVS.
221
222 This structure is generally as follows
223
224 Pegasus Pegasus Root directory
225
226 cgi Source for the Pegasus WEB Based Test client
227 cgi-bin CGI Directories for WEB demonstration.
228 This directory is normally empty but can
229 be populated from the runtime with the make
230 from cgi.
231 htdocs HTML Pages for Pegasus WEB emonstration
232 a.arora 1.21 doc Miscellaneous Pegasus Documents.
233 DevManual Source and build files for developers' manual
234 mak General make files (used by other makes)
235 src All Pegasus Source Files
236 ACEExample Test directrory with examples of the use of ACE (obsolete).
237 Clients Source for various test clients and client SDK
238 CGICLIENT Pegasus test client that uses a WEB browser
239 JAVA Java Client support modules
240 Pegasus
241 Client Pegasus Client API Tests
242 depends
243 tests
244 Common Pegasus Common Functions (C++ source and headers
245 tests Test programs for the common functions
246 Compiler Pegasus MOF compiler
247 Config TBD
248 Consumer TBD
249 ControlProvidersImplementation of Pegasus internal providers
250 ExportClient TBD
251 ExportServer TBD
252 Handler TBD
253 a.arora 1.21 HandlerService TBD
254 IndicationService TBD
255 Listener TBD
256 Protocol Pegasus Client HTTP/XML Protocol Modules
257 depends
258 Provider Pegasus Provider interface functions
259 ProviderManager Provider Manager service that manages providers
260 ProviderManager2Pluggable Provider Manager service
261 Repository Pegasus Repository Interfaces and Simple Repository
262 tests Tests for Repository Functions
263 Security TBD
264 Server Pegasus Server Modules
265 WQL TBD
266 Providers Pegasus test and required providers
267 generic TBD this and following
268 IndicationConsumer
269 Linux
270 ManaedSystem
271 slp
272 statistic
273 sample
274 a.arora 1.21 testproviders
275
276 Server Pegasus executable build
277 slp
278 StandardIncludes
279 tools MU and other utilities written for Pegasus support
280 Unsupported Code that is made available but is not supported or included
281 in the normal make.
282 WMIMapper Pegasus implementation that implements mapping to Microsoft
283 WMI objects.
284
285 Runtime Directories
286 $PEGASUS_HOME$ Home directory for runtime. All compiler, linker
287 documentation creation, etc. is put here.
288 bin Destination for executable and DLL modules from
289 Pegasus build
290 Manual HTML output of the Pegasus Manual
291 lib Destination for Pegasus LIB modules
292 obj Destination for object modules
293 repository This Directory contains the created repository
294
295 a.arora 1.21
296 6. Installation
297 ================
298
299 Pegasus today is provided only as a source distribution.
300
301 To install Pegasus, you must check it out using CVS (Common Version System)
302 or download the snapshot. You download, compile, and use it.
303
304 For the snapshot, the installation of Pegasus involves expanding the snapshot
305 distribution files, building the runtime, the test files and test clients, and
306 building the repository.
307
308
309 7. Building Pegasus
310 =====================
311
312 1. Check that you have requisite programs (listed in Pegasus Dependencies).
313
314 These include GNU Make, MU.EXE (if using Windows), Flex, and Bison (Flex
315 and Bison only required if changes will be made to the MOF compiler or WQL
316 a.arora 1.21 parser),dlcompat (if using Mac OS X/Darwin).
317
318 Be sure these are on your path.
319
320
321 2. Define the following three environment variables:
322
323 PEGASUS_ROOT - this should be the "pegasus" directory you've pulled from CVS
324
325 PEGASUS_HOME - to point to a directory to contain output binary files
326 (e.g., set it to $HOME/pegasus_home). Then the output will go into
327 $HOME/pegasus_home/bin and $HOME/pegasus_home/lib
328
329 PEGASUS_PLATFORM - this must be set to a supported platform identifier.
330
331 This identifier has the following form:
332
333 <Operating-System>_<Architecture>_<Compiler>
334
335 For example (Linux on IA32 platform using the GNU Compiler):
336 LINUX_IX86_GNU
337 a.arora 1.21
338 For a complete list, refer to the platform_ make files found in directory
339 pegasus/mak
340
341
342 Note: if you plan on doing parallel builds, you might consider setting
343 PEGASUS_HOME to something like this:
344
345 $HOME/pegasus_home_LINUX_IX86_GNU
346
347 That way, the output of each build will be placed in its own directory.
348
349 3. Now place $PEGASUS_HOME/bin on your path
350
351 and
352
353 Place $PEGASUS_HOME/lib on your LD_LIBRARY_PATH (for Unix only).
354 For RedHat/SuSE/UL, edit /etc/ld.so.conf and add $PEGASUS_HOME/lib
355
356 4. Change to the root of the Pegasus distrubution and type "make"
357 (where make refers to GNU make).
358 a.arora 1.21
359 5. Then create the repository, which is needed to serve data.
360 "make repository"
361
362 6. To test the build type "make tests".
363
364 The following make targets are supported:
365
366 <default> - Build everything.
367 clean - Clean out all objects, libs, and executables.
368 depend - Create the dependencies.
369 repository - Create the repository in $PEGASUS_HOME/repository
370 tests - Execute all tests (except client server tests).
371 rebuild - clean, depend, <default>
372 world - depend, <default>
373
374 The Pegasus Client server tests are executed separately from the above because
375 they require the initiation of separate process for the Pegasus server and
376 Pegasus client. To execute these tests please refer to the scripts in
377 pegasus/mak/BuildMakefile - refer to the prestarttests and poststarttests.
378
379 a.arora 1.21 For information on particular installation characteristics, tools, etc. for
380 each platform see the appropriate sections below:
381
382 Generally the build commands are as follows:
383
384 1. There is a Makefile in the Pegasus root directory. Simply executing
385 make in the Pegasus root directory will make everything. "make rebuild"
386 will clean and rebuild everything. The "make rebuild" will also populate
387 the repository with the current CIM Schemas.
388
389 2. To test a fresh release, go to the pegasus root and type
390
391 "make world".
392
393
394 This will build dependencies, build binaries, and then run all
395 tests except the Client/Server tests.
396
397 3. To execute the basic test suite that is shipped with pegasus type
398
399 "make tests". This also reintalls the repository.
400 a.arora 1.21
401 Running "make -s tests" suppresses extraneous output such as the
402 enter/leave directory messages.
403
404 4. "make clean" removes all object and library files from the structure.
405
406
407 5. A new build system has been added to Pegasus where a new CVS checkout is done,
408 built, and tests are run. Do it by: "make -f mak/BuildMakefile cleanbuild"
409
410
411 8. Populate the Repository
412 ===========================
413
414 Before using Pegasus you must populate the repository with the providers. The makefile
415 does it all for you, but in case you are wondering what it does or how to do it
416 manually:
417
418 1. Register the MOF (Managed Object Format) file describing the skeleton of the object.
419 2. Register a second MOF which only points out which lib*.so file to be loaded when a
420 specific object is activated.
421 a.arora 1.21
422 This is done automatically for the providers included in Pegasus by doing:
423 make repository.
424
425 The 'make repository' in pegasus/Schemas does three things
426 Runs MOF compiler (cimmofl) on:
427 -Schema v2.7
428 Generates the CIM Schema v2.7 in the repository (skeleton of CIM objects)
429 -PG_InterOp
430 Internal to Pegasus schema for operating (shutdown, add users, etc)
431 CIM_Indication’s (SNMP, Events, Alert, Threshold, etc)
432 -PG_ManagedSystem
433 Registers included CIM Providers (libOSProvider.so, libDNSProvider.so, … )
434 in Pegasus (which are located in src/Providers)
435
436 For more information about using the MOF compiler, refer to user's manual on the
437 openpegasus.org.
438
439
440 9. The MU Utility
441 ===================
442 a.arora 1.21
443 In order to provide a consistent build structure across multiple platforms, we
444 developed a small utility to provide a consistent set of small utilities
445 across these platforms. The MU utilityis a simple utility that contains many
446 commands. For example:
447
448
449 C:\> mu rm myfile.cpp yourfile.cpp
450
451
452 You may type "mu" to get a list of valid commands. Here are some
453 of them:
454
455
456 rm, rmdirhier, mkdirhier, echo, touch, pwd, copy, move, compare depend
457
458
459 The MU utility supports globing (expansion of wildcards) so
460 you can do things like this:
461
462
463 a.arora 1.21 C:\> mu rm *.obj *.exe
464
465 MU is required to build under the Windows environment.MU is available as part
466 of the distribution of Pegasus.
467
468
469 10. Notes about Building Pegasus on Linux
470 ===========================================
471
472 No problem. Just make sure you have the environment variables set.
473
474
475 11. Notes about Building Pegasus on Mac OS X/Darwin
476 =====================================================
477
478 No problem. Just make sure you have the environment variables set.
479
480
481 12. Notes about Building Pegasus with SSL
482 ==========================================
483
484 a.arora 1.21 To build with SSL you need the OpenSSL libraries and header files. Make sure
485 you have them in a standard directory so Pegasus can find them. If that's not
486 the case, set the environment varialble OPENSSL_HOME= to point where your OpenSSL
487 installation is.
488
489 Also have the PEGASUS_HAS_SSL=yes variable set. Then just run 'make' in Pegasus
490 directory and you will have Pegasus with SSL enabled. See section "Creating SSL
491 certificates" for more information of how to use SSL.
492
493
494 13. Building Pegasus on Windows 2000 (SP3 or later recommended) or Windows XP
495 With Microsoft Visual C++
496 ======================================================================
497
498 Today we build Pegasus on Windows using a set of make files contained
499 in the source distribution, the Microsoft compilers (DevStudio 5.x is not
500 supported, Visual Studio 6.0, SP5 supported) and the GNUMAKE make utility.The
501 following is the basic setup steps for the environment.
502
503
504 Setup the environment variables and path for the Micrososft Visual C compiler.
505 a.arora 1.21 Typically this can be done by running the VCVARS32.BAT file supplied with
506 Microsoft Visual C++. (contained in the same directory as cl.exe).
507
508 For Windows, try the following for an example environment:
509
510 REM call the standard Microsoft .bat for VC 6 setup.
511 call 'C:/Program Files/Microsoft Visual Studio/VC98/Bin/Vcvars32.bat'
512 REM Set debug to something if you want compile in debug mode
513 set PEGASUS_DEBUG=true
514 REM set PEGASUS_ROOT to top of source tree
515 set PEGASUS_ROOT=C:/cimom/pegasus
516 REM set PEGASUS_HOME to where you want repository and executables
517 set PEGASUS_HOME=%PEGASUS_ROOT%
518 REM setup the path to the runtime files.
519 set path=%path%;%PEGASUS_HOME%/bin
520
521 14. Installing the Pegasus HTML Test Client:
522 =============================================
523
524 This is a separate test tool that allows Pegasus requests to be initiated from
525 any WEB browser and that uses a WEB browser, CGI scritps and HTML pages for
526 a.arora 1.21 the formating and connections. It requires a WEB server, etc. The
527 instructions for setting up this environment are maintained in a separate
528 readme in the CGI directory.
529
530
531 15. Development with Pegasus and Pegasus Tools:
532 ================================================
533
534 ATTN: This section needs to be completed. It should reference the more
535 complete documentation
536 ATTN: Write about providers?
537
538
539 16. Commands:
540 =============
541
542 The manpages for each of the commands are in rpm/manLinux/man1.Z directory (on CVS)
543
544 To see simple help for each of the commands, use the "-h" flag.
545 Examples:
546 bin/cimserver –s (Shuts it down)
547 a.arora 1.21 bin/cimserver traceLevel=4 traceComponents=ALL (starts server with config flags)
548 bin/cimprovider –l –s (lists providers and their status)
549 bin/cimprovider –e –m OperatingSystemModule (enables the OperatingSystem provider)
550 bin/cimuser –a –u guest –w ThePassword
551 bin/cimuser –l (lists the users)
552 bin/tomof CIM_Config (extract CIM_Config from repository and present it in MOF type)
553
554
555 17. Creating SSL certifications
556 ================================
557
558 Please follow section 11, titled "Notes about Building Pegasus with SSL"
559 before embarking on this endeavour.
560
561 Type these commands in your shell to create the SSL certifications. The PEGASUS_ROOT
562 and PEGASUS_HOME have to be set to your respective installation and source directory.
563
564 CN="Common Name"
565 EMAIL="test@email.address"
566 HOSTNAME=`uname -n`
567 sed -e "s/$CN/$HOSTNAME/" \
568 a.arora 1.21 -e "s/$EMAIL/root@$HOSTNAME/" $PEGASUS_ROOT/src/Server/ssl.cnf \
569 > $PEGASUS_HOME/ssl.cnf
570 chmod 644 $PEGASUS_HOME/ssl.cnf
571 chown bin $PEGASUS_HOME/ssl.cnf
572 chgrp bin $PEGASUS_HOME/ssl.cnf
573
574 /usr/bin/openssl req -x509 -days 365 -newkey rsa:512 \
575 -nodes -config $PEGASUS_HOME/ssl.cnf \
576 -keyout $PEGASUS_HOME/key.pem -out $PEGASUS_HOME/cert.pem
577
578 cat $PEGASUS_HOME/key.pem $PEGASUS_HOME/cert.pem > $PEGASUS_HOME/server.pem
579 cp $PEGASUS_HOME/cert.pem $PEGASUS_HOME/client.pem
580 rm $PEGASUS_HOME/key.pem $PEGASUS_HOME/cert.pem
581
582 18. Configuring Pegasus to use SSL
583 ================================
584
585 Please follow section 11 and 16 before reading this section.
586
587 To configure Pegasus to take advantage of SSL, configure
588 CIMserver to have the following configuration options set to:
589 a.arora 1.21
590 sslTrustFilePath=client.pem
591 sslCertificateFilePath=server.pem
592 sslKeyFilePath=file.pem
593 httpsPort=5989
594 enableHttpsConnection=true
595
596 using the 'cimconfig' utility:
597
598 cimconfig -p -s enableHttpsConnection=true
599
600 (The client.pem and server.pem are the certifications
601 files created per the steps in the earlier section).
602
603 For good riddance you might consider closing down
604 the cleartext 5988 port. Modify your CIMserver to
605 (using 'cimconfig') to have the option:
606
607 enableHttpConnection=false
608
609 19.PAM Authentication
610 a.arora 1.21 ===================
611
612 In order to use PAM Authentication you have to compile Pegasus
613 with one extra enviroment flags:
614
615 PEGASUS_PAM_AUTHENTICATION=1
616
617 You can also set the PEGASUS_ALWAYS_USE_PAM=1 flag to disable
618 Pegasus password authentication using a flag text-file (recommended).
619
620 After compiling (refer to section 17 for details), follow these two
621 important steps:
622
623 a). Copy the rpm/wbem file in-to /etc/pam.d directory.
624 This notifies PAM what kind of libraries to use when authenticating
625 Pegasus.
626 b). Modify CIMserver configuration options:
627
628 usePAMAuthentication=true
629 enableAuthentication=true
630
631 a.arora 1.21 And if you want to allow 'root' (*not recommended*)
632 enableRemotePrivilegedUserAccess=true
633
634 using the 'cimconfig' operation, such as:
635
636 cimconfig -p -s usePAMAuthentication=true
637
638 The user is authenticated using HTTP Basic method, thererfore it is
639 strongly suggested you use SSL connection instead of normal HTTP connection.
640 Refer to section 16 for more details on creating and using SSL keys.
641
642 20. Testing with ICU enabled:
643 ==============================
644
645 ICU (International Compoments for Unicode) refers to the set of libraries that
646 Pegasus uses to run globalized. For example: these libraries are used to
647 load messages in different languages, format currency and numbers according to
648 a specific locale etc. In order to enable globalization in Pegasus, Pegasus
649 must be built with ICU enabled, ie. the right environment variables must be
650 set prior to running "make". Refer to the GlobalizationHOWTO.htm in the docs
651 directory for details. That said, when users run "make poststarttests"
652 a.arora 1.21 to verify the integrity of a Pegasus download, a series of tests are run that
653 require the cimserver to be running. These tests currently depend on specific
654 messages returned from the server. When ICU is enabled, all messages come
655 from the resource bundles and these usually do not match the hardcoded
656 default messages within Pegasus. These hardcoded default messages
657 are what the various test programs expect in order to complete
658 successfully. If the ICU enabled server is started without
659 disabling message loading from the bundles, "make poststartests" will fail.
660 In order to run "make poststarttests" successfully with ICU enabled, an
661 environment variable called PEGASUS_USE_DEFAULT_MESSAGES must exist prior to
662 starting the server. Once this is defined, when the cimserver starts, all
663 messages generated will be the default hardcoded messages. This will enable
664 "make poststarttests" to complete successfully. Once "make poststarttests" is
665 complete, you should stop the cimserver and then undefine PEGASUS_USE_DEFAULT_MESSAGES.
666 If this variable is left defined, Pegasus will not be able to load messages
667 using ICU resource bundles.
668
669 21. Documentation:
670 ===================
671
672 The documentation is currently in preperation. The preliminary documentation
673 a.arora 1.21 is not provided with this snapshot but is avialable from the OpenGroup Pegasus
674 WEB pages. The current documentation is maintained both as a manual created
675 under the tool DOC++ in the runtime subdirectory manual/html and as other
676 miscelaneous documentation in the doc directory.
677
678 Note that the Pegasus WEB site at The Open Group will be the source of most
679 documentation in the future and today is the source of most discussion and
680 design documentation.
681
682
683 22. Participate!
684 =================
685
686 We are looking for people who want to join the Pegasus work group and
687 contribute to effort of getting this Pegasus off the ground. Please join
688 the mailing list by visiting www.openpegasus.org, and click on Mailing Lists.
|
Return to
readme.txt
CVS log
Up to [Pegasus] / pegasus