linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ivan Baidakou <the.dmol@gmail.com>
To: Bastien Nocera <hadess@hadess.net>
Cc: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: Re: dund
Date: Sun, 12 Sep 2010 11:44:11 +0300	[thread overview]
Message-ID: <20100912114411.2678ffbe@gmail.com> (raw)
In-Reply-To: <16C0AC8E-F3CC-41A8-BE7D-C1BCB7F10CCC@hadess.net>

---=== reply ===---

You haven't real experience, right? In any case I don't know how to do
it: in the official pilot-link guide there is need to establish TCP
connection to sync (http://howto.pilot-link.org/bluesync/gb.html), and
to establish it they recommend to launch dund
(http://howto.pilot-link.org/bluesync/ga.html). 

That's why I do ask here, what thing in new bluez can replace the 
deprecated dund?

Best regards,
Ivan Baidakou

---=== original message ===---
Date: Sun, 12 Sep 2010 00:26:57 +0100
Subj: Re: dund
From: Bastien Nocera <hadess@hadess.net>
To: Ivan Baidakou <the.dmol@gmail.com>


On 11 Sep 2010, at 19:45, Ivan Baidakou <the.dmol@gmail.com> wrote:

> Hi All,
> 
> There was DUN daemon in bluez 2.x, but in current version it moved to
> old daemons and considered deprecated. If I understand correctly its
> aim is simple to launch pppd on incoming connection.
> 
> Is is possible to reach the same behaviour via current implementation
> without dund? Currently I do need dund to sync my Palm with desktop; I
> performed internet search and found not any solution. 

Gnome-pilot and pilot-link both support native Bluetooth connections.
 
Cheers


  reply	other threads:[~2010-09-12  8:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-11 18:45 dund Ivan Baidakou
2010-09-11 23:26 ` dund Bastien Nocera
2010-09-12  8:44   ` Ivan Baidakou [this message]
2010-09-12 14:37     ` dund Vladimir Botka
2010-09-12 14:45       ` dund Bastien Nocera
2010-09-13 20:47       ` dund Ivan Baidakou

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=20100912114411.2678ffbe@gmail.com \
    --to=the.dmol@gmail.com \
    --cc=hadess@hadess.net \
    --cc=linux-bluetooth@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).