summaryrefslogtreecommitdiff
path: root/doc/kernel.texi
diff options
context:
space:
mode:
authorpaul <paul>2003-08-12 12:40:20 +0000
committerpaul <paul>2003-08-12 12:40:20 +0000
commit7190f4ea215c294abc269b6dfa12f5f114bd2ed6 (patch)
tree288cc608f1ee0e4f959ed3d684eb6edc5e1a0fb7 /doc/kernel.texi
parentbb8ff1e7fe7d25a03b9f81bfd23f10347423e860 (diff)
2003-08-12 Paul Jakma <paul@dishone.st>
* doc/: GNU Zebra -> Quagga, in most places. Update Url and list URL to quagga.net. zebra.texi -> quagga.texi.
Diffstat (limited to 'doc/kernel.texi')
-rw-r--r--doc/kernel.texi6
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/kernel.texi b/doc/kernel.texi
index b863a1f6..5aac110f 100644
--- a/doc/kernel.texi
+++ b/doc/kernel.texi
@@ -32,7 +32,7 @@ information.
@item netlink
On recent Linux kernels (2.0.x and 2.2.x), there is a kernel/user
communication support called @code{netlink}. It makes asynchronous
-communication between kernel and Zebra possible, similar to a routing
+communication between kernel and Quagga possible, similar to a routing
socket on BSD systems.
Before you use this feature, be sure to select (in kernel configuration)
@@ -42,7 +42,7 @@ the kernel/netlink support option 'Kernel/User network link driver' and
Today, the /dev/route special device file is obsolete. Netlink
communication is done by reading/writing over netlink socket.
-After the kernel configuration, please reconfigure and rebuild Zebra.
-You can use netlink as a dynamic routing update channel between Zebra
+After the kernel configuration, please reconfigure and rebuild Quagga.
+You can use netlink as a dynamic routing update channel between Quagga
and the kernel.
@end table