From: Stefan Seyfried <seife@suse.de>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: linux-bluetooth@vger.kernel.org,
Bastien Nocera <hadess@hadess.net>,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: Packaging question
Date: Thu, 18 Sep 2008 19:40:06 +0200 [thread overview]
Message-ID: <48D29276.5060708@suse.de> (raw)
In-Reply-To: <1221758180.6782.22.camel@californication>
Marcel Holtmann wrote:
>> I had that old udev rule hack that would call the init script at adapter
>> plugin, but that's ugly and racy (because it typically starts before DBus is
>> started).
>>
>> Any innovative ideas?
>
> we had the discussion for Fedora and we want to start it via udev,
> however then we need D-Bus before udev runs and that is not an option
> right now. So the current solution is to just do it via init.d, but in
> the future we want udev.
What about the old hack that I had back in the old days that would let hcid
wait until D-Bus came up? ;-) One problem with init.d is that the daemon is
running, even if there is no device plugged in...
> The D-Bus service activation is nice, but makes
> problems when you wanna use the mouse and keyboard early.
Yes, I already noticed that :)
--
Stefan Seyfried
R&D Team Mobile Devices | "Any ideas, John?"
SUSE LINUX Products GmbH, Nürnberg | "Well, surrounding them's out."
This footer brought to you by insane German lawmakers:
SUSE Linux Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
next prev parent reply other threads:[~2008-09-18 17:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-09 14:19 Packaging question Stefan Seyfried
2008-09-10 22:15 ` Marcel Holtmann
2008-09-11 8:40 ` Stefan Seyfried
2008-09-12 16:34 ` Marcel Holtmann
2008-09-18 10:36 ` Stefan Seyfried
2008-09-18 17:16 ` Marcel Holtmann
2008-09-18 17:40 ` Stefan Seyfried [this message]
2008-09-18 20:39 ` Marcel Holtmann
2008-09-23 18:46 ` Stefan Seyfried
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=48D29276.5060708@suse.de \
--to=seife@suse.de \
--cc=dwmw2@infradead.org \
--cc=hadess@hadess.net \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.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