Elektra, is it possible that you can update the batman package in the potato repository to OpenWRT trunk and build some potato packages for the vis server?
https://dev.openwrt.org/browser/packages/net/batman
Do you know who the maintainer is for the Ubuntu packaging?
Packages for generic Atheros routers can be found at:
http://downloads.afrimesh.org/stable/packages/mips/vis_r1439-1_mips.ipk
And Broadcom at:
http://downloads.afrimesh.org/stable/packages/mips/vis_r1439-1_mips.ipk
- antoine
--
http://7degrees.co.za
"Libré software for human education"
do you mean a vis server package to run on the MPs? Thats a simple matter of
issuing
opkg install
http://downloads.afrimesh.org/stable/packages/mips/vis_r1439-1_mips.ipk
(ought to be one line)
The open-mesh.net server always has the latest, they are build automatically.
I can include it into the VT build system as well. Vis is also included and
running in the VTSRV installation CD.
Cheers,
Elektra
> Hello Antoine -
>
> do you mean a vis server package to run on the MPs? Thats a simple matter of
> issuing
>
> opkg install
> http://downloads.afrimesh.org/stable/packages/mips/vis_r1439-1_mips.ipk
Oh cool, the vis package in the afrimesh repository was built against Kamikaze 8.09_2 stable - didn't realize they'd run okay on the MP, tx Elektra!
> The open-mesh.net server always has the latest, they are build automatically.
>
> I can include it into the VT build system as well.
Please do - there are some new afrimesh-* packages coming soon with vis as a dependency.
> Vis is also included and running in the VTSRV installation CD.
Awesome! :)
Speaking of, do you know who the maintainer is for the Ubuntu packaging of B.A.T.M.A.N. that we can get a .deb for vis in there too?
> On a related note, what is the work required from VT's perspective to
> include DNA as an option in the MP build?
in order to add DNA to the potato repository you can create a folder in the
"package" directory. We can move it later into a feed, but if you are in the
process of developing a package it is OK to start here. Then add a OpenWRT-
compatible Makefile to the newly created folder. As a starting point you can
use a Makefile from a existing package and customize it to your needs. When you
think it is worth a try you can start "make menuconfig", check if your package
pops up in the menu in the section you have choosen, enable it, build it.
make package/dna{clean,compile,install} V=99
For example libpcap's Makefile is not too complex:
#
# Copyright (C) 2006 OpenWrt.org
#
# This is free software, licensed under the GNU General Public License v2.
# See /LICENSE for more information.
#
# $Id: Makefile 12225 2008-08-06 22:10:29Z nbd $
include $(TOPDIR)/rules.mk
PKG_NAME:=libpcap
PKG_VERSION:=0.9.8
PKG_RELEASE:=1
PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.gz
PKG_SOURCE_URL:=http://www.tcpdump.org/release/
PKG_MD5SUM:=5208f24d0328ee7c20b52c43eaa9aa0e
include $(INCLUDE_DIR)/package.mk
define Package/libpcap
SECTION:=libs
CATEGORY:=Libraries
TITLE:=Low-level packet capture library
URL:=http://www.tcpdump.org/
endef
define Package/libpcap/description
This package contains a system-independent library for user-level network
packet capture.
endef
TARGET_CFLAGS += $(FPIC)
CONFIGURE_ARGS += \
--enable-shared \
--enable-static \
--disable-yydebug \
--enable-ipv6 \
--with-build-cc="$(HOSTCC)" \
--with-pcap=linux
define Build/Compile
$(MAKE) -C $(PKG_BUILD_DIR) \
CCOPT="$(TARGET_CFLAGS) -I$(BUILD_DIR)/linux/include" \
DESTDIR="$(PKG_INSTALL_DIR)" \
all install
endef
define Build/InstallDev
mkdir -p $(1)/usr/include
$(CP) $(PKG_INSTALL_DIR)/usr/include/pcap{,-bpf,-namedb}.h \
$(1)/usr/include/
mkdir -p $(1)/usr/lib
$(CP) $(PKG_INSTALL_DIR)/usr/lib/libpcap.{a,so*} \
$(1)/usr/lib/
endef
define Package/libpcap/install
$(INSTALL_DIR) $(1)/usr/lib
$(CP) $(PKG_INSTALL_DIR)/usr/lib/libpcap.so.* $(1)/usr/lib/
endef
$(eval $(call BuildPackage,libpcap))
Cheers,
Elektra
You're dead right. The website has been in need of an improved
structure for finding information for some time now and not just for
developers. Unfortunately it has been pushed out of the way by other
issues but is reaching the point where it can't be ignored.
Thanks for the gentle prod. A better section for developers is a good
place to start.
A couple of questions for everyone. 1) Is there other information
you have searched for on the VT site that you have found to be a pain
to locate? 2) Are there things that should obviously be on the home
page or within 1-2 clicks that aren't there?
Thanks... Steve
On 31 July 2010 13:16, Paul Gardner-Stephen
> --
> You received this message because you are subscribed to the Google Groups "village-telco-dev" group.
> To post to this group, send email to village-...@googlegroups.com.
> To unsubscribe from this group, send email to village-telco-...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/village-telco-dev?hl=en.
>
>
--
Steve Song
Telecommunications Fellow, Shuttleworth Foundation
email: steve...@shuttleworthfoundation.org
work: +27 21 970 1220
mobile: +27 83 482 2088
skype: steve_l_song
blog: http://manypossibilities.net
twitter: stevesong
Nope, I know where everything is :-)
Seriously, yes the wiki was built in layers over time as we worked on
one project after another. It now needs a re-org with respect to
current needs. Old stuff needs to be filed away with contextual notes,
i.g. "this page documented MP Phase 2 in 2009 and is no longer up to
date but is provided for historical reasons".
> 2) Are there things that should obviously be on the home
> page or within 1-2 clicks that aren't there?
Yes I have that problem. A lot of stuff seems to need several redundant
clicks to get to.
- David
There are some challenging assumptions about sustainability in the
spreadsheet that are worth exploring.
My own take on this is that there are currently so many variables
that, at the moment, any VT business model is at best speculative.
Our chief goal now is to get some networks into technical AND
financial operation in order to iterate the business model as quickly
as possible based on real world scenarios.
Cheers... Steve
>> village-telco-...@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/village-telco-dev?hl=en.
>>
>>
>
>
>
> --
> Steve Song
> Telecommunications Fellow, Shuttleworth Foundation
>
> email: steve...@shuttleworthfoundation.org
> work: +27 21 970 1220
> mobile: +27 83 482 2088
> skype: steve_l_song
> blog: http://manypossibilities.net
> twitter: stevesong
>
> --
> You received this message because you are subscribed to the Google Groups
> "village-telco-dev" group.
> To post to this group, send email to village-...@googlegroups.com.
> To unsubscribe from this group, send email to
> village-telco-...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/village-telco-dev?hl=en.
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "village-telco-dev" group.
> To post to this group, send email to village-...@googlegroups.com.
> To unsubscribe from this group, send email to
> village-telco-...@googlegroups.com.