From: Marek Lindner <lindner_marek@yahoo.de>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@lists.open-mesh.net>
Subject: Re: [B.A.T.M.A.N.] List policy for none subscribers
Date: Wed, 26 Aug 2009 16:51:16 +0800 [thread overview]
Message-ID: <200908261651.16980.lindner_marek@yahoo.de> (raw)
In-Reply-To: <200908261001.31814.sven.eckelmann@gmx.de>
On Wednesday 26 August 2009 16:01:27 Sven Eckelmann wrote:
> It is the name of the protocol and it doesn't make sense to have two
> complete different B.A.T.M.A.N. things with the exact name hanging around.
> One in the mainline kernel and one in here for layer 3 stuff. I have also
> personally a problem with the algorithm and the layer 3 protocol having the
> same name - but with completely different version numbering scheme.
You are right - the situation still is a bit messy. I think Andrew has a point
saying that "adv" might be rejected. I even could imagine that the name
"batman" causes some irritation. ;-)
A while back Justin Dean suggested a new name for the protocol:
stateless proactive adhoc networking protocol
Does not sound too bad in my opinion. Other opinions ?
> To the wiki stuff. The policy was long time correct if I remember it
> correct (send my first stuff without being subscribed). Maybe it was
> accidentally changed when the administrator upgraded the mailing list/mail
> stuff.
Yes, it was configured as described in the wiki but nobody was checking the
moderator requests which made the problem worse as some people thought their
mail will be handled at some point. Instead they were hanging there forever.
I just forgot to adjust the wiki.
> > Should /proc/net/batman-adv/interface be replaced with an IOCTL interface
> > similar to brctl?
>
> How to design the kernel<->userspace interface that it doesn't end like
> wireless-tools?
I'm not so familiar with the iwconfig situation you seem to refer to. Could you
outline the issues ?
> I found also some other things and also told that Marek - but I think that
> not everything was included in the patch I send some weeks ago. Maybe it
> was only to break printk statements to fit in 80 chars per line, but I am
> not sure right now.
Yes, you found a way to break a long string into smaller pieces although I
can't quite remember how you did it. ;-)
> And as my position as random guy I want to thank you for contacting Greg
> G-K
Thanks from me as well!
Regards,
Marek
next prev parent reply other threads:[~2009-08-26 8:51 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-26 6:41 [B.A.T.M.A.N.] List policy for none subscribers Andrew Lunn
2009-08-26 7:54 ` Marek Lindner
2009-08-26 8:27 ` Andrew Lunn
2009-08-26 8:01 ` Sven Eckelmann
2009-08-26 8:51 ` Marek Lindner [this message]
2009-08-26 10:47 ` [B.A.T.M.A.N.] Breaking long lines Andrew Lunn
2009-08-26 10:52 ` [B.A.T.M.A.N.] New name for batman-adv? Andrew Lunn
2009-08-27 9:58 ` Marek Lindner
2009-08-27 19:44 ` Andrew Lunn
2009-08-28 1:57 ` Outback Dingo
2009-08-28 3:08 ` Andrew de Andrade
2009-08-28 6:42 ` Antoine van Gelder
2009-10-09 18:57 ` Linus Lüssing
2009-08-26 11:01 ` [B.A.T.M.A.N.] Configuration interface Andrew Lunn
2009-08-27 13:57 ` [B.A.T.M.A.N.] List policy for none subscribers Bernd Petrovitsch
2009-08-26 9:19 ` elektra
2009-08-26 10:41 ` Andrew Lunn
2009-08-26 18:08 ` Andrew Lunn
2009-08-27 10:05 ` Marek Lindner
2009-08-27 11:10 ` elektra
2009-08-27 14:17 ` Andrew Lunn
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=200908261651.16980.lindner_marek@yahoo.de \
--to=lindner_marek@yahoo.de \
--cc=b.a.t.m.a.n@lists.open-mesh.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