diff options
Diffstat (limited to 'en_US.ISO8859-1/articles/nanobsd/article.xml')
| -rw-r--r-- | en_US.ISO8859-1/articles/nanobsd/article.xml | 81 |
1 files changed, 39 insertions, 42 deletions
diff --git a/en_US.ISO8859-1/articles/nanobsd/article.xml b/en_US.ISO8859-1/articles/nanobsd/article.xml index a12c10305d..52d64f9bd6 100644 --- a/en_US.ISO8859-1/articles/nanobsd/article.xml +++ b/en_US.ISO8859-1/articles/nanobsd/article.xml @@ -1,17 +1,12 @@ <?xml version="1.0" encoding="iso-8859-1"?> -<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook XML V4.5-Based Extension//EN" - "../../../share/xml/freebsd45.dtd"> - -<article lang='en'> - <articleinfo> - <title>Introduction to NanoBSD</title> +<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook XML V5.0-Based Extension//EN" + "../../../share/xml/freebsd50.dtd"> +<article xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" xml:lang="en"> + <info><title>Introduction to NanoBSD</title> + <authorgroup> - <author> - <firstname>Daniel</firstname> - <surname>Gerzo</surname> - <!-- 14 March 2006 --> - </author> + <author><personname><firstname>Daniel</firstname><surname>Gerzo</surname></personname></author> </authorgroup> <copyright> @@ -19,7 +14,7 @@ <holder>The FreeBSD Documentation Project</holder> </copyright> - <legalnotice id="trademarks" role="trademarks"> + <legalnotice xml:id="trademarks" role="trademarks"> &tm-attrib.freebsd; &tm-attrib.general; </legalnotice> @@ -34,9 +29,9 @@ create &os; system images for embedded applications, suitable for use on a Compact Flash card (or other mass storage medium).</para> </abstract> - </articleinfo> + </info> - <sect1 id="intro"> + <sect1 xml:id="intro"> <title>Introduction to NanoBSD</title> <indexterm><primary>NanoBSD</primary></indexterm> @@ -87,10 +82,10 @@ </itemizedlist> </sect1> - <sect1 id="howto"> + <sect1 xml:id="howto"> <title>NanoBSD Howto</title> - <sect2 id="design"> + <sect2 xml:id="design"> <title>The design of NanoBSD</title> <para>Once the image is present on the medium, it is possible to @@ -105,24 +100,24 @@ <listitem> <para>The configuration file partition, which can be mounted - under the <filename class="directory">/cfg</filename> directory + under the <filename>/cfg</filename> directory at run time.</para> </listitem> </itemizedlist> <para>These partitions are normally mounted read-only.</para> - <para>The <filename class="directory">/etc</filename> and - <filename class="directory">/var</filename> directories are + <para>The <filename>/etc</filename> and + <filename>/var</filename> directories are &man.md.4; (malloc) disks.</para> <para>The configuration file partition persists under the - <filename class="directory">/cfg</filename> directory. It - contains files for <filename class="directory">/etc</filename> + <filename>/cfg</filename> directory. It + contains files for <filename>/etc</filename> directory and is briefly mounted read-only right after the system boot, therefore it is required to copy modified files - from <filename class="directory">/etc</filename> back to the - <filename class="directory">/cfg</filename> directory if changes + from <filename>/etc</filename> back to the + <filename>/cfg</filename> directory if changes are expected to persist after the system restarts.</para> <example> @@ -137,11 +132,11 @@ <note> <para>The partition containing - <filename class="directory">/cfg</filename> should be mounted + <filename>/cfg</filename> should be mounted only at boot time and while overriding the configuration files.</para> - <para>Keeping <filename class="directory">/cfg</filename> mounted at + <para>Keeping <filename>/cfg</filename> mounted at all times is not a good idea, especially if the <application>NanoBSD</application> system runs off a mass storage medium that may be adversely affected by a large number @@ -156,17 +151,17 @@ <para>A <application>NanoBSD</application> image is built using a simple <filename>nanobsd.sh</filename> shell script, which can be found in the - <filename class="directory"><replaceable>/usr</replaceable>/src/tools/tools/nanobsd</filename> + <filename>/usr/src/tools/tools/nanobsd</filename> directory. This script creates an image, which can be copied on the storage medium using the &man.dd.1; utility.</para> <para>The necessary commands to build a <application>NanoBSD</application> image are:</para> - <screen>&prompt.root; <userinput>cd /usr/src/tools/tools/nanobsd</userinput> <co id="nbsd-cd"/> -&prompt.root; <userinput>sh nanobsd.sh</userinput> <co id="nbsd-sh"/> -&prompt.root; <userinput>cd /usr/obj/nanobsd.full</userinput> <co id="nbsd-cd2"/> -&prompt.root; <userinput>dd if=_.disk.full of=/dev/da0 bs=64k</userinput> <co id="nbsd-dd"/></screen> + <screen>&prompt.root; <userinput>cd /usr/src/tools/tools/nanobsd</userinput> <co xml:id="nbsd-cd"/> +&prompt.root; <userinput>sh nanobsd.sh</userinput> <co xml:id="nbsd-sh"/> +&prompt.root; <userinput>cd /usr/obj/nanobsd.full</userinput> <co xml:id="nbsd-cd2"/> +&prompt.root; <userinput>dd if=_.disk.full of=/dev/da0 bs=64k</userinput> <co xml:id="nbsd-dd"/></screen> <calloutlist> <callout arearefs="nbsd-cd"> @@ -221,8 +216,8 @@ <title>Configuration options</title> <para>With configuration settings, it is possible to configure options - passed to both the <maketarget>buildworld</maketarget> - and <maketarget>installworld</maketarget> stages of the + passed to both the <buildtarget>buildworld</buildtarget> + and <buildtarget>installworld</buildtarget> stages of the <application>NanoBSD</application> build process, as well as internal options passed to the main build process of <application>NanoBSD</application>. Through these options it is @@ -253,18 +248,18 @@ <listitem> <para><literal>CONF_BUILD</literal> — Options passed - to the <maketarget>buildworld</maketarget> stage of the build.</para> + to the <buildtarget>buildworld</buildtarget> stage of the build.</para> </listitem> <listitem> <para><literal>CONF_INSTALL</literal> — Options passed - to the <maketarget>installworld</maketarget> stage of the build.</para> + to the <buildtarget>installworld</buildtarget> stage of the build.</para> </listitem> <listitem> <para><literal>CONF_WORLD</literal> — Options passed to both - the <maketarget>buildworld</maketarget> and - the <maketarget>installworld</maketarget> stage of the build.</para> + the <buildtarget>buildworld</buildtarget> and + the <buildtarget>installworld</buildtarget> stage of the build.</para> </listitem> <listitem> @@ -291,7 +286,7 @@ customize_cmd cust_foo</programlisting> <para>A more useful example of a customization function is the following, which changes the default size of the - <filename class="directory">/etc</filename> directory + <filename>/etc</filename> directory from 5MB to 30MB:</para> <programlisting>cust_etc_size () ( @@ -313,13 +308,13 @@ customize_cmd cust_etc_size</programlisting> <listitem> <para><literal>cust_allow_ssh_root</literal> — Allow - <username>root</username> to login via &man.sshd.8;.</para> + <systemitem class="username">root</systemitem> to login via &man.sshd.8;.</para> </listitem> <listitem> <para><literal>cust_install_files</literal> — Installs files from the - <filename class="directory">nanobsd/Files</filename> + <filename>nanobsd/Files</filename> directory, which contains some useful scripts for system administration.</para> </listitem> @@ -447,7 +442,7 @@ customize_cmd cust_nobeastie</programlisting> <application>NanoBSD</application> system, it is possible to use either the <filename>updatep1</filename> or <filename>updatep2</filename> script located in the - <filename class="directory">/root</filename> directory, depending + <filename>/root</filename> directory, depending from which partition is running the current system.</para> <para>According to which services are available on host serving @@ -485,7 +480,7 @@ get _.disk.image "| sh updatep1"</userinput></screen> <para>At first, open a TCP listener on host serving the image and make it send the image to client:</para> - <screen>myhost&prompt.root; <userinput>nc -l <replaceable>2222</replaceable> < _.disk.image</userinput></screen> + <screen>myhost&prompt.root; <userinput>nc -l 2222 < _.disk.image</userinput></screen> <note> <para>Make sure that the used port is not blocked to @@ -498,10 +493,12 @@ get _.disk.image "| sh updatep1"</userinput></screen> <para>Connect to the host serving new image and execute <filename>updatep1</filename> script:</para> - <screen>&prompt.root; <userinput>nc myhost <replaceable>2222</replaceable> | sh updatep1</userinput></screen> + <screen>&prompt.root; <userinput>nc myhost 2222 | sh updatep1</userinput></screen> </step> </procedure> </sect3> </sect2> </sect1> + + <index/> </article> |