[comp.sys.apollo] tilda

dipaola@soleil.UUCP (Len DiPaola) (08/17/90)

I have two Apollo rings, one ring runs 9.7 aegis only.
The other ring is mixed 9.7 and 10.1 domain/ix .
The first ring will not use tilda correctly.

Tilda will work for the user logged in but,
if your logged in and try "wd ~username" (other then yours),
you get 'name not found (os/ naming server)'.
Yet on the other ring this works.

I have checked both edaccts databases and they show
home directory set to /user/username.

Why is tilda only half working on the first ring?
-- 
Len DiPaola   Apollo Sysadmin      __    __    __      _      _    __  _
Harris Semiconductor 201-685-6289  ||----||   //\\   || \\  || \\  || //\
724 RT.202 Somerville, N.J.08876   _/\/\/\_  //__\\  ||==/  ||==/  || \\
rutgers!nj.semi.harris.com!dipaola ||----|| //    \\ ||  \\ ||  \\ || _//

thompson@PAN.SSEC.HONEYWELL.COM (John Thompson) (08/17/90)

> I have two Apollo rings, one ring runs 9.7 aegis only.
> The other ring is mixed 9.7 and 10.1 domain/ix .
> The first ring will not use tilda correctly.
> 
> Tilda will work for the user logged in but,
> if your logged in and try "wd ~username" (other then yours),
> you get 'name not found (os/ naming server)'.
> Yet on the other ring this works.
> 
> I have checked both edaccts databases and they show
> home directory set to /user/username.
> 
> Why is tilda only half working on the first ring?
First, just a caution that I'm sure EVERYONE already knows.  The
tilde character was processed specially (just like .   ..  and \)
as the first character in a pathname.  You did not need to
separate it from the next component with a slash (/).  At sr10,
this is necessary (JLRU).  So at 9.7 you can say wd ~directory,
but at sr10 you must say ~/directory.

Now, as to what's happening with the tilde.  The ~ maps in Aegis
to the NAMING directory, which is this wonderful thing that's
part of your processes environment, but won't be displayed by an lvar.
If you do an 'nd' on each ring, I suspect that you'll find one of
them returning '/user' and the other returning (e.g.) '/user/jones'.
If this is true, it explains your problem.  It's unlikely that
JONES has a subdirectory smith, which is where ~/smith would try
and go with an nd of /user/jones.

How to fix it?  At some point in the login sequence 
(/sys/dm/startup_login.<NODETYPE> is a good location) put in a
command like this:
      #
      # Assign the naming dir
      es 'nd /user'; en
      #
That asks the DM to put the string 'nd /user' into the input pad,
followed by a <CR-LF> combination.  You can, of course, have it
anywhere in the startup scripts, and you could just tell your users
to do it themselves, but I wouldn't be surprised if you find something
like that already in your "working" ring.

                                         
Good Luck
-- jt --

John Thompson (jt)
Honeywell, SSEC
Plymouth, MN  55441
thompson@pan.ssec.honeywell.com

As ever, my opinions do not necessarily agree with Honeywell's or reality's.
(Honeywell's do not necessarily agree with mine or reality's, either)