From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Permissions of files in /sys/
Date: Wed, 07 Jan 2009 11:43:54 -0600 [thread overview]
Message-ID: <4964E9DA.4050408@gmail.com> (raw)
In-Reply-To: <20090107142956.GB5477@revolver>
Momesso Andrea wrote:
> I'd like to make the file /sys/class/backlight/asus-laptop/brightness
> writeable for users, so that I don't need to be root anymore to change
> the brightness.
>
> Of course I can chown or chmod ot in local.start but I'm asking if there
> is a cleaner way.
>
> Also, are there any security risks on changing permissions on /sys
> files?
>
>
> TopperH
>
> ===========================
> Momesso Andrea
> http://topperh.blogspot.com
> ===========================
>
I have never did this but since /sys is populated during bootup,
anything you change by hand will not survive a reboot. I would think
you would have to find out what creates the file and then get it to
create it with the permissions you want. I'm not sure but could udev be
doing this?
I'm not sure about the security concerns but I do see why having a user
being able to adjust the brightness would be a good idea. I wonder why
it is set up the way it is?
Dale
:-) :-)
next prev parent reply other threads:[~2009-01-07 17:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-07 14:29 [gentoo-user] Permissions of files in /sys/ Momesso Andrea
2009-01-07 17:43 ` Dale [this message]
2009-01-07 17:49 ` Alan McKinnon
2009-01-07 20:36 ` Dale
2009-01-07 20:47 ` Paul Hartman
2009-01-09 16:28 ` Andrea Momesso
2009-01-12 18:13 ` Momesso Andrea
2009-01-12 23:54 ` Neil Bothwick
2009-01-13 6:19 ` Andrea Momesso
2009-01-13 8:17 ` Francisco Ares
2009-01-13 11:09 ` Momesso Andrea
2009-01-13 10:53 ` Volker Armin Hemmann
2009-01-13 10:59 ` Neil Bothwick
2009-01-13 11:11 ` Volker Armin Hemmann
2009-01-13 11:56 ` Neil Bothwick
2009-01-13 11:05 ` Momesso Andrea
2009-01-17 14:30 ` pk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4964E9DA.4050408@gmail.com \
--to=rdalek1967@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox