|  |    Module: Protecting Files And Directories
   My views - not necessarily those of my colleagues.
   Some of these comments I've made elsewhere - I think.
   Page	    Comment
   1-10	    Directory command doesn't appear quite like this.
	    Here's the sample from an earlier reply flagging the
	    File Attributes entry:
    Directory DISK$USER:[EXAMPLES]
    ADDUSER.COM;1                 File ID:  (762,7,0)          
    Size:           28/30         Owner:    [SYSTEM]
    Created:  20-JUL-1990 09:54:26.67
    Revised:  15-FEB-1991 02:45:13.81 (3)
    Expires:   <None specified>
    Backup:    8-MAY-1991 04:02:58.76
    File organization:  Sequential
|   File attributes:    Allocation: 30, Extend: 0, Global buffer count: 0
|			No version limit
    Record format:      Variable length, maximum 83 bytes
    Record attributes:  Carriage return carriage control
    RMS attributes:     None
    Journaling enabled: None
    File protection:    System:RWED, Owner:RWED, Group:RWED, World:R
    Access Cntrl List:  None
    Total of 1 file, 28/30 blocks.
   
   Page	    Comment
   1-11	    First sentence reads oddly. Restructuring it:
	    As system manager, you will have to grant access to
	    certain system objects or files, to users who may belong
	    to different groups.
	    Not sure about it even now.
	    Bullet 5: sub-bullet 3: delete the extra "is"
   1-12	    Again, the directory listing isn't quite the way it's shown.
   1-13	    Bullet 3: line 3: typo sor -> or.
	    This particular sentence is long. How about:
	    In this way, a user can read or execute a file that they
	    know is in a directory. However, they cannot search for
	    files whose name they don't know. ?
   1-16	    Callout 2: the font has changed for DOC.DIR;1
   1-17	    Again, the directory listing isn't quite the way it's shown.
 | 
|  | Review chapter
	PROTECTING FILES AND DIRECTORIES
Page 1-6: third bullet 
	    Missing the fifth - Control the file 
            Perhaps you mentioned it under modify. But it is something you can
	    give with the access in the ACE of the ACL.
Page 1-7a: Tell here something about why you are SYSTEM if your UIC group
	   number is less or equal 10.
           Mention the system parameter MAXSYSGROUP. If here is the value of
	   decimal 4000 then you have a lott more system groups. (7640).
Page 1-9:  The example is oke, but take some different filenames. These two
	   looks almost the same.
           For instant  DIRECTORY1.LIS and   MEMO.TXT
Page 1-13: Deleting a directory file.
           One extra point of concern. Be sure your DEFAULT is not in this
           directory. Because it works, but after deleting the directory file, 
	   the system don't know where you are.
           It's like blowing a bridge. Two ways that works:
        
               1 while you are standing on the bridge. (it works)
               2 while you are somewhere else  (better way to do)
Page 1-14: Notes on examples point 3 & 7.
           Noticed them on the qualifiers as /LOG and /CONFIRM
Page 1-16: notes on example point 2
           Since VMS V5.0 you need RWD. so you can leave the E behind.
Page 1-17 If you wanna make a SAVE SET then you must give the following command
             
	  $BACKUP  input-specifier   output-specifier  /SAVE_SET
Doei Arjen.
    
 | 
|  | 
                           Module 8
                     Protecting Files and Directories
1-6 You give the range for group number, but not for member number.
     You also show that UIC's can be alphanumeric, they will want to know
     how this is set up, and maybe that should be saved for the system
     mang. modules.
1-11 You memntion ACL Based protection, but not how to set it up. If SYSNET II
     covers this topic in more detail maybe we should just leave this page out.
1-17 How does this page begin to fit into this chapter? TAKE IT OUT.
Wendy Mullenhoff
 |