This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/incubator-nuttx-website.git
The following commit(s) were added to refs/heads/asf-site by this push:
new e826e7a Publishing web: 1b39f27b512cbb1fc294b70e0e70a67d0092b98d
docs: 2f32c8dcf2211e0be4b323c53440c9349acc041e
e826e7a is described below
commit e826e7a73a04bd26c5cd1369f0a2cc3ff6aa4d05
Author: Abdelatif <[email protected]>
AuthorDate: Fri Apr 22 00:14:22 2022 +0000
Publishing web: 1b39f27b512cbb1fc294b70e0e70a67d0092b98d docs:
2f32c8dcf2211e0be4b323c53440c9349acc041e
---
content/docs/10.0.0/index.html | 2 +-
content/docs/10.0.1/index.html | 2 +-
content/docs/10.1.0/index.html | 2 +-
content/docs/10.2.0/index.html | 2 +-
.../_sources/applications/nsh/config.rst.txt | 12 +++--
.../_sources/applications/nsh/customizing.rst.txt | 31 +++++++-----
.../_sources/applications/nsh/installation.rst.txt | 51 +++++++++++++-------
.../latest/_sources/applications/nsh/login.rst.txt | 4 +-
.../latest/_sources/applications/nsh/nsh.rst.txt | 45 +++++++++++-------
content/docs/latest/applications/nsh/config.html | 20 +++++---
.../docs/latest/applications/nsh/customizing.html | 30 +++++++-----
.../docs/latest/applications/nsh/installation.html | 55 ++++++++++++++--------
content/docs/latest/applications/nsh/login.html | 4 +-
content/docs/latest/applications/nsh/nsh.html | 49 ++++++++++++-------
content/docs/latest/index.html | 2 +-
content/docs/latest/searchindex.js | 2 +-
content/feed.xml | 4 +-
17 files changed, 203 insertions(+), 114 deletions(-)
diff --git a/content/docs/10.0.0/index.html b/content/docs/10.0.0/index.html
index ef08927..89135bd 100644
--- a/content/docs/10.0.0/index.html
+++ b/content/docs/10.0.0/index.html
@@ -207,7 +207,7 @@ by following these <a class="reference internal"
href="contributing/documentatio
<div class="section" id="nuttx-documentation">
<h1>NuttX Documentation<a class="headerlink" href="#nuttx-documentation"
title="Permalink to this headline">¶</a></h1>
<p>NuttX is a real-time operating system (RTOS) with an emphasis on standards
compliance and small footprint. Scalable from 8-bit to 32-bit microcontroller
environments, the primary governing standards in NuttX are Posix and ANSI
standards. Additional standard APIs from Unix and other common RTOS’s (such as
VxWorks) are adopted for functionality not available under these standards, or
for functionality that is not appropriate for deeply-embedded environments
(such as fork()).</p>
-<p>Last Updated: 21 April 22 at 00:10</p>
+<p>Last Updated: 22 April 22 at 00:11</p>
<div class="toctree-wrapper compound">
<p class="caption"><span class="caption-text">Table of Contents</span></p>
<ul class="current">
diff --git a/content/docs/10.0.1/index.html b/content/docs/10.0.1/index.html
index 420a59a..e83acb3 100644
--- a/content/docs/10.0.1/index.html
+++ b/content/docs/10.0.1/index.html
@@ -215,7 +215,7 @@ by following these <a class="reference internal"
href="contributing/documentatio
<div class="section" id="nuttx-documentation">
<h1>NuttX Documentation<a class="headerlink" href="#nuttx-documentation"
title="Permalink to this headline">¶</a></h1>
<p>NuttX is a real-time operating system (RTOS) with an emphasis on standards
compliance and small footprint. Scalable from 8-bit to 32-bit microcontroller
environments, the primary governing standards in NuttX are Posix and ANSI
standards. Additional standard APIs from Unix and other common RTOS’s (such as
VxWorks) are adopted for functionality not available under these standards, or
for functionality that is not appropriate for deeply-embedded environments
(such as fork()).</p>
-<p>Last Updated: 21 April 22 at 00:11</p>
+<p>Last Updated: 22 April 22 at 00:11</p>
<div class="toctree-wrapper compound">
<p class="caption"><span class="caption-text">Table of Contents</span></p>
<ul class="current">
diff --git a/content/docs/10.1.0/index.html b/content/docs/10.1.0/index.html
index 4127048..eeb4140 100644
--- a/content/docs/10.1.0/index.html
+++ b/content/docs/10.1.0/index.html
@@ -215,7 +215,7 @@ by following these <a class="reference internal"
href="contributing/documentatio
<div class="section" id="nuttx-documentation">
<h1>NuttX Documentation<a class="headerlink" href="#nuttx-documentation"
title="Permalink to this headline">¶</a></h1>
<p>NuttX is a real-time operating system (RTOS) with an emphasis on standards
compliance and small footprint. Scalable from 8-bit to 64-bit microcontroller
environments, the primary governing standards in NuttX are POSIX and ANSI
standards. Additional standard APIs from Unix and other common RTOS’s (such as
VxWorks) are adopted for functionality not available under these standards, or
for functionality that is not appropriate for deeply-embedded environments
(such as fork()).</p>
-<p>Last Updated: 21 April 22 at 00:11</p>
+<p>Last Updated: 22 April 22 at 00:12</p>
<div class="toctree-wrapper compound">
<p class="caption"><span class="caption-text">Table of Contents</span></p>
<ul class="current">
diff --git a/content/docs/10.2.0/index.html b/content/docs/10.2.0/index.html
index 6c0a359..db1043f 100644
--- a/content/docs/10.2.0/index.html
+++ b/content/docs/10.2.0/index.html
@@ -216,7 +216,7 @@ by following these <a class="reference internal"
href="contributing/documentatio
<div class="section" id="nuttx-documentation">
<h1>NuttX Documentation<a class="headerlink" href="#nuttx-documentation"
title="Permalink to this headline">¶</a></h1>
<p>NuttX is a real-time operating system (RTOS) with an emphasis on standards
compliance and small footprint. Scalable from 8-bit to 64-bit microcontroller
environments, the primary governing standards in NuttX are POSIX and ANSI
standards. Additional standard APIs from Unix and other common RTOS’s (such as
VxWorks) are adopted for functionality not available under these standards, or
for functionality that is not appropriate for deeply-embedded environments
(such as fork()).</p>
-<p>Last Updated: 21 April 22 at 00:12</p>
+<p>Last Updated: 22 April 22 at 00:12</p>
<div class="toctree-wrapper compound">
<p class="caption"><span class="caption-text">Table of Contents</span></p>
<ul class="current">
diff --git a/content/docs/latest/_sources/applications/nsh/config.rst.txt
b/content/docs/latest/_sources/applications/nsh/config.rst.txt
index 9166f66..8195ede 100644
--- a/content/docs/latest/_sources/applications/nsh/config.rst.txt
+++ b/content/docs/latest/_sources/applications/nsh/config.rst.txt
@@ -298,9 +298,10 @@ Configuration Description
registered as ``/dev/mmcsd``\ *N* where
*N* is the minor number.
Default is zero.
- ``CONFIG_NSH_ROMFSETC`` Mount a ROMFS file system at ``/etc`` and
provide a startup
- script at ``/etc/init.d/rcS``.
- The default startup script will mount a
FAT FS RAMDISK at
+ ``CONFIG_NSH_ROMFSETC`` Mount a ROMFS file system at ``/etc`` and
provide a system init
+ script at ``/etc/init.d.rc.sysinit`` and
a startup script at
+ ``/etc/init.d/rcS``.
+ The default system init script will mount
a FAT FS RAMDISK at
``/tmp`` but the logic is `easily
extensible <#startupscript>`__.
``CONFIG_NSH_CONSOLE`` If ``CONFIG_NSH_CONSOLE`` is set to *y*,
then a serial console
@@ -462,6 +463,9 @@ Configuration Description
``CONFIG_NSH_ROMFSMOUNTPT`` The default mountpoint for the ROMFS volume is
``"/etc"``,
but that can be changed with this setting. This
must be a
absolute path beginning with '``/``' and
enclosed in quotes.
+``CONFIG_NSH_SYSINITSCRIPT`` This is the relative path to the system init
script within the
+ mountpoint. The default is
``"init.d/rc.sysinit"``. This is a relative
+ path and must not start with '``/``' but must
be enclosed in quotes.
``CONFIG_NSH_INITSCRIPT`` This is the relative path to the startup script
within the
mountpoint. The default is ``"init.d/rcS"``.
This is a relative
path and must not start with '``/``' but must
be enclosed in quotes.
@@ -473,7 +477,7 @@ Configuration Description
Any value selected must be a power of 2.
==============================
==============================================================
-When the default ``rcS`` file used when ``CONFIG_NSH_ROMFSETC`` is
+When the default ``rc.sysinit`` file used when ``CONFIG_NSH_ROMFSETC`` is
selected, it will mount a FAT FS under ``/tmp``. The following
selections describe that FAT FS.
diff --git a/content/docs/latest/_sources/applications/nsh/customizing.rst.txt
b/content/docs/latest/_sources/applications/nsh/customizing.rst.txt
index 38b28a0..384b66a 100644
--- a/content/docs/latest/_sources/applications/nsh/customizing.rst.txt
+++ b/content/docs/latest/_sources/applications/nsh/customizing.rst.txt
@@ -46,18 +46,18 @@ does the following:
~~~~~~~~~~~~~~~~~~~~
The NSH initialization function, ``nsh_initialize()``, be found in
-``apps/nshlib/nsh_init.c``. It does only three things:
+``apps/nshlib/nsh_init.c``. It does only four things:
- #. ``nsh_romfsetc()``: If so configured, it executes an NSH start-up
- script that can be found at ``/etc/init.d/rcS`` in the target file
- system. The ``nsh_romfsetc()`` function can be found in
- ``apps/nshlib/nsh_romfsetc.c``. This function will (1) register a
- ROMFS file system, then (2) mount the ROMFS file system. ``/etc`` is
- the default location where a read-only, ROMFS file system is mounted
- by ``nsh_romfsetc()``.
+ #. ``nsh_romfsetc()``: If so configured, it executes NSH system init and
+ start-up script that can be found at ``/etc/init.d/rc.sysinit`` and
+ ``/etc/init.d/rcS`` in the target file system. The ``nsh_romfsetc()``
+ function can be found in ``apps/nshlib/nsh_romfsetc.c``.
+ This function will (1) register a ROMFS file system, then (2) mount
+ the ROMFS file system. ``/etc`` is the default location where a
+ read-only, ROMFS file system is mounted by ``nsh_romfsetc()``.
The ROMFS image is, itself, just built into the firmware. By default,
- this ``rcS`` start-up script contains the following logic::
+ this ``rc.sysinit`` system init script contains the following logic::
# Create a RAMDISK and mount it at XXXRDMOUNTPOINTXXX
@@ -79,7 +79,7 @@ The NSH initialization function, ``nsh_initialize()``, be
found in
- ``XXXRDMOUNTPOINTXXX`` will become the configured mount point.
Default: ``/etc``
- By default, the substituted values would yield an ``rcS`` file like::
+ By default, the substituted values would yield an ``rc.sysinit`` file
like::
# Create a RAMDISK and mount it at /tmp
@@ -96,8 +96,8 @@ The NSH initialization function, ``nsh_initialize()``, be
found in
- Mount the FAT file system at a configured mountpoint, ``/tmp``.
- This ``rcS`` template file can be found at
- ``apps/nshlib/rcS.template``. The resulting ROMFS file system can be
+ This ``rc.sysinit.template`` template file can be found at
+ ``apps/nshlib/rc.sysinit.template``. The resulting ROMFS file system can
be
found in ``apps/nshlib/nsh_romfsimg.h``.
#. ``board_app_initialize()``: Next any architecture-specific NSH
@@ -110,6 +110,13 @@ The NSH initialization function, ``nsh_initialize()``, be
found in
#. ``nsh_netinit()``: The ``nsh_netinit()`` function can be found in
``apps/nshlib/nsh_netinit.c``.
+ #. The start-up script ``rcS`` is executed after the system-init script
+ to startup some application and other system service.
+
+ This ``rcS`` template file can be found at
+ ``apps/nshlib/rcS.template``. The resulting ROMFS file system can be
+ found in ``apps/nshlib/nsh_romfsimg.h``.
+
NSH Commands
************
diff --git a/content/docs/latest/_sources/applications/nsh/installation.rst.txt
b/content/docs/latest/_sources/applications/nsh/installation.rst.txt
index a6bd2e1..29e03a2 100644
--- a/content/docs/latest/_sources/applications/nsh/installation.rst.txt
+++ b/content/docs/latest/_sources/applications/nsh/installation.rst.txt
@@ -61,8 +61,10 @@ behave as follows at NSH start-up time:
`--init.d/
`-- rcS
+ `-- rc.sysinit
Where ``rcS`` is the NSH start-up script.
+ Where ``rc.sysinit`` is the NSH system-init script.
- NSH will then mount the ROMFS file system at ``/etc``, resulting in::
@@ -71,8 +73,9 @@ behave as follows at NSH start-up time:
`--etc/
`--init.d/
`-- rcS
+ `-- rc.sysinit
- - By default, the contents of ``rcS`` script are::
+ - By default, the contents of ``rc.sysinit`` script are::
# Create a RAMDISK and mount it at /tmp
@@ -80,9 +83,9 @@ behave as follows at NSH start-up time:
mkfatfs /dev/ram1
mount -t vfat /dev/ram1 /tmp
- - NSH will execute the script at ``/etc/init.d/rcS`` at start-up
- (before the first NSH prompt). After execution of the script, the
- root FS will look like::
+ - NSH will execute the script at ``/etc/init.d/rc.sysinit`` at system
+ init (before the first NSH prompt). After execution of the script,
+ the root FS will look like::
|--dev/
| |-- ram0
@@ -90,6 +93,7 @@ behave as follows at NSH start-up time:
|--etc/
| `--init.d/
| `-- rcS
+ | `-- rc.sysinit
`--tmp/
**Example Configurations**. Here are some configurations that have
@@ -105,15 +109,16 @@ provide useful examples:
- ``boards/sim/sim/sim/touchscreen``
In most of these cases, the configuration sets up the *default*
-``/etc/init.d/rcS`` script. The default script is here:
-``apps/nshlib/rcS.template``. (The funny values in the template like
-``XXXMKRDMINORXXX`` get replaced via ``sed`` at build time). This
+``/etc/init.d/rc.sysinit`` and ``/etc/init.d/rcS`` script. The default
+script is here: ``apps/nshlib/rc.sysinit.template`` and
+``apps/nshlib/rcS.template``. (The funny values in the rc.sysinit.template
+like ``XXXMKRDMINORXXX`` get replaced via ``sed`` at build time). This
default configuration creates a ramdisk and mounts it at ``/tmp`` as
discussed above.
If that default behavior is not what you want, then you can provide your
-own custom ``rcS`` script by defining ``CONFIG_NSH_ARCHROMFS=y`` in the
-configuration file.
+own custom ``rc.sysinit`` and ``rcS`` script by defining
+``CONFIG_NSH_ARCHROMFS=y`` in the configuration file.
**Modifying the ROMFS Image**. The contents of the ``/etc`` directory
are retained in the file ``apps/nshlib/nsh_romfsimg.h`` OR, if
@@ -146,21 +151,34 @@ behavior, there are three things to study:
is a normal part of a complete Linux or Cygwin installation,
usually as part of the ``vi`` package).
- #. The file ``apps/nshlib/rcS.template`` (OR, if
+ #. The file ``apps/nshlib/rc.sysinit.template`` (OR, if
+ ``CONFIG_NSH_ARCHROMFS`` is defined
+ ``include/arch/board/rc.sysinit.template``.
+
+ The file ``apps/nshlib/rcS.template`` (OR, if
``CONFIG_NSH_ARCHROMFS`` is defined
``include/arch/board/rcs.template``.
- #. ``rcS.template``. The file ``apps/nshlib/rcS.template`` contains the
+ #. ``rc.sysinit.template``. The file ``apps/nshlib/rc.sysinit.template``
+ contains the general form of the ``rc.sysinit`` file; configured values
+ are plugged into this template file to produce the final ``rc.sysinit``
file.
+
+ ``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.
- To generate a custom ``rcS`` file a copy of ``rcS.template`` needs to
+ To generate a custom ``rc.sysinit`` and ``rcS`` file a copy of
+ ``rc.sysinit.template`` and ``rcS.template`` needs to
be placed at ``tools/`` and changed according to the desired start-up
behaviour. Running ``tools/mkromfsimg.h`` creates ``nsh_romfsimg.h``
which needs to be copied to ``apps/nshlib`` OR if
``CONFIG_NSH_ARCHROMFS`` is defined to
``boards/<arch>/<chip>/<board>/include``.
+``rc.sysinit.template``. The default ``rc.sysinit.template``,
+``apps/nshlib/rc.sysinit.template``, generates the standard, default
+``apps/nshlib/nsh_romfsimg.h`` file.
+
``rcS.template``. The default ``rcS.template``,
``apps/nshlib/rcS.template``, generates the standard, default
``apps/nshlib/nsh_romfsimg.h`` file.
@@ -171,10 +189,11 @@ then a custom, board-specific ``nsh_romfsimg.h`` file
residing in
is configured, ``include/arch/board`` will be linked to
``boards/<arch>/<chip>/<board>/include``.
-All of the startup-behavior is contained in ``rcS.template``. The role
-of ``mkromfsimg.sh`` script is to (1) apply the specific configuration
-settings to ``rcS.template`` to create the final ``rcS``, and (2) to
-generate the header file ``nsh_romfsimg.h`` containing the ROMFS file
+All of the startup-behavior is contained in ``rc.sysinit.template`` and
+``rcS.template``. The role of ``mkromfsimg.sh`` script is to (1) apply
+the specific configuration settings to ``rc.sysinit.template`` to create
+the final ``rc.sysinit``, and ``rcS.template`` to create the final ``rcS``,
+and (2) to generate the header file ``nsh_romfsimg.h`` containing the ROMFS
file
system image. To do this, ``mkromfsimg.sh`` uses two tools that must be
installed in your system:
diff --git a/content/docs/latest/_sources/applications/nsh/login.rst.txt
b/content/docs/latest/_sources/applications/nsh/login.rst.txt
index 01d5386..b8d1ea5 100644
--- a/content/docs/latest/_sources/applications/nsh/login.rst.txt
+++ b/content/docs/latest/_sources/applications/nsh/login.rst.txt
@@ -164,9 +164,11 @@ and containing the password file, ``passwd`` like::
/etc/init.d:
dr-xr-xr-x 0 ..
-r--r--r-- 110 rcS
+ -r--r--r-- 110 rc.sysinit
nsh>
-Where ``/etc/init.d/rcS`` is the start-up script; ``/etc/passwd`` is a
+Where ``/etc/init.d/rc.sysinit`` is the system init script and
+``/etc/init.d/rcS`` is the start-up script; ``/etc/passwd`` is a
the password file. Note that here we assume that you are already using a
start-up script. We can then piggyback the passwd file into the ``/etc``
file system already mounted for the NSH start up file as described above
diff --git a/content/docs/latest/_sources/applications/nsh/nsh.rst.txt
b/content/docs/latest/_sources/applications/nsh/nsh.rst.txt
index 4cdde17..ee2d71e 100644
--- a/content/docs/latest/_sources/applications/nsh/nsh.rst.txt
+++ b/content/docs/latest/_sources/applications/nsh/nsh.rst.txt
@@ -276,8 +276,10 @@ NSH to behave as follows at NSH startup time:
`--init.d/
`-- rcS
+ `-- rc.sysinit
Where rcS is the NSH start-up script.
+ Where rc.sysinit is the NSH system init script.
- NSH will then mount the ROMFS file system at ``/etc``,
resulting in::
@@ -287,8 +289,9 @@ NSH to behave as follows at NSH startup time:
`--etc/
`--init.d/
`-- rcS
+ `-- rc.sysinit
- - By default, the contents of rcS script are::
+ - By default, the contents of rc.sysinit script are::
# Create a RAMDISK and mount it at XXXRDMOUNTPOINTXXX
@@ -296,9 +299,9 @@ NSH to behave as follows at NSH startup time:
mkfatfs /dev/ram1
mount -t vfat /dev/ram1 /tmp
- - NSH will execute the script at ``/etc/init.d/rcS`` at start-up
- (before the first NSH prompt). After execution of the script,
- the root FS will look like::
+ - NSH will execute the script at ``/etc/init.d/rc.sysinit`` at
+ system init script(before the first NSH prompt). After
+ execution of the script, the root FS will look like::
|--dev/
| |-- ram0
@@ -306,6 +309,7 @@ NSH to behave as follows at NSH startup time:
|--etc/
| `--init.d/
| `-- rcS
+ | `-- rc.sysinit
`--tmp/
**Modifying the ROMFS Image**. The contents of the ``/etc``
@@ -330,28 +334,37 @@ start-up behavior, there are three things to study:
- The configuration settings then installed configuration.
- The ``genromfs`` tool (available from
http://romfs.sourceforge.net).
- - The file ``apps/nshlib/rcS.template`` (OR, if
+ - The file ``apps/nshlib/rc.sysinit.template`` (OR, if
+ ``CONFIG_NSH_ARCHROMFS`` is defined
+ ``include/arch/board/rc.sysinit.template``.
+ The file ``apps/nshlib/rcS.template`` (OR, if
``CONFIG_NSH_ARCHROMFS`` is defined
``include/arch/board/rcs.template``.
- #. ``rcS.template``: The file ``apps/nshlib/rcS.template``
+ #. ``rc.sysinit.template``: The file ``apps/nshlib/rc.sysinit.template``
+ contains the general form of the ``rc.sysinit`` file; configured
+ values are plugged into this template file to produce the final
+ ``rc.sysinit`` file.
+
+ ``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.
.. note::
- ``apps/nshlib/rcS.template`` generates the standard,
- default ``nsh_romfsimg.h`` file. If ``CONFIG_NSH_ARCHROMFS`` is
- defined in the NuttX configuration file, then a custom,
- board-specific ``nsh_romfsimg.h`` file residing in the
- ``boards/<arch>/<chip>/<board>/include`` directory will be used.
- NOTE when the OS is configured, ``include/arch/board`` will be
+ ``apps/nshlib/rcS.template`` and ``apps/nshlib/rc.sysinit.template``
+ generates the standard, default ``nsh_romfsimg.h`` file.
+ If ``CONFIG_NSH_ARCHROMFS`` is defined in the NuttX configuration
+ file, then a custom, board-specific ``nsh_romfsimg.h`` file residing
+ in the ``boards/<arch>/<chip>/<board>/include`` directory will be
+ used. NOTE when the OS is configured, ``include/arch/board`` will be
linked to ``boards/<arch>/<chip>/<board>/include``.
-All of the startup-behavior is contained in ``rcS.template``. The
-role of ``mkromfsimg.sh`` is to (1) apply the specific
-configuration settings to ``rcS.template`` to create the final
-``rcS``, and (2) to generate the header file ``nsh_romfsimg.h``
+All of the startup-behavior is contained in ``rc.sysinit.template``
+and ``rcS.template``. The role of ``mkromfsimg.sh`` is to (1) apply
+the specific configuration settings to ``rc.sysinit.template`` to create
+the final ``rc.sysinit``, and ``rc.sysinit.template`` to create the final
+``rcS`` and (2) to generate the header file ``nsh_romfsimg.h``
containing the ROMFS file system image.
**Further Information**. See the section on `Customizing the
diff --git a/content/docs/latest/applications/nsh/config.html
b/content/docs/latest/applications/nsh/config.html
index 555051a..1d6a690 100644
--- a/content/docs/latest/applications/nsh/config.html
+++ b/content/docs/latest/applications/nsh/config.html
@@ -796,9 +796,10 @@ registered as <code class="docutils literal
notranslate"><span class="pre">/dev/
Default is zero.</p></td>
</tr>
<tr class="row-even"><td><p><code class="docutils literal notranslate"><span
class="pre">CONFIG_NSH_ROMFSETC</span></code></p></td>
-<td><p>Mount a ROMFS file system at <code class="docutils literal
notranslate"><span class="pre">/etc</span></code> and provide a startup
-script at <code class="docutils literal notranslate"><span
class="pre">/etc/init.d/rcS</span></code>.
-The default startup script will mount a FAT FS RAMDISK at
+<td><p>Mount a ROMFS file system at <code class="docutils literal
notranslate"><span class="pre">/etc</span></code> and provide a system init
+script at <code class="docutils literal notranslate"><span
class="pre">/etc/init.d.rc.sysinit</span></code> and a startup script at
+<code class="docutils literal notranslate"><span
class="pre">/etc/init.d/rcS</span></code>.
+The default system init script will mount a FAT FS RAMDISK at
<code class="docutils literal notranslate"><span
class="pre">/tmp</span></code> but the logic is <a class="reference external"
href="#startupscript">easily extensible</a>.</p></td>
</tr>
<tr class="row-odd"><td><p><code class="docutils literal notranslate"><span
class="pre">CONFIG_NSH_CONSOLE</span></code></p></td>
@@ -1062,16 +1063,21 @@ that can be found at <code class="docutils literal
notranslate"><span class="pre
but that can be changed with this setting. This must be a
absolute path beginning with ‘<code class="docutils literal notranslate"><span
class="pre">/</span></code>’ and enclosed in quotes.</p></td>
</tr>
-<tr class="row-even"><td><p><code class="docutils literal notranslate"><span
class="pre">CONFIG_NSH_INITSCRIPT</span></code></p></td>
+<tr class="row-even"><td><p><code class="docutils literal notranslate"><span
class="pre">CONFIG_NSH_SYSINITSCRIPT</span></code></p></td>
+<td><p>This is the relative path to the system init script within the
+mountpoint. The default is <code class="docutils literal notranslate"><span
class="pre">"init.d/rc.sysinit"</span></code>. This is a relative
+path and must not start with ‘<code class="docutils literal notranslate"><span
class="pre">/</span></code>’ but must be enclosed in quotes.</p></td>
+</tr>
+<tr class="row-odd"><td><p><code class="docutils literal notranslate"><span
class="pre">CONFIG_NSH_INITSCRIPT</span></code></p></td>
<td><p>This is the relative path to the startup script within the
mountpoint. The default is <code class="docutils literal notranslate"><span
class="pre">"init.d/rcS"</span></code>. This is a relative
path and must not start with ‘<code class="docutils literal notranslate"><span
class="pre">/</span></code>’ but must be enclosed in quotes.</p></td>
</tr>
-<tr class="row-odd"><td><p><code class="docutils literal notranslate"><span
class="pre">CONFIG_NSH_ROMFSDEVNO</span></code></p></td>
+<tr class="row-even"><td><p><code class="docutils literal notranslate"><span
class="pre">CONFIG_NSH_ROMFSDEVNO</span></code></p></td>
<td><p>This is the minor number of the ROMFS block device.
The default is ‘<code class="docutils literal notranslate"><span
class="pre">0</span></code>’ corresponding to <code class="docutils literal
notranslate"><span class="pre">/dev/ram0</span></code>.</p></td>
</tr>
-<tr class="row-even"><td><p><code class="docutils literal notranslate"><span
class="pre">CONFIG_NSH_ROMFSSECTSIZE</span></code></p></td>
+<tr class="row-odd"><td><p><code class="docutils literal notranslate"><span
class="pre">CONFIG_NSH_ROMFSSECTSIZE</span></code></p></td>
<td><p>This is the sector size to use with the ROMFS volume. Since the
default volume is very small, this defaults to 64 but should
be increased if the ROMFS volume were to be become large.
@@ -1079,7 +1085,7 @@ Any value selected must be a power of 2.</p></td>
</tr>
</tbody>
</table>
-<p>When the default <code class="docutils literal notranslate"><span
class="pre">rcS</span></code> file used when <code class="docutils literal
notranslate"><span class="pre">CONFIG_NSH_ROMFSETC</span></code> is
+<p>When the default <code class="docutils literal notranslate"><span
class="pre">rc.sysinit</span></code> file used when <code class="docutils
literal notranslate"><span class="pre">CONFIG_NSH_ROMFSETC</span></code> is
selected, it will mount a FAT FS under <code class="docutils literal
notranslate"><span class="pre">/tmp</span></code>. The following
selections describe that FAT FS.</p>
<table class="docutils align-default">
diff --git a/content/docs/latest/applications/nsh/customizing.html
b/content/docs/latest/applications/nsh/customizing.html
index e3b372d..6f7585e 100644
--- a/content/docs/latest/applications/nsh/customizing.html
+++ b/content/docs/latest/applications/nsh/customizing.html
@@ -272,18 +272,18 @@ finished the entire NSH initialization sequence.</p></li>
<div class="section" id="nsh-initialize">
<h3><code class="docutils literal notranslate"><span
class="pre">nsh_initialize()</span></code><a class="headerlink"
href="#nsh-initialize" title="Permalink to this headline">¶</a></h3>
<p>The NSH initialization function, <code class="docutils literal
notranslate"><span class="pre">nsh_initialize()</span></code>, be found in
-<code class="docutils literal notranslate"><span
class="pre">apps/nshlib/nsh_init.c</span></code>. It does only three things:</p>
+<code class="docutils literal notranslate"><span
class="pre">apps/nshlib/nsh_init.c</span></code>. It does only four things:</p>
<blockquote>
<div><ol class="arabic">
-<li><p><code class="docutils literal notranslate"><span
class="pre">nsh_romfsetc()</span></code>: If so configured, it executes an NSH
start-up
-script that can be found at <code class="docutils literal notranslate"><span
class="pre">/etc/init.d/rcS</span></code> in the target file
-system. The <code class="docutils literal notranslate"><span
class="pre">nsh_romfsetc()</span></code> function can be found in
-<code class="docutils literal notranslate"><span
class="pre">apps/nshlib/nsh_romfsetc.c</span></code>. This function will (1)
register a
-ROMFS file system, then (2) mount the ROMFS file system. <code class="docutils
literal notranslate"><span class="pre">/etc</span></code> is
-the default location where a read-only, ROMFS file system is mounted
-by <code class="docutils literal notranslate"><span
class="pre">nsh_romfsetc()</span></code>.</p>
+<li><p><code class="docutils literal notranslate"><span
class="pre">nsh_romfsetc()</span></code>: If so configured, it executes NSH
system init and
+start-up script that can be found at <code class="docutils literal
notranslate"><span class="pre">/etc/init.d/rc.sysinit</span></code> and
+<code class="docutils literal notranslate"><span
class="pre">/etc/init.d/rcS</span></code> in the target file system. The <code
class="docutils literal notranslate"><span
class="pre">nsh_romfsetc()</span></code>
+function can be found in <code class="docutils literal notranslate"><span
class="pre">apps/nshlib/nsh_romfsetc.c</span></code>.
+This function will (1) register a ROMFS file system, then (2) mount
+the ROMFS file system. <code class="docutils literal notranslate"><span
class="pre">/etc</span></code> is the default location where a
+read-only, ROMFS file system is mounted by <code class="docutils literal
notranslate"><span class="pre">nsh_romfsetc()</span></code>.</p>
<p>The ROMFS image is, itself, just built into the firmware. By default,
-this <code class="docutils literal notranslate"><span
class="pre">rcS</span></code> start-up script contains the following logic:</p>
+this <code class="docutils literal notranslate"><span
class="pre">rc.sysinit</span></code> system init script contains the following
logic:</p>
<div class="highlight-none notranslate"><div
class="highlight"><pre><span></span># Create a RAMDISK and mount it at
XXXRDMOUNTPOINTXXX
mkrd -m XXXMKRDMINORXXX -s XXMKRDSECTORSIZEXXX XXMKRDBLOCKSXXX
@@ -302,7 +302,7 @@ device.</p></li>
<li><p><code class="docutils literal notranslate"><span
class="pre">XXXRDMOUNTPOINTXXX</span></code> will become the configured mount
point.
Default: <code class="docutils literal notranslate"><span
class="pre">/etc</span></code></p></li>
</ul>
-<p>By default, the substituted values would yield an <code class="docutils
literal notranslate"><span class="pre">rcS</span></code> file like:</p>
+<p>By default, the substituted values would yield an <code class="docutils
literal notranslate"><span class="pre">rc.sysinit</span></code> file like:</p>
<div class="highlight-none notranslate"><div
class="highlight"><pre><span></span># Create a RAMDISK and mount it at /tmp
mkrd -m 1 -s 512 1024
@@ -317,8 +317,8 @@ mount -t vfat /dev/ram1 /tmp
then</p></li>
<li><p>Mount the FAT file system at a configured mountpoint, <code
class="docutils literal notranslate"><span
class="pre">/tmp</span></code>.</p></li>
</ul>
-<p>This <code class="docutils literal notranslate"><span
class="pre">rcS</span></code> template file can be found at
-<code class="docutils literal notranslate"><span
class="pre">apps/nshlib/rcS.template</span></code>. The resulting ROMFS file
system can be
+<p>This <code class="docutils literal notranslate"><span
class="pre">rc.sysinit.template</span></code> template file can be found at
+<code class="docutils literal notranslate"><span
class="pre">apps/nshlib/rc.sysinit.template</span></code>. The resulting ROMFS
file system can be
found in <code class="docutils literal notranslate"><span
class="pre">apps/nshlib/nsh_romfsimg.h</span></code>.</p>
</li>
<li><p><code class="docutils literal notranslate"><span
class="pre">board_app_initialize()</span></code>: Next any
architecture-specific NSH
@@ -329,6 +329,12 @@ things like: (1) Initialize SPI devices, (2) Initialize
SDIO, and (3)
mount any SD cards that may be inserted.</p></li>
<li><p><code class="docutils literal notranslate"><span
class="pre">nsh_netinit()</span></code>: The <code class="docutils literal
notranslate"><span class="pre">nsh_netinit()</span></code> function can be
found in
<code class="docutils literal notranslate"><span
class="pre">apps/nshlib/nsh_netinit.c</span></code>.</p></li>
+<li><p>The start-up script <code class="docutils literal notranslate"><span
class="pre">rcS</span></code> is executed after the system-init script
+to startup some application and other system service.</p>
+<p>This <code class="docutils literal notranslate"><span
class="pre">rcS</span></code> template file can be found at
+<code class="docutils literal notranslate"><span
class="pre">apps/nshlib/rcS.template</span></code>. The resulting ROMFS file
system can be
+found in <code class="docutils literal notranslate"><span
class="pre">apps/nshlib/nsh_romfsimg.h</span></code>.</p>
+</li>
</ol>
</div></blockquote>
</div>
diff --git a/content/docs/latest/applications/nsh/installation.html
b/content/docs/latest/applications/nsh/installation.html
index 981a041..6b5c7c6 100644
--- a/content/docs/latest/applications/nsh/installation.html
+++ b/content/docs/latest/applications/nsh/installation.html
@@ -281,9 +281,11 @@ behave as follows at NSH start-up time:</p>
ROMFS file system containing the following:</p>
<div class="highlight-none notranslate"><div
class="highlight"><pre><span></span>`--init.d/
`-- rcS
+ `-- rc.sysinit
</pre></div>
</div>
-<p>Where <code class="docutils literal notranslate"><span
class="pre">rcS</span></code> is the NSH start-up script.</p>
+<p>Where <code class="docutils literal notranslate"><span
class="pre">rcS</span></code> is the NSH start-up script.
+Where <code class="docutils literal notranslate"><span
class="pre">rc.sysinit</span></code> is the NSH system-init script.</p>
</li>
<li><p>NSH will then mount the ROMFS file system at <code class="docutils
literal notranslate"><span class="pre">/etc</span></code>, resulting in:</p>
<div class="highlight-none notranslate"><div
class="highlight"><pre><span></span>|--dev/
@@ -291,10 +293,11 @@ ROMFS file system containing the following:</p>
`--etc/
`--init.d/
`-- rcS
+ `-- rc.sysinit
</pre></div>
</div>
</li>
-<li><p>By default, the contents of <code class="docutils literal
notranslate"><span class="pre">rcS</span></code> script are:</p>
+<li><p>By default, the contents of <code class="docutils literal
notranslate"><span class="pre">rc.sysinit</span></code> script are:</p>
<div class="highlight-none notranslate"><div
class="highlight"><pre><span></span># Create a RAMDISK and mount it at /tmp
mkrd -m 1 -s 512 1024
@@ -303,15 +306,16 @@ mount -t vfat /dev/ram1 /tmp
</pre></div>
</div>
</li>
-<li><p>NSH will execute the script at <code class="docutils literal
notranslate"><span class="pre">/etc/init.d/rcS</span></code> at start-up
-(before the first NSH prompt). After execution of the script, the
-root FS will look like:</p>
+<li><p>NSH will execute the script at <code class="docutils literal
notranslate"><span class="pre">/etc/init.d/rc.sysinit</span></code> at system
+init (before the first NSH prompt). After execution of the script,
+the root FS will look like:</p>
<div class="highlight-none notranslate"><div
class="highlight"><pre><span></span>|--dev/
| |-- ram0
| `-- ram1
|--etc/
| `--init.d/
| `-- rcS
+| `-- rc.sysinit
`--tmp/
</pre></div>
</div>
@@ -333,14 +337,15 @@ provide useful examples:</p>
</ul>
</div></blockquote>
<p>In most of these cases, the configuration sets up the <em>default</em>
-<code class="docutils literal notranslate"><span
class="pre">/etc/init.d/rcS</span></code> script. The default script is here:
-<code class="docutils literal notranslate"><span
class="pre">apps/nshlib/rcS.template</span></code>. (The funny values in the
template like
-<code class="docutils literal notranslate"><span
class="pre">XXXMKRDMINORXXX</span></code> get replaced via <code
class="docutils literal notranslate"><span class="pre">sed</span></code> at
build time). This
+<code class="docutils literal notranslate"><span
class="pre">/etc/init.d/rc.sysinit</span></code> and <code class="docutils
literal notranslate"><span class="pre">/etc/init.d/rcS</span></code> script.
The default
+script is here: <code class="docutils literal notranslate"><span
class="pre">apps/nshlib/rc.sysinit.template</span></code> and
+<code class="docutils literal notranslate"><span
class="pre">apps/nshlib/rcS.template</span></code>. (The funny values in the
rc.sysinit.template
+like <code class="docutils literal notranslate"><span
class="pre">XXXMKRDMINORXXX</span></code> get replaced via <code
class="docutils literal notranslate"><span class="pre">sed</span></code> at
build time). This
default configuration creates a ramdisk and mounts it at <code class="docutils
literal notranslate"><span class="pre">/tmp</span></code> as
discussed above.</p>
<p>If that default behavior is not what you want, then you can provide your
-own custom <code class="docutils literal notranslate"><span
class="pre">rcS</span></code> script by defining <code class="docutils literal
notranslate"><span class="pre">CONFIG_NSH_ARCHROMFS=y</span></code> in the
-configuration file.</p>
+own custom <code class="docutils literal notranslate"><span
class="pre">rc.sysinit</span></code> and <code class="docutils literal
notranslate"><span class="pre">rcS</span></code> script by defining
+<code class="docutils literal notranslate"><span
class="pre">CONFIG_NSH_ARCHROMFS=y</span></code> in the configuration file.</p>
<p><strong>Modifying the ROMFS Image</strong>. The contents of the <code
class="docutils literal notranslate"><span class="pre">/etc</span></code>
directory
are retained in the file <code class="docutils literal notranslate"><span
class="pre">apps/nshlib/nsh_romfsimg.h</span></code> OR, if
<code class="docutils literal notranslate"><span
class="pre">CONFIG_NSH_ARCHROMFS</span></code> is defined,
@@ -358,7 +363,7 @@ settings associated with creating and mounting the <code
class="docutils literal
directory, then it will be necessary to re-generate this header file
using the <code class="docutils literal notranslate"><span
class="pre">tools/mkromfsimg.sh</span></code> script.</p>
<p>The behavior of this script depends upon several things:</p>
-<ol class="arabic simple">
+<ol class="arabic">
<li><p>The configuration settings then installed configuration.</p></li>
<li><p>The <code class="docutils literal notranslate"><span
class="pre">genromfs</span></code> tool(available from
<a class="reference external"
href="http://romfs.sourceforge.net/";>http://romfs.sourceforge.net</a>)
@@ -368,15 +373,23 @@ snapshot available in the NuttX tools repository
<li><p>The <code class="docutils literal notranslate"><span
class="pre">xxd</span></code> tool that is used to generate the C header files
(xxd
is a normal part of a complete Linux or Cygwin installation,
usually as part of the <code class="docutils literal notranslate"><span
class="pre">vi</span></code> package).</p></li>
-<li><p>The file <code class="docutils literal notranslate"><span
class="pre">apps/nshlib/rcS.template</span></code> (OR, if
+<li><p>The file <code class="docutils literal notranslate"><span
class="pre">apps/nshlib/rc.sysinit.template</span></code> (OR, if
<code class="docutils literal notranslate"><span
class="pre">CONFIG_NSH_ARCHROMFS</span></code> is defined
-<code class="docutils literal notranslate"><span
class="pre">include/arch/board/rcs.template</span></code>.</p></li>
+<code class="docutils literal notranslate"><span
class="pre">include/arch/board/rc.sysinit.template</span></code>.</p>
+<p>The file <code class="docutils literal notranslate"><span
class="pre">apps/nshlib/rcS.template</span></code> (OR, if
+<code class="docutils literal notranslate"><span
class="pre">CONFIG_NSH_ARCHROMFS</span></code> is defined
+<code class="docutils literal notranslate"><span
class="pre">include/arch/board/rcs.template</span></code>.</p>
+</li>
</ol>
</li>
-<li><p><code class="docutils literal notranslate"><span
class="pre">rcS.template</span></code>. The file <code class="docutils literal
notranslate"><span class="pre">apps/nshlib/rcS.template</span></code> contains
the
+<li><p><code class="docutils literal notranslate"><span
class="pre">rc.sysinit.template</span></code>. The file <code class="docutils
literal notranslate"><span
class="pre">apps/nshlib/rc.sysinit.template</span></code>
+contains the general form of the <code class="docutils literal
notranslate"><span class="pre">rc.sysinit</span></code> file; configured values
+are plugged into this template file to produce the final <code class="docutils
literal notranslate"><span class="pre">rc.sysinit</span></code> file.</p>
+<p><code class="docutils literal notranslate"><span
class="pre">rcS.template</span></code>. The file <code class="docutils literal
notranslate"><span class="pre">apps/nshlib/rcS.template</span></code> contains
the
general form of the <code class="docutils literal notranslate"><span
class="pre">rcS</span></code> file; configured values are plugged into
this template file to produce the final <code class="docutils literal
notranslate"><span class="pre">rcS</span></code> file.</p>
-<p>To generate a custom <code class="docutils literal notranslate"><span
class="pre">rcS</span></code> file a copy of <code class="docutils literal
notranslate"><span class="pre">rcS.template</span></code> needs to
+<p>To generate a custom <code class="docutils literal notranslate"><span
class="pre">rc.sysinit</span></code> and <code class="docutils literal
notranslate"><span class="pre">rcS</span></code> file a copy of
+<code class="docutils literal notranslate"><span
class="pre">rc.sysinit.template</span></code> and <code class="docutils literal
notranslate"><span class="pre">rcS.template</span></code> needs to
be placed at <code class="docutils literal notranslate"><span
class="pre">tools/</span></code> and changed according to the desired start-up
behaviour. Running <code class="docutils literal notranslate"><span
class="pre">tools/mkromfsimg.h</span></code> creates <code class="docutils
literal notranslate"><span class="pre">nsh_romfsimg.h</span></code>
which needs to be copied to <code class="docutils literal notranslate"><span
class="pre">apps/nshlib</span></code> OR if
@@ -385,6 +398,9 @@ which needs to be copied to <code class="docutils literal
notranslate"><span cla
</li>
</ol>
</div></blockquote>
+<p><code class="docutils literal notranslate"><span
class="pre">rc.sysinit.template</span></code>. The default <code
class="docutils literal notranslate"><span
class="pre">rc.sysinit.template</span></code>,
+<code class="docutils literal notranslate"><span
class="pre">apps/nshlib/rc.sysinit.template</span></code>, generates the
standard, default
+<code class="docutils literal notranslate"><span
class="pre">apps/nshlib/nsh_romfsimg.h</span></code> file.</p>
<p><code class="docutils literal notranslate"><span
class="pre">rcS.template</span></code>. The default <code class="docutils
literal notranslate"><span class="pre">rcS.template</span></code>,
<code class="docutils literal notranslate"><span
class="pre">apps/nshlib/rcS.template</span></code>, generates the standard,
default
<code class="docutils literal notranslate"><span
class="pre">apps/nshlib/nsh_romfsimg.h</span></code> file.</p>
@@ -393,10 +409,11 @@ then a custom, board-specific <code class="docutils
literal notranslate"><span c
<code class="docutils literal notranslate"><span
class="pre">boards/<arch>/<chip>/<board>/include</span></code>will
be used. NOTE when the OS
is configured, <code class="docutils literal notranslate"><span
class="pre">include/arch/board</span></code> will be linked to
<code class="docutils literal notranslate"><span
class="pre">boards/<arch>/<chip>/<board>/include</span></code>.</p>
-<p>All of the startup-behavior is contained in <code class="docutils literal
notranslate"><span class="pre">rcS.template</span></code>. The role
-of <code class="docutils literal notranslate"><span
class="pre">mkromfsimg.sh</span></code> script is to (1) apply the specific
configuration
-settings to <code class="docutils literal notranslate"><span
class="pre">rcS.template</span></code> to create the final <code
class="docutils literal notranslate"><span class="pre">rcS</span></code>, and
(2) to
-generate the header file <code class="docutils literal notranslate"><span
class="pre">nsh_romfsimg.h</span></code> containing the ROMFS file
+<p>All of the startup-behavior is contained in <code class="docutils literal
notranslate"><span class="pre">rc.sysinit.template</span></code> and
+<code class="docutils literal notranslate"><span
class="pre">rcS.template</span></code>. The role of <code class="docutils
literal notranslate"><span class="pre">mkromfsimg.sh</span></code> script is to
(1) apply
+the specific configuration settings to <code class="docutils literal
notranslate"><span class="pre">rc.sysinit.template</span></code> to create
+the final <code class="docutils literal notranslate"><span
class="pre">rc.sysinit</span></code>, and <code class="docutils literal
notranslate"><span class="pre">rcS.template</span></code> to create the final
<code class="docutils literal notranslate"><span class="pre">rcS</span></code>,
+and (2) to generate the header file <code class="docutils literal
notranslate"><span class="pre">nsh_romfsimg.h</span></code> containing the
ROMFS file
system image. To do this, <code class="docutils literal notranslate"><span
class="pre">mkromfsimg.sh</span></code> uses two tools that must be
installed in your system:</p>
<blockquote>
diff --git a/content/docs/latest/applications/nsh/login.html
b/content/docs/latest/applications/nsh/login.html
index 0a02376..78d115a 100644
--- a/content/docs/latest/applications/nsh/login.html
+++ b/content/docs/latest/applications/nsh/login.html
@@ -388,10 +388,12 @@ nsh> ls -Rl /etc
/etc/init.d:
dr-xr-xr-x 0 ..
-r--r--r-- 110 rcS
+ -r--r--r-- 110 rc.sysinit
nsh>
</pre></div>
</div>
-<p>Where <code class="docutils literal notranslate"><span
class="pre">/etc/init.d/rcS</span></code> is the start-up script; <code
class="docutils literal notranslate"><span
class="pre">/etc/passwd</span></code> is a
+<p>Where <code class="docutils literal notranslate"><span
class="pre">/etc/init.d/rc.sysinit</span></code> is the system init script and
+<code class="docutils literal notranslate"><span
class="pre">/etc/init.d/rcS</span></code> is the start-up script; <code
class="docutils literal notranslate"><span
class="pre">/etc/passwd</span></code> is a
the password file. Note that here we assume that you are already using a
start-up script. We can then piggyback the passwd file into the <code
class="docutils literal notranslate"><span class="pre">/etc</span></code>
file system already mounted for the NSH start up file as described above
diff --git a/content/docs/latest/applications/nsh/nsh.html
b/content/docs/latest/applications/nsh/nsh.html
index df766b5..b09cf79 100644
--- a/content/docs/latest/applications/nsh/nsh.html
+++ b/content/docs/latest/applications/nsh/nsh.html
@@ -545,9 +545,11 @@ NSH to behave as follows at NSH startup time:</p>
tiny ROMFS file system containing the following:</p>
<div class="highlight-none notranslate"><div
class="highlight"><pre><span></span>`--init.d/
`-- rcS
+ `-- rc.sysinit
</pre></div>
</div>
-<p>Where rcS is the NSH start-up script.</p>
+<p>Where rcS is the NSH start-up script.
+Where rc.sysinit is the NSH system init script.</p>
</li>
<li><p>NSH will then mount the ROMFS file system at <code class="docutils
literal notranslate"><span class="pre">/etc</span></code>,
resulting in:</p>
@@ -556,10 +558,11 @@ resulting in:</p>
`--etc/
`--init.d/
`-- rcS
+ `-- rc.sysinit
</pre></div>
</div>
</li>
-<li><p>By default, the contents of rcS script are:</p>
+<li><p>By default, the contents of rc.sysinit script are:</p>
<div class="highlight-none notranslate"><div
class="highlight"><pre><span></span># Create a RAMDISK and mount it at
XXXRDMOUNTPOINTXXX
mkrd -m 1 -s 512 1024
@@ -568,15 +571,16 @@ mount -t vfat /dev/ram1 /tmp
</pre></div>
</div>
</li>
-<li><p>NSH will execute the script at <code class="docutils literal
notranslate"><span class="pre">/etc/init.d/rcS</span></code> at start-up
-(before the first NSH prompt). After execution of the script,
-the root FS will look like:</p>
+<li><p>NSH will execute the script at <code class="docutils literal
notranslate"><span class="pre">/etc/init.d/rc.sysinit</span></code> at
+system init script(before the first NSH prompt). After
+execution of the script, the root FS will look like:</p>
<div class="highlight-none notranslate"><div
class="highlight"><pre><span></span>|--dev/
| |-- ram0
| `-- ram1
|--etc/
| `--init.d/
| `-- rcS
+| `-- rc.sysinit
`--tmp/
</pre></div>
</div>
@@ -605,31 +609,40 @@ file using the <code class="docutils literal
notranslate"><span class="pre">tool
<li><p>The configuration settings then installed configuration.</p></li>
<li><p>The <code class="docutils literal notranslate"><span
class="pre">genromfs</span></code> tool (available from
<a class="reference external"
href="http://romfs.sourceforge.net";>http://romfs.sourceforge.net</a>).</p></li>
-<li><p>The file <code class="docutils literal notranslate"><span
class="pre">apps/nshlib/rcS.template</span></code> (OR, if
+<li><p>The file <code class="docutils literal notranslate"><span
class="pre">apps/nshlib/rc.sysinit.template</span></code> (OR, if
+<code class="docutils literal notranslate"><span
class="pre">CONFIG_NSH_ARCHROMFS</span></code> is defined
+<code class="docutils literal notranslate"><span
class="pre">include/arch/board/rc.sysinit.template</span></code>.
+The file <code class="docutils literal notranslate"><span
class="pre">apps/nshlib/rcS.template</span></code> (OR, if
<code class="docutils literal notranslate"><span
class="pre">CONFIG_NSH_ARCHROMFS</span></code> is defined
<code class="docutils literal notranslate"><span
class="pre">include/arch/board/rcs.template</span></code>.</p></li>
</ul>
</li>
-<li><p><code class="docutils literal notranslate"><span
class="pre">rcS.template</span></code>: The file <code class="docutils literal
notranslate"><span class="pre">apps/nshlib/rcS.template</span></code>
+<li><p><code class="docutils literal notranslate"><span
class="pre">rc.sysinit.template</span></code>: The file <code class="docutils
literal notranslate"><span
class="pre">apps/nshlib/rc.sysinit.template</span></code>
+contains the general form of the <code class="docutils literal
notranslate"><span class="pre">rc.sysinit</span></code> file; configured
+values are plugged into this template file to produce the final
+<code class="docutils literal notranslate"><span
class="pre">rc.sysinit</span></code> file.</p>
+<p><code class="docutils literal notranslate"><span
class="pre">rcS.template</span></code>: The file <code class="docutils literal
notranslate"><span class="pre">apps/nshlib/rcS.template</span></code>
contains the general form of the <code class="docutils literal
notranslate"><span class="pre">rcS</span></code> file; configured
values are plugged into this template file to produce the final
-<code class="docutils literal notranslate"><span class="pre">rcS</span></code>
file.</p></li>
+<code class="docutils literal notranslate"><span class="pre">rcS</span></code>
file.</p>
+</li>
</ol>
</div></blockquote>
<div class="admonition note">
<p class="admonition-title">Note</p>
-<p><code class="docutils literal notranslate"><span
class="pre">apps/nshlib/rcS.template</span></code> generates the standard,
-default <code class="docutils literal notranslate"><span
class="pre">nsh_romfsimg.h</span></code> file. If <code class="docutils literal
notranslate"><span class="pre">CONFIG_NSH_ARCHROMFS</span></code> is
-defined in the NuttX configuration file, then a custom,
-board-specific <code class="docutils literal notranslate"><span
class="pre">nsh_romfsimg.h</span></code> file residing in the
-<code class="docutils literal notranslate"><span
class="pre">boards/<arch>/<chip>/<board>/include</span></code>
directory will be used.
-NOTE when the OS is configured, <code class="docutils literal
notranslate"><span class="pre">include/arch/board</span></code> will be
+<p><code class="docutils literal notranslate"><span
class="pre">apps/nshlib/rcS.template</span></code> and <code class="docutils
literal notranslate"><span
class="pre">apps/nshlib/rc.sysinit.template</span></code>
+generates the standard, default <code class="docutils literal
notranslate"><span class="pre">nsh_romfsimg.h</span></code> file.
+If <code class="docutils literal notranslate"><span
class="pre">CONFIG_NSH_ARCHROMFS</span></code> is defined in the NuttX
configuration
+file, then a custom, board-specific <code class="docutils literal
notranslate"><span class="pre">nsh_romfsimg.h</span></code> file residing
+in the <code class="docutils literal notranslate"><span
class="pre">boards/<arch>/<chip>/<board>/include</span></code>
directory will be
+used. NOTE when the OS is configured, <code class="docutils literal
notranslate"><span class="pre">include/arch/board</span></code> will be
linked to <code class="docutils literal notranslate"><span
class="pre">boards/<arch>/<chip>/<board>/include</span></code>.</p>
</div>
-<p>All of the startup-behavior is contained in <code class="docutils literal
notranslate"><span class="pre">rcS.template</span></code>. The
-role of <code class="docutils literal notranslate"><span
class="pre">mkromfsimg.sh</span></code> is to (1) apply the specific
-configuration settings to <code class="docutils literal notranslate"><span
class="pre">rcS.template</span></code> to create the final
-<code class="docutils literal notranslate"><span
class="pre">rcS</span></code>, and (2) to generate the header file <code
class="docutils literal notranslate"><span
class="pre">nsh_romfsimg.h</span></code>
+<p>All of the startup-behavior is contained in <code class="docutils literal
notranslate"><span class="pre">rc.sysinit.template</span></code>
+and <code class="docutils literal notranslate"><span
class="pre">rcS.template</span></code>. The role of <code class="docutils
literal notranslate"><span class="pre">mkromfsimg.sh</span></code> is to (1)
apply
+the specific configuration settings to <code class="docutils literal
notranslate"><span class="pre">rc.sysinit.template</span></code> to create
+the final <code class="docutils literal notranslate"><span
class="pre">rc.sysinit</span></code>, and <code class="docutils literal
notranslate"><span class="pre">rc.sysinit.template</span></code> to create the
final
+<code class="docutils literal notranslate"><span class="pre">rcS</span></code>
and (2) to generate the header file <code class="docutils literal
notranslate"><span class="pre">nsh_romfsimg.h</span></code>
containing the ROMFS file system image.</p>
<p><strong>Further Information</strong>. See the section on <a
class="reference external" href="#customizingnsh">Customizing the
NuttShell</a> for additional, more detailed
diff --git a/content/docs/latest/index.html b/content/docs/latest/index.html
index 6c0a359..db1043f 100644
--- a/content/docs/latest/index.html
+++ b/content/docs/latest/index.html
@@ -216,7 +216,7 @@ by following these <a class="reference internal"
href="contributing/documentatio
<div class="section" id="nuttx-documentation">
<h1>NuttX Documentation<a class="headerlink" href="#nuttx-documentation"
title="Permalink to this headline">¶</a></h1>
<p>NuttX is a real-time operating system (RTOS) with an emphasis on standards
compliance and small footprint. Scalable from 8-bit to 64-bit microcontroller
environments, the primary governing standards in NuttX are POSIX and ANSI
standards. Additional standard APIs from Unix and other common RTOS’s (such as
VxWorks) are adopted for functionality not available under these standards, or
for functionality that is not appropriate for deeply-embedded environments
(such as fork()).</p>
-<p>Last Updated: 21 April 22 at 00:12</p>
+<p>Last Updated: 22 April 22 at 00:12</p>
<div class="toctree-wrapper compound">
<p class="caption"><span class="caption-text">Table of Contents</span></p>
<ul class="current">
diff --git a/content/docs/latest/searchindex.js
b/content/docs/latest/searchindex.js
index 8f5d4db..decc843 100644
--- a/content/docs/latest/searchindex.js
+++ b/content/docs/latest/searchindex.js
@@ -1 +1 @@
-Search.setIndex({docnames:["applications/index","applications/nsh/builtin","applications/nsh/commands","applications/nsh/config","applications/nsh/customizing","applications/nsh/index","applications/nsh/installation","applications/nsh/login","applications/nsh/nsh","components/binfmt","components/drivers/block/index","components/drivers/character/analog","components/drivers/character/can","components/drivers/character/foc","components/drivers/character/index","components/drivers/character
[...]
\ No newline at end of file
+Search.setIndex({docnames:["applications/index","applications/nsh/builtin","applications/nsh/commands","applications/nsh/config","applications/nsh/customizing","applications/nsh/index","applications/nsh/installation","applications/nsh/login","applications/nsh/nsh","components/binfmt","components/drivers/block/index","components/drivers/character/analog","components/drivers/character/can","components/drivers/character/foc","components/drivers/character/index","components/drivers/character
[...]
\ No newline at end of file
diff --git a/content/feed.xml b/content/feed.xml
index 862f7c1..dac2ae7 100644
--- a/content/feed.xml
+++ b/content/feed.xml
@@ -5,8 +5,8 @@
<description></description>
<link>/</link>
<atom:link href="/feed.xml" rel="self" type="application/rss+xml"/>
- <pubDate>Thu, 21 Apr 2022 00:14:04 +0000</pubDate>
- <lastBuildDate>Thu, 21 Apr 2022 00:14:04 +0000</lastBuildDate>
+ <pubDate>Fri, 22 Apr 2022 00:14:20 +0000</pubDate>
+ <lastBuildDate>Fri, 22 Apr 2022 00:14:20 +0000</lastBuildDate>
<generator>Jekyll v3.8.5</generator>
<item>
