From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-21-ewr.dyndns.com (mxout-060-ewr.mailhop.org [216.146.33.60]) by lists.bufferbloat.net (Postfix) with ESMTP id 9DD2B2E0132 for ; Thu, 7 Apr 2011 18:42:09 -0700 (PDT) Received: from scan-21-ewr.mailhop.org (scan-21-ewr.local [10.0.141.243]) by mail-21-ewr.dyndns.com (Postfix) with ESMTP id BC983158C for ; Fri, 8 Apr 2011 01:42:08 +0000 (UTC) X-Spam-Score: 0.0 () X-Mail-Handler: MailHop by DynDNS X-Originating-IP: 130.207.199.162 Received: from relay1.gtri.gatech.edu (relay3.gtri.gatech.edu [130.207.199.162]) by mail-21-ewr.dyndns.com (Postfix) with ESMTP id EC37D252 for ; Fri, 8 Apr 2011 01:42:01 +0000 (UTC) Received: from aeatlgtrmfe3.gtri.ext (unknown [130.207.199.225]) by relay1.gtri.gatech.edu (Spam & Virus Firewall) with ESMTP id D1419C3BA5A; Thu, 7 Apr 2011 21:42:00 -0400 (EDT) Received: from aeatlgtrmfe3.gtri.ext ([130.207.199.225]) by relay1.gtri.gatech.edu with ESMTP id XyMBAW5ZZEEn2pmd; Thu, 07 Apr 2011 21:41:58 -0400 (EDT) Received: from AEATLGTRMBX01.gtri.ext ([fe80::e559:bd84:4baa:c5d]) by aeatlgtrmfe3.gtri.ext ([2002:82cf:c7e1::82cf:c7e1]) with mapi; Thu, 7 Apr 2011 21:42:00 -0400 From: "Poole, Brian" To: Dave Taht , "bismark-devel@lists.bufferbloat.net" Thread-Topic: [Bismark-devel] bismark software package requirements Thread-Index: AQHL9YpuLsaJV7oRsk6jkCrCJYJTXpRTLiIQ Date: Fri, 8 Apr 2011 01:41:59 +0000 Message-ID: References: <4D9E6195.8040602@taht.net> In-Reply-To: <4D9E6195.8040602@taht.net> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Mailman-Approved-At: Thu, 07 Apr 2011 18:45:06 -0700 Subject: Re: [Bismark-devel] bismark software package requirements X-BeenThere: bismark-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: BISMark related software development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Apr 2011 01:42:10 -0000 Well, I got the first bismark package (and the custom feed) setup. It's ugl= y (very ugly) but I'm getting a handle on the package building system so it= should shape up pretty quickly.=0A= =0A= I foresee splitting off the D-ITG & shaperprobe into their own package and = just adding dependencies to reduce the complexity of the bismark package. W= e'll probably ultimately also have a few bismark-* pkgs rather than just on= e to allow for different levels of participation but that can be thought ab= out a little later.=0A= =0A= Walter, what about the tar that Sri built was wrong? I would like to get th= e packages further along tomorrow and knowing that will help. I did see a c= ouple of symlinks (rather than original files) were packed in the keys and = that there are some non-essential ITG binaries included. Were there other p= roblems? =0A= =0A= Also, I think moving /root/scripts/* and /root/bin/* into /usr/bin or /usr/= sbin as appropriate would be a good idea. Other than a few path updates I c= an't imagine this causing much of a problem. Opinions? Any scripts/binaries= that you know would be sbin versus bin?=0A= =0A= Finally, I'm guessing that the authorized_keys and known_hosts will probabl= y be moved from the bismark svn to the source control for the custom feed. = This is because we don't want to just copy those files in (might overwrite = what the user already had) but rather concatenate the keys dynamically as p= art of a post-install process for the package. I'm not 100% on this yet as = I haven't played with the post-install but I encountered a similar situatio= n with /etc/rc.local (which was already being provided by another core pack= age.)=0A= =0A= Brian=0A= =0A= ________________________________________=0A= From: bismark-devel-bounces@lists.bufferbloat.net [bismark-devel-bounces@li= sts.bufferbloat.net] on behalf of Dave Taht [d@taht.net]=0A= Sent: Thursday, April 07, 2011 9:15 PM=0A= To: bismark-devel@lists.bufferbloat.net=0A= Subject: [Bismark-devel] bismark software package requirements=0A= =0A= I put the details on the wndr up on the wiki. All members of this=0A= project have wiki editing privs,=0A= so if there is a procedure you can document or a bug you have to file,=0A= please do so.=0A= =0A= http://www.bufferbloat.net/projects/bismark/wiki/Wndr3700=0A= =0A= libstdcpp is a package requirement for the bismark software according to ld= d=0A= =0A= root@OpenWrt:/etc/bismark/bin# ldd ./ITGSend=0A= libpthread.so.0 =3D> /lib/libpthread.so.0 (0x2b6fc000)=0A= libstdc++.so.6 =3D> /usr/lib/libstdc++.so.6 (0x2b720000)=0A= libm.so.0 =3D> /lib/libm.so.0 (0x2b7fe000)=0A= libgcc_s.so.1 =3D> /lib/libgcc_s.so.1 (0x2b822000)=0A= libc.so.0 =3D> /lib/libc.so.0 (0x2b844000)=0A= libdl.so.0 =3D> /lib/libdl.so.0 (0x2b8a9000)=0A= ld-uClibc.so.0 =3D> /lib/ld-uClibc.so.0 (0x2b6e4000)=0A= =0A= And bash is also a requirement at the present time (it is not in the=0A= default image, but is built)=0A= =0A= How to create a feed is documented here=0A= =0A= http://wiki.openwrt.org/doc/devel/feeds=0A= =0A= There should probably be a bismark-all meta package...=0A= =0A= http://www.bufferbloat.net/issues/64=0A= =0A= And multiple other issues are on the issue tracker.=0A= =0A= _______________________________________________=0A= Bismark-devel mailing list=0A= Bismark-devel@lists.bufferbloat.net=0A= https://lists.bufferbloat.net/listinfo/bismark-devel=0A=