From: Andries Brouwer <Andries.Brouwer@cwi.nl>
To: Chris Wedgwood <cw@f00f.org>
Cc: Petr Vandrovec <vandrove@vc.cvut.cz>,
koke@amedias.org, linux-kernel@vger.kernel.org,
Andries Brouwer <Andries.Brouwer@cwi.nl>
Subject: Re: strange delays on console logouts (tty != 1)
Date: Sun, 2 May 2004 15:54:24 +0200 [thread overview]
Message-ID: <20040502135424.GA20578@apps.cwi.nl> (raw)
In-Reply-To: <20040501234444.GA24120@taniwha.stupidest.org>
On Sat, May 01, 2004 at 04:44:44PM -0700, Chris Wedgwood wrote:
> On Sun, May 02, 2004 at 01:24:48AM +0200, Petr Vandrovec wrote:
>
> > (1) agetty (at least from util-linux 2.12 from current debian
> > unstable) opens /dev/console and calls VT_OPENQRY to find first
> > unopened VT.
>
> yes, this i discovered too
Thank you for cc-ing me.
However, my agetty source does not contain the string VT_OPENQRY.
I suppose this is a private Debian change. Maybe you should
contact Debian people to find out who did this and why.
(And/or try the vanilla agetty to see whether the problems go away.)
Andries
[Just found the Debian patch. Strange, broken code.]
next prev parent reply other threads:[~2004-05-02 13:54 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-30 19:53 strange delays on console logouts (tty != 1) Jorge Bernal
2004-05-01 21:46 ` Chris Wedgwood
2004-05-01 23:24 ` Petr Vandrovec
2004-05-01 23:44 ` Chris Wedgwood
2004-05-02 0:36 ` Petr Vandrovec
2004-05-02 0:45 ` Chris Wedgwood
2004-05-02 13:54 ` Andries Brouwer [this message]
2004-05-02 1:03 ` Andrew Morton
2004-05-02 8:00 ` Russell King
2004-05-02 8:13 ` Andrew Morton
2004-05-02 8:17 ` Russell King
2004-05-02 9:37 ` Russell King
2004-05-02 10:17 ` Russell King
2004-05-02 12:01 ` Petr Vandrovec
2004-05-02 17:53 ` Chris Wedgwood
2004-05-02 18:01 ` Russell King
2004-05-02 18:19 ` Chris Wedgwood
2004-05-02 18:04 ` Russell King
2004-05-01 22:20 ` Chris Wedgwood
2004-05-02 0:26 ` Jorge Bernal
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=20040502135424.GA20578@apps.cwi.nl \
--to=andries.brouwer@cwi.nl \
--cc=cw@f00f.org \
--cc=koke@amedias.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vandrove@vc.cvut.cz \
/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