dev-manual: Changed "$" to "#" for runtime packaging section

This fixes the prompt to be "#" rather than "$", which is a
convention for running commands at a different level according
to Trevor Woerner.

(From yocto-docs rev: b8eebdf4738c8655db724498a2293a44cae331dc)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

1 files changed, 11 insertions, 11 deletions

diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml
index 1f49cb24f4..ff4bbcd3ea 100644
--- a/documentation/dev-manual/dev-manual-common-tasks.xml
+++ b/documentation/dev-manual/dev-manual-common-tasks.xml
@@ -3844,15 +3844,15 @@
                                 If your development system is using Fedora or
                                 CentOS, use the following:
                                 <literallayout class='monospaced'>
-     $ service httpd reload
+     # service httpd reload
                                 </literallayout>
                                 For Ubuntu and Debian, use the following:
                                 <literallayout class='monospaced'>
-     $ /etc/init.d/apache2 reload
+     # /etc/init.d/apache2 reload
                                 </literallayout>
                                 For OpenSUSE, use the following:
                                 <literallayout class='monospaced'>
-     $ /etc/init.d/apache2 reload
+     # /etc/init.d/apache2 reload
                                 </literallayout></para></listitem>
                             <listitem><para>
                                 If you are using Security-Enhanced Linux
@@ -3862,7 +3862,7 @@
                                 host.
                                 This example assumes RPM package types:
                                 <literallayout class='monospaced'>
-     $ chcon -R -h -t httpd_sys_content_t tmp/deploy/rpm
+     # chcon -R -h -t httpd_sys_content_t tmp/deploy/rpm
                                 </literallayout></para></listitem>
                         </orderedlist>
                     </para>
@@ -3890,7 +3890,7 @@
                         then you might create a link from your build location
                         to lighttpd's document-root as follows:
                         <literallayout class='monospaced'>
-    $ ln -s $(PWD)/tmp/deploy/ipk /var/www/lighttpd/BOARD-dir
+    # ln -s $(PWD)/tmp/deploy/ipk /var/www/lighttpd/BOARD-dir
                         </literallayout>
                     </para>
 
@@ -3900,7 +3900,7 @@
                         distribution.
                         However, one basic method that starts it by hand is:
                         <literallayout class='monospaced'>
-    $ lighttpd -f /etc/lighttpd/lighttpd.conf
+    # lighttpd -f /etc/lighttpd/lighttpd.conf
                         </literallayout>
                     </para>
                 </section>
@@ -3936,14 +3936,14 @@
                         Given this example, issue the following commands on the
                         target:
                         <literallayout class='monospaced'>
-     $ smart channel --add all type=rpm-md baseurl=http://server.name/rpm/all
-     $ smart channel --add i585 type=rpm-md baseurl=http://server.name/rpm/i586
-     $ smart channel --add qemux86 type=rpm-md baseurl=http://server.name/rpm/qemux86
+     # smart channel --add all type=rpm-md baseurl=http://server.name/rpm/all
+     # smart channel --add i585 type=rpm-md baseurl=http://server.name/rpm/i586
+     # smart channel --add qemux86 type=rpm-md baseurl=http://server.name/rpm/qemux86
                         </literallayout>
                         Also from the target machine, fetch the repository
                         information using this command:
                         <literallayout class='monospaced'>
-     $ smart update
+     # smart update
                         </literallayout>
                         You can now use the <filename>smart query</filename>
                         and <filename>smart install</filename> commands to
@@ -4017,7 +4017,7 @@
                         On the target machine, fetch (or refresh) the
                         repository information using this command:
                         <literallayout class='monospaced'>
-     $ opkg update
+     # opkg update
                         </literallayout>
                         You can now use the <filename>opkg list</filename> and
                         <filename>opkg install</filename> commands to find and