Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 24 Sep 2002 16:04:41 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 24 Sep 2002 16:04:41 -0400 Received: from parcelfarce.linux.theplanet.co.uk ([195.92.249.252]:35087 "EHLO www.linux.org.uk") by vger.kernel.org with ESMTP id ; Tue, 24 Sep 2002 16:04:41 -0400 Message-ID: <3D90C670.90508@pobox.com> Date: Tue, 24 Sep 2002 16:09:20 -0400 From: Jeff Garzik Organization: MandrakeSoft User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1) Gecko/20020826 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Chris Friesen CC: Rusty Russell , linux-kernel mailing list , Alan Cox , cgl_discussion mailing list , evlog mailing list , "ipslinux (Keith Mitchell)" , Linus Torvalds , Hien Nguyen , James Keniston , Mike Sullivan Subject: Re: alternate event logging proposal References: <20020924073051.363D92C1A7@lists.samba.org> <3D90C183.5020806@pobox.com> <3D90C3B0.8090507@nortelnetworks.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: 808 Lines: 23 Chris Friesen wrote: > Also related is "how can userspace be notified of kernel events?". There > is no way for a userspace app to be notified that, for instance, an ATM > device got a loss of signal. The drivers print it out, but the > userspace app has no clue. (sorry for the second reply) To address your more general point, a general way to notify interested, credentialed (is that a word?) 3rd party processes of device events would indeed be useful. Since such events are essential out-of-band info, netlink might indeed be applicable. Jeff - 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/