UDF 2.00 - OSTA - Optical Storage Technology Association

More documents

Recommendations

Info

3.2 Part 3 - Volume Structure 3.2.1 Logical Volume Header Descriptor struct LogicalVolumeHeaderDesc { /* ECMA 167 4/14.15 */ Uint64 UniqueID, bytes reserved[24] } 3.2.1.1 Uint64 UniqueID This field contains the next UniqueID value which should be used. The field is initialized to 16, and it monotonically increases with each assignment described below. Whenever the lower 32-bits of this value reach #FFFFFFFF, the upper 32-bits are incremented by 1, as would be expected for a 64-bit value, but the lower 32-bits “wrap” to 16 (the initialization value). This behavior supports Mac OS which uses an ID number space of 16 through 2^32 - 1 inclusive, and will not cause problems for other platforms. UniqueID is used whenever a new file or directory is created, or another name is linked to an existing file or directory. The File Identifier Descriptors and File Entries/Extended File Entries used for a stream directory and named streams associated with a file or directory do not use UniqueID; rather, the unique ID fields in these structures take their value from the UniqueID of the File Entry/Extended File Entry of the file/directory the streams are associated with. When a file or directory is created, this UniqueID is assigned to the UniqueID field of the File Entry/Extended File Entry, the lower 32-bits of UniqueID are assigned to UDFUniqueID in the Implementation Use bytes of the long_ad in the File Identifier Descriptor (see 2.3.4.2), and UniqueID is incremented by the policy described above. When a name is linked to an existing file or directory, the lower 32-bits of NextUniqueID are assigned to UDFUniqueID in the Implementation Use bytes of the long_ad in the File Identifier Descriptor (see 2.3.4.2), and UniqueID is incremented by the policy described above. The lower 32-bits shall be the same in the File Entry/Extended File Entry and its first File Identifier Descriptor, but they shall differ in subsequent FIDs. All UDF implementations shall maintain the UDFUniqueID in the FID and UniqueID in the FE/EFE as described in this section. The LVHD in a closed Logical Volume Integrity Descriptor shall have a valid UniqueID. UDF 2.00 April 3, 1998 49
3.3 Part 4 - File System 3.3.1 File Identifier Descriptor struct FileIdentifierDescriptor { /* ECMA 167 4/14.4 */ struct tag DescriptorTag; Uint16 FileVersionNumber; Uint8 FileCharacteristics; Uint8 LengthofFileIdentifier; struct long_ad ICB; Uint16 LengthofImplementationUse; byte ImplementationUse[]; char FileIdentifier[]; byte Padding[]; } NOTE: All UDF directories shall include a File Identifier Descriptor that indicates the location of the parent directory. The File Identifier Descriptor describing the parent directory shall be the first File Identifier Descriptor recorded in the directory. The parent directory of the Root directory shall be Root, as stated in ECMA 167-4, section 8.6 3.3.1.1 Uint8 FileCharacteristics The following sections describe the usage of the FileCharacteristics under various operating systems. 3.3.1.1.1 MS-DOS, OS/2, Windows 95, Windows NT, Macintosh $ If Bit 0 is set to ONE, the file shall be considered a "hidden" file. If Bit 1 is set to ONE, the file shall be considered a "directory." If Bit 2 is set to ONE, the file shall be considered "deleted." If Bit 3 is set to ONE, the ICB field within the associated FileIdentifier structure shall be considered as identifying the "parent" directory of the directory that this descriptor is recorded in ? If the file is designated as a "hidden" file, Bit 0 shall be set to ONE. If the file is designated as a "directory," Bit 1 shall be set to ONE. If the file is designated as "deleted," Bit 2 shall be set to ONE. 3.3.1.1.2 UNIX Under UNIX these bits shall be processed the same as specified in 3.3.1.1.1., except for hidden files which will be processed as normal nonhidden files. UDF 2.00 April 3, 1998 50
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: 3. System Dependent Requirements 3.
Page 59 and 60: 3.3.2.1.2 Macintosh Bits 6 & 7 (Set
Page 61 and 62: ? For operating systems that do not
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?