From: John Floren <slawmaster@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] how to lock cpu console
Date: Wed, 1 Sep 2010 00:44:58 -0400 [thread overview]
Message-ID: <AANLkTik_Sb5krZ+Lxu+mohAo=gTGnbdtGL0z41_V7zqe@mail.gmail.com> (raw)
In-Reply-To: <AANLkTim-4vx2KLkUOdg2YkeyrYbKfUw5CTn2JT4CP8Bd@mail.gmail.com>
Don't do this under drawterm, at least not on Windows. It'll gobble
your mouse right up, or at least it did mine.
Of course, there's no reason to run this in drawterm, since your host
OS is certain to have its own screen locker...
John
On Wed, Sep 1, 2010 at 12:21 AM, Federico G. Benavento
<benavento@gmail.com> wrote:
> now there's also screenlock(8)
>
> http://plan9.bell-labs.com/magic/man2html/8/screenlock
>
> similar to conslock, but authenticates against the auth server
>
> On Tue, Aug 31, 2010 at 5:45 PM, Skip Tavakkolian <9nut@9netics.com> wrote:
>> see: /n/sources/contrib/steve/rc/conslock
>>
>> if you have more than one cpu, change this line:
>> pwd=$home/lib/conslock.hash
>> to
>> pwd=$home/lib/conslock.^$sysname^.hash
>>
>>
>>
>
>
>
> --
> Federico G. Benavento
>
>
--
"With MPI, familiarity breeds contempt. Contempt and nausea. Contempt,
nausea, and fear. Contempt, nausea, fear, and .." -- Ron Minnich
next prev parent reply other threads:[~2010-09-01 4:44 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-31 14:20 baux80
2010-08-31 14:31 ` Robert Raschke
2010-08-31 14:55 ` John Floren
2010-08-31 15:04 ` erik quanstrom
2010-08-31 15:25 ` David Leimbach
2010-08-31 15:25 ` Skip Tavakkolian
2010-08-31 18:18 ` Francisco J Ballesteros
2010-08-31 19:54 ` andrey mirtchovski
2010-08-31 20:45 ` Skip Tavakkolian
2010-09-01 4:21 ` Federico G. Benavento
2010-09-01 4:44 ` John Floren [this message]
2010-09-01 15:11 ` erik quanstrom
2010-09-01 16:57 ` Federico G. Benavento
2010-09-01 17:22 ` erik quanstrom
2010-09-01 17:44 ` John Floren
2010-09-01 18:14 ` erik quanstrom
2010-09-01 18:31 ` John Floren
2010-09-01 18:51 ` erik quanstrom
2010-09-01 19:41 ` John Floren
2010-09-01 18:24 ` frank
2010-09-01 17:56 ` Federico G. Benavento
2010-09-01 10:09 ` baux80
2010-09-01 10:09 ` baux80 at gmail.com
2010-09-01 9:56 ` baux80 at gmail.com
2010-09-01 9:56 ` baux80
[not found] ` <E1Oqk2g-0003Ze-1W@gouda.swtch.com>
2010-09-01 19:14 ` Corey
2010-09-01 19:52 ` erik quanstrom
2010-09-01 20:23 ` Corey
2010-09-01 9:48 ` baux80 at gmail.com
2010-09-01 9:48 ` baux80
2010-08-31 14:20 baux80 at gmail.com
[not found] <E1OqRh3-0005IS-Hi@gouda.swtch.com>
2010-08-31 14:29 ` erik quanstrom
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='AANLkTik_Sb5krZ+Lxu+mohAo=gTGnbdtGL0z41_V7zqe@mail.gmail.com' \
--to=slawmaster@gmail.com \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).