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