---
docs/command-line.txt | 5 +++--
docs/kickstart-docs.txt | 12 ++++++------
2 files changed, 9 insertions(+), 8 deletions(-)
diff --git a/docs/command-line.txt b/docs/command-line.txt
index 941dafb..75c1dc1 100644
--- a/docs/command-line.txt
+++ b/docs/command-line.txt
@@ -1,4 +1,4 @@
-8-15-2005
+07-15-2010
---------
Boot time command args:
@@ -145,7 +145,8 @@ dns=<dns> Comma separated list of nameservers to use for a network
dhcptimeout=<sec> Set different dhcp timeout to workaround STP delays
with some Cisco switches
-method=nfs:<path> Use <path> for an NFS installation.
+method=nfs(:options):<path> Use <path> for an NFS installation. NFS mount
+ options are optional.
method=http://<path> Use <path> for an HTTP installation
diff --git a/docs/kickstart-docs.txt b/docs/kickstart-docs.txt
index de21f4b..5352ded 100644
--- a/docs/kickstart-docs.txt
+++ b/docs/kickstart-docs.txt
@@ -1680,13 +1680,13 @@ Making the Kickstart File Available on the Network
Other options to start a kickstart installation are as follows:
- ks=nfs:<server>:/<path>
+ ks=nfs(:options):<server>:/<path>
- The installation program will look for the kickstart file on the
- NFS server <server>, as file <path>. The installation program will
- use DHCP to configure the Ethernet card. For example, if your NFS
- server is server.example.com and the kickstart file is in the NFS
- share /mydir/ks.cfg, the correct boot command would be
+ The installation program will look for the kickstart file on the NFS
+ server <server>, as file <path>. The (:options) part is optional. The
+ installation program will use DHCP to configure the Ethernet card. For
+ example, if your NFS server is server.example.com and the kickstart file
+ is in the NFS share /mydir/ks.cfg, the correct boot command would be
ks=nfs:server.example.com:/mydir/ks.cfg.
ks=http://<server>/<path>
--
1.7.1.1
_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list
