eric@snark.UUCP (Eric S. Raymond) (07/29/88)
I am trying to develop some tools for automatic generation of map file
entries, to be included in the news distribution.
On AT&T and other POSIX-conforming systems I want to use `uname' as a way to
get processor/os/version in a reasonably standard format. To do this, I need
to know what variations in uname output to expect.
*IF YOU ARE A SITE GURU* (I make this caveat so I won't get more than maybe
10 replies per site :-)) please take a moment to fill out the following form
and return it via reply email:
Site name:
Processor/machine:
OS name/version:
uname -s output:
uname -n output:
uname -m output:
uname -r output:
uname -v output:
The left-of semicolon and right-of-semicolon fields in your map entry will do
for lines 2 and 3; the idea is these should be the descriptions humans expect.
If you administer more than one site, try to return one of these for each
*different kind* of machine you have on site (i.e. I don't need to see one
each from the 23 identical workstations on your ethernet).
Your assistance will help me create tools to help keep the maps database up
to date with less effort from site administrators and map coordinators.
Thanks in advance,
--
Eric S. Raymond (the mad mastermind of TMN-Netnews)
UUCP: ..!{uunet,att,rutgers!vu-vlsi}!snark!eric Smail: eric@snark.UUCP
Post: 22 South Warren Avenue, Malvern, PA 19355 Phone: (215)-296-5718gwyn@brl-smoke.ARPA (Doug Gwyn ) (07/30/88)
In article <dfLyw#3mPN5p=eric@snark.UUCP> eric@snark.UUCP (Eric S. Raymond) writes: >On AT&T and other POSIX-conforming systems I want to use `uname' as a way to >get processor/os/version in a reasonably standard format. To do this, I need >to know what variations in uname output to expect. Forget it -- years ago I tried to get the vendors to cooperate on standardizing the use of the various uname fields, which AT&T neglected to do. Unfortunately many of them made what appear to be random choices in their use of the fields. It wasn't helped any by the fact that vendor OS version numbers didn't match the closest UNIX System V version numbers, and the latter have been so disorganized that very few people can correctly interpret one. E.g. "UNIX System V Release 2 Version 2 for DEC VAX", not to be confused with SVR2.2 for DEC VAX, nor with SVR2V2 for 3B20, nor with DEC's Ultrix-32 for the VAX (any release). If you want such a facility, you or 1003.2 will have to design it yourself. uname is hopelessly broken as it now exists.