>
> Good points.
>
> There are, however, some very strong advantages to Linuxconf:
>
> 1) Newbie related: Most newbies are going with RedHat. Linuxconf is THE
> standard configuration tool in RedHat.
>
> 2) Linuxconf works in 3 modes, 1: GUI 2: Shell/text 3: Remote-Browser.
> However, none of them is dependant upon the other modes being available.
> I use Linuxconf for standard config through GUI, but have never yet used
> the Browser config. Heck, I don't even have an HTTP server installed!
> It's just "optionally" available.
>
> 3) Linuxconf remains seperate from the actual config files and simply
> reads them when it initialzes, thus you can still manually "hack" the
> .conf files if you want to.
>
This sounds like the right way to go.
> The goal of having diald "work or almost work" strait from installation
> is not that hard to do. 0.16 came with some preconfigured "generic/demo"
> conf files that required very little change to make work. Stay with that
> idea.
>
One potential complexity is that people usually start by getting ppp to
work by hand, then try to use diald. And the default ppp scripts aren't
compatible with diald. There may have to be some integration with however
linuxconf sets up pppd so it is an easy step from starting pppd by hand
to running diald.
Also, I'd suggest considering including support for more than one diald
process (i.e. multiple links). As more and more people work at home it
becomes more and more common for people to have ppp accounts several
places. I.E. an isp for mail, a work site, and perhaps a customer or
two. This is kind of complex to set up by hand.
-- cary
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
