Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 14 Aug 2002 00:39:15 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 14 Aug 2002 00:39:15 -0400 Received: from neon-gw-l3.transmeta.com ([63.209.4.196]:56594 "EHLO neon-gw.transmeta.com") by vger.kernel.org with ESMTP id ; Wed, 14 Aug 2002 00:39:10 -0400 Message-ID: <3D59DFBE.4020007@zytor.com> Date: Tue, 13 Aug 2002 21:42:38 -0700 From: "H. Peter Anvin" User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.0) Gecko/20020703 X-Accept-Language: en-us, en, sv MIME-Version: 1.0 To: Benjamin LaHaise CC: Linus Torvalds , Alexander Viro , Andrew Morton , lkml Subject: Re: [patch] printk from userspace References: <20020814003505.A16322@redhat.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1249 Lines: 33 Benjamin LaHaise wrote: > On Tue, Aug 13, 2002 at 09:26:45PM -0700, Linus Torvalds wrote: > >>That said, I like the notion. I've always hated the fact that all the >>boot-time messages get lost, simply because syslogd hadn't started, and >>as a result things like fsck ran without any sign afterwards. The kernel >>log approach saves it all in one place. >> >>But /dev/console just sounds potentially _too_ noisy. > > > /dev/kmsg was another suggestion for the name. But please revert the > yet-another-syscall variant -- having a duplicate way for logging that > doesn't work with stdio just seems sick to me (sys_syslog should die). > Something like the following untested code is much better. > a) /dev/kmsg bettwe be S_IRUSR|S_IWUSR... reading /{proc,dev}/kmsg should drain the ring buffer. b) Hook up the /proc/kmsg read to this thing. It really needs to be a /dev node, not a /proc node; procfs is likely *not* to be mounted; however, manifesting a /dev node is easy enough. -hpa - 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/