public inbox for util-linux@vger.kernel.org
 help / color / mirror / Atom feed
From: Karel Zak <kzak@redhat.com>
To: Alexey Gladkov <gladkov.alexey@gmail.com>
Cc: Petr Pisar <ppisar@redhat.com>,
	util-linux@vger.kernel.org, "Dmitry V. Levin" <ldv@altlinux.org>
Subject: Re: vlock command
Date: Thu, 15 Nov 2012 10:48:30 +0100	[thread overview]
Message-ID: <20121115094830.GB26255@x2.net.home> (raw)
In-Reply-To: <50A4B774.4010005@gmail.com>

On Thu, Nov 15, 2012 at 01:35:48PM +0400, Alexey Gladkov wrote:
> 15.11.2012 12:48, Petr Pisar wrote:
> > It's similar but insufficient. The difference between your clear_str[]
> > = "\33[H\33[J" and my string is my way clears scroll-back buffer of Linux
> > virtual terminal too. This prevents from reading history using Shift-PgUp
> > while the terminal is locked. Read current console_codes(4) page, especially
> > search for word "buffer".
> > 
> > So what I ask is to prepend "\33[3J" to your clear_str[]. This even users with
> > older kernel not implementing this code get console cleared.
> 
> Sounds reasonable.
> 
> > If I understand the code correctly, you clear screen only if it's a virtual
> > terminal. I have no idea how usefull is vlock on other terminals (I use
> > "screen" there), so I do not request any change in this matter.
> 
> Ok. This is what I wanted to find out.
> 
> Guys, I want to release the new version of kbd next month. This will
> be the first kbd release with the vlock. Do you have any more
> suggestions on vlock?

 Rename --enable-vlock to --disable-vlock and enable it by default :-)

    Karel

-- 
 Karel Zak  <kzak@redhat.com>
 http://karelzak.blogspot.com

  reply	other threads:[~2012-11-15  9:48 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-14 10:35 vlock command Karel Zak
2012-11-14 11:04 ` Alexey Gladkov
2012-11-14 12:22   ` Karel Zak
2012-11-14 23:54     ` Dmitry V. Levin
2012-11-16  8:36       ` Karel Zak
2012-11-14 12:26   ` Karel Zak
2012-11-14 12:38     ` Alexey Gladkov
2012-11-14 23:31     ` Dmitry V. Levin
2012-11-15  6:44       ` Alexey Gladkov
2012-11-15  7:52         ` Karel Zak
2012-11-15  8:48           ` Petr Pisar
2012-11-15  9:35             ` Alexey Gladkov
2012-11-15  9:48               ` Karel Zak [this message]
2012-11-15 10:03                 ` Alexey Gladkov
2012-11-15 10:23               ` Petr Pisar
2012-11-16 10:01                 ` Alexey Gladkov
2012-11-16 13:21                   ` Petr Pisar

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=20121115094830.GB26255@x2.net.home \
    --to=kzak@redhat.com \
    --cc=gladkov.alexey@gmail.com \
    --cc=ldv@altlinux.org \
    --cc=ppisar@redhat.com \
    --cc=util-linux@vger.kernel.org \
    /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