How I got XFCE to allow users to shutdown or reboot Slackware 10.2
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
How I got XFCE to allow users to shutdown or reboot Slackware 10.2
Hi all,
Just putting this here becuase it took me 4 hours to figure this out
As allways back up first.
1. open terminal as root.
2. type "visudo" and hit enter.
3. use your arrow keys to navigate down to #samples section.
4. use "X" key to get rid of # sign by %users...then when done hit escape key.
5. then go to next line (that is the next line down without anything in it under the users) and hit "i" key to insert the following line:
%users pooter-name=NOPASSWD: /usr/libexec/xfsm-shutdown-helper
6. now hit escape key
7: now type ":"
8. now type w
9. now type ":"
10. now type "q"
I empathize with Old_Fogie. Although I can more or less use vi/vim when in a pinch, I find all 'nix console text editors to be a Neanderthal joke (See Item No. 1 at A Software Wish List).
I keep a short cheat sheet handy so I can use vim in those few situations when I can't launch X and must edit a file from the console. Otherwise I use Kate to modify all of my config files, including my sudoers list.
As mentioned by phil.d.g, visudo provides some syntax and typo error checking, and that is a Good Thing. However, one can run visudo independently to only check errors (visudo -c) and need not use that Neanderthal tool to actually edit the sudoers file. Read the visudo man page for additional details. Do know that by default the sudoers file is not writeable and users must first chmod +x the file before editing with an editor other than visudo.
I've just read the man page for visudo and you can change the editor used by visudo, in your sudoers file you can put a line
Code:
Defaults editor=/path/to/your/editor
So you get all the benefits of visudo and you get to use your favourite editor. Though, personally I think I'll stick to that "Neanderthal joke" of an editor that goes by the more common name "vi"
but, interestingly enough I too have found myself using it when at console/tty. it works quite well.
another point of mention; i cannot use "visudo" in mepis even as root. strange.
LOL Woodsman, you should see my notebooks over here, printouts, sticky's
Hi,
Some good points! Vi is not goofy if you understand the syntax.
Try the vi tutorial!
I think everyone should at least get the experience with vi,vim or whatever basic text editor to allow edits of config files.
Hey, at times you might not have that X app that you faithfully use to make the task easier on you. Sure I use X and like it for ease of use. But and a big BUT here. You need to be aware of cli usage or you will fall to the use of a poor OS. I want slack to run at the best possible configuration on any machine within my control.
Am I the only one here who likes MidnightCommander?
I just type mc at the command line as root, and can do anything.
I use mc and mc edit. However, because I seldom need to edit files from the console I tend to forget about using the mc editor until I need to manage files from the console. Using mc to manage files is easier than playing command line commando. As I mentioned, I can use vim, but there simply does not exist a console-based editor that satisfies my criteria of an editor. vi/vim/emacs, etc., probably all made sense 20 to 30 years ago, but nobody will convince me that those editors are user-friendly. Still, mc edit is another option to consider.
I use mc and mc edit. However, because I seldom need to edit files from the console I tend to forget about using the mc editor until I need to manage files from the console. Using mc to manage files is easier than playing command line commando. As I mentioned, I can use vim, but there simply does not exist a console-based editor that satisfies my criteria of an editor. vi/vim/emacs, etc., probably all made sense 20 to 30 years ago, but nobody will convince me that those editors are user-friendly. Still, mc edit is another option to consider.
Hi,
Like I said in a previous post an admin needs to be able to use a basic editor. mc seems to meet your needs. As for the 20-30 years ago reference, the core of the thought is to use a simple editor on the cli. No one stated they are user friendly! But if you use them on a regular basis then the ease of use becomes comfortable.
Tell me the first time you used mc you knew it. No mc had a learning curve but the use is intuitive. I don't use mc that often but when I need to the use is easy. I'm comfortable with vi/vim and the layout of my system so the point and click is not that important to me.
Heck, I do some maintenance in X for some of the installations.
But most is cli.
Tools are tools! You should use the one that meets the needs at the time. Be for hardware or software!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.