UDF 2.00 - OSTA - Optical Storage Technology Association

More documents

Recommendations

Info

The write protect flags appear in the Logical Volume Descriptor and in the File Set Descriptor. They shall be interpreted as follows: is_fileset_write_protected = LVD.HardWriteProtect || LVD.SoftWriteProtect || FSD.HardWriteProtect || FSD.SoftWriteProtect is_fileset_hard_protected = LVD.HardWriteProtect || FSD.HardWriteProtect is_fileset_soft_protected = (LVD.SoftWriteProtect || FSD.SoftWriteProtect) && (! is_vol_hard_protected) is_vol_write_protected = LVD.HardWriteProtect || LVD.SoftWriteProtect is_vol_hard_protected = LVD.HardWriteProtect is_vol_soft_protected = LVD.SoftWriteProtect && !LVD.HardWriteProtect Implementation use Entity Identifiers defined by UDF (appendix 6.1) the IdentifierSuffix field shall be constructed as follows: UDF IdentifierSuffix RBP Length Name Contents 0 2 UDF Revision Uint16 (= #0200) 2 1 OS Class Uint8 3 1 OS Identifier Uint8 4 4 Reserved bytes (= #00) The contents of the OS Class and OS Identifier fields are described in the Appendix on Operating System Identifiers. For implementation use Entity Identifiers not defined by UDF the IdentifierSuffix field shall be constructed as follows: Implementation IdentifierSuffix RBP Length Name Contents 0 1 OS Class Uint8 1 1 OS Identifier Uint8 2 6 Implementation Use Area bytes NOTE: It is important to understand the intended use and importance of the OS Class and OS Identifier fields. The main purpose of these fields is to aid in debugging when problems are found on a UDF volume. The fields also provide useful information which could be provided to the end user. When set correctly these two fields provide an implementation with information such as the following: • Identify under which operating system a particular structure was last modified. • Identify under which operating system a specific file or directory was last modified. • If a developer supports multiple operating systems with their implementation, it helps to determine under which operating system a problem may have occurred. UDF 2.00 April 3, 1998 15
2.2 Part 3 - Volume Structure 2.2.1 Descriptor Tag struct tag { /* ECMA 167 3/7.2 */ Uint16 TagIdentifier; Uint16 DescriptorVersion; Uint8 TagChecksum; byte Reserved; Uint16 TagSerialNumber; Uint16 DescriptorCRC; Uint16 DescriptorCRCLength; Uint32 TagLocation; } 2.2.1.1 Uint16 TagSerialNumber $ Ignored. Intended for disaster recovery. ? Reset to a unique value at volume initialization. The TagSerialNumber shall be set to a value that differs from ones previously recorded, upon volume re-initialization. It is suggested that: TagSerialNumber = ((TagSerialNumber of the Primary Volume Descriptor) + 1). 2.2.1.2 Uint16 DescriptorCRCLength CRCs shall be supported and calculated for each descriptor. The value of this field shall be set to (Size of the Descriptor) - (Length of Descriptor Tag). When reading a descriptor the CRC should be validated. 2.2.1.3 Uint32 TagLocation For structures referenced via a virtual address (i.e. referenced through the VAT), this value shall be the virtual address, not the physical or logical address. UDF 2.00 April 3, 1998 16
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: implementation wrote a bad structur
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?