"Paul Sargent" <[EMAIL PROTECTED]> writes:
> On Tue, Apr 23, 2002 at 05:45:08PM -0500, Shyamal Prasad wrote:
> > "Michael" == Michael D Crawford <[EMAIL PROTECTED]> writes:
> >
> > Michael> That's why, when you update the xserver-xfree86, you
> > Michael> shouldn't overwrite the settings the user has laboured to
> > Michael> create. They are precious.
> >
> > I'm assuming you made a common mistake. While I agree that it would be
> > nice to make this bullet proof, I also know that it's often nearly
> > impossible to protect us from ourselves ;-)
>
> I hit this the other night aswell, but I couldn't work out a way of making
> sure it didn't happen again.
>
> The XF86Config file says that "bits outside of ### DEBCONF START and END
> will not be touched" (I'm paraphrasing), so I moved the DEBCONF_START and
> DEBCONF_END so they were together at the end of the file, but really I want
> to set debconf to not mess with the file anymore. dpkg-reconfigure didn't
> give me the option, just asked me a load of x-setup question and rewrote the
> file again.
>
> I'm just glad backups are always made before debconf writes to files.
Just do:
dpkg-reconfigure --priority=low xserver-xfree86
and tell it not to let debconf manage the configuration. In other
words anser "No" to the first question. Subsequent upgrades shouldn't
touch the XF86Config-4 file.
This is on a Debian system running the "testing" distribution and may
be different for other distributions.
Gary
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
