how to -- shell SVR4 detect (uname and SVR4)

how to -- shell SVR4 detect (uname and SVR4)

Post by Scott G. Ha » Tue, 10 Sep 1996 04:00:00




>I'm intersted in confirming the correct results for uname(1), particular
>the POSIX.2 standard and on AT&T, NCR, SVR4 boxes.

>I've seen a couple SVR4 boxes on our network at work, and these ATT/NCR
>boxes came back with the machine name as if uname -s really was uname -n.

>Question : what should shell script writers expect on ATT/NCR
>boxes when they use uname -s. And shouldn't it be "UNIX_SVR4" even though
>sysadm's can routinely run setuname to whatever they want?

It is not a problem with NCR UNIX, but rather with people's use of an
old SVR3 command.  We sell products with UnixWare, used to sell products
with SVR3.2, and our customer's got used to the "uname -S node" command
of the older UNIX and insist on using it instead of "setuname -n node".

You see, it was thought that for UUCP to work correctly, you needed to
set the "system" name to that used in the other box's Systems file.  So
"uname -S" did exactly that, set both the node and the system name to
the same value, and scripts got written to either value.  What they
didn't realize is that the originators of UNIX where operating-system
centric, and so when they say 'system', they mean 'operating system',
regardless of what the UUCP system considers a "system".

Even now, one of our department servers running UnixWare (an SVR4.2)
displays the following to a "uname -a":

        machinename machinename 4.2 1 i386 386/AT

The people installing your NCR-UNIX boxes should have used the
"setuname -n" command to set the nodename.  The "setuname -s" command
can be used to correctly set the system value back to "UNIX_SV" or
"UNIX_SVR4".

Quote:>How dows the gnu software figure out which machine they are on in this
>exact same scenario?

It checks for both the system and the node fields, and if they are the
same, it ignores those fields and pokes around UNIX'isms unique to
System-V or unique to BSD, and then pokes further to test for files and
directory structures that changed between releases.

Note this can fail, as in the SVR2.4 system I have at home (one of the
last 16-bit UNIXes) that added some SVR3-type things (like shadow
passwords and such) and Berkeley utilities and libraries.  If I had
software that look for file differences between versions, it might
mistake that system for a SVR3 system, and fail to build software (the
compiler is *VERY* SVR2 centric).

--
"It was our last, best hope for peace -- it failed.       | Scott G. Hall
Now it's our last best hope." (Babylon-5 opener)          | Lucent Technologies
----------------------------------------------------------| Bell Labs - BCS

 
 
 

how to -- shell SVR4 detect (uname and SVR4)

Post by Duncan Ida » Tue, 10 Sep 1996 04:00:00


I'm intersted in confirming the correct results for uname(1), particular
the POSIX.2 standard and on AT&T, NCR, SVR4 boxes.

I have an old draft 11 of the Posix standard which says that

        uname -s
and
        uname

should be the same and display the implementation name of the OS. For
systems like AIX, HP, and SUn, they all clearly conform and report things
like AIX, HP-UX, and SunOS.

I've seen a couple SVR4 boxes on our network at work, and these ATT/NCR
boxes came back with the machine name as if uname -s really was uname -n.

Whereas, my internet ISP has a UNIXWare machine which has always returned

        UNIX_SVR4

Question : what should shell script writers expect on ATT/NCR
boxes when they use uname -s. And shouldn't it be "UNIX_SVR4" even though
sysadm's can routinely run setuname to whatever they want?

How dows the gnu software figure out which machine they are on in this
exact same scenario?

Thanks in advance, reply by e-mail please.

- D
--
.... (C) 1995 Copyright Duncan Idaho, All Rights Reserved ..................
There are "three absolute rights [sic] the right of personal security, personal
liberty and personal property," Sir William Blackstone.  "The protection of
these faculties is the first object of government." Madison, Federalist 10.

 
 
 

1. SVR4 cpio -c conversion / CMS QIC Tape for SVR4

Two questions:

1. On SVR4, the cpio -c archive header is not the same as pre-SVR4 cpio -c
   headers. In order to read an SVR4-created archive you must use -H odc
   option. However, there are cases where -H odc was not used to create the
   SVR4 cpio archive, and still we needed it to be read on an SVR3 machine.

   Has anybody written a filter to convert the SVR4 format to the pre-SVR4
   format, or must one attempt writing his own?

2. There is a QIC-150 tape drive with a QIC-02 interface from a company
   called CMS Enhancements Inc, in Irvine CA. The drive is called the
   TapeMaster 150. Did anybody test this one with 386 SVR4 on AT-bus?
   Can it be used with Consensys or MST SVR4?

   What are good alternatives (QIC150 drives with AT-bus non-SCSI) that
   are known to work with Consensys/MST for say 800-800$ range? Pls provide
   Email address if possible.

Pls email me of any clues you have.
Thanks in advance.
--
Khalid M. Bahey-elDin           UUCP: ..!uunet!ncrlnk!ncrsaud!kbahey
Systems Services Division       Fax: +966-2-651-8804  Tel: +966-2-651-2727 x 25


2. eOne and Linux - modem question

3. Problem running a sub-shell on SVR4

4. printer daemon not found

5. /bin/false, SVR4, escape to shell

6. Documentation Source Code

7. SVR4 shell

8. question about how to set the ghome

9. sendto() returns 0 on NCR SVR4

10. SVR4, sacadm, no_sac

11. Printing to a SVR4 printer (lp not lpr!)

12. Modifying driver for > 1 cards in UnixWare/SVR4 ?

13. Question about init/inittab on SVR4