| 1 |
On Thu, 12 Feb 2009 00:52:22 +0100, b.n. wrote: |
| 2 |
|
| 3 |
> > The file /etc/sudoers should always be edited with visudo. visudo uses |
| 4 |
> > file locking, provides basic sanity checks and checks for parse |
| 5 |
> > errors. |
| 6 |
> |
| 7 |
> This always made me crazy. |
| 8 |
> |
| 9 |
> Why, why, why should I use a specialized editor to edit a system file? |
| 10 |
> It's not like we have vixorgconf, vifstab. You are welcome to edit these |
| 11 |
> files with any editor you like. Why is /etc/sudoers special? |
| 12 |
|
| 13 |
It's no more special than /etc/passwd, which should be edited with vipw. |
| 14 |
And it's not a specialised editor, these are just wrappers that call |
| 15 |
$EDITOR, so you end up using the same program to edit the files, but with |
| 16 |
a safety net. Remember that some systems restrict root access, so a |
| 17 |
fscked /etc/sudoers could lock you out. |
| 18 |
|
| 19 |
It's not like you HAVE to use the wrapper either, there's nothing to stop |
| 20 |
you using any editor you like, directly, and it's the best choice if you |
| 21 |
want to be free to screw up the file. |
| 22 |
|
| 23 |
|
| 24 |
-- |
| 25 |
Neil Bothwick |
| 26 |
|
| 27 |
Procedure: (n.) a method of performing a program sub-task in an |
| 28 |
inefficient way by extensively using the stack instead of a GOTO. |
Archives