Agreed. It does give a lot more flexibility to local solutions. I
actually quoted your idea (with reference to you :) in an additional
comment to the bug report.
The problem is that RH has already started to overwrite the ppp.local
(unless they will revert that solution) and it's sort of too late for
us. Rpms are already using it.
I lost some work. Many other people risk to loose a lot. The odd thing
is that I don't even have any ISDN software in my system. Don't know why
they insisted in installing ISDN specific configuration in my box.
(I use an external ISDN TA, but to my system it has the look and feel of
a traditional modem.)
I sincerely hope they will consider your idea.
Regards
Gustav
Gordon Messmer wrote:
>
> Gustav Schaffter wrote:
> >
> > Makes sense, Gordon.
> >
> > > Or... they could get jiggy and create /etc/ppp/ip-up.d/ and run all of
> > > the scripts in there!! :)
>
> The more I think about it, the more I like the idea of
> /etc/ppp/ip-up.d/. I created ip-up.local scripts in my EQL rpm, too.
> They automatically add the eq device, and add ppp slaves to it.
>
> In any case, once rpms start using ip-up.local, there needs to be a
> mechanism for multiple scripts.
>
> MSG
>
> --
> To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
> as the Subject.
--
pgp = Pretty Good Privacy. To get my public pgp key, send an e-mail to:
[EMAIL PROTECTED]
Visit my web site at http://www.schaffter.com
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
