Re: visudo, /etc/sudo.conf, probe_interfaces

2024-01-08 Thread Greg Wooledge
name)" give a correct-looking response in a reasonable amount of time? The idea that visudo would *look up your hostname in DNS* is news to me, and I'm going to insist on some actual *proof* here. > 'visudo /etc/sudo.conf' shows a line '# Set probe_interfaces > fa

visudo, /etc/sudo.conf, probe_interfaces

2024-01-08 Thread Mike McClain
lains that my hostname can't be found via DNS, which I don't find surprising since I'm a single user system serving no ports. It's been like that for years and never caused a problem until I installed Devuan. 'visudo /etc/sudo.conf' shows a line '# Set probe_inter

Re: [help-a-newb] Why nano (or was it pico) instead of vi for visudo? (was question about adduser)

2011-03-20 Thread Joel Rees
'll > be lazy and blame it on my age. > > ;-> > > On Mon, Mar 21, 2011 at 1:18 PM, Doug wrote: >> On 03/20/2011 10:15 PM, Tom H wrote: >>> >>> On Sun, Mar 20, 2011 at 8:30 PM, Joel Rees  wrote: >>> >>> It's nano and the reason

Re: [help-a-newb] Why nano (or was it pico) instead of vi for visudo? (was question about adduser)

2011-03-20 Thread Doug
On 03/20/2011 10:15 PM, Tom H wrote: On Sun, Mar 20, 2011 at 8:30 PM, Joel Rees wrote: It's nano and the reason that nano's called by visudo (paradoxically) is that visudo calls "/usr/bin/editor" and the alternatives system maps it to "/usr/bin/nano". You can run

Re: [help-a-newb] Why nano (or was it pico) instead of vi for visudo? (was question about adduser)

2011-03-20 Thread Tom H
On Sun, Mar 20, 2011 at 8:30 PM, Joel Rees wrote: It's nano and the reason that nano's called by visudo (paradoxically) is that visudo calls "/usr/bin/editor" and the alternatives system maps it to "/usr/bin/nano". You can run visudo with "EDITOR=vi visudo&qu

Fwd: [help-a-newb] Why nano (or was it pico) instead of vi for visudo? (was question about adduser)

