Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!columbia!rutgers!dayton!ems!eta!lmcvoy
From: lmcvoy@eta.ETA.COM (Larry McVoy)
Newsgroups: comp.unix.wizards
Subject: Re: multiple-machine executables for Suns?
Message-ID: <8700146@eta.ETA.COM>
Date: Thu, 6-Aug-87 14:51:10 EDT
Article-I.D.: eta.8700146
Posted: Thu Aug  6 14:51:10 1987
Date-Received: Sat, 8-Aug-87 17:51:19 EDT
References: <1853@megaron.arizona.edu>
Reply-To: lmcvoy@eta.UUCP (Larry McVoy)
Organization: ETA Systems, Inc., St Paul, MN, USA
Lines: 20

In article <1853@megaron.arizona.edu> whm@arizona.edu (Bill Mitchell) writes:
>I find myself frequently inconvenienced by the incompatibilities between
>different Sun binaries.  Sun-2 binaries will work on a Sun-3, but not

Hmmm...  It seems like you are going about this in a "hard" way.  Here's an
easy fix:

	Have an environment var MACHINE which == the machine type

	Have /sun2/{bin,usr/bin} , /sun3/{bin,usr/bin} etc

	Then in /bin and /usr/bin replace each program with a shell script that
	figures out which program to execute.

	You'll pay a price, but you could also get around that by setting your
	path correctly at login time.

I dunno, but this seems a lot easier than hacking up the a.out format and being
incompatible with the rest of the world.  But I might be wrong, it's happened
before :)