Lines Matching full:system

56 system call to prepare and graft a
58 device or the remote node (rhost:path) on to the file system tree at the point
68 The system maintains a list of currently mounted file systems.
96 root file system which is always remounted to preserve
99 Causes everything to be done except for the actual system call.
112 a file system mount status from read-write to read-only.
114 forces the R/W mount of an unclean file system (dangerous; use with
149 All I/O to the file system should be done asynchronously.
152 flag to set, since it does not guarantee that the file system structure
162 This flag indicates that the file system was mounted by
167 Mount the file system read-write.
169 then automatically try to mount the file system read-only.
174 the mounted file system.
181 a file system mount status from read-write to read-only.
183 forces the R/W mount of an unclean file system (dangerous; use with caution).
189 file for the file system.
191 This file system should be skipped when
201 to use the specified program to mount the file system, instead of calling
210 system.
211 If the file system supports multilabel operation, individual labels will
212 be maintained for each object in the file system, rather than using a
243 This file system should be skipped when
256 Do not allow execution of any binaries on the mounted file system.
267 wrapper is installed on your system.
271 on the mounted file system.
275 mount the file system read-only (even the super-user may not write it).
283 Snapshot files must be created in the file system that is being
285 You may create up to 20 snapshots per file system.
287 and remount operations and across system reboots.
308 Assuming that the file system was clean when it was mounted, you should always
316 You will get a dump that is consistent with the file system as of the timestamp
320 Mount the snapshot as a frozen image of the file system.
330 file system at
343 A directory on the mounted file system will respond to the SUID bit
361 All I/O to the file system should be done synchronously.
365 indicate that the status of an already mounted file system should be changed.
368 of the mounted file system root and the existing directory.
369 Lookups will be done in the mounted file system first.
372 All creates are done in the mounted file system.
374 The file system is untrusted and the kernel should use more
375 extensive checks on the file-system's metadata before using it.
381 Any additional options specific to a file system type that is not
412 Additional options specific to file system types
428 The file system is to be mounted read-only.
429 Mount the file system read-only (even the super-user may not write it).
438 is used to indicate the file system type.
448 The list of file system types can be prefixed with
450 to specify the file system types for which action should
468 system call in the
472 However, for the following file system types:
489 is replaced by the file system type name.
501 system should be changed.
506 also a file system can be changed from read-only to read-write
509 files on the file system are currently open for writing unless the
526 flag and show additional information about each file system (including fsid
529 The file system object is to be read and write.
548 file system table
553 .Dl XXXXX file system is not available
555 The kernel does not support the respective file system type.
557 support for a particular file system might be provided either on a static
601 is accessible from the mounted file system.
608 is preferred over the use of the file system specific
616 only when the file system is mounted via
619 It is possible for a corrupted file system to cause a crash.