here - OSTA - Optical Storage Technology Association

More documents

Recommendations

Info

In order to assist a UDF implementation that may have read the standard without this interpretation, implementations shall follow these rules when a FID’s deleted bit is set: If the compression ID of the File Identifier is 8, rewrite the compression ID to 254. If the compression ID of the File Identifier is 16, rewrite the compression ID to 255. Leave the remaining bytes of the File Identifier unchanged In this way a utility wishing to undelete a file or directory can recover the original name by reversing the rewrite of the compression ID. NOTE: Implementations should re-use FIDs that have the deleted bit set to one and ICBs set to zero in order to avoid growing the size of the directory unnecessarily. 2.3.4.3 struct long_ad ICB The Implementation Use bytes of the long_ad in all File Identifier Descriptors shall be used to store the UDF Unique ID for the file and directory namespace. The Implementation Use bytes of a long_ad hold an ADImpUse structure as defined by 2.3.10.1. The four impUse bytes of that structure will be interpreted as a Uint32 holding the UDF Unique ID. ADImpUse structure holding UDF Unique ID RBP Length Name Contents 0 2 Flags (see 2.3.10.1) Uint16 2 4 UDF Unique ID Uint32 Section 3.2.1 Logical Volume Header Descriptor describes how UDF Unique ID field in Implementation Use bytes of the long_ad in the File Identifier Descriptor and the UniqueID field in the File Entry and Extended File Entry are set. 2.3.4.4 Uint16 LengthofImplementationUse Shall specify the length of the ImplementationUse field. Shall specify the length of the ImplementationUse field. This field may contain zero, indicating that the ImplementationUse field has not been used. Otherwise, this field shall contain at least 32 as required by 2.3.4.5. When writing a File Identifier Descriptor to write-once media, to ensure that the Descriptor Tag field of the next FID will never span a block boundary, if there are less than 16 bytes remaining in the current block after the FID, the length of the FID shall be increased (using the Implementation Use field) enough to prevent UDF 2.01 53 March50 April
this. Remember that in the latter case, the Implementation Use field shall be at least 32 bytes. 2.3.4.5 byte ImplementationUse[] If the LengthofImplementationUse field is non ZERO then the first 32 bytes of this field shall be interpreted as specifying the implementation identifier EntityID of the implementation which last modified the File Identifier Descriptor. If the LengthofImplementationUse field is non ZERO then the first 32 bytes of this field shall be set to the implementation identifier EntityID of the current implementation. NOTE: For additional information on the proper handling of this field refer to the section on Entity Identifier. This field allows an implementation to identify which implementation last created and/or modified a specific File Identifier Descriptor . 2.3.4.6 char FileIdentifier[] Contains a File Identifier stored in the OSTA Compressed Unicode format, see 2.1.1. The byte length of this field shall be greater than 1 with the sole exception of 0 for a parent FID. If the deleted bit is set in the File Characteristics field of this File Identifier Descriptor, then see 2.3.4.2 for additional rules. If the deleted bit is not set, then the Unicode representation of the File Identifier shall be unique in this directory. This requires not only byte-wise uniqueness as required by ECMA 4/8.6, but also uniqueness of the Unicode identifier resulting from uncompress of the OSTA Compressed Unicode format. 2.3.5 ICB Tag struct icbtag { /* ECMA 167 4/14.6 */ Uint32 PriorRecordedNumberofDirectEntries; Uint16 StrategyType; byte StrategyParameter[2]; Uint16 MaximumNumberofEntries; byte Reserved; Uint8 FileType; Lb_addr ParentICBLocation; Uint16 Flags; } UDF 2.01 54 March50 April
Page 1 and 2:
Universal Disk Format ® Specificat
Page 3 and 4:
REVISION HISTORY 1.00 October 24, 1
Page 6 and 7:
CONTENTS 1. INTRODUCTION ..........
Page 8 and 9:
6.4 OSTA Compressed Unicode Algorit
Page 10 and 11:
1. Introduction The OSTA Universal
Page 12 and 13: 1.2 Compliance This document requir
Page 14 and 15: Media Block Address NOTE 1: This is
Page 16 and 17: 1.3.3 Terms May Optional Shall Shou
Page 18 and 19: non-overlapping Partitions with 2 p
Page 20 and 21: 2.1 Part 1 - General 2.1.1 Characte
Page 22 and 23: length of the field. The characters
Page 24 and 25: 2.1.5.2 char Identifier[23] Unless
Page 26 and 27: The Suffix Type column in the above
Page 28 and 29: For an Application Entity Identifie
Page 30 and 31: 2.2 Part 3 - Volume Structure 2.2.1
Page 32 and 33: NOTE: This field is used to determi
Page 34 and 35: 2.2.4 Logical Volume Descriptor str
Page 36 and 37: 2.2.5 Unallocated Space Descriptor
Page 38 and 39: EntityID. The scope of this EntityI
Page 40 and 41: 2.2.7.2.2 dstring LogicalVolumeIden
Page 42 and 43: Layout of Type 2 partition map for
Page 44 and 45: • Bits 1-7: Reserved. Shall be se
Page 46 and 47: Virtual Allocation Table structure
Page 48 and 49: the offset and length of a partitio
Page 50 and 51: The Metadata Partition Map (see2.2.
Page 52 and 53: 2.2.13.1 Metadata File (and Metadat
Page 54 and 55: 2.2.13.4 Procedure for de-allocatin
Page 56 and 57: } struct EntityID byte byte Impleme
Page 58 and 59: 2.3.2 File Set Descriptor struct Fi
Page 60 and 61: 2.3.2.7 struct EntityID DomainIdent
Page 64 and 65: 2.3.5.1 Uint16 StrategyType The co
Page 66 and 67: 2.3.6 File Entry struct FileEntry {
Page 68 and 69: 2.3.6.8 FileLinkCount Hard links to
Page 70 and 71: Descriptors should be used. For exa
Page 72 and 73: 2.3.11.2 Uint32 PreviousAllocationE
Page 74 and 75: 3.2 Part 3 - Volume Structure 3.2.1
Page 76 and 77: 3.3 Part 4 - File System 3.3.1 File
Page 78 and 79: 3.3.2.1.2 Macintosh Bits 6 & 7 (Set
Page 80 and 81: 3.3.3 File Entry struct FileEntry {
Page 82 and 83: would be considered writable if the
Page 84 and 85: 3.3.3.5 byte Extended Attributes Se
Page 86 and 87: ignored and the file creation time
Page 88 and 89: 3.3.4.5.1.1 FreeEASpace This extend
Page 90 and 91: MacVolumeInfo format RBP Length Nam
Page 92 and 93: UDFFXInfo format (Volume IV, page 1
Page 94 and 95: The ApplicationUse area for this ex
Page 96 and 97: stream directory. If present, there
Page 98 and 99: Since the streams listed above have
Page 100 and 101: Object Logical Block Number is the
Page 102 and 103: mechanism for the host software to
Page 104 and 105: Vendor ID - The Vendor ID reported
Page 106 and 107: The OS2EA Stream contains a table o
Page 108 and 109: 4.2.2 File Identifier Descriptor st
Page 110 and 111: Definitions: A FileIdentifier shall
Page 112 and 113:
3. Invalid Characters: A FileIdenti
Page 114 and 115:
4. Trailing Periods and Spaces: All
Page 116 and 117:
If there is a file extension then t
Page 118 and 119:
defined as space that is not direct
Page 120 and 121:
UDF 2.01 111 March50 April
Page 122 and 123:
6.2 UDF Entity Identifier Values En
Page 124 and 125:
8 0 BeOS - generic 9 0 Windows CE -
Page 126 and 127:
} } returnValue = unicodeIndex; } r
Page 128 and 129:
} return crc; #ifdef MAIN unsigned
Page 130 and 131:
6.6 Algorithm for Strategy Type 409
Page 132 and 133:
nameLen = udfNameLen; } else { /* A
Page 134 and 135:
} needsCRC = TRUE; /* Append the CR
Page 136 and 137:
if (index < udfLabelLen || index ==
Page 138 and 139:
UDF 2.01 129 March50 April
Page 140 and 141:
unicode_t *udfName, /* (Input) Name
Page 142 and 143:
} #ifdef (OS2 | WIN_95 | WIN_NT) /*
Page 144 and 145:
6.8 Extended Attribute Checksum Alg
Page 146 and 147:
• The data of each file shall be
Page 148 and 149:
Read the File Identifier Descriptor
Page 150 and 151:
• An intermediate state is allowe
Page 152 and 153:
• The host shall perform read/mod
Page 154 and 155:
6.10.2.6.3 Level 3 No restrictions
Page 156 and 157:
ISO 9660 converted to UDF 1 st sess
Page 158 and 159:
For File Structure: 5. Unallocated
Page 160 and 161:
6.13 Recommendations for DVD+R and
Page 162 and 163:
6.13.1.4.2 Anchor Volume Descriptor
Page 164 and 165:
6.13.2.1 Requirements • The packe
Page 166 and 167:
6.126.15 UDF Media Format Revision
Page 168 and 169:
Description DCN Updated in UDF Revi
Page 170 and 171:
Registration Form Disk Format Speci
Page 172 and 173:
L Logical Block Size, 8, 9, 2425 Lo
show all

here - OSTA - Optical Storage Technology Association

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?