Path: utzoo!censor!geac!torsqnt!lethe!yunexus!ists!helios.physics.utoronto.ca!news-server.csri.toronto.edu!bonnie.concordia.ca!nstn.ns.ca!news.cs.indiana.edu!rutgers!usc!sdd.hp.com!uakari.primate.wisc.edu!aplcen!jhunix!barrett
From: barrett@jhunix.HCF.JHU.EDU (Dan Barrett)
Newsgroups: comp.sys.amiga
Subject: Re: Backup links on 2.0
Message-ID: <7304@jhunix.HCF.JHU.EDU>
Date: 7 Jan 91 22:55:30 GMT
References: <MWM.91Jan5214524@fenris.relay.pa.dec.com> <10046@pasteur.Berkeley.EDU> <1991Jan7.213909.12776@mintaka.lcs.mit.edu>
Organization: The Johns Hopkins University - HCF
Lines: 20

In article <1991Jan7.213909.12776@mintaka.lcs.mit.edu> rjc@wookumz.ai.mit.edu (Ray Cromwell) writes:
>  TO tell links apart from other files, how about using one of the
>protection bits. So a link would look like
> Things    0     6Jan90    Link   ---lrwed

	It's concise, but inconsistent.  All the other protection bits can
be changed with the "protect" command, but what would 

		1>  protect myFile +L

mean???  Since links have nothing to do with file protections, this is
perhaps not a good place for link information.

                                                        Dan

 //////////////////////////////////////\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
| Dan Barrett, Department of Computer Science      Johns Hopkins University |
| INTERNET:   barrett@cs.jhu.edu           |                                |
| COMPUSERVE: >internet:barrett@cs.jhu.edu | UUCP:   barrett@jhunix.UUCP    |
 \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\/////////////////////////////////////