Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!rutgers!labrea!decwrl!pyramid!prls!philabs!ttidca!sa
From: sa@ttidca.TTI.COM (Steve Alter)
Newsgroups: comp.unix.wizards
Subject: Re: multiple-machine executables for Suns?
Message-ID: <1080@ttidca.TTI.COM>
Date: Sat, 8-Aug-87 05:46:35 EDT
Article-I.D.: ttidca.1080
Posted: Sat Aug  8 05:46:35 1987
Date-Received: Mon, 10-Aug-87 04:40:52 EDT
References: <1853@megaron.arizona.edu> <639@ima.ISC.COM>
Sender: news@ttidca.TTI.COM
Reply-To: sa@ttidca (The Sa of all Evil)
Organization: Citicorp/TTI, Santa Monica
Lines: 16
Keywords: Keep It Simple, Stu***

It makes much more sense to stick with symbolic-links to the
directories containing the binaries (just one executable per file) for
whichever machine you happen to be running on.  Mr. Tannenbaum noted
that such is already the case on machines that have done dual-ports of
BSD and SYS V, i.e. if you're running in BSD mode then /bin is really
a symlink to something like /.bsdbin whereas the SYS V mode /bin is a
symlink to /.attbin (we have a Pyramid that does something like this.)

Additionally, SUN has done something like this too.  We have a network of
Sun 2's and Sun 3's that all have NFS-mounts to files on a common server.
From the Sun 2, /bin is a symlink to something like /pub/MC68010.bin
whereas from the Sun 3, /bin is symlinked to /pub/MC68020.bin.

If you want to start archiving your executables and have the kernel
do an extraction upon every invocation (even with supreme caching!)
then you're just pouring your performance down the drain!