#Making /sys writable by users in wheel group? (without sudo)
1 messages · Page 1 of 1 (latest)
With sudo I would receive a password prompt, while without sudo it would guarantee it's runnable by other applications running as that user
how about chown root:wheel and chmod 775
IIRC, the permission of sysfs is defined in kernel space and can't be changed with userspace tools.
yeah, that's what I thought
but it should be possible if I run chown and chmod each boot?
nvm, operation not permitted
Perhaps it is now time to regard it as an ancient legend.
maybe you can google "how to chown /sys" and there will be more answers
Actually, I just found out that the kernel seems to support chmod() or chown() on these nodes.
huh? But i cant
We have similar laptops as my battery also has this interface.
We have similar laptops as my battery also has this interface.
sudo chown $USER:$USER conservation_mode
stat conservation_mode
sudo chmod 664 conservation_mode
Since /sys is not managed by udev, I think you can write a systemd service to change its permissions after boot.
there was no write permission on the second user after : (wheel in my case)
It is not a second user, but a group permission
These concepts are related, but they are not the same
is first "user" a specific user? or can it be a group too?
so, it may be a group too, but it's like the owner, right?
group owner
ðe permission bits are
rw- |rw- |r--
root|wheel|all other users
chown - change owner
chmod - change file mode bits, inc. permissions
chown group1:group2 file
rw- |rw- |r--
group1|group2|all other users
is that right?
Why don't you read the chmod man page and let it tell you?
As mentioned above, the format is user|group|other.