RON:

	We have a problem in the expansion of may of the macros in symbolic 
links.  The problem is that the expansion is done by the server and not the
client.  The current macros which we support are:

	$BUS		QBUS | VME
	$CPU		68010 | 68020 | ????
	$UNIVERSE	BSD | SYSV | UNKNOWN
	$HOST		<hostname>
	$RHOST		<hostname> | ""
	$REMOTE		remote | ""

Consider a diskless node trying to execute "/bin/ls" in the system 5 universe.

	bin	->	/.bin.$UNIVERSE

	.bin.BSD	is directory with BSD executables
	.bin.SYSV	is directory with SYSV executables

Since the root is remote the entire string "/bin/ls" is sent to the server where
the symbolic link is expanded by the cousin (who has no idea the the client is
in the system 5 universe) to be "/.bin.BSD/ls".  The same problem exists
for the $BUS and $CPU macros - they are evaluated by the server with no
knowledge of the clients context.

I can envision two possible solutions to the problem:

	o	Client context information is communicated to the servers
		minfo structure, and the server interogates this to
		determine how to expand a macro.

	o	A mechanism is devised so that the server can send a pathname
		back to the client for macro expansion.  This mechanism would
		be used to expand macros in the clients context.

I cannot evaluate the implementation issues for these two approaches, however,
one advantage of the second approach is that once implemented it is extensable 
without further protocol changes.
