- It is important that /export directory allow access to everyone (777 permissions) as we will be accessing the NFS share from the client with no authentication.
+ It is important that /export directory allow access to everyone (777 permissions) as we will be accessing the NFS share from the client with no authentication.
# sudo chmod 777 /export @@ -327,7 +327,7 @@ directory machine1(option11,option12) In our case we are using all the default options except for therothat we replaced withrwso that our client will have read and write access to the directory that we are exporting. - After we do all the require configurations, we are ready to start the server with the next command: + After we do all the require configurations, we are ready to start the server with the next command:
# sudo /etc/init.d/nfs-kernel-server start @@ -337,7 +337,7 @@ directory machine1(option11,option12) or run command exportfs.
-# sudo /etc/init.d/nfs-kernel-server start +# sudo /etc/init.d/nfs-kernel-server start
Or
diff --git a/Documentation/NuttShell.html b/Documentation/NuttShell.html index 4130294cc42..0f90e761099 100644 --- a/Documentation/NuttShell.html +++ b/Documentation/NuttShell.html @@ -8,7 +8,7 @@@@ -1301,7 +1301,7 @@ nsh> df Size Blocks Used Available Mounted on 64 6 6 0 /etc 512 985 2 983 /tmp -nsh> +nsh> NuttShell (NSH)
-Last Updated: February 19, 2014
+Last Updated: February 20, 2014
If
The availability of the above commands depends upon features that
- may or may not be enabled in the NuttX configuration file. The
+ may or may not be enabled in the NuttX configuration file. The
following table indicates the dependency of each command on NuttX
configuration settings. General configuration settings are discussed
in the NuttX Porting Guide.
@@ -2664,7 +2664,7 @@ nsh>
- The NSH start-up sequence is very simple.
+ The NSH start-up sequence is very simple.
As an example, the code at
- Mount the FAT filesystem at a configured mountpoint,
@@ -3502,7 +3502,7 @@ mount -t vfat /dev/ram1 /tmp
Overview.
NSH supports a variety of commands as part of the NSH program.
All of the NSH commands are listed in the NSH documentation above.
- Not all of these commands may be available at any time, however.
+ Not all of these commands may be available at any time, however.
Many commands depend upon certain NuttX configuration options.
You can enter the help command at the NSH prompt to see the commands actual available:
Overview.
In addition to these commands that are a part of NSH, external programs can also be executed as NSH commands.
- These external programs are called "Built-In" Applications for historic reasons.
+ These external programs are called "Built-In" Applications for historic reasons.
That terminology is somewhat confusing because the actual NSH commands as described above are truly "built-into" NSH whereas these applications are really external to NuttX.
@@ -3716,7 +3716,7 @@ Builtin Apps:
The NuttX build occurs in several phases as different build targets are executed:
(1) context when the configuration is established,
(2) depend when target dependencies are generated, and
- (3) default (
You replace the sample code at
Default Start-Up Behavior.
The implementation that is provided is intended to provide great flexibility for the use of Start-Up files.
- This paragraph will discuss the general behavior when all of the configuration options are set to the default values.
+ This paragraph will discuss the general behavior when all of the configuration options are set to the default values.
- In this default case, enabling
- NSH will create a read-only RAM disk (a ROM disk), containing a tiny ROMFS filesystem containing the following:
+ NSH will create a read-only RAM disk (a ROM disk), containing a tiny ROMFS filesystem containing the following:
- Where
- NSH will then mount the ROMFS filesystem at
- By default, the contents of
NSH will execute the script at
Modifying the ROMFS Image.
The contents of the
- The behavior of this script depends upon several things:
+ The behavior of this script depends upon several things:
- The configuration settings then installed configuration.
+ The configuration settings then installed configuration.
@@ -4089,7 +4089,7 @@ mount -t vfat /dev/ram1 /tmp
CONFIG_NSH_CMDOPT_DF_H is defined in the NuttX configuration, then the df will also support an option -h which may be used to show the volume information in human readable format.
@@ -1653,7 +1653,7 @@ losetup [-o dd) and losetup is
- used to make the file accessible as a block device.
+ used to make the file accessible as a block device.
A FAT file system is created (mkfatfs) and mounted (mount).
Files can then be managed on the loop-mounted file.
@@ -2488,7 +2488,7 @@ nsh>
mkdir!
+ CONFIG_DISABLE_MOUNTPOINT && CONFIG_NFILE_DESCRIPTORS > 0 && CONFIG_FS_WRITABLE4(((!
CONFIG_DISABLE_MOUNTPOINT && CONFIG_FS_WRITABLE) || !CONFIG_DISABLE_PSEUDOFS_OPERATIONS) && CONFIG_NFILE_DESCRIPTORS > 0)4CONFIG_NSH_DISABLE_MKDIR
@@ -2689,7 +2689,7 @@ nsh>
mv!
+ CONFIG_DISABLE_MOUNTPOINT && CONFIG_NFILE_DESCRIPTORS > 0 && CONFIG_FS_WRITABLE3(((!
CONFIG_DISABLE_MOUNTPOINT && CONFIG_FS_WRITABLE) || !CONFIG_DISABLE_PSEUDOFS_OPERATIONS) && CONFIG_NFILE_DESCRIPTORS > 0)4CONFIG_NSH_DISABLE_MV
@@ -2722,12 +2722,12 @@ nsh>
rm!
+ CONFIG_DISABLE_MOUNTPOINT && CONFIG_NFILE_DESCRIPTORS > 0 && CONFIG_FS_WRITABLE4(((!
CONFIG_DISABLE_MOUNTPOINT && CONFIG_FS_WRITABLE) || !CONFIG_DISABLE_PSEUDOFS_OPERATIONS) && CONFIG_NFILE_DESCRIPTORS > 0)4CONFIG_NSH_DISABLE_RM
rmdirCONFIG_NFILE_DESCRIPTORS > 0(((!
CONFIG_DISABLE_MOUNTPOINT && CONFIG_FS_WRITABLE) || !CONFIG_DISABLE_PSEUDOFS_OPERATIONS) && CONFIG_NFILE_DESCRIPTORS > 0)4CONFIG_NSH_DISABLE_RMDIR
@@ -3007,7 +3007,7 @@ set FOOBAR ABC_${FOO}_${BAR}
CONFIG_NSH_USBCONSOLE.
If defined, then the an arbitrary USB device may be used to as the NSH console.
- In this case, CONFIG_NSH_CONDEV must be defined to indicate which USB device to use as the console.
+ In this case, CONFIG_NSH_CONDEV must be defined to indicate which USB device to use as the console.
The advantage of using a device other that /dev/console is that normal debug output can not use /dev/console while NSH uses CONFIG_NSH_USBCONDEV.
CONFIG_NSH_USBCONDEV.
@@ -3365,7 +3365,7 @@ set FOOBAR ABC_${FOO}_${BAR}
4.1.1 NSH Initialization sequence
apps/examples/nsh/nsh_main.c illustrates how to start NSH.
It simple does the following:
/tmp.
+ Mount the FAT filesystem at a configured mountpoint, /tmp.
all) when the normal compilation and link operations are performed.
+ (3) default (all) when the normal compilation and link operations are performed.
Built-in application information is collected during the make context build phase.
apps/examples/nsh/nsh_main.c with whatever start-up logic that you want.
- NSH is a library at apps/nshlib.
+ NSH is a library at apps/nshlib.
apps.examplex/nsh is just a tiny, example start-up function (CONFIG_USER_ENTRYPOINT()) that that runs immediately and illustrates how to start NSH
If you want something else to run immediately then you can write your write your own custom CONFIG_USER_ENTRYPOINT() function and then start other tasks from your custom CONFIG_USER_ENTRYPOINT().
CONFIG_NSH_ROMFSETC=y, but has several other related configuration options as described with the NSH-specific configuration settings paragraph.
- This capability also depends on:
+ This capability also depends on:
@@ -3962,26 +3962,26 @@ CONFIGURED_APPS += examples/hello
CONFIG_NSH_ROMFSETC will cause NSH to behave as follows at NSH start-up time:
+ In this default case, enabling CONFIG_NSH_ROMFSETC will cause NSH to behave as follows at NSH start-up time:
`--init.d/
`-- rcS
rcS is the NSH start-up script.
+ Where rcS is the NSH start-up script.
/etc, resulting in:
+ NSH will then mount the ROMFS filesystem at /etc, resulting in:
|--dev/
@@ -3992,7 +3992,7 @@ CONFIGURED_APPS += examples/hello
rcS script are:
+ By default, the contents of rcS script are:
# Create a RAMDISK and mount it at /tmp
@@ -4004,7 +4004,7 @@ mount -t vfat /dev/ram1 /tmp
/etc/init.d/rcS at start-up (before the first NSH prompt).
- After execution of the script, the root FS will look like:
+ After execution of the script, the root FS will look like:
|--dev/
@@ -4048,7 +4048,7 @@ mount -t vfat /dev/ram1 /tmp
/etc directory are retained in the file apps/nshlib/nsh_romfsimg.h OR, if CONFIG_NSH_ARCHROMFS is defined, include/arch/board/rcs.template.
- In order to modify the start-up behavior, there are three things to study:
+ In order to modify the start-up behavior, there are three things to study:
@@ -4062,15 +4062,15 @@ mount -t vfat /dev/ram1 /tmp
tools/mkromfsimg.sh Script.
The script tools/mkromfsimg.sh creates nsh_romfsimg.h.
It is not automatically executed.
- If you want to change the configuration settings associated with creating and mounting the /tmp directory, then it will be necessary to re-generate this header file using the tools/mkromfsimg.sh script.
+ If you want to change the configuration settings associated with creating and mounting the /tmp directory, then it will be necessary to re-generate this header file using the tools/mkromfsimg.sh script.
@@ -4273,7 +4273,7 @@ mount -t vfat /dev/ram1 /tmp
rcS.template.
- The file apps/nshlib/rcS.template contains the general form of the rcS file; configured values are plugged into this template file to produce the final rcS file.
+ The file apps/nshlib/rcS.template contains the general form of the rcS file; configured values are plugged into this template file to produce the final rcS file.
nshlib)nshlib)nsh_archinitialize()nsh_consolemain()nsh_consolemain()nsh_initialize()nsh_main()nsh_main.c