Browsing Asturian translation

1.

Host Properties

2.

&Name/address:

3.

<b>Name / Address field</b>
<p>
Here you can enter the host name or address.<br>
The host may be specified in a number of ways:
<p>
<i>single host</i>
<p>
This is the most common format. You may specify a host either by an abbreviated name recognized by the resolver, the fully qualified domain name, or an IP address.
</p>

<i>netgroups</i>
<p>
NIS netgroups may be given as @group. Only the host part of each netgroup members is consider in checking for membership. Empty host parts or those containing a single dash (-) are ignored.
</p>

<i>wildcards</i>
<p>
Machine names may contain the wildcard characters * and ?. This can be used to make the exports file more compact; for instance, *.cs.foo.edu matches all hosts in the domain cs.foo.edu. However, these wildcard characters do not match the dots in a domain name, so the above pattern does not include hosts such as a.b.cs.foo.edu.
</p>

<i>IP networks</i>
<p>
You can also export directories to all hosts on an IP (sub-) network simultaneously. This is done by specifying an IP address and netmask pair as address/netmask where the netmask can be specified in dotted-decimal format, or as a contiguous mask length (for example, either `/255.255.252.0' or `/22' appended to the network base address result in identical subnetworks with 10 bits of host).
</p>

4.

&Public access

5.

<b>Public access</b>
<p>
If you check this, the host address will be a single wildcard , which means public access.
This is just the same as if you would enter a wildcard in the address field.
</p>

6.

Options

7.

&Writable

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>