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: util-linux@vger.kernel.org
Subject: Re: vlock command
Date: Wed, 14 Nov 2012 13:22:07 +0100	[thread overview]
Message-ID: <20121114122207.GE1835@x2.net.home> (raw)
In-Reply-To: <50A37AD8.6060601@gmail.com>

On Wed, Nov 14, 2012 at 03:04:56PM +0400, Alexey Gladkov wrote:
> 14.11.2012 14:35, Karel Zak wrote:
> > 
> >  vlock(1) - Virtual Console lock program
> > 
> > This nice and small program used by admins on machines with consoles
> > only. Unfortunately it has inactive upstream(s).
> > 
> > The original upstream for vlock-1.3 at
> > 
> >     ftp://tsx-11.mit.edu:/pub/linux/sources/usr.bin/
> > 
> > is inactive for years. There is also new upstream at
> > 
> >    http://freecode.com/projects/vlock
> >    http://repo.or.cz/w/vlock.git
> > 
> > but this also seems inactive and from my point of view vlock-2.x is
> > over-engineering rhapsody (glib, plug-ins, dependences resolver,
> > external scripts etc.)
> > 
> > What about to merge vlock-1.3 into utils-linux? It's 630 lines of code
> > (including unnecessary non-PAM code).
> > 
> > Comments & Objections?
> > 
> 
> We have another version of vlock, which is being supported by Dmitry
> V. Levin.
> 
> http://git.altlinux.org/people/ldv/packages/vlock.git

 it seems the same code as the original vlock-1.3

> Some time ago, I have merged this version in kbd project:
> 
> http://git.altlinux.org/people/legion/packages/kbd.git?p=kbd.git;a=tree;f=src/vlock;h=92419b98175d215a71f83bfb06b409daa97b13c4;hb=768b8c314e1d3c465d895b206da4aa4543914d1d
> 
> I have a collection of utilities for manipulation in console (openvt,
> chvt, deallocvt ...) I consider logical to have the utility for
> terminal blocking.
> 
> What do you think?

 Well, vlock is mostly about authentication, but I have no strong
 opinion about it -- we can keep it in kbd as well.

    Karel

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

  reply	other threads:[~2012-11-14 12:22 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 [this message]
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
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=20121114122207.GE1835@x2.net.home \
    --to=kzak@redhat.com \
    --cc=gladkov.alexey@gmail.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