Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!sdd.hp.com!spool.mu.edu!caen!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!ucbvax!cel.cummins.com!philip
From: philip@cel.cummins.com (Philip D. Pokorny)
Newsgroups: comp.sys.apollo
Subject: Re: How does BLDT get info...
Message-ID: <9106272014.AA09381@cel.cummins.com>
Date: 27 Jun 91 20:14:40 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 36

In a previous posting, Paul Szabo wrote:

> You might want to look at the osinfo calls. The online documentation is
> misleading, 'man osinfo' or 'help calls osinfo' only mention the
> osinfo_$get_rev ('man osinfo_get_rev' or 'help calls osinfo_$get_rev') call.
> The include file is better... Below is an example of use (at SR10.2).

The example included does NOT work at SR10.1...  This is because
of a bug in the include file that has been fixed (I presume at
10.2, it's still fixed at 10.3)  The following change needs to
be made:

      $ cmf //circus/usr/include/apollo/osinfo.h /usr/include/apollo/osinfo.h
      
      A60                 short           textlen,
      changed to
      B60                 short           &textlen,
      
      
      1 discrepancy found.

In looking at the SR10.3 version of the file, we find:

      Changes:
        01/30/90 garyf  standardize inclusion protection
        03/06/89 sekhar pass textlen by reference (i.e. &textlen ) in osinfo_$mem_size
                                                       ^^^
        12/21/88 gilbert Modifications for C++.
        08/31/88 joelm  add new calls
        06/08/88 joelm  add status codes
        03/03/88 joelm  original coding for os_rev_$t

FYI

philip@cel.cummins.com
:)