Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752985AbaB0OAX (ORCPT ); Thu, 27 Feb 2014 09:00:23 -0500 Received: from mailout32.mail01.mtsvc.net ([216.70.64.70]:53996 "EHLO n23.mail01.mtsvc.net" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1750904AbaB0OAW (ORCPT ); Thu, 27 Feb 2014 09:00:22 -0500 Message-ID: <530F44F2.6050802@hurleysoftware.com> Date: Thu, 27 Feb 2014 09:00:18 -0500 From: Peter Hurley User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 To: Kay Sievers CC: Greg Kroah-Hartman , Jiri Slaby , LKML , Ray Strode , David Herrmann , Lennart Poettering , Werner Fink Subject: Re: [PATCH] tty: Add sysfs symlink for console name->tty device References: <1393425651-7374-1-git-send-email-peter@hurleysoftware.com> <530F3E47.5040904@hurleysoftware.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Authenticated-User: 990527 peter@hurleysoftware.com X-MT-ID: 8FA290C2A27252AACF65DBC4A42F3CE3735FB2A4 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 02/27/2014 08:36 AM, Kay Sievers wrote: > On Thu, Feb 27, 2014 at 2:31 PM, Peter Hurley wrote: >> On 02/27/2014 06:13 AM, Kay Sievers wrote: >>> >>> On Wed, Feb 26, 2014 at 3:40 PM, Peter Hurley >>> wrote: >>>> >>>> Enable a user-space process to discover the underlying tty device >>>> for a console, if one exists, and when the tty device is later >>>> created or destroyed. >>>> >>>> Add sysfs symlinks for registered consoles to their respective >>>> devices in [sys/class,sys/devices/virtual]/tty/console. >>>> Scan consoles at tty device (un)registration to handle deferred >>>> console<->device (un)binding. >>> >>> What tool is supposed to read that? I can't think of anything >>> interested in this, as soon as we have fixed the "active" console >>> output. > >> With all due respect, that "fix" is a ridiculous hack, > > No, it is not. It's fine to handle tty0 special, as it is special. I wasn't just referring to the plymouth workaround. >> being done >> for self-serving expedience. > > I don't see the problem. > >> It already caused one user-space breakage >> which you did not expect. > > That is normal way to do things, only people who don't do things don't > break things. And broken things get fixed, and the "active" file is still > fixable, and that is what we should do. But what's the plan when more user-space breakage is uncovered after that change has been in 10 kernel releases? Then everyone will point to how much user-space breakage reverting it will cause. > We don't need to invent new things because we did not get things right > with the first try. > >> This sysfs interface is superior in every way. > > But nothing uses it now, and probably never will, so I don't see the > need for it at this moment. Let's just avoid the mess right up-front. Regards, Peter Hurley -- 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/