Sudo list.

**rrfish72** · 08-05-2004, 01:43 AM

How do I add myself to the sudoers.

**Stephen** · 08-05-2004, 02:26 AM

Originally Posted by rrfish72

How do I add myself to the sudoers.

As root visudo then use the examples in the file for your guide.

**mzilikazi** · 08-05-2004, 02:56 AM

Aw cmon Stephen are you gonna punish the noobs w/ vi?

vi is about as friendly as a coiled rattlesnake! You don't have to use vi you can use any editor you want.

su
<passwd>
xedit /etc/sudoers

**Stephen** · 08-05-2004, 03:23 AM

Originally Posted by mzilikazi

Aw cmon Stephen are you gonna punish the noobs w/ vi?

vi is about as friendly as a coiled rattlesnake! You don't have to use vi you can use any editor you want.

su
<passwd>
xedit /etc/sudoers

Code:

# sudoers file.
#
# This file MUST be edited with the 'visudo' command as root.
#
# See the man page for details on how to write a sudoers file.
#

Not according to that ...

**mzilikazi** · 08-05-2004, 04:20 AM

Well I don't even have vi on my Linux boxen but I'm a sudoer! OK so I'm a rebel. :P

**Durand Hicks** · 08-05-2004, 11:49 PM

Me too! I purged vi because, I couldn't figure that editor out. How anyone ended up liking vi as an editor is beyond me, that is the most unfriendly, unintiutive editor I have ever laid eyes on. Perhaps the warning could have said that it can be edited in a straight ascii editor such as nano, mcedit, ... you get the idea, as long as it is anything but vi.

**Stephen** · 08-06-2004, 01:16 AM

Originally Posted by Durand Hicks

Me too! I purged vi because, I couldn't figure that editor out. How anyone ended up liking vi as an editor is beyond me, that is the most unfriendly, unintiutive editor I have ever laid eyes on. Perhaps the warning could have said that it can be edited in a straight ascii editor such as nano, mcedit, ... you get the idea, as long as it is anything but vi.

The warning is there because when using the visudo it locks the file and prevents any other editing access to it for as long as you have it open this is the same reason vipw exists as well. Oh and BTW you were using VIM (vi improved) not VI if you think it was bad you should try the real thing.

**CrashedAgain** · 08-06-2004, 02:22 AM

Originally Posted by Stephen

Originally Posted by Durand Hicks

Me too! I purged vi because, I couldn't figure that editor out. How anyone ended up liking vi as an editor is beyond me, that is the most unfriendly, unintiutive editor I have ever laid eyes on. Perhaps the warning could have said that it can be edited in a straight ascii editor such as nano, mcedit, ... you get the idea, as long as it is anything but vi.

The warning is there because when using the visudo it locks the file and prevents any other editing access to it for as long as you have it open this is the same reason vipw exists as well. Oh and BTW you were using VIM (vi improved) not VI if you think it was bad you should try the real thing.

I never understood why this warning was there before. I've long since edited it out.

Personally I use Kate, I have a RootKate icon on the desktop. Just drag'n'drop the Kate icon from the start menu & edit to run as root...with KDE3.2 this is in 'advanced application' properties setups. Anyway, I highly recommend using Kate for newbies unfamiliar with CLI editors.

For CLI editor I use 'joe' (Ms Cuddles favorite app javascript:emoticon('

') just because it's an interface I'm familiar with from a long time ago in the land before Windows or Linux.

**Markus** · 08-06-2004, 08:24 AM

Is this where you post your favorite editor?

I think visudo also refuses to save the file if you've made a mistake in the syntax, or at least tells you about the mistake.
That said, I once ran vimtutor and the next command was apt-get install nano.