patch-2.1.107 linux/fs/super.c

• Lines: 38
• Date: Wed Jun 24 14:30:11 1998
• Orig file: v2.1.106/linux/fs/super.c
• Orig date: Thu May 14 19:47:43 1998

diff -u --recursive --new-file v2.1.106/linux/fs/super.c linux/fs/super.c
@@ -5,8 +5,8 @@
  *
  *  super.c contains code to handle: - mount structures
  *                                   - super-block tables.
- *                                   - mount systemcall
- *                                   - umount systemcall
+ *                                   - mount system call
+ *                                   - umount system call
  *
  *  Added options to /proc/mounts
  *  Torbjörn Lindh (torbjorn.lindh@gopta.se), April 14, 1996.
@@ -645,9 +645,9 @@
 
 	/*
 	 * Before checking whether the filesystem is still busy,
-	 * make sure the kernel doesn't hold any quotafiles open
+	 * make sure the kernel doesn't hold any quota files open
 	 * on the device. If the umount fails, too bad -- there
-	 * are no quotas running anymore. Just turn them on again.
+	 * are no quotas running any more. Just turn them on again.
 	 */
 	DQUOT_OFF(dev);
 
@@ -810,12 +810,12 @@
  * [21-Mar-97] T.Schoebel-Theuer: Now this can be overridden when
  * supplying a leading "!" before the dir_name, allowing "stacks" of
  * mounted filesystems. The stacking will only influence any pathname lookups
- * _after_ the mount, but open filedescriptors or working directories that
+ * _after_ the mount, but open file descriptors or working directories that
  * are now covered remain valid. For example, when you overmount /home, any
  * process with old cwd /home/joe will continue to use the old versions,
  * as long as relative paths are used, but absolute paths like /home/joe/xxx
  * will go to the new "top of stack" version. In general, crossing a
- * mountpoint will always go to the top of stack element.
+ * mount point will always go to the top of stack element.
  * Anyone using this new feature must know what he/she is doing.
  */