2011-03-20 Thread Joel Rees
(Still forgetting and hitting the reply button instead of reply-all followed by manually clearing the to: field. Sorry, Rob.) -- Forwarded message -- From: Joel Rees Date: Mon, Mar 21, 2011 at 9:20 AM Subject: Re: [help-a-newb] adduser okay? (problem with authenticating with gui

Re: Configuring sudo by file, not by visudo etc

2008-10-09 Thread Tzafrir Cohen
On Wed, Oct 08, 2008 at 09:19:51PM +, T o n g wrote: > Hi, > > Is it possible to configure sudo by file, not by visudo etc? > > I know that visudo provides security checks, parses for errors, and > protects against multiple edits of the file. But each time I just copy

Re: Configuring sudo by file, not by visudo etc

2008-10-09 Thread Andrei Popescu
On Thu,09.Oct.08, 03:09:43, T o n g wrote: > On Wed, 08 Oct 2008 16:53:34 -0500, ReikoShea wrote: > > >> Is it possible to configure sudo by file, not by visudo etc? > >> > > Most definitely can just overwrite /etc/sudoers instead of using visudo. > > Not rec

Re: Configuring sudo by file, not by visudo etc

2008-10-08 Thread T o n g
On Wed, 08 Oct 2008 16:53:34 -0500, ReikoShea wrote: >> Is it possible to configure sudo by file, not by visudo etc? >> > Most definitely can just overwrite /etc/sudoers instead of using visudo. > Not recommended, but does work. Thanks. It works. Don't know why it didn&

Re: Configuring sudo by file, not by visudo etc

2008-10-08 Thread ReikoShea
On Wed, 2008-10-08 at 21:19 +, T o n g wrote: > Hi, > > Is it possible to configure sudo by file, not by visudo etc? > > I know that visudo provides security checks, parses for errors, and > protects against multiple edits of the file. But each time I just copy > and

Configuring sudo by file, not by visudo etc

2008-10-08 Thread T o n g
Hi, Is it possible to configure sudo by file, not by visudo etc? I know that visudo provides security checks, parses for errors, and protects against multiple edits of the file. But each time I just copy and paste what I prepared into it. I'm wondering if I can omit this extra step en

Re: visudo not vi?

2001-03-14 Thread will trillich
On Tue, Mar 13, 2001 at 05:31:43PM +0100, Turbo Fredriksson wrote: > Quoting "Matus \"fantomas\" Uhlar" <[EMAIL PROTECTED]>: > > > -> > Here is what I got: > > -> > > > -> > > > > -> > > > -> > File read and write ^X I ^X^W Left, down, up, right ^B ^N ^P > > -> > ^F > > ->

Re: visudo not vi?

2001-03-14 Thread Justin B Rye
Aaron Lehmann wrote: > Using a non-vi-compatable editor on boot disks is a hanging offense > that debian will pay for once sysadmins try to install Debian but > realize they have better things to do than learn a whimpy editor. It > would be excusable if it was emacs-compatable, but it's not. e3 > s

Re: visudo not vi?

2001-03-14 Thread Hamish Moffatt
On Wed, Mar 14, 2001 at 01:47:06PM +0100, Peter Korsgaard wrote: > > "Hamish" == Hamish Moffatt <[EMAIL PROTECTED]> writes: > > Hamish> I thought somebody said they made a mistake and there is no C > Hamish> version -- just the i386 assembler. > > No the package both contains an asm version

Re: visudo not vi?

2001-03-14 Thread Peter Korsgaard
> "Hamish" == Hamish Moffatt <[EMAIL PROTECTED]> writes: Hamish> I thought somebody said they made a mistake and there is no C Hamish> version -- just the i386 assembler. No the package both contains an asm version for i386 machines and a version in C for other architectures. Someone said

Re: visudo not vi?

2001-03-14 Thread Hamish Moffatt
On Wed, Mar 14, 2001 at 11:03:39AM +0100, Peter Korsgaard wrote: > > "Hamish" == Hamish Moffatt <[EMAIL PROTECTED]> writes: > > >> would be excusable if it was emacs-compatable, but it's not. e3 > >> supports vi, emacs, wordstar, AND pico bindings. It just depends > >> whether you type vi,

Re: visudo not vi?

2001-03-14 Thread Peter Korsgaard
> "Hamish" == Hamish Moffatt <[EMAIL PROTECTED]> writes: >> would be excusable if it was emacs-compatable, but it's not. e3 >> supports vi, emacs, wordstar, AND pico bindings. It just depends >> whether you type vi, emacs, or pico to start it. Hamish> .. but is not suitable as it's not po

Re: visudo not vi?

2001-03-14 Thread Hamish Moffatt
On Wed, Mar 14, 2001 at 12:42:10AM -0800, Aaron Lehmann wrote: > would be excusable if it was emacs-compatable, but it's not. e3 > supports vi, emacs, wordstar, AND pico bindings. It just depends > whether you type vi, emacs, or pico to start it. .. but is not suitable as it's not portable. Hami

Re: visudo not vi?

2001-03-14 Thread Aaron Lehmann
On Wed, Mar 14, 2001 at 12:57:07AM -0800, Alexander Hvostov wrote: > 1) nano-tiny is relatively easy to use. > 2) nano-tiny has fewer bugs. Using a non-vi-compatable editor on boot disks is a hanging offense that debian will pay for once sysadmins try to install Debian but realize they have better

Re: visudo not vi?

2001-03-14 Thread Alexander Hvostov
John Galt wrote: On Tue, 13 Mar 2001, Chris Lawrence wrote: On Mar 13, Wichert Akkerman wrote: Previously Matus fantomas Uhlar wrote: it should be probably replaced by elvis-tiny , even on distribution disks... 1. not everyone knows how to use vi 2. ae is *small*. lots smaller then elvis

Re: visudo not vi?

2001-03-14 Thread John Galt
On Tue, 13 Mar 2001, Chris Lawrence wrote: >On Mar 13, Wichert Akkerman wrote: >> Previously Matus fantomas Uhlar wrote: >> > it should be probably replaced by elvis-tiny , even on distribution >> > disks... >> >> 1. not everyone knows how to use vi >> 2. ae is *small*. lots smaller then elvis-ti

Re: visudo not vi?

2001-03-13 Thread Hamish Moffatt
On Tue, Mar 13, 2001 at 05:31:43PM +0100, Turbo Fredriksson wrote: > that emacs is just to big for this purpose. So came ae, which let's you > have a little of both worlds (at a big cost in both worlds unfortunatly, > but that's usually what a compromise will do). You mean the worst of both worlds

