summaryrefslogtreecommitdiff
path: root/apps/nshlib/README.txt
diff options
context:
space:
mode:
authorpatacongo <patacongo@42af7a65-404d-4744-a932-0658087f49c3>2012-08-05 17:44:11 +0000
committerpatacongo <patacongo@42af7a65-404d-4744-a932-0658087f49c3>2012-08-05 17:44:11 +0000
commit33ea935548e0389f36f583fd826a09b7277ce85c (patch)
tree1cb241b0a84123081c115f5f382fa207ad83cb68 /apps/nshlib/README.txt
parent3609cc6eb6f7f30654cb95b0ce02487c742c9487 (diff)
downloadnuttx-33ea935548e0389f36f583fd826a09b7277ce85c.tar.gz
nuttx-33ea935548e0389f36f583fd826a09b7277ce85c.tar.bz2
nuttx-33ea935548e0389f36f583fd826a09b7277ce85c.zip
I learned how to spell PSEUDO
git-svn-id: svn://svn.code.sf.net/p/nuttx/code/trunk@5010 42af7a65-404d-4744-a932-0658087f49c3
Diffstat (limited to 'apps/nshlib/README.txt')
-rw-r--r--apps/nshlib/README.txt16
1 files changed, 8 insertions, 8 deletions
diff --git a/apps/nshlib/README.txt b/apps/nshlib/README.txt
index a6cb2d7d7..d8edd8969 100644
--- a/apps/nshlib/README.txt
+++ b/apps/nshlib/README.txt
@@ -505,14 +505,14 @@ o mkfatfs <path>
Format a fat file system on the block device specified by path.
NSH provides this command to access the mkfatfs() NuttX API.
- This block device must reside in the NuttX psuedo filesystem and
+ This block device must reside in the NuttX pseudo filesystem and
must have been created by some call to register_blockdriver() (see
include/nuttx/fs/fs.h).
o mkfifo <path>
Creates a FIFO character device anywhere in the pseudo file system,
- creating whatever psuedo directories that may be needed to complete
+ creating whatever pseudo directories that may be needed to complete
the full path. By convention, however, device drivers are place in
the standard /dev directory. After it is created, the FIFO device
may be used as any other device driver. NSH provides this command
@@ -584,7 +584,7 @@ o mount [-t <fstype> <block-device> <dir-path>]
If the mount parameters are provied on the command after the 'mount'
command, then the 'mount' command will mount a file system in the
- NuttX psuedo-file system. 'mount' performs a three way association,
+ NuttX pseudo-file system. 'mount' performs a three way association,
binding:
File system. The '-t <fstype>' option identifies the type of
@@ -592,19 +592,19 @@ o mount [-t <fstype> <block-device> <dir-path>]
of this writing, vfat is the only supported value for <fstype>
Block Device. The <block-device> argument is the full or relative
- path to a block driver inode in the psuedo filesystem. By convention,
+ path to a block driver inode in the pseudo filesystem. By convention,
this is a name under the /dev sub-directory. This <block-device>
must have been previously formatted with the same file system
type as specified by <fstype>
- Mount Point. The mount point is the location in the psuedo file
+ Mount Point. The mount point is the location in the pseudo file
system where the mounted volume will appear. This mount point
- can only reside in the NuttX psuedo filesystem. By convention, this
+ can only reside in the NuttX pseudo filesystem. By convention, this
mount point is a subdirectory under /mnt. The mount command will
- create whatever psuedo directories that may be needed to complete
+ create whatever pseudo directories that may be needed to complete
the full path but the full path must not already exist.
- After the volume has been mounted in the NuttX psuedo file
+ After the volume has been mounted in the NuttX pseudo file
system, it may be access in the same way as other objects in the
file system.