lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20101027092744.GA27071@boole.suse.de>
Date:	Wed, 27 Oct 2010 11:27:44 +0200
From:	"Dr. Werner Fink" <werner@...e.de>
To:	Al Viro <viro@...IV.linux.org.uk>
Cc:	Jiri Slaby <jslaby@...e.cz>, Greg Kroah-Hartman <gregkh@...e.de>,
	linux-kernel@...r.kernel.org, Alan Cox <alan@...rguk.ukuu.org.uk>
Subject: Re: [PATCH 28/49] tty: Add a new file /proc/tty/consoles

On Wed, Oct 27, 2010 at 01:50:45AM +0100, Al Viro wrote:
> On Mon, Oct 25, 2010 at 09:51:25AM +0200, Dr. Werner Fink wrote:
> > > Maybe I wouldn't bother with marking the "current" console by star at
> > > all as it seems not to pay off.
> > 
> > This is the main reason for what I've done this patch:
> > To see on which console line the reading process is
> > located. Please do not skip this part as this is
> > currently the only way to detect the real console below
> > /dev/console ... it could be used in user space: e.g. in
> > plymouth or bootlogd (to deterime the main console) or
> > sulogin (to be able to provide a prompt on all console
> > lines).
> 
> You've got to be kidding.  So all this stuff is about getting TIOCGDEV
> into the mainline?  In a form that would, presumably, be more acceptable
> than an ioctl?

What is kidding about this user space problem?  Currently
there is no way to detect the terminal lines used for the
system console.  Running on /dev/console an application
has to steal the controlling tty to detect the preferred
terminal line of the system console (and only the preferred
line).  Last week the author of systemd had asked me why
the TIOCGDEV patch was not send upstream.  I've told him
that this was done but that several patches were never
accepted upstream, compare with:

http://lkml.org/lkml/2000/12/15/160

and the follow ups there. Even more the author of the old
SysVinit had run into the same problem:

http://lkml.org/lkml/1998/3/21/57

It seems to me that the list of the terminal devices of
the system consoles are useful in user space as Randy
Dunlap tolds me here

http://article.gmane.org/gmane.linux.kernel.api/1653

Such a list would be very helpful e.g. to extend sulogin
to be able to prompt for maintenance on all terminal lines
of the system console after e.g. failed fsck.  Currently
only the preferred terminal line is prompted for maintenance.

> > -- 
> >   "Having a smoking section in a restaurant is like having
> >           a peeing section in a swimming pool." -- Edward Burr
> 
> Ironic, innit?

depends on ;)

Werner

-- 
System V style init programs - http://savannah.nongnu.org/projects/sysvinit/
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