Re: visudo not vi?

2001-03-13 Thread Chris Lawrence
On Mar 13, Wichert Akkerman wrote: > Previously Matus fantomas Uhlar wrote: > > it should be probably replaced by elvis-tiny , even on distribution disks... > > 1. not everyone knows how to use vi > 2. ae is *small*. lots smaller then elvis-tiny. We probably should change to nano-tiny, because (a

Re: visudo not vi?

2001-03-13 Thread Matus \"fantomas\" Uhlar
-> Previously Matus fantomas Uhlar wrote: -> > it should be probably replaced by elvis-tiny , even on distribution disks... -> -> 1. not everyone knows how to use vi -> 2. ae is *small*. lots smaller then elvis-tiny. requires more libraries... -- Matus "fantomas" Uhlar, sysadmin at NEXTRA, Sl

Re: visudo not vi?

2001-03-13 Thread Turbo Fredriksson
Quoting "Matus \"fantomas\" Uhlar" <[EMAIL PROTECTED]>: > -> > Here is what I got: > -> > > -> > > > -> > > -> > File read and write ^X I ^X^W Left, down, up, right ^B ^N ^P > -> > ^F > -> > -> > what the heck is this editor? > -> > -> ae. It's supposed to be an easy e

Re: visudo not vi?

2001-03-13 Thread Nick Croft
point taken.

Re: visudo not vi?

2001-03-13 Thread Colin Watson
Nick Croft <[EMAIL PROTECTED]> wrote: >Just do: > vim /etc/sudoers > >You don't need visudo Read the man page - using visudo is a good idea, assuming you've set $EDITOR properly. -- Colin Watson [EMAIL PROTECTED]

Re: visudo not vi?

2001-03-13 Thread Nick Croft
Just do: vim /etc/sudoers You don't need visudo N

Re: visudo not vi?

2001-03-13 Thread Drew Parsons
On Tue, Mar 13, 2001 at 03:12:34PM +0100, Matus fantomas Uhlar wrote: > -> > Here is what I got: > -> > > -> > > > -> > > -> > File read and write ^X I ^X^W Left, down, up, right ^B ^N ^P Shouldn't that be "up up down down..." ;) Drew -- PGP public key available at htt

Re: visudo not vi?

2001-03-13 Thread Ethan Benson
On Tue, Mar 13, 2001 at 03:12:34PM +0100, Matus fantomas Uhlar wrote: > > agreed, wtf it's still in the base distribution? > it should be probably replaced by elvis-tiny , even on distribution disks... it has. check debian-boot archives. > comments? -- Ethan Benson http://www.alaska.net/~er

Re: visudo not vi?

2001-03-13 Thread Wichert Akkerman
Previously Matus fantomas Uhlar wrote: > it should be probably replaced by elvis-tiny , even on distribution disks... 1. not everyone knows how to use vi 2. ae is *small*. lots smaller then elvis-tiny. Wichert. -- / Generally

Re: visudo not vi?

2001-03-13 Thread Matus \"fantomas\" Uhlar
-> > Here is what I got: -> > -> > > -> > -> > File read and write ^X I ^X^W Left, down, up, right ^B ^N ^P -> > ^F -> -> > what the heck is this editor? -> -> ae. It's supposed to be an easy editor. I find it's a pain in the ass. agreed, wtf it's still in the base di

Re: visudo not vi?

2001-03-13 Thread kmself
It's supposed to be an easy editor. I find it's a pain in the ass. > how to let visudo use vi instead? man visudo Check your environment, particularly $EDITOR and $VISUAL. -- Karsten M. Self http://kmself.home.netcom.com/ What part of "Gestalt" don&#

visudo not vi?

2001-03-13 Thread Jack
Invert case C 5...105...205...305...405...505...605...705...80 # 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. # # Host alias specification

Re: visudo

1998-04-09 Thread Daniel Martin at cush
Corey Miller <[EMAIL PROTECTED]> writes: > While I was editing my /etc/sudoers file using the visudo command, > my computer lost power. When I was able to restore power, everything > seemed to be functioning alright. Except, I tried to run the visudo > command, and got t

visudo

1998-04-09 Thread Corey Miller
While I was editing my /etc/sudoers file using the visudo command, my computer lost power. When I was able to restore power, everything seemed to be functioning alright. Except, I tried to run the visudo command, and got the following error: visudo: sudoers file busy, try again later