Lines Matching full:disk
197 system, provides accesses to the entire disk as though it were a general
264 there were various structures which I assumed they are disk images - Appear
265 exactly like that on the disk.
757 <Literal remap="tt">Disk activity - disk.c</Literal>
759 <Literal remap="tt">disk.c</Literal> is handles the lower level interaction with the
760 device. All disk activity is passed through this file - The various
761 functions through the source code request disk actions from the
772 In a similar way to <Literal remap="tt">disk.c</Literal>, the user-interface functions and
813 disk.c
1788 <Title>The disk interface</Title>
1791 All the disk activity with regard to the filesystem passes through the file
1792 <Literal remap="tt">disk.c</Literal>. This is done that way to provide additional levels of safety
1793 concerning the disk access. This way, global decisions considering the disk
1865 command should be issued to make the changes active in the disk.
1913 access to the disk in the lowest level - In <Literal remap="tt">low_write</Literal> itself.
1924 written to the disk, the logging option will still log exactly the
1972 <Literal remap="tt">disk.c</Literal>.
2189 Data change is done in memory only. An update to the disk if followed by an
2190 explicit <Literal remap="tt">writedata</Literal> command to the disk. The <Literal remap="tt">write_data</Literal>
3293 appropriate and modify <Literal remap="tt">disk.c</Literal> to use the llseek system call.
