From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] patch: custom devup script
Date: Wed, 18 Jan 2006 14:20:15 +0100 [thread overview]
Message-ID: <1137590415.27515.17.camel@localhost> (raw)
In-Reply-To: <43CD92AE.20006@fillibach.de>
Hi Kosta,
> As my zeroconf implementation is incomplete (only generates an IP
> address, but does not check for conflicts), I instead added an option to
> run a custom devup script instead of /etc/bluetooth/pan/dev-up.
>
> Why? Because the mobile phone running embedded linux has a read-only
> /etc. This way, I can move my devup-script anywhere I want, without
> needing to recompile if its location changes.
your email client eats all the whitespaces and tabs. Please resend it
and attach it this time or use another (working) email client.
Regards
Marcel
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2006-01-18 13:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-09 16:41 [Bluez-devel] pan link quality Kosta Welke
2006-01-10 16:07 ` Marcel Holtmann
2006-01-18 0:58 ` [Bluez-devel] patch: custom devup script Kosta Welke
2006-01-18 13:20 ` Marcel Holtmann [this message]
2006-01-18 17:37 ` Claudio Takahasi
2006-01-18 22:18 ` Konstantin 'Kosta' Welke
2006-01-19 0:51 ` Marcel Holtmann
2006-01-19 1:55 ` Kosta Welk
2006-01-20 1:43 ` Marcel Holtmann
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=1137590415.27515.17.camel@localhost \
--to=marcel@holtmann.org \
--cc=bluez-devel@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;
as well as URLs for NNTP newsgroup(s).