linux-kernel - Re: [PATCH, RFC, BAD IDEA] /proc/tty/console

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20080229150730.GA8209@nostromo.devel.redhat.com>
Date:	Fri, 29 Feb 2008 10:07:30 -0500
From:	Bill Nottingham <notting@...hat.com>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH, RFC, BAD IDEA] /proc/tty/console

Andrew Morton (akpm@...ux-foundation.org) said: 
> > The attached patch adds /proc/tty/console. The contents of it are
> > simply a description of the current drivers attached to /dev/console.
> > For example, a boot with 'console=ttyS3,115200n1 console=tty0' would
> > yield:
> > 
> > # cat /proc/tty/console
> > unknown             /dev/tty0
> > serial              /dev/ttyS3
> 
> I must say that the what-consoles-are-registered problem makes my head spin
> sometimes too.  Seems a worthy objective.
> 
> However I think that a bunch of plain old printks which are emitted when a
> console is added or removed would suffice?

We already do that in register_console(), albeit without flags.

My concern is I'd like to easily programmatically do something with this
info - ideally it would be in sysfs so it can easily be used from udev
or something similar.

Bill
--
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/