public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
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@open-mesh.net>
Subject: Re: [B.A.T.M.A.N.] maybe some reason
Date: Mon, 18 Jun 2007 15:43:53 +0200	[thread overview]
Message-ID: <200706181543.53498.lindner_marek@yahoo.de> (raw)
In-Reply-To: <1D2535A1-F70E-46F3-B24F-A12C33DCC097@port-x.de>


Hi,

> i'think about some smal tool ... or batmand have this option to
> update himself. for example the option batmand -vn,  he look every day
> for a new stable version ... or some seperat tool ... what can update
> a lot nodes ... to do this bei manual is grrrr ....
>
> it's only some idea.

an integrated auto-update mechanism is difficult because we have many batman 
users outside of Germany. Should they all update via open-mesh ? On the other 
hand may be they don't want to have the latest version because they are happy 
with what they have. Or they want to test it before the whole network 
updates.
I better solution would be a custom skript which checks for updates and logs 
into the router via SSH to install it. Axel wrote such a script. I think he 
could give it to you.
Is it worth considering to publish it on open-mesh ?


> so, some other info ... the batman net run here nice ... only the
> gatway get a lot of cpu work ... sometimes it's grow up
> to 80% ... but it's working. i'wait for the version what made the
> routing on layer 2 ... and  i'will fast roll out it.

I hope you take some time to test it before you that or your users may become 
unhappy.  ;-)

Regards,
Marek

  reply	other threads:[~2007-06-18 13:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-16 14:26 [B.A.T.M.A.N.] maybe some reason Mario Roeber
2007-06-18 13:43 ` Marek Lindner [this message]
2007-06-24 14:24   ` Marek Lindner

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=200706181543.53498.lindner_marek@yahoo.de \
    --to=lindner_marek@yahoo.de \
    --cc=b.a.t.m.a.n@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