here - OSTA - Optical Storage Technology Association

More documents

Recommendations

Info

ignored and the file creation time from the main File Entry shall be used. If the main File Entry is an Extended File Entry, this structure shall not be recorded with a file creation time. If the main File Entry is not an Extended File Entry and the File Times Extended Attribute does not exist or does not contain the file creation time then an implementation shall use the Modification Time field of the File Entry to represent the file creation time. 3.3.4.4 Device Specification Extended Attribute struct DeviceSpecificationExtendedAttribute { /* ECMA 167 4/14.10.7 */ Uint32 AttributeType; Uint8 AttributeSubtype; byte Reserved[3]; Uint32 AttributeLength; Uint32 ImplementationUseLength; /* (=IU_L) */ Uint32 MajorDeviceIdentification; Uint32 MinorDeviceIdentification; byte ImplementationUse[IU_L]; } The following paradigm shall be followed by an implementation that creates a Device Specification Extended Attribute associated with a file : If and only if a file has a DeviceSpecificationExtendedAttribute associated with it, the contents of the FileType field in the icbtag structure shall be set to 6 (indicating a block special device file), OR 7 (indicating a character special device file). If the contents of the FileType field in the icbtag structure do not equal 6 or 7, the DeviceSpecificationExtendedAttribute associated with a file shall be ignored. In the event that the contents of the FileType field in the icbtag structure equals 6 or 7, and the file does not have a DeviceSpecificationExtendedAttribute associated with it, access to the file shall be denied. For operating system environments that do not provide for the semantics associated with a block special device file, requests to open/read/write/close a file that has the DeviceSpecificationExtendedAttribute associated with it shall be denied. UDF 2.01 77 March50 April
All implementations shall record a developer IDAs the first structure in the ImplementationUse field that, an EntityID shall be recorded by all implementations. This EntityID uniquely identifies the current implementation. by a Developer ID, see 2.1.5. 3.3.4.5 Implementation Use Extended Attribute struct ImplementationUseExtendedAttribute { /* ECMA 167 4/14.10.8 */ Uint32 AttributeType; Uint8 AttributeSubtype; byte Reserved[3]; Uint32 AttributeLength; Uint32 ImplementationUseLength; /* (=IU_L) */ struct EntityID ImplementationIdentifier; byte ImplementationUse[IU_L]; } The AttributeLength field specifies the length of the entire extended attribute. For variable length extended attributes defined using the Implementation Use Extended Attribute the Attribute Length field should be large enough to leave padding space between the end of the Implementation Use field and the end of the Implementation Use Extended Attribute. The following sections describe how the Implementation Use Extended Attribute is used under various operating systems to store operating system specific extended attributes. The structures defined in the following sections contain a header checksum field. This field represents a 16-bit checksum of the Implementation Use Extended Attribute header. The fields AttributeType through ImplementationIdentifier inclusively represent the data covered by the checksum. The header checksum field is used to aid in disaster recovery of the extended attributes space. C source code for the header checksum may be found in the appendix. NOTE: All compliant implementations shall preserve existing extended attributes encountered on the media. Implementations shall create and support the extended attributes for the operating system they currently support. For example, a Macintosh implementation shall preserve any OS/2 extended attributes encountered on the media. It shall also create and support all Macintosh extended attributes specified in this document. 3.3.4.5.1 All Operating Systems UDF 2.01 78 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 62 and 63: In order to assist a UDF implementa
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 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

Create successful ePaper yourself

Delete template?

Save as template?