Revision 9084,
1.3 KB
checked in by ghudson, 28 years ago
(diff) |
This commit was generated by cvs2svn to compensate for changes in r9083,
which included commits to RCS files with non-trunk default branches.
|
-
Property svn:executable set to
*
|
Line | |
---|
1 | #! /bin/sh |
---|
2 | # |
---|
3 | # Top is very sensitive to differences in the kernel, so much so that an |
---|
4 | # executable created on one sub-architecture may not work on others. It |
---|
5 | # is also quite common for a minor OS revision to require recompilation of |
---|
6 | # top. Both of these problems are especially prevalent on Suns. For |
---|
7 | # example, a top executable made under SunOS 4.1.1 will not run correctly |
---|
8 | # under SunOS 4.1.2, and vice versa. "metatop" attempts to solve this |
---|
9 | # problem by choosing one of several possible top executables to run then |
---|
10 | # executing it. |
---|
11 | # |
---|
12 | # To use metatop your operating system needs to have the command "uname" |
---|
13 | # as part of the standard OS release. MAKE SURE IT DOES before proceeding. |
---|
14 | # It will try to execute the command "top-`uname -m`-`uname -r`" For |
---|
15 | # example, on a sparcstation 1 running SunOS 4.1.1, it will try to run |
---|
16 | # "top-sun4c-4.1.1". |
---|
17 | # |
---|
18 | # INSTALLATION is easy. Just compile top as normal. Then use the command |
---|
19 | # "make metainstall" (on the same machine!) instead of the usual. "make" |
---|
20 | # will insure that this shell script is installed correctly then will install |
---|
21 | # the most recently made top executable with the correct name. Remember: |
---|
22 | # you will need to "make clean" and "make metainstall" on every different |
---|
23 | # combination of sub-architecture and OS version that you have. |
---|
24 | # |
---|
25 | exec $0-`uname -m`-`uname -r` "$@" |
---|
Note: See
TracBrowser
for help on using the repository browser.