[comp.sys.apple] Extended files & GS/OS

delton@pro-carolina.UUCP (System Administrator) (05/17/89)

I'm working on a revision to ECP16 (a GS/OS shell program) and am adding a
column to the catalog display to show whether a file is forked or not. 
Currently the dir format is like:

*+ FILENAME TYPE BLOCKS MOD AUX LENGTH

where * = locked, + = backup needed.  

What I need is a special character like */+ to designate a forked file. 
Anyone have any preferences here?

UUCP: [ sdcsvax nosc ] !crash!pro-carolina!delton
ARPA: crash!pro-carolina!delton@nosc.mil
INET: delton@pro-carolina.cts.com

Pro-Carolina: 803-776-3936 (300-2400 baud, login as 'register')
     US Mail: 3207 Berkeley Forest Drive, Columbia, SC  29209-4111

farrier@Apple.COM (Cary Farrier) (05/17/89)

In article <8905170121.AA11161@obsolete.UUCP> delton@pro-carolina.UUCP (System Administrator) writes:
>What I need is a special character like */+ to designate a forked file. 
>Anyone have any preferences here?

	The GS/OS System Call Exerciser uses a '+', which obviously doesn't
	help you much.  How about '!'.

Cary Farrier

KMILES@CC.USU.EDU ("Kurt Miles, VAX Consultant") (05/17/89)

>
>I'm working on a revision to ECP16 (a GS/OS shell program) and am adding a
>column to the catalog display to show whether a file is forked or not.
>Currently the dir format is like:
> 
>*+ FILENAME TYPE BLOCKS MOD AUX LENGTH
> 
>where * = locked, + = backup needed.
> 
>What I need is a special character like */+ to designate a forked file.
>Anyone have any preferences here?
> 

How about a '=' for a forked file and a '-'for a non-forked file?  Another
alternative would be a 'Y' for forked file and a '|' for a non-forked file.

Just a few random thoughts from a random mind.

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
                               ___    ____               ____     ____   _
                              |   \   |   \     /\      /    \   /    \  |\   |
GreyMan ---->  and the  <---- |    \  |___/    /  \     |  ___   |    |  | \  |
/     \                       |    /  |  \    /====\    |     |  |    |  |  \ |
                              |___/   |   \  /      \   \____/|  \____/  |   \|
.............................
Kurt Miles                  :        ..... remember, sometimes the DRAGON wins!
KMILES@USU (Bitnet)         :                                      ------ 
KMILES@CC.USU.EDU (Internet):
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

dlyons@Apple.COM (David Lyons) (05/18/89)

In article <8905170121.AA11161@obsolete.UUCP> delton@pro-carolina.UUCP (System Administrator) writes:
>What I need is a special character like */+ to designate a forked file. 
>Anyone have any preferences here?
>
I suggest "R" (for Resource), or maybe "2" (for 2 forks).

 --Dave Lyons, Apple Computer, Inc.          |   DAL Systems
   AppleLink--Apple Edition: DAVE.LYONS      |   P.O. Box 875
   AppleLink--Personal Edition: Dave Lyons   |   Cupertino, CA 95015-0875
   GEnie: D.LYONS2 or DAVE.LYONS         CompuServe: 72177,3233
   Internet/BITNET:  dlyons@apple.com    UUCP:  ...!ames!apple!dlyons

   My opinions are my own, not Apple's.

JWANKERL@UTCVM.BITNET ("Josef W. Wankerl") (05/18/89)

On Wed, 17 May 89 15:37:20 GMT Cary Farrier said:
>In article <8905170121.AA11161@obsolete.UUCP> delton@pro-carolina.UUCP (System
> Administrator) writes:
>>What I need is a special character like */+ to designate a forked file.
>>Anyone have any preferences here?
>
>    The GS/OS System Call Exerciser uses a '+', which obviously doesn't
>    help you much.  How about '!'.
>
>Cary Farrier

Why not 'Y'?  It looks like a fork to me.

   -Gonzo

(Okay I know it's not a 'special' character, but will it work?)

/**********************************************************************\
|*  Joe "Gonzo" Wankerl          |*|                                  *|
|*                               |*|   The views expressed here are   *|
|* BitNet =>  JWANKERL@UTCVM     |*|   not necessarily yours...       *|
|*                               |*|   ...but they should be.         *|
\**********************************************************************/

dseah@wpi.wpi.edu (David I Seah) (05/18/89)

In article <8905170121.AA11161@obsolete.UUCP> delton@pro-carolina.UUCP (System Administrator) writes:
>What I need is a special character like */+ to designate a forked file. 
>Anyone have any preferences here?

How about a "{"?  It kinda looks forked...or a "="?  Or a "Y", but that isn't
a special char...any good mousetext characters?  If this is for ECP16, then
maybe there's a good mousetext char availiable.  (Sorry, I don't have my
han-dee-dan-dee MouseText chart right now...:)

Dave Seah (dseah@wpi.wpi.edu)

jerryk@pro-beagle.cts.com (Jerry Kindall) (05/19/89)

Network Comment: to #7885 by pnet01!crash!apple.com!dlyons

Dave Lyons quotes Don Elton:  :)
>What I need is a special character like */+ to designate a forked file. 
>Anyone have any preferences here? 
 
If you use a special character to denote a forked file, how will you denote a
LOCKED forked file (ie, if you put the special character in the "lock"
column)?
 
