PERFORCE change 160244 for review

[Rene Ladan]

http://perforce.freebsd.org/chv.cgi?CH=160244

Change 160244 by rene at rene_self on 2009/04/05 19:49:48

	solid-state article:
	* remove superfluous para tags around screen tags, this should remove the big white space in the HTML output
	* /var/db/port.mkversion doesn't exist anymore
	* mknod(8) was obsoleted in 5.X

Affected files ...

.. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/solid-state/article.sgml#7 edit

Differences ...

==== //depot/projects/docproj_nl/en_US.ISO8859-1/articles/solid-state/article.sgml#7 (text+ko) ====

@@ -285,11 +285,9 @@
 
 	<para>Exit the custom installation menu, and from the main
 	  installation menu choose the <literal>fixit</literal> option.  After
-	  entering the fixit environment, enter the following commands:</para>
+	  entering the fixit environment, enter the following command:</para>
 
-	<para><screen>&prompt.root; <userinput>mknod /dev/ad0a c 116 0</userinput>
-&prompt.root; <userinput>mknod /dev/ad0c c 116 2</userinput>		      
-&prompt.root; <userinput>disklabel -e /dev/ad0c</userinput></screen></para>
+	<screen>&prompt.root; <userinput>disklabel -e /dev/ad0c</userinput></screen>
 
 	<para>At this point you will have entered the vi editor under the
 	  auspices of the disklabel command.  Next, you need to add
@@ -305,8 +303,8 @@
 	  sure that fstype is <literal>4.2BSD</literal>.  Save the file and
 	  exit.</para>
 
-	<para><screen>&prompt.root; <userinput>disklabel -B -r /dev/ad0c</userinput>
-&prompt.root; <userinput>newfs /dev/ad0a</userinput></screen></para>
+	<screen>&prompt.root; <userinput>disklabel -B -r /dev/ad0c</userinput>
+&prompt.root; <userinput>newfs /dev/ad0a</userinput></screen>
       </step>
 
       <step>
@@ -314,7 +312,7 @@
 
 	<para>Mount the newly prepared flash media:</para>
 
-	<para><screen>&prompt.root; <userinput>mount /dev/ad0a /flash</userinput></screen></para>
+	<screen>&prompt.root; <userinput>mount /dev/ad0a /flash</userinput></screen>
 	
 	<para>Bring this machine up on the network so we may transfer our tar
 	  file and explode it onto our flash media filesystem.  One example of
@@ -429,9 +427,8 @@
 	lifespan.</para>
 
       <para>To make it possible to enter a ports directory and successfully
-	run <command>make install</command>, it is necessary for the file
-	<filename>/var/db/port.mkversion</filename> to exist, and that it has
-	a correct date in it.  Further, we must create a packages directory on
+	run <command>make install</command>,
+	we must create a packages directory on
 	a non-memory filesystem that will keep track of our packages across
 	reboots. Because it is necessary to mount your filesystems as
 	read-write for the installation of a package anyway, it is sensible to
@@ -450,21 +447,9 @@
 
       <screen>&prompt.root; <userinput>ln -s /etc/pkg /var/db/pkg</userinput></screen>
       
-      <para>Add another line in <filename>/etc/rc.diskless2</filename> that
-	creates and populates
-	<filename>/var/db/port.mkversion</filename></para>
-
-      <screen>&prompt.root; <userinput>touch /var/db/port.mkversion</userinput>
-&prompt.root; <userinput>chmod 0644 /var/db/port.mkversion</userinput>
-&prompt.root; <userinput>echo <replaceable>20010412</replaceable> >> /var/db/port.mkversion</userinput></screen>
-
-      <para>where <replaceable>20010412</replaceable> is a date that is
-	appropriate for your particular release of FreeBSD</para>
-
       <para>Now, any time that you mount your filesystems as read-write and
-	install a package, the <command>make install</command> will work
-	because it finds a suitable
-	<filename>/var/db/port.mkversion</filename>, and package information
+	install a package, the <command>make install</command> will work,
+	and package information
 	will be written successfully to <filename>/etc/pkg</filename> (because
 	the filesystem will, at that time, be mounted read-write) which will
 	always be available to the operating system as