Design goals: A configuration interface which is flexible, but can be
configured without much knowledge of networking or diald's operation.
A configuration interface that integrates seamlessly with the existing
redhat network configuration set.  Something that can be extended to
support a GUI.  A configuration that makes the network "disappear" so
that the user never need worry about whether it's up or not.  A
configuration that supports the use of dctrl, the diald monitoring
program.

Diald is started after the network daemons so that starting the system
does not always cause the phone to dial.  It is stopped after the
network daemons are stopped so that they can finish their business on
the network before it goes down.

LCP_ECHO_FAILURE and LCP_ECHO_INTERVAL should really be part of the
ppp configuration, but, for now, they are part of the diald
configuration because the redhat ppp configuration doesn't use them.

The lcp comments above also apply to the NOIPDEFAULT option.

I would have rather had two flags, one each associated with REMIP and
IPADDR, which would indicate whether or not the associated ip number
_must_ be the number used or simply may be the number used, instead of
having LINK_DOWN_REMIP, and LINK_DOWN_IPADDR.  There are two problems
with the flags though.  The first is that the current redhat ppp setup
would have to be modified to set the flags.  The second, and more
important, is that REMIP and IPADDR would _have_ to be specified, and
this is inconsistent with the current redhat ppp setup.  So, the
upgrade would be required and the user would have to make some changes
to his ppp configuration.  I'm really not up for changing the redhat
ppp network control panel.

The fifos in /etc/diald/ should probably go in /var so that /etc can
be mounted read-only, but I've not a good idea where to put them so in
/etc they sit.  The names and locations are configurable, however.

It's not at all clear that establishment of routing cannot be improved
upon.

diald-connect requires the formatting of logged messages contain the
pid in square braces "[]".  This means that if the formst of the
system log messages is changed, diald-connect may break.

I'm none too clear on exactly which shell features are posix.  Some of
the shell scripting in this package may be bash dependent.

I decided to separate those low level configuration files that contain
straight-up diald configuration directives from those files that are
processed by m4 to generate diald configuration directives.  This was
done both for reasons of symmerty, /etc/diald.conf will always be
processed by diald and not by m4 and yet we want a m4 file that
generates global directives, and because this way people who are know
diald but are nervous about m4 can rest easy.
