System group to access LED subsystem
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
Is there a group to which a user can be added, that gives permission to write to the LED subsystem of Linux (/sys/class/leds/)?
If not, is it possible to create such a group?
I do not want to run my application as sudo.
Edit:
I only want to change permission of a few devices for which I really needed the write permission and not for the whole leds subsystem. I have posted a solution that works for me.
linux filesystems
add a comment |
Is there a group to which a user can be added, that gives permission to write to the LED subsystem of Linux (/sys/class/leds/)?
If not, is it possible to create such a group?
I do not want to run my application as sudo.
Edit:
I only want to change permission of a few devices for which I really needed the write permission and not for the whole leds subsystem. I have posted a solution that works for me.
linux filesystems
fabiobaltieri.com/2011/09/21/linux-led-subsystem
– fixer1234
Jan 28 at 22:24
Thank you, but that is what I am doing. But on my distribution, access to these files is limited to root.
– p0kR
Jan 29 at 23:05
I have a new idea how to solve my problem and will post the answer when it works like I hope.
– p0kR
Jan 29 at 23:10
add a comment |
Is there a group to which a user can be added, that gives permission to write to the LED subsystem of Linux (/sys/class/leds/)?
If not, is it possible to create such a group?
I do not want to run my application as sudo.
Edit:
I only want to change permission of a few devices for which I really needed the write permission and not for the whole leds subsystem. I have posted a solution that works for me.
linux filesystems
Is there a group to which a user can be added, that gives permission to write to the LED subsystem of Linux (/sys/class/leds/)?
If not, is it possible to create such a group?
I do not want to run my application as sudo.
Edit:
I only want to change permission of a few devices for which I really needed the write permission and not for the whole leds subsystem. I have posted a solution that works for me.
linux filesystems
linux filesystems
edited Feb 4 at 22:05
p0kR
asked Jan 28 at 22:05
p0kRp0kR
115
115
fabiobaltieri.com/2011/09/21/linux-led-subsystem
– fixer1234
Jan 28 at 22:24
Thank you, but that is what I am doing. But on my distribution, access to these files is limited to root.
– p0kR
Jan 29 at 23:05
I have a new idea how to solve my problem and will post the answer when it works like I hope.
– p0kR
Jan 29 at 23:10
add a comment |
fabiobaltieri.com/2011/09/21/linux-led-subsystem
– fixer1234
Jan 28 at 22:24
Thank you, but that is what I am doing. But on my distribution, access to these files is limited to root.
– p0kR
Jan 29 at 23:05
I have a new idea how to solve my problem and will post the answer when it works like I hope.
– p0kR
Jan 29 at 23:10
fabiobaltieri.com/2011/09/21/linux-led-subsystem
– fixer1234
Jan 28 at 22:24
fabiobaltieri.com/2011/09/21/linux-led-subsystem
– fixer1234
Jan 28 at 22:24
Thank you, but that is what I am doing. But on my distribution, access to these files is limited to root.
– p0kR
Jan 29 at 23:05
Thank you, but that is what I am doing. But on my distribution, access to these files is limited to root.
– p0kR
Jan 29 at 23:05
I have a new idea how to solve my problem and will post the answer when it works like I hope.
– p0kR
Jan 29 at 23:10
I have a new idea how to solve my problem and will post the answer when it works like I hope.
– p0kR
Jan 29 at 23:10
add a comment |
1 Answer
1
active
oldest
votes
I found a solution fitting my problem.
I added a udev rule like it is described in this answer to a similar question.
First I had to create a new group called leds. Then I created the udev rule in /etc/udev/rules.d/10-buzzers.rules (I created the file by myself, it did not exist before).
Since I wanted to only use the Buzzer LEDs of the Buzzer controllers for the Playstation 2, I optimized the rule to only affect the files for the controllers.
The rule only applies to devices that match the kernel information in the field KERNEL.
The rule executes chgrp and chmod that the matching device files are owned by the leds group and that the owning group has write permission.
My final rule:
SUBSYSTEM=="leds", KERNEL=="0003:054C:1000.[0-9]*::buzz[1-4]", ACTION=="add", RUN+="/bin/chgrp -R leds /sys%p", RUN+="/bin/chmod -R g=u /sys%p"
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1399431%2fsystem-group-to-access-led-subsystem%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I found a solution fitting my problem.
I added a udev rule like it is described in this answer to a similar question.
First I had to create a new group called leds. Then I created the udev rule in /etc/udev/rules.d/10-buzzers.rules (I created the file by myself, it did not exist before).
Since I wanted to only use the Buzzer LEDs of the Buzzer controllers for the Playstation 2, I optimized the rule to only affect the files for the controllers.
The rule only applies to devices that match the kernel information in the field KERNEL.
The rule executes chgrp and chmod that the matching device files are owned by the leds group and that the owning group has write permission.
My final rule:
SUBSYSTEM=="leds", KERNEL=="0003:054C:1000.[0-9]*::buzz[1-4]", ACTION=="add", RUN+="/bin/chgrp -R leds /sys%p", RUN+="/bin/chmod -R g=u /sys%p"
add a comment |
I found a solution fitting my problem.
I added a udev rule like it is described in this answer to a similar question.
First I had to create a new group called leds. Then I created the udev rule in /etc/udev/rules.d/10-buzzers.rules (I created the file by myself, it did not exist before).
Since I wanted to only use the Buzzer LEDs of the Buzzer controllers for the Playstation 2, I optimized the rule to only affect the files for the controllers.
The rule only applies to devices that match the kernel information in the field KERNEL.
The rule executes chgrp and chmod that the matching device files are owned by the leds group and that the owning group has write permission.
My final rule:
SUBSYSTEM=="leds", KERNEL=="0003:054C:1000.[0-9]*::buzz[1-4]", ACTION=="add", RUN+="/bin/chgrp -R leds /sys%p", RUN+="/bin/chmod -R g=u /sys%p"
add a comment |
I found a solution fitting my problem.
I added a udev rule like it is described in this answer to a similar question.
First I had to create a new group called leds. Then I created the udev rule in /etc/udev/rules.d/10-buzzers.rules (I created the file by myself, it did not exist before).
Since I wanted to only use the Buzzer LEDs of the Buzzer controllers for the Playstation 2, I optimized the rule to only affect the files for the controllers.
The rule only applies to devices that match the kernel information in the field KERNEL.
The rule executes chgrp and chmod that the matching device files are owned by the leds group and that the owning group has write permission.
My final rule:
SUBSYSTEM=="leds", KERNEL=="0003:054C:1000.[0-9]*::buzz[1-4]", ACTION=="add", RUN+="/bin/chgrp -R leds /sys%p", RUN+="/bin/chmod -R g=u /sys%p"
I found a solution fitting my problem.
I added a udev rule like it is described in this answer to a similar question.
First I had to create a new group called leds. Then I created the udev rule in /etc/udev/rules.d/10-buzzers.rules (I created the file by myself, it did not exist before).
Since I wanted to only use the Buzzer LEDs of the Buzzer controllers for the Playstation 2, I optimized the rule to only affect the files for the controllers.
The rule only applies to devices that match the kernel information in the field KERNEL.
The rule executes chgrp and chmod that the matching device files are owned by the leds group and that the owning group has write permission.
My final rule:
SUBSYSTEM=="leds", KERNEL=="0003:054C:1000.[0-9]*::buzz[1-4]", ACTION=="add", RUN+="/bin/chgrp -R leds /sys%p", RUN+="/bin/chmod -R g=u /sys%p"
answered Feb 4 at 22:03
p0kRp0kR
115
115
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1399431%2fsystem-group-to-access-led-subsystem%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
fabiobaltieri.com/2011/09/21/linux-led-subsystem
– fixer1234
Jan 28 at 22:24
Thank you, but that is what I am doing. But on my distribution, access to these files is limited to root.
– p0kR
Jan 29 at 23:05
I have a new idea how to solve my problem and will post the answer when it works like I hope.
– p0kR
Jan 29 at 23:10