[dahdi-commits] tzafrir: tools/trunk r4544 - /tools/trunk/doc/system.conf

[SVN commits to the DAHDI project]

Author: tzafrir
Date: Sun Jul  6 05:43:18 2008
New Revision: 4544

URL: http://svn.digium.com/view/dahdi?view=rev&rev=4544
Log:
The Zaptel->DAHDI sed. And one typo fixed.

Modified:
    tools/trunk/doc/system.conf

Modified: tools/trunk/doc/system.conf
URL: http://svn.digium.com/view/dahdi/tools/trunk/doc/system.conf?view=diff&rev=4544&r1=4543&r2=4544
==============================================================================
--- tools/trunk/doc/system.conf (original)
+++ tools/trunk/doc/system.conf Sun Jul  6 05:43:18 2008
@@ -1,7 +1,7 @@
 #
-# Zaptel Configuration File
-#
-# This file is parsed by the Zaptel Configurator, ztcfg
+# DAHDI Configuration File
+#
+# This file is parsed by the DAHDI Configurator, dahdi_cfg
 #
 # Span Configuration
 # ~~~~~~~~~~~~~~~~~~
@@ -66,7 +66,7 @@
 # driver specific address (like a MAC for eth), <numchans> is the number
 # of channels, and <timing> is a timing priority, like for a normal span.
 # use "0" to not use this as a timing source, or prioritize them as
-# primary, secondard, etc.  Note that you MUST have a REAL zaptel device
+# primary, secondard, etc.  Note that you MUST have a REAL DAHDI device
 # if you are not using external timing.
 #
 #   dynamic=eth,eth0/00:02:b3:35:43:9c,24,0
@@ -118,11 +118,11 @@
 #   Like 'clear' except all channels are treated individually and
 #   are not bundled.  'inclear' is an alias for this.
 # rawhdlc::
-#   The zaptel driver performs HDLC encoding and decoding on the 
+#   The DAHDI driver performs HDLC encoding and decoding on the 
 #   bundle, and the resulting data is communicated via the master
 #   device.
 # dchan::
-#   The zapdel driver performs HDLC encoding and decoding on the
+#   The DAHDI driver performs HDLC encoding and decoding on the
 #   bundle and also performs incoming and outgoing FCS insertion
 #   and verification.  'fcshdlc' is an alias for this.
 # hardhdlc::
@@ -131,7 +131,7 @@
 #   and verification.  Is subject to limitations and support of underlying
 #   hardware.
 # nethdlc::
-#   The zaptel driver bundles the channels together into an
+#   The DAHDI driver bundles the channels together into an
 #   hdlc network device, which in turn can be configured with
 #   sethdlc (available separately). In 2.6.x kernels you can also optionally
 #   pass the name for the network interface after the channel list.
@@ -142,10 +142,10 @@
 #   in system e.g eth.
 #
 # dacs::
-#   The zaptel driver cross connects the channels starting at
+#   The DAHDI driver cross connects the channels starting at
 #   the channel number listed at the end, after a colon
 # dacsrbs::
-#   The zaptel driver cross connects the channels starting at
+#   The DAHDI driver cross connects the channels starting at
 #   the channel number listed at the end, after a colon and 
 #   also performs the DACSing of RBS bits
 #
@@ -180,14 +180,14 @@
 # Tone Zone Data
 # ~~~~~~~~~~~~~~
 # Finally, you can preload some tone zones, to prevent them from getting
-# overwritten by other users (if you allow non-root users to open /dev/zap/*
+# overwritten by other users (if you allow non-root users to open /dev/dahdi/*
 # interfaces anyway.  Also this means they won't have to be loaded at runtime.
 # The format is "loadzone=<zone>" where the zone is a two letter country code.
 # 
 # You may also specify a default zone with "defaultzone=<zone>" where zone
 # is a two letter country code.
 #
-# An up-to-date list of the zones can be found in the file zaptel/zonedata.c
+# An up-to-date list of the zones can be found in the file zonedata.c
 #
 loadzone = us
 #loadzone = us-old
@@ -210,11 +210,11 @@
 # (see http://www.zapatatelephony.org/app_rpt.html)
 #
 # The PCI Radio Interface card interfaces up to 4 two-way radios (either
-# a base/mobile radio or repeater system) to Zaptel channels. The driver
+# a base/mobile radio or repeater system) to DAHDI channels. The driver
 # may work either independent of an application, or with it, through
 # the driver;s ioctl() interface. This file gives you access to specify
 # load-time parameters for Radio channels, so that the driver may run
-# by itself, and just act like a generic Zaptel radio interface.
+# by itself, and just act like a generic DAHDI radio interface.
 #
 # Unlike the rest of this file, you specify a block of parameters, and
 # then the channel(s) to which they apply. CTCSS is specified as a frequency