The Tuesday 2003-12-30 at 17:04 -0600, Chuck Stuettgen wrote:
Having recently converted from Mandrake to SuSe 9.0 Pro. I found it annoying that my regular user account could not shutdown or restart the computer. Having to log off and then shutdown from the display manager was getting very tiresome and opening a console to SU so I could shutdown was almost as bad.
~/.alias: alias shutdown="sudo /sbin/shutdown..." /etc/sudoers: cer nimrodel= (root) /sbin/shutdown Then you can shutdown as user - it will only ask for your password. Or you can log off X, then type ctrl-alt-F1, then ctrl-alt-del.
Then I set SUID to the link.
chmod u+s /sbin/shutdown
And that will surely be cleared by suseconfig. Enter that change to /etc/permissions.local.
BTW I am really beginning to become annoyed with SuSeconfig. Every time I run YAST2 or YOU it changes the startup order of the services in /etc/rc.d/rc5.d back to the SuSe defaults. Completely, ignoring what *I* need.
No, it is you that ignored the SuSE boot concept: read "man init.d", and or the SuSE admin book (paper or pdf). You can not directly edit the runlevels symlinks.
SuSe is not alone in ignoring laptop users. None of the distributions I have used have a package group and default configuration designed specifically for laptops. According to industry experts
I also would like a power saving module in yast, that configures the system to minimize power, letting the HD go to sleep (changing all those configurations that need to be modified to avoid accessing the HD every few seconds, for example. -- Cheers, Carlos Robinson