Browsing Romanian translation

8.

<b>Writable</b>
<p>
Allow both read and write requests on this NFS volume.
</p>
<p>
The default is to disallow any request which changes the filesystem
</p>

9.

&Insecure

10.

<b>Insecure</b>
<p>
If this option is checked, it is not required that requests originate on an internet port less than IPPORT_RESERVED (1024).
</p>
<p>
If unsure leave it unchecked.
</p>

11.

&Sync

12.

<b>Sync</b>
<p>
This option requests that all file writes be committed to disk before the write request completes. This is required for complete safety of data in the face of a server crash, but incurs a performance hit.
</p>
<p>
The default is to allow the server to write the data out whenever it is ready.
</p>

13.

No w&delay

14.

<b>No wdelay</b>
<p>
This option only has effect if sync is also set. The NFS server will normally delay committing a write request to disk slightly if it suspects that another related write request may be in progress or may arrive soon. This allows multiple write requests to be committed to disk with the one operation which can improve performance. If an NFS server received mainly small unrelated requests, this behavior could actually reduce performance, so no wdelay is available to turn it off. </p>

15.

No &hide

16.

<b>No hide</b>
<p>
This option is based on the option of the same name provided in IRIX NFS. Normally, if a server exports two filesystems one of which is mounted on the other, then the client will have to mount both filesystems explicitly to get access to them. If it just mounts the parent, it will see an empty directory at the place where the other filesystem is mounted. That filesystem is "hidden".
</p>
<p>
Setting the nohide option on a filesystem causes it not to be hidden, and an appropriately authorized client will be able to move from the parent to that filesystem without noticing the change.
</p>
<p>
However, some NFS clients do not cope well with this situation as, for instance, it is then possible for two files in the one apparent filesystem to have the same inode number.
</p>
<p>
The nohide option is currently only effective on single host exports. It does not work reliably with netgroup, subnet, or wildcard exports.
</p>
<p>
This option can be very useful in some situations, but it should be used with due care, and only after confirming that the client system copes with the situation effectively.
</p>

17.

No su&btree check