Elektrified X.org released (was: X configuration paradigm, and a proposal)

Avi Alkalay avibrazil at gmail.com
Wed Dec 1 21:44:31 EET 2004

On Wed, 01 Dec 2004 13:29:28 -0500, Sean Middleditch
<elanthis at awesomeplay.com> wrote:
> > Notifications is there already. Check the code. Transactions needs
> > some stabilization, yes.
> Your notifications API is a gross hack.  It might be the best you can do
> without a daemon, but it's still practically unusable.  Discussed
> already in another message.

Just to let you know, I studied FAM source code to learn how to do
that. And surprisingly, it simply polls the monitored files :-) Oh
yes, it has a compilation option to use a kernel module called imon,
which is an SGI contribution proted from IRIX. But now guess: imon is
not in the kernel. So just to make it clear, FAM POLLS THE MONITORED
FILES, so Elektra monitoring is as good as FAM.

Well, this is not an excuse to make it this bad way, but since Elektra
is completely decentralized and not a single point of failure, I
couldn't find a way to make it more efficiently. You are welcome to
contribute, though :-)

And you want to know more?
Only desktop applications need monitoring. Actually Gnome likes
monitoring for fancy things like having the entire desktop theme
change when you click on a different one inside a dialog. Or you want
/sbin/init to instantly change its runlevel after changing the
runlevel key?  So the point is: notification needs are application
specific, and Elektra implements the very bottom of the infrastructure
needed to support it, because this is the scope of Elektra.

More information about the xdg mailing list