Path: utzoo!mnetor!uunet!husc6!hao!ames!oliveb!sun!pepper!cmcmanis
From: cmcmanis%pepper@Sun.COM (Chuck McManis)
Newsgroups: comp.sys.amiga
Subject: Re: Suggestion for assignment of another protection bit
Message-ID: <37368@sun.uucp>
Date: 24 Dec 87 16:44:37 GMT
References: <8712240640.AA24010@cory.Berkeley.EDU>
Sender: news@sun.uucp
Reply-To: cmcmanis@sun.UUCP (Chuck McManis)
Organization: Sun Microsystems, Mountain View
Lines: 33

In article <8712240640.AA24010@cory.Berkeley.EDU> (Matt Dillon) writes:
>	How about another archive bit:
>
>		"Do not bother to archive this file because it can easily
>		 be regenerated"

My backup program does this by having a command "Mark as Archived." So that
commands that are not rewritten can be set initially to 'archived' so that
they won't be backed up, and the selection criteria allows you to exclude
directories from the backup set so you can selectively not backup /t or
whatever.

>	As far as execution goes, why not adopt the UNIX standard:
>
>#!C:EXECUTE		(as the first line in file)

But Matt even on UNIX the shell does this, not the O/S. You could use the
same technique that csh uses, check the file to see if it is a binary
file (read the first 'hunk header') and look for non ascii characters.
If binary run it as is, if it is text then check the first line for a
processor name and prepend that to the arglist and then try to run it
again (now executing the shell). A binary/text bit would be nice to 
speed this up. (This would also make TYPE default to HEX mode.)

>	So one can make 'standard' script files which use other
>interpreters rather than EXECUTE (such as SHELL).

Another option might be a 'Batch' bit in the protection word that says
this is a batch file.

--Chuck McManis
uucp: {anywhere}!sun!cmcmanis   BIX: cmcmanis  ARPAnet: cmcmanis@sun.com
These opinions are my own and no one elses, but you knew that didn't you.