Sie suchten nach: host (Tadschik - Englisch)

... host
x login on remote host

% 1:% 2... host
%1: %2

lmhosts host wins bcast
lmhosts host wins bcast

Временный% 1 is a host name
dummy

Рӯйхати нави ба ҳар сӯ фиристонӣarguments are host name, datetime
select distribution list

Номи шабака@ title: column... of named host
hostname

Ягон чопгар дар ин адрес/ узел ёфт нашуд! unknown host - 1 is the ip
no printer found at this address/ port.

no hide 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". 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. 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. the nohide option is currently only effective on single host exports. it does not work reliably with netgroup, subnet, or wildcard exports. 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.
no hide 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". 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. 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. the nohide option is currently only effective on single host exports. it does not work reliably with netgroup, subnet, or wildcard exports. 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.