Subject: Re: [PATCH] Console: fall back to /dev/null when no console is
	availlable
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Russell King <rmk+lkml@arm.linux.org.uk>
Cc: Greg KH <greg@kroah.com>, J?rn Engel <joern@wohnheim.fh-wedel.de>,
       Andrew Morton <akpm@osdl.org>,
       Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
In-Reply-To: <20041005221333.L6910@flint.arm.linux.org.uk>
References: <20041005185214.GA3691@wohnheim.fh-wedel.de>
	 <20041005212712.I6910@flint.arm.linux.org.uk>
	 <20041005210659.GA5276@kroah.com>
	 <20041005221333.L6910@flint.arm.linux.org.uk>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Message-Id: <1097074822.29251.51.camel@localhost.localdomain>
Mime-Version: 1.0
Date: Wed, 06 Oct 2004 16:00:23 +0100
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1024
Lines: 22

On Maw, 2004-10-05 at 22:13, Russell King wrote:
> I'm redirecting them in the /sbin/hotplug script to something sane,
> but I think the kernel itself should be directing these three fd's
> to somewhere whenever it invokes any user program, even if it is
> /dev/null.

Someone should yes. There are lots of fascinating things happen when
hotplug opens a system file, it gets assigned fd 2 and then we write to
stderr.

> I think Alan disagrees with me, but I think the history that these
> types of problems _keep_ cropping up over and over is proof enough
> that it's necessary for sane userspace.

Userspace to userspace execution is quite precisely defined. What
happens for kernel->userspace isn't so I have no problem with the kernel
attaching hotplug to the system console.
-
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/