Jeffrey Walton <noloa...@gmail.com> writes: > Thanks Shawn. Sorry to go offlist. > > So, I'm trying to do some initial testing. I'm on a MacBook with > OpenBSD in a VM. All I want to do is run my compiler over some source > files.
Parallels? > MacBooks have a funky keyboard, and when I try to use visudo to move > the cursor around, some of the arrow keys don't work. Not to mention > the DELETE key (or the key combinations I know to use to simulate > delete). visudo responds with ^? is not valid. I'm sure I'll have that > file corrupted shortly. The vi(1) editor in base doesn't behave the same way as vim wrt. some keys. export EDITOR=mg and profit. > I really don't get why this shit is so f**k'ing difficult. How is > running around with a root terminal open more secure than exec'ing one > command under sudo??? No one said it was "more secure". As I already said in another mail, you can't meet a new OS and expect everything to work as you think they should. > Thanks for the advice. > > Jeff > > > On Sat, Sep 14, 2013 at 7:53 PM, Shawn K. Quinn <skqu...@rushpost.com> wrote: >> On Sat, Sep 14, 2013, at 06:47 PM, Martin Schröder wrote: >>> 2013/9/15 Jeffrey Walton <noloa...@gmail.com>: >>> >> man visudo >>> > I don't know vi. I do known emacs, but its not on this system so I >>> >>> Then learn it. This is unix. >>> You really should use visudo to edit /etc/sudoers, not an editor. >> >> Note that you can configure visudo, vipw, and vigr to use an editor >> besides vi. It's possible to get by on Unix without knowing vi, I did so >> on GNU/Linux systems for most of 4 years, but I finally broke down and >> figured it out and promptly realized it wasn't as hard as it had been >> made out to be. >> >> -- >> Shawn K. Quinn >> skqu...@rushpost.com > -- jca | PGP: 0x06A11494 / 61DB D9A0 00A4 67CF 2A90 8961 6191 8FBF 06A1 1494
