Yes, the problem of course is that if one makes a change to the pppd
options file and then months later upgrades pppd that one is unlikely
to remember the earlier change and instead is mystified at why "the
new pppd" does not work. I admit that where the package management
system saves the old file then at least the user has a chance to
determine the problem.
I suppose that my position though is strongly influenced by the position
taken by the pppd maintainers. Because the package maintainers assert
that the default "auth" should not be changed to "noauth" IN the config
file that they supply then such a change should not be made.
Carrying this another step... The package system programmers have every
right NOT to try to parse the old file for "unauthorized" user changes.
As packaging systems such as RPM, dselect, and apt continue to evolve
the sophistication of handling package upgrades increases greatly. Many
package upgrades now incorporate user configuration items from existing
configuration files even when the new files have a completely different
syntax, structure, or even different relationships to other files.
I am enough of an anarchist that I believe that I should be able to do
whatever I want to my own system(s). OTOH, I should accept the
consequences (intended or otherwise) of my actions.
In my opinion, recommending that another do something that is likely to
"set them up" for future failure _when_ there is another solution should
be avoided.
This is NOT written to chastise, "slam", or "flame" anyone. I recognize
that making the change to the pppd option file WILL work and as long as
the change is sustained and the system is not used for dial-in there
should be no problems.
On Sun, Oct 10, 1999 at 12:38:31PM -0400, Gyepi SAM wrote:
> On Sun, Oct 10, 1999 at 11:11:00AM -0400, Bill Leach wrote:
> > I have not run a Red Hat system for well over a year now but I suspect that
> > this consideration applies to RPM as well as Debian's dselect/apt package
> > system... If you make changes to ppp/options these changes will be lost
> > whenever you do an upgrade because you are not supposed to alter the
> > ppp/options files.
>
> This is not quite true. rpm will rename the ppp/options file to ppp/options.rpmsave
> before installing the new file. This only works, of course, if the package
> builder specified that ppp/options is a configuration file.
>
> So the file is not lost but one has to either replace the new options file
> with the old one or merge the two.
>
> rpm also supports a command option to list the package configuration files
> but AFAIK does not have an option to keep existing configuration files.
>
> --
> Gyepi Sam --+-- Designer/Programmer --+-- Network/System Administrator
> [EMAIL PROTECTED] --+-- http://www.praxis-sw.com/gyepi
>
> The only perfect science is hind-sight.
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-diald" in
> the body of a message to [EMAIL PROTECTED]
>
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
