Lines Matching refs:it
2 @c %MENU% Controlling the system and getting information about it
7 for getting information about it. Anyone can generally use the
31 Every Unix system (also known as a host) has a host name, whether it's
33 computer networks were an issue, it's just a word like @samp{chicken}.
36 But any system attached to the Internet or any network like it conforms
73 Confusing things even more is the fact that in the DNS, it is possible for
75 exactly one of them that is the true host name, and it is called the
95 This function returns the host name of the system on which it is called,
113 But you can't count on this to exist, so it is cleaner to handle
118 truncated host name is good enough. If it is, you can ignore the
128 calls it to @var{name}, a string with length @var{length}. Only
132 Often, the program that calls it sets it to the value it finds in the
144 This process cannot set the host name because it is not privileged.
156 on which it is called. Note that this is not the more popular DNS
171 on which it is called. Note that this is not the more popular DNS
182 @c HOSTIDFILE, reads an int32_t and closes; if that fails, it calls
187 systems it is a meaningless but unique number which is hard-coded for
203 it happens just once, at system boot time.
217 This process cannot set the host name because it is not privileged.
273 hardware, it consists of the first two parts of the configuration name:
274 @samp{@var{cpu}-@var{manufacturer}}. For example, it might be one of these:
295 is a relatively recent invention and use of it is not as portable as
307 @c then fills in the other fields with constants; on HURD, it calls
314 @code{EFAULT}, which we normally don't mention as it is always a
341 filesystem driver on the fly whenever you ask for it. And when you
342 write to it, the data you write causes changes in the system. No data
355 For some programs it is desirable and necessary to access information
356 about whether a certain filesystem is mounted and, if it is, where, or
366 syntax and it is crucial that this syntax is followed all the time.
367 Therefore it is best to never directly write to the files. The functions
375 mount, if the system's administration policy allows it. But programs
416 partition, but it could also be a more or less generic string. For
417 @dfn{NFS} it would be a hostname and directory name combination.
419 Even though the element is not declared @code{const} it shouldn't be
431 kernel understands it can be any string.
440 If the value of this element must be processed it should ideally be done
458 This is not a real filesystem, it is a swap device.
540 Since there is normally exactly one entry for each special device it
562 Since there is normally exactly one entry for each mount point it
599 But since the kernel can support arbitrary filesystems it does not
610 since it names the default NFS implementation, in case both version 2
620 @code{struct fstab} it is best to use the function @code{getsubopt}
625 might be many more options which are possible so it doesn't make much sense
630 Expands to @code{"defaults"}. This option should be used alone since it
634 Expands to @code{"ro"}. See the @code{FSTAB_RO} value, it means the
637 Expands to @code{"rw"}. See the @code{FSTAB_RW} value, it means the
648 will ignore this entry if it is started with the @code{-a} option to
652 As for the @code{FSTAB_*} entries introduced above it is important to
701 The return value is @math{1} unless an error occurred in which case it
720 separate the fields. This makes it harder to use names containing one
757 same way as it happens for @code{getmentent}.
854 files in it) is no longer visible; in its place (and still with the name
859 filesystem and mounts it over @var{dir} and ignores @var{special_file}.
864 operations on the filesystem while it is mounted. It does not mean
895 This multibit field contains a magic number. If it does not have the value
900 This bit on means to remount the filesystem. Off means to mount it.
908 while it is mounted. This cannot be overridden by @code{ioctl}. This
913 filesystem shall be ignored while it is mounted.
924 This bit on specifies that all writes to the filesystem while it is
941 @c S_WRITE), but I can't see what it does. Turns on quotas, I guess.
968 it is @code{-1} and @code{errno} is set appropriately. The values of
986 The mount point is busy. (E.g. it is some process' working directory or
987 has a filesystem mounted on it already).
1010 device) and the process attempted to mount it read/write (by setting the
1017 @var{special_file} is not accessible because it is in a filesystem that is
1050 busy, by making it unbusy first. If the bit is off and the filesystem is
1073 is visible, as are any files in it.
1077 If the unmounting is successful, the return value is zero. Otherwise, it
1084 The filesystem cannot be unmounted because it is busy. E.g. it contains
1105 to zeroes. It is more widely available than @code{umount2} but since it