06.08.2013 Views

pSOSystem System Calls - Read

pSOSystem System Calls - Read

pSOSystem System Calls - Read

SHOW MORE
SHOW LESS

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

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

pHILE+ <strong>System</strong> <strong>Calls</strong> annex_f<br />

Notes<br />

See Also<br />

Hex Mnemonic Description<br />

0x201A E_FIDBIG Invalid FID; exceeds maximum.<br />

0x201B E_FIDOFF Invalid FID, file is closed.<br />

0x201C E_ININFULL Index block is full.<br />

0x201D E_VFULL Volume is full.<br />

0x2026 E_BADMS MS-DOS volume; illegal operation.<br />

0x2050 E_BADNFS NFS volume; illegal operation.<br />

0x2060 E_BADCD CD-ROM volume; illegal operation.<br />

1. annex_f() expands the physical size of a file but does not change its logical<br />

size or the end-of-file position.<br />

2. read_f() and lseek_f() calls into annexed blocks are not allowed until the<br />

logical length of the file is extended by writing data into the annexed blocks.<br />

3. A volume full error occurs if no blocks can be added to the file.<br />

4. Unless the blocks are merged into the file's last extent, a new extent descriptor<br />

is added to the file as a result of an annex_f() call.<br />

5. On volumes with separate control and data regions, the pHILE+ file system<br />

manager automatically determines the type of block to be annexed (based on<br />

the file type.) Directory files receive control blocks, and ordinary files receive<br />

data blocks.<br />

6. Annexes to BITMAP.SYS and FLIST.SYS are not allowed.<br />

write_f, open_f, read_f, lseek_f<br />

<strong>pSO<strong>System</strong></strong> <strong>System</strong> <strong>Calls</strong> 2-9<br />

2

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!