Differences between current version and previous revision of mount(2).
Other diffs: Previous Major Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 3 | Last edited on Saturday, March 15, 2003 12:56:17 am | by PerryLorier | |
| Older page: | version 2 | Last edited on Saturday, March 15, 2003 12:55:36 am | by PerryLorier | Revert |
@@ -36,11 +36,9 @@
;[EPERM]: The user is not the super-user.
;[ENODEV]: ''Filesystemtype'' not configured in the kernel.
;[ENOTBLK]: ''Specialfile'' is not a block device (if a device was required).
-;[EBUSY]: ''Specialfile'' is already mounted. Or, it cannot be remounted read-only, because it still holds files open for
-
-
+;[EBUSY]: ''Specialfile'' is already mounted. Or, it cannot be remounted read-only, because it still holds files open for writing. Or, it cannot be mounted on ''dir'' because ''dir'' is still busy (it is the working directory of some task, the mount point of another device, has open files, etc.).
;[EINVAL]: ''Specialfile'' had an invalid superblock. Or, a remount was attempted, while ''specialfile'' was not already mounted on ''dir''. Or, an umount was attempted, while ''dir'' was not a mount point.
;[EFAULT]: One of the pointer arguments points outside the user address space.
;[ENOMEM]: The kernel could not allocate a free page to copy filenames or data into.
;[ENAMETOOLONG]: A pathname was longer than MAXPATHLEN.
