Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!mcnc!ecsvax!kms
From: kms@ecsvax.UUCP (Ken Steele)
Newsgroups: comp.sys.amiga
Subject: Re: problem using "assign"
Summary: does lc location matter?
Keywords: find the dumb mistake
Message-ID: <7145@ecsvax.UUCP>
Date: 10 Jun 89 02:03:21 GMT
References: <7144@ecsvax.UUCP> <17283@louie.udel.EDU>
Distribution: na
Organization: UNC Educational Computing Service
Lines: 33

In article <17283@louie.udel.EDU>, new@udel.EDU (Darren New) writes:
> If you have an assign to a directory on the disk and then remove the
> disk from the drive, the assign command will only tell you the
> disk name and not the full directory path. This is because the
> assign creates a lock (containing a pointer back to the volume lock).
> All of the intermediate directory names on the path are not around
> anywhere when the disk is out. Try doing the assigns and put the
> LC1: disk back in to check the assigns on that volume.
> Since you say that the LC command does not find the locks, 
> something may indeed be wrong; but it sounds like a misinterpretation
> of output to me... -- Darren

I didn't have THE disks handy, so I grabbed a couple that were
handy and checked.  Just as you said (and I had unconsciously
assumed).  That leaves the question of why LC fails, which is
what led me to the question about assigns.

LC is located in sys:u  and hello.c is located in sys:src
(call me mr. originality). LC1 and LC2 are located in L1:c,
everything else is in L2:.

What seems to happen is this.  If L1: is already in the drive,
then LC exits after the first disk swap (to L2:) with the error that
it can't find LC2.  If L2: is in the drive, then LC exits 
with the error that it can't find LC1.  

Any suggestions?


-- 
Ken Steele   Dept. of Psychology    kms@ecsvax.[bitnet || UUCP]
             Mars Hill College      kms@ecsvax.uncecs.edu
             Mars Hill, NC 28754