From: Jeff Garzik <jgarzik@pobox.com>
To: Chris Friesen <cfriesen@nortelnetworks.com>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
linux-kernel mailing list <linux-kernel@vger.kernel.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
cgl_discussion mailing list <cgl_discussion@osdl.org>,
evlog mailing list <evlog-developers@lists.sourceforge.net>,
"ipslinux (Keith Mitchell)" <ipslinux@us.ibm.com>,
Linus Torvalds <torvalds@home.transmeta.com>,
Hien Nguyen <hien@us.ibm.com>,
James Keniston <kenistoj@us.ibm.com>,
Mike Sullivan <sullivam@us.ibm.com>
Subject: Re: alternate event logging proposal
Date: Tue, 24 Sep 2002 16:09:20 -0400 [thread overview]
Message-ID: <3D90C670.90508@pobox.com> (raw)
In-Reply-To: 3D90C3B0.8090507@nortelnetworks.com
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
next prev parent reply other threads:[~2002-09-24 20:04 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-24 1:54 [PATCH-RFC} 3 of 4 - New problem logging macros, plus template generation Larry Kessler
2002-09-24 2:12 ` Jeff Garzik
2002-09-24 5:47 ` Rusty Russell
2002-09-24 6:05 ` Jeff Garzik
2002-09-24 7:06 ` Rusty Russell
2002-09-24 7:23 ` Jeff Garzik
2002-09-24 7:30 ` Rusty Russell
2002-09-24 19:48 ` alternate event logging proposal Jeff Garzik
2002-09-24 19:57 ` Chris Friesen
2002-09-24 20:03 ` Jeff Garzik
2002-09-24 20:54 ` Tim Hockin
2002-09-24 22:32 ` Brad Hards
2002-09-24 23:31 ` Jeff Garzik
2002-09-24 23:37 ` Brad Hards
2002-09-24 23:59 ` Tim Hockin
2002-09-24 23:38 ` Tim Hockin
2002-09-25 0:09 ` Ben Greear
2002-09-25 0:47 ` Tim Hockin
2002-09-25 1:14 ` Brad Hards
2002-09-25 1:38 ` Tim Hockin
2002-09-24 20:09 ` Jeff Garzik [this message]
2002-09-24 20:27 ` [evlog-dev] " Larry Kessler
2002-09-24 20:35 ` Jeff Garzik
2002-09-24 21:11 ` Larry Kessler
2002-09-24 21:26 ` Jeff Garzik
2002-09-25 0:15 ` Larry Kessler
2002-09-24 21:27 ` Horst von Brand
2002-09-24 21:50 ` Larry Kessler
2002-09-25 14:44 ` Lars Marowsky-Bree
2002-09-24 20:54 ` [evlog-dev] " Daniel E. F. Stekloff
2002-09-24 21:04 ` Jeff Garzik
2002-09-30 22:43 ` Pavel Machek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3D90C670.90508@pobox.com \
--to=jgarzik@pobox.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=cfriesen@nortelnetworks.com \
--cc=cgl_discussion@osdl.org \
--cc=evlog-developers@lists.sourceforge.net \
--cc=hien@us.ibm.com \
--cc=ipslinux@us.ibm.com \
--cc=kenistoj@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=sullivam@us.ibm.com \
--cc=torvalds@home.transmeta.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).