[Pkg-uml-commit] r103 - trunk/src/rootstrap

[Mattia Dongili]

Author: malattia
Date: 2006-05-27 16:16:04 +0000 (Sat, 27 May 2006)
New Revision: 103

Modified:
   trunk/src/rootstrap/rootstrap.sgml
Log:
update manpage with recent changes and reindent a little (hope it displays correctly for all)

Modified: trunk/src/rootstrap/rootstrap.sgml
===================================================================
--- trunk/src/rootstrap/rootstrap.sgml	2006-05-27 16:01:18 UTC (rev 102)
+++ trunk/src/rootstrap/rootstrap.sgml	2006-05-27 16:16:04 UTC (rev 103)
@@ -381,50 +381,50 @@
 
       <para>
         When a module is invoked, the filesystem being created is
-        mounted on $TARGET.  /etc and /tmp are tmpfs filesystems
+        mounted on $TARGET. /dev, /etc and /tmp are tmpfs filesystems
         internal to the UML system, while the root filesystem is a
-        hostfs mount of the system where rootstrap is running.  This
-        means that most software on the host system should be
+	hostfs mount of the system where rootstrap is running. /lib/modules is
+	tmpfs too and bind mounted to the host's /usr/lib/uml/modules to let
+	scripts load necessary kernel modules.
+	This means that most software on the host system should be
         available and work as expected.  The working directory where
         rootstrap is run is available as $WORKDIR.  The environment is
         generated from the configuration file as described above.
       </para>
 	  
-	  <para>
-	  	Since you launch rootstrap and you invoke <command>linux</command>
-		command, you need to use the $TARGET on the host filesystem.
-		This means that <command>linux</command> needs a shared filesystem to
-		work with and to create the final result, the filesystem image
-		itself.
-	  </para>
+      <para>
+	Since you launch rootstrap and you invoke <command>linux</command>
+	command, you need to use the $TARGET on the host filesystem.
+	This means that <command>linux</command> needs a shared filesystem to
+	work with and to create the final result, the filesystem image itself.
+      </para>
 
-	  <para>
-	    This is indeed the case of the /tmp/, /tmp/host, /tmp/target
-		($TARGET) as well as /etc/rootstrap ($WORKDIR) in case you need to read the system wide
-		rootstrap.conf. These directories are needed by the
-		<command>builder</command> python script invoked by rootstrap
-		(init=/usr/lib/rootstrap/builder).
-	  </para>
+      <para>
+	This is indeed the case of the /tmp/, /tmp/host, /tmp/target ($TARGET)
+	as well as /etc/rootstrap ($WORKDIR) in case you need to read the
+	system wide rootstrap.conf. These directories are needed by the
+	<command>builder</command> python script invoked by rootstrap
+	(init=/usr/lib/rootstrap/builder).
+      </para>
 
-	  <para>
-	  	User Mode Linux kernel, <command>linux</command>, is allowed to share
-		the host filesystem, once is mounted as hostfs in its
-		/etc/fstab, thus the rootstrap idea of building a filesystem
-		image is mainly based on this feature. This means that you can
-		share the host resources and build filesystem on it, as well as
-		to share host binaries to perform whatever task you may need.
-	  </para>
+      <para>
+	User Mode Linux kernel, <command>linux</command>, is allowed to share
+	the host filesystem, once is mounted as hostfs in its /etc/fstab, thus
+	the rootstrap idea of building a filesystem image is mainly based on
+	this feature. This means that you can share the host resources and
+	build filesystem on it, as well as to share host binaries to perform
+	whatever task you may need.
+      </para>
 
-	  <para>
-	  	If you would like to have the hostfs support for you
-		<command>linux</command> or at least for the filesystem creation
-		with rootstrap, you need to configure the CONFIG_HOSTFS=y, then to compile the
-		UML guest kernel in order to include this feature. In particular
-		it is recommended to set it as included in the
-		<command>linux</command> file, not as module because it is
-		required during the rootstrap launch, and not included in the
-		following modules copy on the guest filesystem.
-		</para>
+      <para>
+	If you would like to have the hostfs support for you
+	<command>linux</command> or at least for the filesystem creation with
+	rootstrap, you need to configure the CONFIG_HOSTFS=y, then to compile
+	the UML guest kernel in order to include this feature. In particular it
+	is recommended to set it as included in the <command>linux</command>
+	file, not as module because it is required during the rootstrap launch,
+	and not included in the following modules copy on the guest filesystem.
+      </para>
     </refsect2>
 
   </refsect1>