update the docs.

ChangeLog

@@ -1,3 +1,11 @@
+2000-06-08  OKUJI Yoshinori  <okuji@gnu.org>
+
+	* docs/tutorial.texi (Network): The body is moved to ...
+	(General usage of network support): ... this new section.
+	(Diskless): New section.
+	* docs/user-ref.texi (General commands): Added a description
+	about the command "tftpserver".
+	
 2000-06-08  OKUJI Yoshinori  <okuji@gnu.org>
 
 	* netboot/main.c (decode_rfc1533) [GRUB]: Eliminate trailing

docs/tutorial.texi

@@ -560,6 +560,15 @@ support. To using the network support, you need to enable at least one
 network driver in the build process. For more information please see
 @file{netboot/README.netboot} in the source distribution.
 
+@menu
+* General usage of network support::
+* Diskless::
+@end menu
+
+
+@node General usage of network support
+@section How to set up your network
+
 First, you have to set up servers in your network. GRUB requires a
 server that will assign an IP address, and a file server. The former is
 either BOOTP, DHCP or a RARP server (RARP is deprecated, since it cannot
@@ -596,6 +605,52 @@ grub> boot
 @end example
 
 
+@node Diskless
+@section Booting from a network
+
+It is sometimes very useful to boot from a network, especially, when you
+use a machine which has no local disk. In this case, you need to obtain
+a kind of Net Boot @sc{rom}, such as a PXE @sc{rom} or a free software
+package like Etherboot. Such a Boot @sc{rom} first boots the machine,
+sets up the network card installed into the machine, and downloads a
+second stage boot image from the network. Then, the second image will
+try to boot an operating system from the network actually.
+
+GRUB provides two second stage images, @file{nbgrub} and
+@file{pxegrub}. Those images are the same as the normal Stage 2, except
+that they set up a network automatically, and try to load a
+configuration file from the network, if specified. The usage is very
+simple: If the machine has a PXE @sc{rom}, use @file{pxegrub}. If the
+machine has a NBI loader such as Etherboot, use @file{nbgrub}. There is
+no difference between them but their formats. As how to load a second
+stage image you want to use should be described in the manual on your
+Net Boot @sc{rom}, please refer to the manual, for more details. The
+topic is beyond the scope of this documentation.
+
+However, there is one thing specific to GRUB. Namely, how to specify a
+configuration file in a BOOTP/DHCP server. For now, GRUB uses the tag
+@samp{150}, to get the name of a configuration file. This below is an
+example about a BOOTP configuration:
+
+@example
+@group
+allhost:hd=/tmp:bf=null:\
+        :ds=145.71.35.1 145.71.32.1:\
+        :sm=255.255.254.0:\
+        :gw=145.71.35.1:\
+        :sa=145.71.35.5:
+
+foo:ht=1:ha=63655d0334a7:ip=145.71.35.127:\
+        :bf=/nbgrub:\
+        :tc=allhost:\
+        :T150="/tftpboot/menu.lst.foo":
+@end group
+@end example
+
+See the manual about your BOOTP/DHCP server, for more information. The
+exact syntax should differ from the example, more or less.
+
+
 @node Configuration
 @chapter Configuration
 

docs/user-ref.texi

@@ -752,6 +752,12 @@ character each of the symbols corresponds to:
 @end table
 @end deffn
 
+@deffn Command tftpserver ipaddr
+Override a TFTP server address returned by a BOOTP/DHCP/RARP server. The
+argument @var{ipaddr} must be in the standard format, like
+@samp{192.168.0.15}.
+@end deffn
+
 @deffn Command unhide partition
 Unhide @var{partition} by clearing the @dfn{hidden} bit in its partition
 type code. This is useful only for DOS or Windows when multiple primary

netboot/README.netboot

@@ -15,6 +15,13 @@ to specify them.
   Define this for PCI BIOSes that do not implement BIOS32 or not
   correctly.
 
+--enable-diskless
+  Enable the diskless support. If specified, you will get two optional
+  images, called "nbgrub" and "pxegrub". The former is the ``Net Boot
+  Image Proposal'' format, which is used by Etherboot and Netboot, while
+  the latter is the ``Preboot Execution Environment" format, which is
+  used by a PXE ROM. You may buy a PXE ROM from some companies.
+
 Here is the information about the device drivers. They are all disabled
 by default, so you must specify configure options to enable drivers you
 want to use. Some drivers have extra per-driver options, so the extra