ppcrcd/trunk/doc/README.net

[sparky]

Author: sparky
Date: Wed Aug  9 21:58:33 2006
New Revision: 7642

Modified:
   ppcrcd/trunk/doc/README.net
Log:
- partially rewritten


Modified: ppcrcd/trunk/doc/README.net
==============================================================================
--- ppcrcd/trunk/doc/README.net	(original)
+++ ppcrcd/trunk/doc/README.net	Wed Aug  9 21:58:33 2006
@@ -1,15 +1,15 @@
 === Networking in PPCRCD ===
 
 -------------------------------------------------------------------------------
-== Big WARNING as a first thing ==
+== WARNING as a first thing ==
     By default sshd server is started, to have easy access if console isn't
-working. But you should disable it, with option </<nosshd>/> if you are in
+working. You should disable it, with option </<nosshd>/> if you are in
 unsecure network. Or change root password, after booting it is '<*<ppcrcd>*>'.
 -------------------------------------------------------------------------------
 
 == Bringing up network on boot ==
-    Ultimately <_<udev>_> has complicated things a little, as it detects
-network cards dinamically, but order of interfaces may vary between one and
+    Recently <_<udev>_> has complicated things a little, as it detects
+network cards dinamically, but order of interfaces may change between one and
 annother boot. That's why I support two ways to configure network:
 
 = Old way, disabling udev automation =
@@ -19,13 +19,15 @@
 = New way, dynamic interfaces asignment by udev =
     If you specify </<eth=>/> option in kernel cmdline or nvram udev when finds
 some interface, checks its driver <*<ethtool -i $IF>*> and uses your
-configuration for it, but this way you can configure only very simple
+configuration for it. Using this way you can configure only very simple
 connections.
-    For more complicated interface configuration it was normal to save
-<_</etc/sysconfig/interfaces/ifcfg-eth0>_> in configuration. But it depends on
-interface, and we normally can't be sure it will be detected same way next
-time. The only time you can be sure is when you have only one network card,
-but remember, FireWire is detected as network too. To bypass it save your
-configuration to <_</etc/sysconfig/interfaces/</<<module>>/>.ifcfg>_>, without
-specyfying DEVICE. It will be moved by udev script to apropiate ifcfg-</<$IF>/>
-file, and apropiate DEVICE=</<$IF>/> option will be added.
+    For more complicated interface configuration one used to save
+<_</etc/sysconfig/interfaces/ifcfg-eth0>_> in configuration file. But it
+depends on interface, and we normally can't be sure if it will be detected
+same way next time. The only situation you can be sure about it is when
+you have only one network card. But remember, FireWire is detected as
+network too.
+    To solve this problem save your configuration to
+<_</etc/sysconfig/interfaces/</<<module>>/>.ifcfg>_>, without specyfying
+DEVICE in file. It will be moved by udev script to correct ifcfg-</<$IF>/>
+file, and appropiate DEVICE=</<$IF>/> option will be added.