swift       05/04/16 21:36:17

  Modified:    xml/htdocs/doc/en diskless-howto.xml
  Log:
  Need to create /dev/console, reported by anxt (forum user), confirmed by 
Adrian Owne, does not hurt by SwifT :)

Revision  Changes    Path
1.15      +13 -3     xml/htdocs/doc/en/diskless-howto.xml

file : 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/diskless-howto.xml?rev=1.15&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/diskless-howto.xml?rev=1.15&content-type=text/plain&cvsroot=gentoo
diff : 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/diskless-howto.xml.diff?r1=1.14&r2=1.15&cvsroot=gentoo

Index: diskless-howto.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/diskless-howto.xml,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -r1.14 -r1.15
--- diskless-howto.xml  9 Apr 2005 11:35:15 -0000       1.14
+++ diskless-howto.xml  16 Apr 2005 21:36:17 -0000      1.15
@@ -1,5 +1,5 @@
 <?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/diskless-howto.xml,v 1.14 
2005/04/09 11:35:15 swift Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/diskless-howto.xml,v 1.15 
2005/04/16 21:36:17 swift Exp $ -->
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
 
 <guide link="/doc/en/diskless-howto.xml">
@@ -25,8 +25,8 @@
 
 <license/>
 
-<version>1.10</version>
-<date>2005-04-09</date>
+<version>1.11</version>
+<date>2005-04-16</date>
 
 <chapter>
 <title>Introduction</title>
@@ -378,6 +378,16 @@
 this HOWTO right before you attempt to boot the slave.
 </p>
 
+<p>
+Even though <path>/dev</path> is populated by <c>udev</c> later on, you need to
+create the <path>console</path> entry. If not, you will receive the error
+"unable to open initial console".
+</p>
+
+<pre caption="Creating console entry in the /dev">
+# <i>mknod /diskless/182.168.1.21/dev/console c 5 1</i>
+</pre>
+
 </body>
 </section>
 </chapter>



-- 
[email protected] mailing list

Reply via email to