linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ilya Konstantinov <anon1@future.shiny.co.il>
To: linux-hotplug@vger.kernel.org
Subject: Re: xhotplugd -- project idea
Date: Wed, 19 Jun 2002 20:19:06 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-102451810209460@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-102406538226828@msgid-missing>

Hi Jim,

Here are my comments. Hope all this discussion doesn't end up in
all-talk-no-code. Seen one good discussion go that way already...

XFree-or-not
======
For things like changing the mouse protocol or tablet support on the
fly, implementing the support inside XFree86's code seems reasonable,
since this stuff is XFree86 specific anyway.

What's about:
- Keyboard model reconfiguration (XKB) ?
- Application invocation on plugging in new devices ?

No reason to lock down users into XFree86 for this. Linux can also
display into a remote X display, and there are other X servers too.

Files or sockets
========

I preferred stat()ing a file because it allows X sessions to "poll" for
new devices -- so that /sbin/hotplug wouldn't need to think "How do I
find all X sessions which are running on this machine? Where are those
little notification sockets which every X session has opened for me?".

Having something like /var/run/hotplug-sockets/ containing sockets of
all X session looked much messier and error-prone to me than a single
/var/run/hotplug-state.xml.

Desktop environments or not
=============	
For the mouse / Xkb model switching functionality, an X-wide solution
looks smarter.
For custom application events / launching functionality, a desktop
environment specific solution seems a better idea because:
  1. Programs could get notifications in the desktop environment's
standard fashion, e.g. DCOP. Using ICE directly is unnecessarily
difficult. Forcing everyone to link with a special library which'll talk
ICE for them is a library overkill.
  2. Mostly users would want a GNOME photo app to launch on plugging
their camera when running GNOME, and a KDE photo app to launch when
running KDE, so there's little benefit in "unifying the
app-launching-on-event". Even the "New Hardware Was Found" dialogs would
be different.




----------------------------------------------------------------------------
                   Bringing you mounds of caffeinated joy
                   >>>     http://thinkgeek.com/sf    <<<

_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

  parent reply	other threads:[~2002-06-19 20:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-14 14:34 xhotplugd -- project idea Ilya Konstantinov
2002-06-14 15:59 ` Bill Nottingham
2002-06-14 16:49 ` Greg KH
2002-06-14 17:55 ` Tim Jansen
2002-06-14 18:04 ` Chris Hanson
2002-06-15  0:22 ` Ilya Konstantinov
2002-06-15  0:38 ` Tim Jansen
2002-06-15  0:48 ` Ilya Konstantinov
2002-06-15  9:44 ` Tim Jansen
2002-06-18 17:14 ` Jim.Gettys
2002-06-19 20:19 ` Ilya Konstantinov [this message]
2002-06-20 14:06 ` Jim.Gettys
2002-06-20 17:28 ` David Brownell

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=marc-linux-hotplug-102451810209460@msgid-missing \
    --to=anon1@future.shiny.co.il \
    --cc=linux-hotplug@vger.kernel.org \
    /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).