From: Stefan Seyfried <seife@suse.de>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] dund and bluez
Date: Mon, 18 Dec 2006 10:38:28 +0100 [thread overview]
Message-ID: <20061218093828.GD960@suse.de> (raw)
In-Reply-To: <20061218090305.GA960@suse.de>
On Mon, Dec 18, 2006 at 10:03:05AM +0100, Stefan Seyfried wrote:
> On Sun, Dec 17, 2006 at 10:36:31AM -0800, Mark S. Townsley wrote:
> > Hi: I would like to find out more about how DUN profile (and DUND daem=
on)
> > works with Bluez.
> > Is there any config tutorial or programming tutorial about how to integ=
rate
> > DUN profile with Bluez?
> =
> Marcel, these two files are in the SUSE package for quite some time.
> Maybe they are good for upstream bluez-utils, too?
Oops. Mentioning YaST does not help too much :-) I'll clean them up a bit
and resend.
-- =
Stefan Seyfried
QA / R&D Team Mobile Devices | "Any ideas, John?"
SUSE LINUX Products GmbH, N=FCrnberg | "Well, surrounding them's out." =
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3DDE=
VDEV
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2006-12-18 9:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-17 18:36 [Bluez-users] dund and bluez Mark S. Townsley
2006-12-18 9:03 ` Stefan Seyfried
2006-12-18 9:38 ` Stefan Seyfried [this message]
[not found] ` <be976db60612180918n6666e9tec5d7c6a9a80dfe7@mail.gmail.com>
2006-12-18 17:40 ` 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=20061218093828.GD960@suse.de \
--to=seife@suse.de \
--cc=bluez-users@lists.sourceforge.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