On Tue, Jan 08, 2002 at 10:13:25AM -0800, Craig Dickson wrote:
| If the config script can't tell the difference between a version 3
| config file and one for version 4, it's pretty dumb. The filenames
| aren't even the same.
If you are using X4 and have only XF86Config (not XF86Config-4) then
it
Bill Wohler wrote:
> Dave Sherohman <[EMAIL PROTECTED]> writes:
> > On Mon, Jan 07, 2002 at 07:58:09PM -0600, Dimitri Maziuk wrote:
> > > The bug affects only a tiny minority of users: I've seen three
> > > reports on d-u counting mine so far.
> >
> > Make me number 4, unless you've already coun
Dave Sherohman <[EMAIL PROTECTED]> writes:
> On Mon, Jan 07, 2002 at 07:58:09PM -0600, Dimitri Maziuk wrote:
> > The bug affects only a tiny minority of users: I've seen three
> > reports on d-u counting mine so far.
>
> Make me number 4, unless you've already counted my comments from two
> mont
* Dave Sherohman ([EMAIL PROTECTED]) spake thusly:
[ dexconf ]
> And I still say that this isn't needed.
How can you say that? What about all those poor newbies who don't
know how to read TFM and edit their XF86Config-4? Surely it's better
to have a luser-friendly dancing paperclip create XF86Con
On Mon, Jan 07, 2002 at 07:58:09PM -0600, Dimitri Maziuk wrote:
> The bug affects only a tiny minority of users: I've seen three
> reports on d-u counting mine so far.
Make me number 4, unless you've already counted my comments from two
months ago.
And I still say that this isn't needed. If an
Dimitri Maziuk <[EMAIL PROTECTED]> writes:
> * Brian Nelson ([EMAIL PROTECTED]) spake thusly:
> > Peter Jay Salzman <[EMAIL PROTECTED]> writes:
> ...
> > > "recovering" was no big deal. like you pointed out, it saved a copy of
> > > the old file. but that's like congratulating someone for takin
Dimitri Maziuk writes:
> The bug affects only a tiny minority of users: I've seen three reports on
> d-u counting mine so far.
You don't know that. For the reasons you cite, most users affected by the
problem will just conclude that they don't know how to configure X (or
perhaps decide it can't b
* Brian Nelson ([EMAIL PROTECTED]) spake thusly:
> Peter Jay Salzman <[EMAIL PROTECTED]> writes:
...
> > "recovering" was no big deal. like you pointed out, it saved a copy of
> > the old file. but that's like congratulating someone for taking a shit
> > in toilet. you'd *expect* it to go into
Peter Jay Salzman <[EMAIL PROTECTED]> writes:
> begin Shaya Potter <[EMAIL PROTECTED]>
> > what were you doing during the upgrade of the package?
> >
> > It clearly asked me if I wanted debconf to configure it.
> >
> > It even keeps a backup of the original, if you were doing it by hand and
> >
begin Shaya Potter <[EMAIL PROTECTED]>
> On Sun, 2002-01-06 at 19:36, Peter Jay Salzman wrote:
> > begin Justin R. Miller <[EMAIL PROTECTED]>
> > > Thus spake Peter Jay Salzman ([EMAIL PROTECTED]):
> > >
> > > > ok, my XF86Config-4 is all wrong now. i need to edit this file. if
> > > > we're n
On Sun, 2002-01-06 at 19:36, Peter Jay Salzman wrote:
> begin Justin R. Miller <[EMAIL PROTECTED]>
> > Thus spake Peter Jay Salzman ([EMAIL PROTECTED]):
> >
> > > ok, my XF86Config-4 is all wrong now. i need to edit this file. if
> > > we're not supposed to edit between the "BEGIN DEBCONF" and
* Noah Meyerhans ([EMAIL PROTECTED]) spake thusly:
> On Sun, Jan 06, 2002 at 07:19:35PM -0500, Justin R. Miller wrote:
> >
> > I believe also that if you run 'dpkg-reconfigure xserver-xfree86' you
> > can choose the first option to not manage the file with debconf.
> > However, I have not tried th
Carl Fink writes:
> If the conf file just said "Run to unmanage this file.
> Run to reconfigure using debconf," then this entire
> thread could have been avoided.
Or better, if it said "De[b|x]conf will merge changes made here".
--
John Hasler
[EMAIL PROTECTED]
Dancing Horse Hill
Elmwood, Wisco
On Mon, Jan 07, 2002 at 01:00:57AM -0500, Noah Meyerhans wrote:
> Exactly. Those who are screaming about bugs in dexconf and chattr +i
> and all that garbage need to learn how the tools actually work before
> trashing them.
Basic principle of interface design: if a complaint occurs because the
On Sun, Jan 06, 2002 at 07:19:35PM -0500, Justin R. Miller wrote:
>
> I believe also that if you run 'dpkg-reconfigure xserver-xfree86' you
> can choose the first option to not manage the file with debconf.
> However, I have not tried this.
>
Exactly. Those who are screaming about bugs in dex
On Sun, 6 Jan 2002 19:19:35 -0500, "Justin R. Miller" <[EMAIL PROTECTED]> wrote:
> Thus spake John Hasler ([EMAIL PROTECTED]):
>
> > Many: my favorites are emacs and vi. Just edit the damn file and
> > ignore the Yast^H^H^H^H Debconf stuff. If an upgrade destroys your
> > changes file a bug.
>
begin Justin R. Miller <[EMAIL PROTECTED]>
> Thus spake Peter Jay Salzman ([EMAIL PROTECTED]):
>
> > ok, my XF86Config-4 is all wrong now. i need to edit this file. if
> > we're not supposed to edit between the "BEGIN DEBCONF" and "END
> > DEBCONF", how the hell am i supposed to get a working X
Thus spake John Hasler ([EMAIL PROTECTED]):
> Many: my favorites are emacs and vi. Just edit the damn file and
> ignore the Yast^H^H^H^H Debconf stuff. If an upgrade destroys your
> changes file a bug.
I believe also that if you run 'dpkg-reconfigure xserver-xfree86' you
can choose the first op
On Sun, Jan 06, 2002 at 06:05:08PM -0500, Justin R. Miller wrote:
> Try 'dpkg-reconfigure xserver-xfree86'.
Maybe it's just me, but if that's required, isn't it a bug that it isn't
mentioned *in the configuration file itself*? If that was in the file, a
whole class of problems could be eliminat
Peter Jay Salzman writes:
> is there a tool that allows us to change this file?
Many: my favorites are emacs and vi. Just edit the damn file and ignore
the Yast^H^H^H^H Debconf stuff. If an upgrade destroys your changes file a
bug.
--
John Hasler
[EMAIL PROTECTED]
Dancing Horse Hill
Elmwood, Wi
* Peter Jay Salzman ([EMAIL PROTECTED]) spake thusly:
> after upgrading woody today, my XF86Config-4 file looks like:
>
>### BEGIN DEBCONF SECTION
>#
># If you want your changes to this file preserved by dexconf, only make
># changes before the "### BEGIN DEBCONF SECTION" line abov
Thus spake Peter Jay Salzman ([EMAIL PROTECTED]):
> ok, my XF86Config-4 is all wrong now. i need to edit this file. if
> we're not supposed to edit between the "BEGIN DEBCONF" and "END
> DEBCONF", how the hell am i supposed to get a working XFree86 again?
>
> is there a tool that allows us to c
22 matches
Mail list logo
