[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: kobject_uevent
- From: Ikke <ikke.lkml@xxxxxxxxx>
- Date: Fri, 7 Jan 2005 22:25:14 +0100
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=Z6uMRCcUNCs7u6ciM4irMUYaIQpodhzUPPjtUPgUw4TSYvAZ/JqHS/sunBVYu+nJ+T3OP/sfeNzVBJntyhqLplvdEasgkgFjpMxvd5zmaARcb+v0ofbJ3eg2ZqDHgFpPEGUznCQOGiFISdogDFbOYAAFghamuoc/JAW0VzrM9f8=
- References: <297f4e01050107065060e0b2ad@mail.gmail.com>
I've been working a bit on the kobject_uevent stuff, and got a
prototype system working (well, almost) which takes kernel's uevents,
and sends them to the DBUS system bus so other software can (ab)use
them.
I'll add more uevents later, once I understand the system completely.
I'm a little confused by the use of KOBJ_* stuff in
include/linux/kobject_uevent.h and the string representation of them
in lib/kobject_uevent.c, which means people must edit 2 files if they
want to add new events?
More information on my little work here [1]
Regards, Ikke
[1] http://blog.eikke.com/index.php/ikke/2005/01/07/kernel_events_to_dbus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Follow-Ups:
References: