Path: utzoo!mnetor!uunet!husc6!cmcl2!rutgers!sri-spam!sri-unix!quintus!pds From: pds@quintus.UUCP (Peter Schachte) Newsgroups: comp.sys.amiga Subject: Re: File System suggestions Message-ID: <454@cresswell.quintus.UUCP> Date: 10 Dec 87 03:37:44 GMT References: <2086@ulowell.cs.ulowell.edu> <387@cresswell.quintus.UUCP> <1236@sugar.UUCP> Organization: Quintus Computer Systems, Mountain View, CA Lines: 20 Summary: Assign isn't the same as a symbolic link In article <1236@sugar.UUCP>, peter@sugar.UUCP (Peter da Silva) writes: > > [symbolic links so you can move files around behind a program's back] > > Isn't that what Assign is for? Not the same thing at all. You can't put an assign in a directory. Symbolic links can be very handy for creating a directory that has pointers to file that are actually located all over the disk(s). It effectively allows you to have more than one directory structure for the same files without having to have multiple copies. > I'd be more interested in a symbolic (late binding) Assign. I'd like to be > able to do things like "assign include: Aztec:include" in my startup sequence > without it asking me to insert Aztec: then & there. Amen. -- -Peter Schachte pds@quintus.uucp ...!sun!quintus!pds