UDF 2.00 - OSTA - Optical Storage Technology Association

More documents

Recommendations

Info

3.3.3 File Entry struct FileEntry { /* ECMA 167 4/14.9 */ struct tag DescriptorTag; struct icbtag ICBTag; Uint32 Uid; Uint32 Gid; Uint32 Permissions; Uint16 FileLinkCount; Uint8 RecordFormat; Uint8 RecordDisplayAttributes; Uint32 RecordLength; Uint64 InformationLength; Uint64 LogicalBlocksRecorded; struct timestamp AccessTime; struct timestamp ModificationTime; struct timestamp AttributeTime; Uint32 Checkpoint; struct long_ad ExtendedAttributeICB; struct EntityID ImplementationIdentifier; Uint64 UniqueID, Uint32 LengthofExtendedAttributes; Uint32 LengthofAllocationDescriptors; byte ExtendedAttributes[]; byte AllocationDescriptors[]; } NOTE: The total length of a FileEntry shall not exceed the size of one logical block. 3.3.3.1 Uint32 Uid $ For operating systems that do not support the concept of a user identifier the implementation shall ignore this field. For operating systems that do support this field a value of 2 32 - 1 shall indicate an invalid UID, otherwise the field contains a valid user identifier. ? For operating systems that do not support the concept of a user identifier the implementation shall set this field to 2 32 - 1 to indicate an invalid UID, unless otherwise specified by the user. 3.3.3.2 Uint32 Gid $ For operating systems that do not support the concept of a group identifier the implementation shall ignore this field. For operating systems that do support this field a value of 2 32 - 1 shall indicate an invalid GID, otherwise the field contains a valid group identifier. UDF 2.00 April 3, 1998 53
? For operating systems that do not support the concept of a group identifier the implementation shall set this field to 2 32 - 1 to indicate an invalid GID, unless otherwise specified by the user. 3.3.3.3 Uint32 Permissions; /* Definitions: */ /* Bit for a File for a Directory */ /* ------- ------------------------ ---------------------------- */ /* Execute May execute file May search directory */ /* Write May change file contents May create and delete files */ /* Read May examine file contents May list files in directory */ /* ChAttr May change file attributes May change dir attributes */ /* Delete May delete file May delete directory */ #define OTHER_Execute 0x00000001 #define OTHER_Write 0x00000002 #define OTHER_Read 0x00000004 #define OTHER_ChAttr 0x00000008 #define OTHER_Delete 0x00000010 #define GROUP_Execute 0x00000020 #define GROUP_Write 0x00000040 #define GROUP_Read 0x00000080 #define GROUP_ChAttr 0x00000100 #define GROUP_Delete 0x00000200 #define OWNER_Execute 0x00000400 #define OWNER_Write 0x00000800 #define OWNER_Read 0x00001000 #define OWNER_ChAttr 0x00002000 #define OWNER_Delete 0x00004000 The concept of permissions which deals with security is not completely portable between operating systems. This document attempts to maintain consistency among implementations in processing the permission bits by addressing the following basic issues: 1. How should an implementation handle Owner, Group and Other permissions when the operating system has no concept of User and Group Ids? 2. How should an implementation process permission bits when encountered, specifically permission bits that do not directly map to an operating system supported permission bit? 3. What default values should be used for permission bits that do not directly map to an operating system supported permission bit when creating a new file? User, Group and Other In general, for operating systems that do not support User and Group Ids the following algorithm should be used when processing permission bits: When reading a specific permission, the logical OR of all three (owner, group, other) permissions should be the value checked. For example a file would be considered writable if the logical OR of OWNER_Write, GROUP_Write and OTHER_Write was equal to one. UDF 2.00 April 3, 1998 54
Page 1 and 2:
OSTA Universal Disk Format Specific
Page 3 and 4:
Revision History: 1.00 October 24,
Page 5 and 6:
3. SYSTEM DEPENDENT REQUIREMENTS...
Page 7 and 8:
This page left intentionally blank
Page 9 and 10: 1.1 Document Layout This document p
Page 11 and 12: ISO/IEC 10149:1993 Orange Book part
Page 13 and 14: Variable Packet Virtual Address vir
Page 15 and 16: Logical Volume Descriptor WORM. The
Page 17 and 18: The value of the OSTA Compressed Un
Page 19 and 20: 2.1.5 Entity Identifier struct Enti
Page 21 and 22: implementation wrote a bad structur
Page 23 and 24: 2.2 Part 3 - Volume Structure 2.2.1
Page 25 and 26: NOTE: This field is used to determi
Page 27 and 28: 2.2.4 Logical Volume Descriptor str
Page 29 and 30: 2.2.5 Unallocated Space Descriptor
Page 31 and 32: implementations shall maintain this
Page 33 and 34: 2.2.7.2.5 bytes ImplementationUse[1
Page 35 and 36: Layout of Type 2 partition map for
Page 37 and 38: Virtual Allocation Table structure
Page 39 and 40: Available sparing areas may be anyw
Page 41 and 42: 2.3 Part 4 - File System 2.3.1 Desc
Page 43 and 44: The next FileSet could represent an
Page 45 and 46: 2.3.4 File Identifier Descriptor st
Page 47 and 48: 2.3.5 ICB Tag struct icbtag { /* EC
Page 49 and 50: 2.3.6 File Entry struct FileEntry {
Page 51 and 52: 2.3.7 Unallocated Space Entry struc
Page 53 and 54: NOTE: There is a benefit of using L
Page 55 and 56: 3. System Dependent Requirements 3.
Page 57 and 58: 3.3 Part 4 - File System 3.3.1 File
Page 59: 3.3.2.1.2 Macintosh Bits 6 & 7 (Set
Page 63 and 64: Attribute directory The directory
Page 65 and 66: 3.3.4.3 File Times Extended Attribu
Page 67 and 68: field is used to aid in disaster re
Page 69 and 70: The value recorded in the OS2Extend
Page 71 and 72: UDFDInfo format (Volume IV, page 10
Page 73 and 74: The ApplicationUse area for this ex
Page 75 and 76: SETUID and SETGID bits of the ICB T
Page 77 and 78: 3.3.7 UDF Defined System Streams Th
Page 79 and 80: Parent Partition Reference Number i
Page 81 and 82: The stream shall be formatted as fo
Page 83 and 84: Drive Unique Area - Optional area f
Page 85 and 86: 4. User Interface Requirements 4.1
Page 87 and 88: y all OSTA UDF compliant implementa
Page 89 and 90: 8. Long Filename: In the event that
Page 91 and 92: CS0 FileIdentifier, followed by '.'
Page 93 and 94: Followed by the separator '#' (#002
Page 95 and 96: 5.3 Boot Descriptor Please refer to
Page 97 and 98: 6.2 UDF Entity Identifier Values En
Page 99 and 100: NOTE: If you wish to add to this li
Page 101 and 102: } { /*Then the next byte to the low
Page 103 and 104: * Take high order byte first--corre
Page 105 and 106: 6.6 Algorithm for Strategy Type 409
Page 107 and 108: unsigned short valueCRC; unicode_t
Page 109 and 110: { } dosName[dosIndex++] = PERIOD; f
Page 111 and 112:
* * Number of unicode characters in
Page 113 and 114:
newName[newIndex++] = hexChar[(valu
Page 115 and 116:
6.8 Extended Attribute Checksum Alg
Page 117 and 118:
• The data of each file shall be
Page 119 and 120:
Read the File Identifier Descriptor
Page 121 and 122:
• An intermediate state is allowe
Page 123 and 124:
• The host shall perform read/mod
Page 125 and 126:
6.10.2.6.3 Level 3 No restrictions
Page 127 and 128:
ISO 9660 converted to UDF 1 st sess
Page 129 and 130:
6.12 Developer Registration Form An
Page 131 and 132:
A Access Control Lists, 77 ACL, 77
Page 133 and 134:
OSTA Universal Disk Format Specific
Page 135 and 136:
} /*Move the first byte to the high
Page 137 and 138:
***********************************
Page 139 and 140:
} else { if (current == SPACE) /* I
Page 141 and 142:
* RETURN VALUE * * Non-zero if file
Page 143 and 144:
***********************************
Page 145 and 146:
maxFilenameLen = ((MAXLEN - 5) - lo
Page 147:
UDF Specification v2.00 - A specifi
show all

UDF 2.00 - OSTA - Optical Storage Technology Association

Create successful ePaper yourself

Delete template?

Save as template?