From: Hibiki Kanzaki <hibikikanzaki@gmail.com>
To: madduck@madduck.net
Cc: linux bluetooth mailinglist <linux-bluetooth@vger.kernel.org>
Subject: Re: How to replace DUN with bluez 4?
Date: Sun, 19 Jul 2009 23:17:42 -0700 [thread overview]
Message-ID: <8c237ea80907192317k39f4353as56a7530cd23b515f@mail.gmail.com> (raw)
In-Reply-To: <20090720052314.GA10357@piper.oerlikon.madduck.net>
> It's scary to see this desktop trend. It's like
> Windows NT 4.0, and the Windows-typical need to log
> in to be able to start a firewall or fileserver.
Tell me about it. I keep seeing people (including me)
looking for command-line applications to do things
with BlueZ 4.x and getting responses along the lines
of "it works with [GNOME/KDE application], so just run
that, or look at the source code"... or people simply
get no response at all. What concerns me is it not
apparent there is a presumption that there needs to
be command-line applications to do everything which
can be done in GUIs. Real, supported applications,
not just pointers to a web page somewhere with a forum
posting with a Python script which calls dbus and sort
of does the desired thing, if the API has not changed
too much since the posting... in which case it may
just fail with an obscure error.
next prev parent reply other threads:[~2009-07-20 6:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-18 5:54 How to replace DUN with bluez 4? martin f krafft
2009-07-19 17:36 ` Luiz Augusto von Dentz
2009-07-19 17:57 ` martin f krafft
2009-07-19 18:20 ` Luiz Augusto von Dentz
2009-07-20 5:23 ` martin f krafft
2009-07-20 6:17 ` Hibiki Kanzaki [this message]
2009-07-20 6:45 ` David Sainty
2009-07-20 11:19 ` Luiz Augusto von Dentz
2009-07-20 11:33 ` martin f krafft
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=8c237ea80907192317k39f4353as56a7530cd23b515f@mail.gmail.com \
--to=hibikikanzaki@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=madduck@madduck.net \
/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