Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!cs.utexas.edu!uunet!ncrlnk!ncr-sd!sceard!mrm
From: mrm@sceard.COM (M.R.Murphy)
Newsgroups: comp.unix.ultrix
Subject: Re: How do you identify VAX/PMAX cpu's from software?
Summary: how to do it
Keywords: CPU identification
Message-ID: <893@sceard.COM>
Date: 1 Jun 89 14:10:08 GMT
References: <7005@cbmvax.UUCP> <105@asihub.UUCP> <1241@riscy.dec.com> <743@dinorah.wustl.edu>
Reply-To: mrm@sceard.COM (0040-M.R.Murphy)
Distribution: na
Organization: Sceard Systems, Inc.  San Marcos, CA  92069
Lines: 49

In article <743@dinorah.wustl.edu> art@dinorah.wustl.edu (Arthur B. Smith) writes:
!In article <1241@riscy.dec.com>, frank@croton.DEC.COM (Frank Wortner) writes:
!> In article <7005@cbmvax.UUCP>, grr@cbmvax.UUCP (George Robbins) writes:
!> 
!> Unfortunately, /etc/sizer does not exist on DECstation 3100 (PMAX), since 
!> the program is VAX-specific.
!> 
!> Distinguishing a VAX from a PMAX can probably be best done at compile 
!> time.
[many lines deleted in the interest of bandwidth]

What you do is look at the front panel of the computer (or the invoice
for the system) and then write a shell script /etc/what_kind_of_system_this_is
that echos said information. This then has the advantage of being able to
be run on lots of different kinds of systems. Even to be extended to the
determination of cabinet configuration, color, or line voltage...

Why, the concept can even be used in (shudder) VMS. The design of the format
for the information from the script is left as an excercise for the reader.

:-)
---
Mike Murphy  Sceard Systems, Inc.  544 South Pacific St. San Marcos, CA  92069
mrm@Sceard.COM        {hp-sdd,nosc,ucsd,uunet}!sceard!mrm      +1 619 471 0655