Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!decwrl!shlump.dec.com!riscy.dec.com!croton.DEC.COM!frank
From: frank@croton.DEC.COM (Frank Wortner)
Newsgroups: comp.unix.ultrix
Subject: Re: How do you identify VAX/PMAX cpu's from software?
Keywords: CPU identification
Message-ID: <1241@riscy.dec.com>
Date: 30 May 89 13:57:00 GMT
References: <7005@cbmvax.UUCP> <105@asihub.UUCP>
Sender: news@riscy.dec.com
Distribution: na
Lines: 29

In article <7005@cbmvax.UUCP>, grr@cbmvax.UUCP (George Robbins) writes:

> Subject: Re: How do you identify VAX/PMAX cpu's from software?

> Assuming you really want to do such a disgusting and questionable thing,
> you might take a look at /etc/sizer (man sizer).  [...]  Apparently it
> looks in the running kernel to see what kind of machine the kernel
> thinks it's running on, though there seems to be a lot of other
> silliness going on.
> 
> I don't know what this program does on the PMAX or on other than VAXen.

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.  Afterall,
you have to generate the proper binary for the proper machine.  As far as distiguishing
subtypes of CPUs, look in /usr/include/machine/hwconf.h on PMAXen and
/usr/include/machine/cpu.h on VAXen for information.  Those files contain macros for
processor type identification.

Regards,

						Frank Wortner
						Ultrix Resource Center
						Digital Equipment Corp.
						frank@croton.dec.com

Opinions expressed here are mine alone.  Feel free to share them.