On 9/22/07, Douglas A. Tutty <[EMAIL PROTECTED]> wrote: > On Sat, Sep 22, 2007 at 06:08:53PM +0200, Joachim Schipper wrote: > > On Fri, Sep 21, 2007 at 12:46:40PM -0400, Douglas A. Tutty wrote: > > > I don't use X much and instead use lots of Virtual Terminals. > > > > > > Since I'm on dialup, sometimes I need to leave multiple VTs open to do > > > things, perhaps downloading something, or its just that I'm in the > > > middle of things. > > > > > > How can I lock the whole virtual termial setup? lock(1) only lets me > > > lock the one VT without blocking the ability to switch to others. On > > > Debian, there's vlock -a that does this. I don't see anything similar > > > in the available packages for OBSD. > > > > > > I can't read code so I don't know how lock(1) works internally. To get > > > it to lock everything, I guess it would have to capture the Alt-Fn key > > > combo. However, the OS (wscons(4)?) likely captures that before the > > > keys get passed on to the application. So I'm sorry, I can't provide a > > > patch. > > > > Switch to GNU screen? You get the locking you desire, and lots of other > > neat stuff thrown in for free. > > > > I do believe lock(1) doesn't really work in this case; I don't know if > > it could be made to work, but since I always use screen I don't really > > care. > > I tried Screen on Debian briefly. I'm not good at remembering magic > keystrokes. If necessary, I'll try again. However, since I'm trying to > get used to the OBSD way of doing things, and since this seemed like a > security issue, I wanted to see how to solve this using what is in OBSD > base.
Does "lock -nv" not work? I just read about this in "BSD Hacks" last night, oddly enough. -Todd
