[ I removed this kenistonj@us.ibm.com from the CC:, it bounces... ]
I'd agree a lot of thought (and agreement :))has to go
into this before changing minor nits and stuff, and not
causing too much disruption..Evolution, as opposed to
revolution ;). I would hope that most wouldnt need changing..
There would be absolutely ZERO disruption if you guys would use you
brains and implement what you're actually trying to achieve, a system
event logging mechanism.
We have a message queueing mechanism using sockets, called netlink,
and you can make whatever actions in the kernel you think should be
monitored go and stuff messages into this system event netlink socket.
Then, you don't have to standardize a bunch of absolutely silly
strings (I mean, the concept is so incredibly stupid), you get events
that are in a precisely defined format going over this netlink socket.
Then whoever in userspace reads out the messages can interpret them
however the fuck it wants to. It is then trivial to parse the
messages and filter them. Furthermore, you could even transmit such
messages over a network connection to a remote logging server as-is.
And hey, look, for network links going up and down we have the hooks
already. Funny that...
-
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/