Lines Matching full:system

59 system call to prepare and graft a
61 device or the remote node (rhost:path) on to the file system tree at the point
71 The system maintains a list of currently mounted file systems.
99 root file system which is always remounted to preserve
102 Causes everything to be done except for the actual system call.
115 a file system mount status from read-write to read-only.
117 forces the R/W mount of an unclean file system (dangerous; use with
152 All I/O to the file system should be done asynchronously.
155 flag to set, since it does not guarantee that the file system structure
165 This flag indicates that the file system was mounted by
170 Mount the file system read-write.
172 then automatically try to mount the file system read-only.
177 the mounted file system.
184 a file system mount status from read-write to read-only.
186 forces the R/W mount of an unclean file system (dangerous; use with caution).
192 file for the file system.
194 This file system should be skipped when
204 to use the specified program to mount the file system, instead of calling
213 system.
214 If the file system supports multilabel operation, individual labels will
215 be maintained for each object in the file system, rather than using a
246 This file system should be skipped when
259 Do not allow execution of any binaries on the mounted file system.
270 wrapper is installed on your system.
274 on the mounted file system.
288 Snapshot files must be created in the file system that is being
290 You may create up to 20 snapshots per file system.
292 and remount operations and across system reboots.
313 Assuming that the file system was clean when it was mounted, you should always
321 You will get a dump that is consistent with the file system as of the timestamp
325 Mount the snapshot as a frozen image of the file system.
335 file system at
348 A directory on the mounted file system will respond to the SUID bit
366 All I/O to the file system should be done synchronously.
370 indicate that the status of an already mounted file system should be changed.
373 of the mounted file system root and the existing directory.
374 Lookups will be done in the mounted file system first.
377 All creates are done in the mounted file system.
379 The file system is untrusted and the kernel should use more
380 extensive checks on the file-system's metadata before using it.
386 Any additional options specific to a file system type that is not
417 Additional options specific to file system types
433 The file system is to be mounted read-only.
434 Mount the file system read-only (even the super-user may not write it).
443 is used to indicate the file system type.
453 The list of file system types can be prefixed with
455 to specify the file system types for which action should
473 system call in the
477 However, for the following file system types:
494 is replaced by the file system type name.
506 system should be changed.
511 also a file system can be changed from read-only to read-write
514 files on the file system are currently open for writing unless the
531 flag and show additional information about each file system (including fsid
534 The file system object is to be read and write.
553 file system table
562 .Dl XXXXX file system is not available
564 The kernel does not support the respective file system type.
566 support for a particular file system might be provided either on a static
610 is accessible from the mounted file system.
617 is preferred over the use of the file system specific
625 only when the file system is mounted via
628 It is possible for a corrupted file system to cause a crash.