Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!cmcl2!brl-adm!umd5!decuac!felix!chuck
From: fuat@cunixc.columbia.edu (Fuat C. Baran)
Newsgroups: comp.unix.ultrix
Subject: Re: Ultrix 2.0 executable dumps core on 1.2
Message-ID: <13285@felix.UUCP>
Date: Wed, 18-Nov-87 12:06:28 EST
Article-I.D.: felix.13285
Posted: Wed Nov 18 12:06:28 1987
Date-Received: Sat, 21-Nov-87 08:27:22 EST
References: <12683@felix.UUCP>
Sender: chuck@felix.UUCP
Reply-To: fuat@cunixc.columbia.edu (Fuat C. Baran)
Organization: Columbia University Center for Computing Activities
Lines: 20
Approved: zemon@felix.UUCP

Reply-Path:



In article <12683@felix.UUCP> mark@applix.UUCP (Mark Fox) writes:
>1) How can I *reliably* tell at runtime that I am on a pre-2.0 version of
>   Ultrix so that my application doesn't issue this or other "Bad system calls"?
>   (A compile-time check that would force me to have separate 1.2 and 2.0
>   distributions of my application is not acceptable. Requiring all of my
>   users to upgrade to 2.0 isn't either.)

You should be able to call uname(2) and check the system type before 
issuing the getmnt system call.  (Unless the uname(2) call is new too.
I can't verify that since I don't have a pre-2.0 system around right
now.)

						--Fuat

-- 
ARPANET: fuat@columbia.edu           U.S. MAIL: Columbia University
BITNET:  fuat@cunixc.columbia.edu               Center for Computing Activities
USENET:  ...!rutgers!columbia!cunixc!fuat       712 Watson Labs, 612 W115th St.
PHONE:   (212) 280-5128                         New York, NY 10025