UDF 2.00 - OSTA - Optical Storage Technology Association

More documents

Recommendations

Info

Logical Volume Descriptor Implementation ID “*Developer ID” Implementation Identifier Suffix Logical Volume Descriptor Domain ID "*OSTA UDF Compliant" DOMAIN Identifier Suffix File Set Descriptor Domain ID "*OSTA UDF Compliant" DOMAIN Identifier Suffix File Identifier Descriptor Implementation ID “*Developer ID” Implementation Identifier Suffix (optional) File Entry Implementation ID “*Developer ID” Implementation Identifier Suffix UDF Extended Implementation ID See Appendix UDF Identifier Suffix Attribute Non-UDF Extended Attribute Implementation ID “*Developer ID” Implementation Identifier Suffix Device Specification Extended Attribute Implementation ID “*Developer ID” Implementation Identifier Suffix Logical Volume Integrity Descriptor Implementation ID “*Developer ID” Implementation Identifier Suffix Partition Integrity Implementation ID N/A N/A Entry Virtual Partition Map Partition Type “*UDF Virtual UDF Identifier Suffix Identifier Partition” Sparable Partition Partition Type “*UDF Sparable UDF Identifier Suffix Map Identifier Partition” Virtual Allocation Entity ID “*UDF Virtual UDF Identifier Suffix Table Alloc Tbl” Sparing Table Sparing Identifier “*UDF Sparing Table” UDF Identifier Suffix NOTE: The value of the Entity Identifier field is interpreted as a sequence of bytes, and not as a dstring specified in CS0. For ease of use the values used by UDF for this field are specified in terms of ASCII character strings. The actual sequence of bytes used for the Entity Identifiers defined by UDF are specified in the appendix. In the ID Value column in the above table “*Developer ID” refers to a Entity Identifier that uniquely identifies the current implementation. The value specified should be used when a new descriptor is created. Also, the value specified should be used for an existing descriptor when anything within the scope of the specified EntityID field is modified. NOTE: The value chosen for a “*Developer ID” should contain enough information to identify the company and product name for an implementation. For example, a company called XYZ with a UDF product called DataOne might choose “*XYZ DataOne” as their developer ID. Also in the suffix of their developer ID they may choose to record the current version number of their DataOne product. This information is extremely helpful when trying to determine which UDF 2.00 April 3, 1998 13
implementation wrote a bad structure on a piece of media when multiple products from different companies have been recording on the media. The Suffix Type column in the above table defines the format of the suffix to be used with the corresponding Entity Identifier. These different suffix types are defined in the following paragraphs. NOTE: All Identifiers defined in this document (appendix 6.1) shall be registered by OSTA as UDF Identifiers. 2.1.5.3 IdentifierSuffix The format of the IdentifierSuffix field is dependent on the type of the Identifier. In regard to OSTA Domain Entity Identifiers specified in this document (appendix 6.1) the IdentifierSuffix field shall be constructed as follows: Domain IdentifierSuffix field format RBP Length Name Contents 0 2 UDF Revision Uint16 (= #0200) 2 1 Domain Flags Uint8 3 5 Reserved bytes (= #00) The UDFRevision field shall contain #0200 to indicate revision 2.00 of this document. This field will allow an implementation to detect changes made in newer revisions of this document. The OSTA Domain Identifiers are only used in the Logical Volume Descriptor and the File Set Descriptor. The DomainFlags field defines the following bit flags: Domain Flags Bit Description 0 Hard Write-Protect 1 Soft Write-Protect 2-7 Reserved The SoftWriteProtect flag is a user settable flag that indicates that the volume or file system structures within the scope of the descriptor in which it resides are write protected. A SoftWriteProtect flag value of ONE shall indicate user write protected structures. This flag may be set or reset by the user. The HardWriteProtect flag is an implementation settable flag that indicates that the scope of the descriptor in which it resides is permanently write protected. A HardWriteProtect flag value of ONE shall indicate a permanently write protected structure. Once set this flag shall not be reset. The HardWriteProtect flag overrides the SoftWriteProtect flag. UDF 2.00 April 3, 1998 14
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: 2.1.5 Entity Identifier struct Enti
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 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

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

Delete template?

Save as template?