tomh0665 at gmail.com
Tue Dec 25 03:39:21 UTC 2012
On Mon, Dec 24, 2012 at 3:35 PM, NoOp <glgxg at sbcglobal.net> wrote:
> On 12/23/2012 01:48 PM, Phil Dobbin wrote:
>> I've just spun up a 12.04 remote virtual machine & when I ran the visudo
>> command, it plonked me into nano. Whilst this is easy to fix (sudo
>> update-alternatives --config editor), I'm puzzled as to when this happened.
>> I know it happened on some of the Red Hat clones but it was duly
>> reported upstream as a bug & upstream confirmed it was bug.
>> Is it a bug on Ubuntu or is this behaviour now the default?
> My 12.04 defaults to vi(m) per
> " There is a hard-coded list of one or more editors that visudo will use
> set at compile-time that may be overridden via the editor sudoers
> Default variable. This list defaults to "/usr/local/bin/vi"."
If you compile and install vi from source, its default location's most
probably "/usr/local/bin/vi" but no distribution installs anything to
The Ubuntu maintainer must have forgotten to edit the man page...
On Debian you get 'This list defaults to "/usr/bin/editor"', which
corresponds to the Ubuntu behavior on 12.10 (and on 12.04 AFAIR).
More information about the ubuntu-users