WELTYC%cievms@CSV.RPI.EDU.UUCP (12/30/86)
In this discussion, mention of what information about a file is necessary for a file system to include was made. Well, I'm sure most of us know what UNIX keeps about its files, but here's what VMS keeps: ---- Directory DUA0:[WELTYC.BS] SFMSS.TXT;16 File ID: (7356,8,0) Size: 5/6 Owner: [STAFF,WELTYC] Created: 18-JUL-1986 10:43 Revised: 18-JUL-1986 10:43 (1) Expires: <None specified> Backup: 10-NOV-1986 12:09 File organization: Sequential File attributes: Allocation: 6, Extend: 0, Global buffer count: 0, No version limit Record format: Variable length, maximum 79 bytes Record attributes: Carriage return carriage control Journaling enabled: None File protection: System:RWED, Owner:RWED, Group:RE, World: Access Cntrl List: None Total of 1 file, 5/6 blocks. ----- I don't know much about the file structure of other non-UNIX systems, but I find this much information a bother, especially in trying to bring in files (on magtape, say) from other systems. I would not advocate using this much information in some "standard" filesystem structure, but in a filesystem whose goal is to be heterogeneous, this information needs to be provided for as well. The only field here I find really useful is the Access Control List (ACL). One of the many features of this is to allow you to specify specific users or groups that can access a file or device. This is an idea foreign to UNIX (and NFS, too, I think). A couple people have expressed dissatisfaction with the protection schemes (or lack of) in NFS, how does the VMS NFS handle this stuff? -Chris weltyc@csv.rpi.edu