Xref: utzoo comp.unix.sysv386:3704 comp.editors:2325
Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!samsung!zaphod.mps.ohio-state.edu!rpi!uupsi!jpradley!jpr
From: jpr@jpradley.jpr.com (Jean-Pierre Radley)
Newsgroups: comp.unix.sysv386,comp.editors
Subject: Re: SCO uname
Message-ID: <1991Jan04.044334.1891@jpradley.jpr.com>
Date: 4 Jan 91 04:43:34 GMT
References: <9101020746.AA08202@robobar.Co.Uk> <1991Jan02.142840.6855@jpradley.jpr.com> <9392@scolex.sco.COM>
Reply-To: jpr@jpradley.UUCP (Jean-Pierre Radley)
Organization: NYC Public Unix
Lines: 43

In article <9392@scolex.sco.COM> chapman@sco.COM (Brian Chapman) writes:
>
>jpr@jpradley.jpr.com (Jean-Pierre Radley) writes:
>
>>Sounds good but it seems to me I already have that version. Running
>>"uname -v -r" shows:
>>	3.2 2
>
>BTW all versions of SCO UNIX uname(C) report "3.2 2".
>
>This is what the utsname contained in the original
>AT+T system V 3.2 tape.  And we have left it alone
>for compatiblity reasons.
>
>In 3.2v2 we have defined a scoutsname structure that
>is printed out w/ uname -X.
>
>If uname -X fails w/ an error message then you have
>3.2.0 or 3.2.1.
>
>Doing a what(C) of the binaries, as jpr points out, is
>a valid test of the version.
>


Ok, thanks for that information, which certainly wasn't obvious.
So now if I type uname -X, I get:

System = jpradley
Node = jpradley
Release = 3.2v2.0
KernelID = 90/06/10
Machine = i80386
BusType = AT
Serial = sco006664
Users = unlim
OEM# = 0
Origin# = 1
NumCPU = 1

Meanwhile my 'vi' is still broken.

 Jean-Pierre Radley	    NYC Public Unix	jpr@jpr.com	CIS: 72160,1341