Re: Permission for 'dev/pmu'
- To: Sven Luther <email@example.com>
- Cc: Martin-Éric Racine <firstname.lastname@example.org>, Christoph Hellwig <email@example.com>, Brad Boyer <firstname.lastname@example.org>, Matt Weber <email@example.com>, firstname.lastname@example.org, email@example.com
- Subject: Re: Permission for 'dev/pmu'
- From: firstname.lastname@example.org (Sjoerd Simons)
- Date: Mon, 10 Jan 2005 09:57:46 +0100
- Message-id: <20050110085746.GA3754@spring.luon.net>
- Mail-followup-to: Sven Luther <email@example.com>, Martin-Éric Racine <firstname.lastname@example.org>, Christoph Hellwig <email@example.com>, Brad Boyer <firstname.lastname@example.org>, Matt Weber <email@example.com>, firstname.lastname@example.org, email@example.com
- In-reply-to: <20050110082108.GA12948@pegasos>
- References: <20050109195459.GA26529@lst.de> <Pine.LNX.firstname.lastname@example.org> <20050110080333.GA15732@spring.luon.net> <20050110082108.GA12948@pegasos>
On Mon, Jan 10, 2005 at 09:21:08AM +0100, Sven Luther wrote:
> On Mon, Jan 10, 2005 at 09:03:33AM +0100, Sjoerd Simons wrote:
> > On Mon, Jan 10, 2005 at 03:17:22AM +0200, Martin-Éric Racine wrote:
> > > On Sun, 9 Jan 2005, Christoph Hellwig wrote:
> > >
> > > > On Sun, Jan 09, 2005 at 08:48:39PM +0100, Sven Luther wrote:
> > > > just kill this warning. Debian works just fine without backlight
> > > > control on both my ibook and the g5. And it's really not worth giving
> > > > hardware control to an unadited GUI program.
> > >
> > > Having been trying various ways to fix this for a number of days, I'm
> > > slowly coming to the conclusion that the best option for Debian would be
> > > to purge all of ACME's Powerbook-specific LCD control code out of the
> > > way.
> > >
> > > If upstream ever gets around cleaning up this code to use safer, more
> > > generic methods, such as doing everything via 'pmud' then we could
> > > reintroduce it.
> > >
> > > Any objection?
> > Just change the code to a g_warning instead of a dialog and stop whining? I
> > personally use this code and so do many others, so removing it isn't an
> > option..
> Ah, you use it and you didn't come to fixing it ? This has been a problema
> since >6 month.
> I would be very interested in knowing how you did solve the error message
> issue in a secure and acceptable for inclusion in the release way.
The error message won't appear if your user has access to the pmu, which is the
case on my system. But that's ofcourse wrong to do by default.
As said just change the current pmu patch in the package to do g_warning
instead of acme_error, which is trivial. No need to making a lot of fuss about
it on several mailinglists, there is a reason we have a bug tracking system.
Fundamentally, there may be no basis for anything.