Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932424Ab0KPUuZ (ORCPT ); Tue, 16 Nov 2010 15:50:25 -0500 Received: from earthlight.etchedpixels.co.uk ([81.2.110.250]:48711 "EHLO www.etchedpixels.co.uk" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S932306Ab0KPUuU (ORCPT ); Tue, 16 Nov 2010 15:50:20 -0500 Date: Tue, 16 Nov 2010 20:49:06 +0000 From: Alan Cox To: Kay Sievers Cc: linux-kernel , Greg KH , Lennart Poettering , Werner Fink , Jiri Slaby Subject: Re: tty: add 'active' sysfs attribute to tty0 and console device Message-ID: <20101116204906.29d840e9@lxorguk.ukuu.org.uk> In-Reply-To: References: <1289922400.1253.3.camel@yio.site> <20101116155717.6671e484@lxorguk.ukuu.org.uk> <20101116171447.29336514@lxorguk.ukuu.org.uk> <20101116195538.7fa66b97@lxorguk.ukuu.org.uk> X-Mailer: Claws Mail 3.7.6 (GTK+ 2.18.9; x86_64-redhat-linux-gnu) Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAFVBMVEWysKsSBQMIAwIZCwj///8wIhxoRDXH9QHCAAABeUlEQVQ4jaXTvW7DIBAAYCQTzz2hdq+rdg494ZmBeE5KYHZjm/d/hJ6NfzBJpp5kRb5PHJwvMPMk2L9As5Y9AmYRBL+HAyJKeOU5aHRhsAAvORQ+UEgAvgddj/lwAXndw2laEDqA4x6KEBhjYRCg9tBFCOuJFxg2OKegbWjbsRTk8PPhKPD7HcRxB7cqhgBRp9Dcqs+B8v4CQvFdqeot3Kov6hBUn0AJitrzY+sgUuiA8i0r7+B3AfqKcN6t8M6HtqQ+AOoELCikgQSbgabKaJW3kn5lBs47JSGDhhLKDUh1UMipwwinMYPTBuIBjEclSaGZUk9hDlTb5sUTYN2SFFQuPe4Gox1X0FZOufjgBiV1Vls7b+GvK3SU4wfmcGo9rPPQzgIabfj4TYQo15k3bTHX9RIw/kniir5YbtJF4jkFG+dsDK1IgE413zAthU/vR2HVMmFUPIHTvF6jWCpFaGw/A3qWgnbxpSm9MSmY5b3pM1gvNc/gQfwBsGwF0VCtxZgAAAAASUVORK5CYII= Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1413 Lines: 38 > > Stuff never stops changing until the machine shuts down, its undefined. > > Either you don't, or you just don't want to understand what all this > is about. :) At what point do you think the current tty stops changing ? The only cases I can think of are shutdown, and when your own processes locks vt changes. > > Except that it doesn't address things like the permissions side of things. > > > > NAK again > > Specifics please. /dev/tty* and sysfs nodes don't track permissions, owner with each other, so you are providing interfaces that either expose information they shouldn't (which screen is valuable info in some environments), or don't expose info they should. sysfs also lacks vhangup so you can't fix it right now either. > > "We have an interface that doesn't quite work for our case and we think > > that is a bug" is not the reasoning behind writing a new random one with > > a totally disconnected permission model that doesn't work either. > > > > Fix the one we have. > > So how do you think you'll fix it? I better don't get into your > ioctl() business. Start by explaining why the current interface doesn't work for you, but in detail. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/