2008/11/9 Michael Hrabanek [EMAIL PROTECTED]
I have been thinking recently about the restricted driver policy. It's
nice to get hardware directly not supported by kernel to work at least
by using non-free drivers, but on the other side this could be
two-edged and lead to ignorance from hw
On Thu, 2008-11-20 at 13:29 +, Chris Coulson wrote:
Michael,
What you seem to be suggesting is nothing short of harrassment.
Although free drivers are nice, some manufacturers will probably never
provide free drivers (Nvidia, for example). That is their own choice,
Maybe a better
tacone [2008-11-19 13:56 +0100]:
What I've been told is the gedit implementation was *not hard to do*.
That sounds overly optimistic to me. In order to teach gedit to edit
system files as normal user, you need a PolicyKit protected backend
which runs as root (probably D-BUS activated).
This
Am 20.11.2008 um 14:29 schrieb Michael Hrabanek:
When our voices will be loud enough we can make change and get rid of
proprietary drivers.
BTW, are those proprietary drivers stored for distribution on a
Ubuntu server or are they downloaded from the original source each
time? The later
Am 20.11.2008 um 16:29 schrieb Martin Pitt:
There goes the remaining bit of user/admin separation which we have,
and we can just as well have anyone work as root in the first place.
Well, if you edit a system file as a normal user, you'd have to
provide the password, don't you? That's like