- Jerry
  jerryk@pro-beagle.cts.com
  crash!pnet01!pro-beagle!jerryk

delton@pro-carolina.UUCP (Don Elton) (05/19/89)

Network Comment: to #2745 by obsolete!dlyons%apple.com

Thanks to all who suggested characters to use to designate forked files. 
Guess I'll just try some of them to see how they look on the screen.  

UUCP: [ sdcsvax nosc ] !crash!pro-carolina!delton
ARPA: crash!pro-carolina!delton@nosc.mil
INET: delton@pro-carolina.cts.com

Pro-Carolina: 803-776-3936 (300-2400 baud, login as 'register')
     US Mail: 3207 Berkeley Forest Drive, Columbia, SC  29209-4111

delton@pro-carolina.UUCP (Don Elton) (05/19/89)

Network Comment: to #2762 by obsolete!JWANKERL%UTCVM.BITNET%cunyvm.cuny.edu

I'm hoping to stick with special characters to keep them from being confused
with part of the file name.  Of course with GS/OS filenames could contain
special characters too so some spacing offset will be required either way.

UUCP: [ sdcsvax nosc ] !crash!pro-carolina!delton
ARPA: crash!pro-carolina!delton@nosc.mil
INET: delton@pro-carolina.cts.com

Pro-Carolina: 803-776-3936 (300-2400 baud, login as 'register')
     US Mail: 3207 Berkeley Forest Drive, Columbia, SC  29209-4111

delton@pro-carolina.UUCP (Don Elton) (05/19/89)

Network Comment: to #2772 by obsolete!ulowell!m2c!wpi!dseah%bbn.com

Yeah, mousetext might be a good option here.  I'll look into that too.

UUCP: [ sdcsvax nosc ] !crash!pro-carolina!delton
ARPA: crash!pro-carolina!delton@nosc.mil
INET: delton@pro-carolina.cts.com

Pro-Carolina: 803-776-3936 (300-2400 baud, login as 'register')
     US Mail: 3207 Berkeley Forest Drive, Columbia, SC  29209-4111

delton@pro-carolina.UUCP (Don Elton) (05/20/89)

Network Comment: to #2837 by obsolete!pro-angmar!pro-beagle!jerryk

Re: How will I denote a locked file in ECP16 if it's a forked file.  There
will be 3 columns of special characters.  Currently there are two where *
means locked and + means backup needed.  i.e.

^+*     FILENAME

might mean that this is a locked forked file that needs a backup (assuming I
used ^ for forked files - which isn't decided yet).

UUCP: [ sdcsvax nosc ] !crash!pro-carolina!delton
ARPA: crash!pro-carolina!delton@nosc.mil
INET: delton@pro-carolina.cts.com

Pro-Carolina: 803-776-3936 (300-2400 baud, login as 'register')
     US Mail: 3207 Berkeley Forest Drive, Columbia, SC  29209-4111

samt@pro-europa.cts.com (Sam Theis) (05/21/89)

Network Comment: to #2527 by pnet01!crash!bloom-beacon.mit.edu!obsolete!pro-carolina!delton

Don, how about using 'Y' to represent a forked file.  Seems to be a graphical
representation of the concept.
 
Sam

mdavis@pro-sol.cts.com (Morgan Davis) (05/23/89)

Network Comment: to #7448 by pnet01!crash!bloom-beacon.mit.edu!obsolete!pro-carolina!delton

Is there any room in your catalog listing to give characters for all of the
access bits?  Example:

        drwnbf

For: directory, read, write, reName, backup bit, forked file, etc.

brianw@microsoft.UUCP (Brian Willoughby) (05/25/89)

In article <8905201127.AA24211@obsolete.UUCP> delton@pro-carolina.UUCP (Don Elton) writes:
>Network Comment: to #2837 by obsolete!pro-angmar!pro-beagle!jerryk
>Re: How will I denote a locked file in ECP16 if it's a forked file.  There
>will be 3 columns of special characters.  Currently there are two where *
>means locked and + means backup needed.  i.e.
>
>^+*     FILENAME

Perhaps you don't need to add a character, but just combine forked files
with an existing column to have more meaning. For example, ' ' and '*'
refer to an unlocked and locked non-forked file, respectively. You could
choose TWO other characters to represent unlocked and locked FORKED
files. This is just a suggestion for an alternative solution, it may
prove to be too confusing, depending upon what characters are used. Of
course, the column for backup could also be mutated similarly.

+ 	UNLOCKED
+*	LOCKED
+f	UNLOCK.FORKED
+F	LOCKED.FORKED

Brian Willoughby                        ...!uw-beaver!microsoft!brianw
                or                      microsoft!brianw@uunet.UU.NET
                or just                 brianw@microsoft.UUCP

delton@pro-carolina.UUCP (Don Elton) (05/25/89)

Network Comment: to #2973 by obsolete!pro-angmar!pro-sol!mdavis

Yeah there's room for all the access bits in ECP16's dir display.  It looks
like the CAT (dir) command will have flags, unix style, to determine what sort
of listing is created.  There's also going to be an alias command as you
requested months ago fyi.

UUCP: [ sdcsvax nosc ] !crash!pro-carolina!delton
ARPA: crash!pro-carolina!delton@nosc.mil
INET: delton@pro-carolina.cts.com

Pro-Carolina: 803-776-3936 (300-2400 baud, login as 'register')
     US Mail: 3207 Berkeley Forest Drive, Columbia, SC  29209-4111