Re: [Barry-devel] Barry Plugin Availability?

[Niels de Vos]

On Mon, Mar 30, 2009 at 12:57 PM, Martin Owens  wrote:
> Did you install a newer version of OpenSync? because is where your
> problem is going to be. I believe barry only supports opensync 0.2x
> right now.

Fedora used to deliver opensync-0.38 something. Just last week it was
decided to go back to a stable 0.22 release:


Kind regards,
Niels

--
___
Barry-devel mailing list
Barry-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/barry-devel

Re: [Barry-devel] kernel driver notes

[Niels de Vos]

Hi Rick,

On Sat, Nov 8, 2008 at 10:14 AM, Rick Scott <[EMAIL PROTECTED]> wrote:
> On Fri, 2008-11-07 at 21:59 -0500, Chris Frey wrote:
>> On Fri, Nov 07, 2008 at 08:04:54PM -0500, Rick Scott wrote:
>> > > I grabbed your latest CVS and noticed you added ifdefs.  I was still 
>> > > having
>> > > trouble compiling against 2.6.26.5, so I'm moving the crypto stuff into
>> > > its own API... I think we only need sha1 right?
>> >
>> > That's all I know about, so far :)
>>
>> Me too. :-)
>>
>> In going through the module, and working on getting it to compile, I
>> was wondering what your plans are for it.  Are you planning to eventually
>> include it in the main kernel?  If so, perhaps it is not worth it to
>> work so hard to support all possible kernels, and focus should be on
>> supporting the latest kernel, and using the kernel coding style guidelines.
>>
>> - Chris
>
> Plans? I plan on using it, and learning a little more about the kernel.
> I don't want to rule out the possibility of it being in the main kernel.
> If it does get to the main kernel, someone else would probably take care
> of little changes, like the URB callback stuff. That would be nice :)
> With all of the #ifdef's creeping in, I'm thinking of doing some
> autoconf macros to spot the differences and using #ifdef HAVE_xxx
> instead of having to figure out the correct kernel version for these
> things. Should be able to get the info from the headers  I started
> out trying automake, but it was insisting on things that didn't work
> with a kernel Makefile :( It should be doable with autoconf though.

Inclusion in main-line should be the target imho. I would also be able
to do some reviewing if you like. I'm not that senior in the
linux-kernel, but I'm working with usb-drivers too.

Instead of working with #ifdef in the main sources for version
checking, I would recommend a compatibility header. Only use the
new/current kernel funtions, backport/fake them in a header which can
be included on the command-line. Same trick does madwifi with
compat..h (http://madwifi-project.org/browser/madwifi/trunk/include/compat.h)
and 'gcc -include  ...'.


> In the short term, it _has_ to work with my Fedora Core [34] and CentOS
> 5.2 boxes, along with my 8800. I have a 6200, 7100, 8700, and 8800 that
> I test with. Oh, and a 6710 which is not relevant for the module but is
> my "gold standard" for the serial protocol, along with the rfcomm
> bluetooth of the newer devices.

Using the same distros here, but I also have the current git-tree of
the kernel for compiling against.

Please let me know if I can be of any help. (Where are the sources exactly?)

Cheers,
Niels

-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
Barry-devel mailing list
Barry-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/barry-devel

Re: [Barry-devel] Putting bcharge -o in pppd script init option

[Niels de Vos]

Hello Julian,

On Mon, Nov 3, 2008 at 8:37 PM, Julian Rush <[EMAIL PROTECTED]> wrote:
...
> But over the USB cable it's been a struggle.
>
...
>
> However, running 'bcharge -o' to force serial mode, and running pppob
> with -s I can connect to the internet OK and repeatedly.
>
> Two questions: first, just to make life a little easier really, can I
> put 'bcharge -o' into the pppd script using pppd's init option, given
> it's benign if repeated?  The man page suggests pppd runs the init
> command in a shell to set up the serial link before running the connect
> script.  Though if the pty option has already grabbed the serial line,
> then I guess it won't fly?

Instead of putting it in the chat-script, you might want to set the option in
/etc/udev/rules.d/10-blackberry.rules.
These rules are executed when the blackberry is connected.

Hope that helps,
Niels

-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
Barry-devel mailing list
Barry-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/barry-devel

Re: [Barry-devel] FC10 & Barry -- USB Chargin

[Niels de Vos]

Hello Chris,

On Mon, Oct 20, 2008 at 3:49 AM, Christopher Stover
<[EMAIL PROTECTED]> wrote:
>
> I just built RPMs for FC10 beta (Rawhide) and USB charging appears to be 
> working.  I receive the charging symbol when I plug in my Sprint BB Pearl 
> 8130.  However, when I plug it in, it prompts me about using it as a mass 
> storage device, I then see a message saying the USB charging current isn't 
> sufficient, then it goes away and is replaced by the message about using it 
> as a mass storage device again.  Is there any way to test the current of the 
> USB port with software so I can make sure it really is getting what it needs?

You can check this with /sbin/lsusb -v'. See the MaxPower attribute of
the device.

(Sorry, but I can't help you with the other questions...)

Niels

-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
Barry-devel mailing list
Barry-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/barry-devel

Re: [Barry-devel] [Announce] Binary packages available via OpenSUSE Build Service

[Niels de Vos]

Hello,

On Sat, Aug 23, 2008 at 4:06 AM, Chris Frey <[EMAIL PROTECTED]> wrote:
> Binary packages for the latest Barry release will be maintained here,
> as well as periodic dated snapshots of CVS, to make it easier for users
> to test and follow along with development.
>
> Currently, binary packages are available in 32bit and 64bit versions,
> for the following distros:
>
>CentOS 5

I'm using the .repo-file for CentOS and installing over YUM works.
However I noticed the version of libtar provided by RPMForge does not
provide a libtar.so. Installing the libtar from EPEL solved this
problem. All other dependencies were satisfied by RPMForge and the
standard CentOS repositories.

Now I'm running barry-gui-0.14-cvs20080823 which does not detect my
Pearl 8100 :( Bcharge does seem to find my BB as it's charging without
warning. Any ideas?

Furthermore I noticed that mounting and charging at the same time
works under Windows. Are there any pointers why this would not work
with barry?

Thanks,
Niels

-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
Barry-devel mailing list
Barry-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/barry-devel

Re: [Barry-devel] Various synching problems

[Niels de Vos]

Hello Richard,

On Sat, Aug 16, 2008 at 9:45 AM, Richard Esplin <[EMAIL PROTECTED]> wrote:
> 1. Barry doesn't talk to my device when I'm plugged in through a USB hub. I
> bought a D-Link powered 7 port USB 2.0 hub (DUB-H7), and when I plug my BB
> into it the device says "connecting to computer" without the picture, and it
> just hangs. I had to remove the battery to get it to be responsive again.
> btool just hangs as well. It won't respond to ctr-c until after I've
> unplugged the device.
>
> Workaround: plug directly into the computer--don't use a hub.

Might be related (or the same) to a bug in the Red Hat Bugzilla:
https://bugzilla.redhat.com/show_bug.cgi?id=379341

I think it was discussed on this mailinglist a while ago.
Unfortunately I can't remember what the outcome or solution was,
should be in the archives though.

Cheers,
Niels

-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
Barry-devel mailing list
Barry-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/barry-devel

Re: [Barry-devel] Blackberry 8120 not recognised

[Niels de Vos]

On Sun, Aug 10, 2008 at 12:51 PM, Rick Scott
<[EMAIL PROTECTED]> wrote:
> On Sun, 2008-08-10 at 12:40 +0200, Niels de Vos wrote:
>> On Sun, Aug 10, 2008 at 12:10 PM, David Harper <[EMAIL PROTECTED]> wrote:
>> > Thanks Niels
>>
>> You're welcome :)
>>
>>
>> > Well, I've just tried again and the 8120 is not recognised whether the SD
>> > card is mounted or not. I checked  /proc/bus/usb/devices and the file is
>> > zero bytes in both circumstances.
>
> The file size will always be zero, it's not really a file. Just cat it,
> don't look at the size, or use lsusb.

Yes, of course. But the version of lsusb on my system does
unfortunately not display any driver information.


> Isn't the 8120 one of the models with the different product ID, not
> recognized by a barry that old?

Oh, didn't notice it was version 0.12-1... So, what about trying the
latest version, binaries available from
<http://download.opensuse.org/repositories/home:/ndprojects/>.

Cheers, Niels

-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
Barry-devel mailing list
Barry-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/barry-devel

Re: [Barry-devel] Blackberry 8120 not recognised

[Niels de Vos]

On Sun, Aug 10, 2008 at 12:10 PM, David Harper <[EMAIL PROTECTED]> wrote:
> Thanks Niels

You're welcome :)


> Well, I've just tried again and the 8120 is not recognised whether the SD
> card is mounted or not. I checked  /proc/bus/usb/devices and the file is
> zero bytes in both circumstances.

Hmm, it could be that Ubuntu doesn't mount /proc/bus/usb by default.
You can try to mount it manually (as root):
mount -t usbfs usbfs /proc/bus/usb

In CVS on http://barry.cvs.sourceforge.net/barry/barry/contrib/ there
is a shellscript (barry-unbind-storage.sh) what the
unbinding/disconnecting of the phone from the usb_storage-driver. For
me this helps sometimes, but for some reason I do not always need
it...

Good luck, Niels

> Cheers - Dave
>
> 2008/8/10 Niels de Vos <[EMAIL PROTECTED]>
>>
>> Hello Dave,
>>
>> On Sun, Aug 10, 2008 at 1:02 AM, David Harper <[EMAIL PROTECTED]>
>> wrote:
>> > I have a 8120 through Telefonica in Spain. I run Ubuntu Hardy 8.10,
>> > Barry
>> > version 0.12-1 Blackberry OS 4.3. Installation was OK but the 8120 was
>> > not
>> > found even though it is mounted and I can communicate with it via file
>> > manager (and also with GPodder).
>>
>> Your BlackBerry can (for now?) only fullfill one function at a time.
>> So, if the SD-card is mounted, you can not use the barry-tools. You
>> should make clear no driver is connected to the USB-interfaces of your
>> phone. You would probably see that one of the USB-interfaces of your
>> phone is connected to the usb_storage driver (you can find this
>> information in /proc/bus/usb/devices). The barry-tools try to
>> disconnect the device from the usb_storage driver, however this will
>> fail if the SD-card is mounted.
>>
>> So, please try the barry-tools again after unmounting the SD-card.
>>
>> Hope that helps,
>> Niels
>>
>> -
>> This SF.Net email is sponsored by the Moblin Your Move Developer's
>> challenge
>> Build the coolest Linux based applications with Moblin SDK & win great
>> prizes
>> Grand prize is a trip for two to an Open Source event anywhere in the
>> world
>> http://moblin-contest.org/redirect.php?banner_id=100&url=/
>> ___
>> Barry-devel mailing list
>> Barry-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/barry-devel
>
>
> -
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great
> prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> ___
> Barry-devel mailing list
> Barry-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/barry-devel
>
>

-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
Barry-devel mailing list
Barry-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/barry-devel

Re: [Barry-devel] Blackberry 8120 not recognised

[Niels de Vos]

Hello Dave,

On Sun, Aug 10, 2008 at 1:02 AM, David Harper <[EMAIL PROTECTED]> wrote:
> I have a 8120 through Telefonica in Spain. I run Ubuntu Hardy 8.10, Barry
> version 0.12-1 Blackberry OS 4.3. Installation was OK but the 8120 was not
> found even though it is mounted and I can communicate with it via file
> manager (and also with GPodder).

Your BlackBerry can (for now?) only fullfill one function at a time.
So, if the SD-card is mounted, you can not use the barry-tools. You
should make clear no driver is connected to the USB-interfaces of your
phone. You would probably see that one of the USB-interfaces of your
phone is connected to the usb_storage driver (you can find this
information in /proc/bus/usb/devices). The barry-tools try to
disconnect the device from the usb_storage driver, however this will
fail if the SD-card is mounted.

So, please try the barry-tools again after unmounting the SD-card.

Hope that helps,
Niels

-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
Barry-devel mailing list
Barry-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/barry-devel

Re: [Barry-devel] Barry version 0.13 released - RHEL5/CentOS-5 Packages

[Niels de Vos]

On Fri, Aug 1, 2008 at 1:49 AM, Chris Frey <[EMAIL PROTECTED]> wrote:
> On Thu, Jul 31, 2008 at 11:02:01PM +0200, Niels de Vos wrote:
>> > So if I can get this working, this should be a great boon to usability. :-)
>>
>> That would be great! I'll keep an eye on these builds when they come out.
>
> The binary packages will slowly appear at this URL, as I keep working
> on them.  Once I'm happy with it, I'll post an announcement.
>
>http://download.opensuse.org/repositories/home:/ndprojects/
>
> Once version 0.13 is building, I hope to add another build for CVS,
> so that there will be a set of binary packages that follow along for
> the latest CVS as well.  :-)

That would be great, as I can't create the src.rpm on CentoOS as
autoconf and/or friends are too old.


>> It's the first in the list on
>> http://wiki.centos.org/AdditionalResources/Repositories :) There is a
>> new ongoing effort to get more packagers to work together. This
>> project runs under http://rpmforge.net.
>
> OpenSUSE Build Service only has the base CentOS install, so I may need
> to grab some of the source packages from there to complete the build.

It would also be possible to get barry into RPMForge. The barry users
only need to configure one additional repository and not RPMForge+OBS.


> Since CentOS has no opensync at all, maybe I can add those packages
> to OBS as well.  The only reason Fedora 9 isn't supported for opensync
> is that they have a conflicting version.

Yes, I understood. But as CentOS (or RPMForge) does not have opensync
(yet?), I never used barry-opensync, so I won't miss it... I don't
know how others are feeling about this, but I think getting opensync
on RHEL/CentOS is not part of your work as barry developer ;)

Thanks, Niels

-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
Barry-devel mailing list
Barry-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/barry-devel

Re: [Barry-devel] Barry version 0.13 released - RHEL5/CentOS-5 Packages

[Niels de Vos]

Hi Chris,

On Thu, Jul 31, 2008 at 10:05 PM, Chris Frey <[EMAIL PROTECTED]> wrote:
> On Wed, Jul 30, 2008 at 11:52:07PM +0200, Niels de Vos wrote:
>> Attached patch was used to create CentOS-5 RPMs. I've taken the
>> fc8.src.rpm and changed one line in the spec-file. There is no
>> opensync on CentOS-5 nor RHEL-5. Therefore it is disabled like it is
>> done for Fedora 9. I've built the RPMs with mock against the latest
>> updates and RPMForge-repository (needed for gtkmm24 and libglademm24:
>> http://wiki.centos.org/AdditionalResources/Repositories/RPMForge).
>
> Thanks for posting the patch!

You're welcome.


> I've been working on getting Barry 0.13 released via the OpenSUSE Build
> Service.  They have an impressive list of distros there, including RHEL4,
> RHEL5, CentOS 5, SLES9, SLE10, Debian Etch, Ubuntu 6.06 to 8.04, Mandriva
> 2007 and 2008, Fedora 8 and 9, and OpenSUSE 10.2 10.3 and 11.0.
>
> And these build for i586 and x86_64.

Hmm, RHEL/CentOS don't really do i586, they use i386 instead...


> So if I can get this working, this should be a great boon to usability. :-)

That would be great! I'll keep an eye on these builds when they come out.


> As you're a CentOS user, I can pump you for info... How do you choose
> extra repositories with CentOS, and what makes you choose RPMForge over,
> say, centos.karan.org?

It's the first in the list on
http://wiki.centos.org/AdditionalResources/Repositories :) There is a
new ongoing effort to get more packagers to work together. This
project runs under http://rpmforge.net.


>> The RPMs for i386 and x86_64 are available on my homepage:
>> http://www.nixpanic.net/software/packages
>> Please notify me if there are any problems regarding these packages.
>
> Thanks for posting these.  I don't have a CentOS system, so I can't test.

No problem. I just hope it'll be easier to get barry on RHEL/CentOS
without rebuilding. It's not a problem for me, but possibly for
others. Of course it would be even better to get barry into the Fedora
Extras+EPEL. That way it's available out of the box for any Red Hat
(or derived distribution) user.

Cheers,
Niels

-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
Barry-devel mailing list
Barry-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/barry-devel

Re: [Barry-devel] Barry version 0.13 released - RHEL5/CentOS-5 Packages

[Niels de Vos]

Hi,

On Wed, Jul 30, 2008 at 10:25 PM, Chris Frey <[EMAIL PROTECTED]> wrote:
> At long last, Barry version 0.13 is here!

Great work again, thanks! :D

> Binary packages are available for Debian stable; Ubuntu 7.10 and 8.04;
> Fedora 7, 8, and 9; and OpenSUSE 10.2.  Source packages are available in
> Debian, RPM, and tarball formats.

Attached patch was used to create CentOS-5 RPMs. I've taken the
fc8.src.rpm and changed one line in the spec-file. There is no
opensync on CentOS-5 nor RHEL-5. Therefore it is disabled like it is
done for Fedora 9. I've built the RPMs with mock against the latest
updates and RPMForge-repository (needed for gtkmm24 and libglademm24:
http://wiki.centos.org/AdditionalResources/Repositories/RPMForge).

The RPMs for i386 and x86_64 are available on my homepage:
http://www.nixpanic.net/software/packages
Please notify me if there are any problems regarding these packages.

Cheers,
Niels
Index: rpm/barry.spec
===
RCS file: /cvsroot/barry/barry/rpm/barry.spec,v
retrieving revision 1.34
diff -u -r1.34 barry.spec
--- rpm/barry.spec	25 Jul 2008 03:35:54 -	1.34
+++ rpm/barry.spec	30 Jul 2008 21:17:04 -
@@ -2,7 +2,8 @@
 %define with_gui 1
 
 # Fedora 9 doesn't support opensync 0.22
-%if 0%{?fc9}
+# RHEL/CentOS do not have opensync at all (even even in rpmforge)
+%if 0%{?fc9}%{?rhel}
 	%define with_opensync 0
 %else
 	%define with_opensync 1
-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/___
Barry-devel mailing list
Barry-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/barry-devel

Re: [Barry-devel] [SCRIPT] Disconnecting from usb-storage, but keep it loaded

[Niels de Vos]

On Fri, Jul 25, 2008 at 6:15 AM, Chris Frey <[EMAIL PROTECTED]> wrote:
> On Thu, Jul 17, 2008 at 10:38:21AM +0200, Niels de Vos wrote:
>> Well, I run it manually and start bcharge/btool after that. It would
>> also be possible to change the udev-rules to start the script
>> too/instead/before bcharge. However I also do think it would be most
>> convenient if libbarry provides comparable functions (or handle it
>> automagically).
>
> In the interest of getting version 0.13 released soon, I'm adding the
> script to contrib/ for now.  We can work on better integration for 0.14,
> which hopefully won't take as long as 0.13 has. :-)
>
> Thanks again!

Thank YOU for including it :)

-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
Barry-devel mailing list
Barry-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/barry-devel

Re: [Barry-devel] [RFC] Make barry utilities setuid?

[Niels de Vos]

Okay, making barry setuid just got dropped from my list :)

Thanks for the very detailed explanations!

Niels


On Thu, Jul 17, 2008 at 8:02 PM, Chris Frey <[EMAIL PROTECTED]> wrote:
> On Thu, Jul 17, 2008 at 05:27:38PM +0200, Niels de Vos wrote:
>> Hello,
>>
>> attached is a patch for the specfile for setting the setuid-bit on
>> some executables. It would be really cool if a normal (non-root) user
>> is able to use the barry utilities.
>> This patch only displays what could be done in the specfile to achieve
>> this. As some execuatbles read/write files, this is very dangerous at
>> the moment; any user would get root-rights for reading/writing files.
>>
>> I would like to compose a TODO-list with:
>> * how to make an executable secure?
>> * which binaries should be secure?
>> * does barrybackup call other binaries or does it use libbarry?
>> * ...
>>
>> Any thoughts?
>
> Hi Niels,
>
> Of your proposed list of binaries, here's my reasoning regarding each one:
>
> bcharge
>
>There are 2 jobs that need to be done when plugging a Blackberry
>into the system:  1) change the mode and have it reset itself so
>that charging is possible, and 2) set the device permissions so that
>other programs can access the device without root privileges.
>
>Option 1 is performed by bcharge, and should be done automatically
>by udev.  Option 2 is already handled by udev rules.  So there is
>no need for bcharge to be setuid root.
>
> breset
>
>If bcharge is setup correctly as above, you can reset your device
>without being root, so setuid root is not needed here either.
>
> pppob
>
>This program is really only called by pppd, which is already setuid
>root on many systems.  Even so, pppob talks to the Blackberry the
>same way that any other Barry program does, and if bcharge and udev
>are setup correctly, there is no need for setuid root.
>
> bidentify
>
>This is a helper program to identify what Blackberry devices are
>attached to the system.  It was added for Martin Owens and his
>device identification system.  I believe this could be called via
>HAL or similar, or just any curious user can call it.  If it is
>called before bcharge, then you need to be root, and if it is part
>of a system configuration process, then the calling system is
>likely root as well.  If bcharge is setup correctly, bidentify
>does not need setuid root anyway.
>
> btool
> brecsum
> upldif
> barrybackup
>
>All of these programs are user level programs. (I realize your spec
>file patch did not include barrybackup as setuid.)  As such,
>they are intended to be run as a non-root user, and any need for
>root privileges is bug in your system's setup, and should be
>addressed by changing the udev rules and how bcharge is called.
>There's no need or intent to add setuid root for these programs.
>
>
> Comments on your TODO list:
>
>> * how to make an executable secure?
>
> This is a tricky task, and best left to the Wietse Venema's and
> Daniel Bernsteins of the world. *wink, wink, nudge, nudge* :-)
>
> Seriously though, to make a program ripe for setuid root privileges,
> it needs to be as simple as possible, as small as possible, focused in
> its task, and peer reviewed.
>
> Currently none of the above programs meet that criteria, except maybe
> breset, which is a really simple program using libusb.  Bcharge is fairly
> simple, but it supports a command line option to write to sysfs to adjust
> autosuspend settings, which would either need to be removed, or have
> a special case.  And the more special cases you put in, the harder it is
> to secure a program.
>
>
>> * which binaries should be secure?
>
> They should all be secure for the target environment they are running in.
> I'm specifically aiming for no program to need to run as root, except
> bcharge, and that is run automatically in a very defined way, by udev,
> so is already fairly secure.
>
>
>> * does barrybackup call other binaries or does it use libbarry?
>
> Barrybackup uses libbarry.  All the above programs use libbarry except
> bcharge and breset.
>
> - Chris
>
>
> -
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the w

[Barry-devel] [RFC] Make barry utilities setuid?

[Niels de Vos]

Hello,

attached is a patch for the specfile for setting the setuid-bit on
some executables. It would be really cool if a normal (non-root) user
is able to use the barry utilities.
This patch only displays what could be done in the specfile to achieve
this. As some execuatbles read/write files, this is very dangerous at
the moment; any user would get root-rights for reading/writing files.

I would like to compose a TODO-list with:
* how to make an executable secure?
* which binaries should be secure?
* does barrybackup call other binaries or does it use libbarry?
* ...

Any thoughts?

Niels
diff --git a/rpm/barry.spec b/rpm/barry.spec
index 3e241ef..abb1033 100644
--- a/rpm/barry.spec
+++ b/rpm/barry.spec
@@ -185,14 +185,14 @@ cd ../
 
 %files util
 %defattr(-,root,root)
-%attr(0755,root,root) %{_sbindir}/bcharge
-%attr(0755,root,root) %{_sbindir}/breset
-%attr(0755,root,root) %{_sbindir}/pppob
-%attr(0755,root,root) %{_bindir}/btool
+%attr(4755,root,barry) %{_sbindir}/bcharge
+%attr(4755,root,barry) %{_sbindir}/breset
+%attr(4755,root,barry) %{_sbindir}/pppob
+%attr(4755,root,barry) %{_bindir}/btool
 %attr(0755,root,root) %{_bindir}/bs11nread
-%attr(0755,root,root) %{_bindir}/bidentify
-%attr(0755,root,root) %{_bindir}/brecsum
-%attr(0755,root,root) %{_bindir}/upldif
+%attr(4755,root,barry) %{_bindir}/bidentify
+%attr(4755,root,barry) %{_bindir}/brecsum
+%attr(4755,root,barry) %{_bindir}/upldif
 %attr(0755,root,root) %{_bindir}/bktrans
 %attr(0755,root,root) %{_bindir}/btranslate
 %attr(0644,root,root) %{_mandir}/man1/btool*
@@ -235,6 +235,13 @@ cd ../
 [ "%{buildroot}" != "/" ] && %{__rm} -rf %{buildroot}
 [ "%{barryroot}" != "/" ] && %{__rm} -rf %{barryroot}
 
+%pre util
+if ! getent group barry > /dev/null
+then
+	groupadd -r barry
+fi
+exit 0
+
 %post -n libbarry
 /sbin/ldconfig
 
@@ -242,6 +249,10 @@ cd ../
 /sbin/ldconfig
 
 %changelog
+* Thu Jul 17 2008 Niels de Vos <[EMAIL PROTECTED]>
+- create system group barry in %pre
+- set setuid bit on some executables for group barry
+
 * Thu May 29 2008 Chris Frey <[EMAIL PROTECTED]> 0.13-1
 - version bump
 - added brecsum
-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/___
Barry-devel mailing list
Barry-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/barry-devel

Re: [Barry-devel] [SCRIPT] Disconnecting from usb-storage, but keep it loaded

[Niels de Vos]

On Wed, Jul 16, 2008 at 9:17 PM, Chris Frey <[EMAIL PROTECTED]> wrote:
> On Tue, Jul 15, 2008 at 12:20:50AM +0200, Niels de Vos wrote:
>> just hacked a little script together which uses the sysfs-structure
>> for finding any BlackBerries (well, at least my BB8100). After some
>> small sanity checks the script disconnects the BlackBerry from
>> usb-storage using the 'unbind' file.
>
> Thanks Niels!
>
> This is an improvement over dropping usb_storage in the module blacklist.

That's the point. Still only roughly tested though. Someone already
mentioned it some months ago in this thread, I just kept on thinking
about it :)
...searching archive... It was Martin Owens:
<http://sourceforge.net/mailarchive/message.php?msg_id=69ff73b20710091437r1335496am691a4ea2054eb754%40mail.gmail.com>


>> Instead of a script, it would of course also be possible to add a
>> C/C++-function to libbarry. The logic is pretty straight forward,
>> however writing it in C/C++ would require quite some more lines ;) For
>> the adventurous wanting to write this code, please see these notes
>> about _not_ using libsysfs:
>> <http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=Documentation/filesystems/sysfs.txt>.
>
> Is this the document you meant to link to?  I didn't see any mention
> of libsysfs.

You're right, it should be
<http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=Documentation/sysfs-rules.txt>.


>> I hope this script helps somebody and explains a bit more how
>> usb-storage can be kept loaded while using barry. I provide this
>> script for inclusion in barry as utility, testcase and/or
>> documentation. Have fun wit it!
>
> Do you run this manually, or do you launch it via hal or udev?
> It would be nice to include this as an optional(?) feature in the binary
> packages, and have this run automatically.

Well, I run it manually and start bcharge/btool after that. It would
also be possible to change the udev-rules to start the script
too/instead/before bcharge. However I also do think it would be most
convenient if libbarry provides comparable functions (or handle it
automagically).

Niels

-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
Barry-devel mailing list
Barry-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/barry-devel

[Barry-devel] [SCRIPT] Disconnecting from usb-storage, but keep it loaded

[Niels de Vos]

Hello,

just hacked a little script together which uses the sysfs-structure
for finding any BlackBerries (well, at least my BB8100). After some
small sanity checks the script disconnects the BlackBerry from
usb-storage using the 'unbind' file.

Instead of a script, it would of course also be possible to add a
C/C++-function to libbarry. The logic is pretty straight forward,
however writing it in C/C++ would require quite some more lines ;) For
the adventurous wanting to write this code, please see these notes
about _not_ using libsysfs:
.

I hope this script helps somebody and explains a bit more how
usb-storage can be kept loaded while using barry. I provide this
script for inclusion in barry as utility, testcase and/or
documentation. Have fun wit it!

Cheers,
Niels


barry-unbind-storage.sh
Description: Bourne shell script
-
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08___
Barry-devel mailing list
Barry-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/barry-devel

Re: [Barry-devel] FC9 and Barry???

[Niels de Vos]

On Tue, Jul 1, 2008 at 7:22 PM, lance raymond <[EMAIL PROTECTED]> wrote:
> Sorry Shannon, nothing to 'help', but also running f9 but a diff error on
> the cvs make, and your right the list is getting a bit quiet.  I also get
> through the build and configure, but I get a lot of errors all pointing at
> usbwrap.h (attached text file as it's way to long to just paste).
>
> Hopefully things progress and we have some syncing soon!

Most important error seems to be this:
In file included from usbwrap.cc:23:
usbwrap.h:27:17: error: usb.h: No such file or directory

My guess is that if 'usb.h' gets found, barry will compile. Please
make sure libusb-devel is installed and usb.h is in the include path.

Good luck,
Niels

-
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
___
Barry-devel mailing list
Barry-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/barry-devel

Re: [Barry-devel] builgen.sh on CentOS-5.1

[Niels de Vos]

On 5/17/08, Chris Frey <[EMAIL PROTECTED]> wrote:
> On Fri, May 16, 2008 at 12:12:27PM -0400, Chris Frey wrote:
>> I don't know any quick way around that
>
> Well, actually the quick way around that is to just run buildgen.sh
> on a newer machine and then tar it up and move it to your older machine,
> but that depends on what you have available.

Ah ,okay, that's of course the easiest solution ;)

Niels

-
This SF.net email is sponsored by: Microsoft 
Defy all challenges. Microsoft(R) Visual Studio 2008. 
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Barry-devel mailing list
Barry-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/barry-devel

[Barry-devel] builgen.sh on CentOS-5.1

[Niels de Vos]

Hi,

I'm trying to get bcharge recognise my Pearl 8100 (productId: 0x0006).
Others were advised to compile bcharge from CVS. Unfortunately
CentOS-5 (and it's rother Red Hat Enterprise) delivers autoconf-2.59.
This seems to be to old for barry-cvs :(. It's easy for me to
recompile barry from a .srpm or .tgz even, but from CVS without a
./configure I'm stuck for now...

Thanks for any ideas,
Niels

-
This SF.net email is sponsored by: Microsoft 
Defy all challenges. Microsoft(R) Visual Studio 2008. 
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Barry-devel mailing list
Barry-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/barry-devel

Re: [Barry-devel] app downloading

[Niels de Vos]

Hello,

On 3/1/08, Brian Edginton <[EMAIL PROTECTED]> wrote:
> > If/When you get useful USB captures, feel free to pass them along to me,
> > and we can put them somewhere public... either in the sourceforge wiki
> > or CVS.
> >
>
> So, what have you found to be the best way to snoop the USB? Is windows
> better than Linux? Is there a tool that produces the same output as you have
> used in the past? Have you standardized anything?

At work we have a Ellisys USB Explorer. This is a hardware USB
Analyser and I could create a trace if you're interested. However the
software for viewing is only available for Windows (free download).

All I need is a URL for a little/cool java app for installing on my BB 8100.

Cheers,
Niels

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Barry-devel mailing list
Barry-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/barry-devel

Re: [Barry-devel] RIM desktopmng installs under wine

[Niels de Vos]

Hi Simon,

On 12/28/07, Simon Ruggier <[EMAIL PROTECTED]> wrote:
> On 12/27/07, Simon Ruggier <[EMAIL PROTECTED]> wrote:
> > I don't have much experience with rpm, but if install the development
> > package for libboost-serialization and compile the barry-util package
> > from source, it will compile against the newer version if the API
> > hasn't changed.

That's exactly what the 'rpmbuild --rebuild ...' does ;) Some
dependencies (like libboost_serialization.so.2) are recognized
automagically when creating the RPM using rpmbuild.

> Sorry, I hadn't read the response in the other thread when I sent this reply.

It's always more helpful to others when a question gets answered more
than once. Asking something on a mailinglist and not getting any
answers ist horrible! If nobody answered the rpmbuild-command, you at
least pointed into the right direction (compiling/linking against a
newer version of a library, libboost in this case).

Cheers,
Niels

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Barry-devel mailing list
Barry-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/barry-devel

Re: [Barry-devel] libboost_serialization

[Niels de Vos]

Hello Robert,

probably the best chance to get Barry working, is rebuilt Barry from
the src.rpm. Just download the one for FC7 and do a 'rpmbuild
--rebuild barry-0.11-1.fc7.src.rpm'. This generates several RPMs under
/usr/src/redhat/RPM/. This worked for me on CentOS-5.

Good luck,
Niels

On 12/27/07, Robert Denton <[EMAIL PROTECTED]> wrote:
>
>  I should mention also that I am running Fedora 8 and I have the following
> already:
>
> [EMAIL PROTECTED] 10]# rpm -qa | grep boost
> boost-devel-1.34.1-5.fc8
> boost-1.34.1-5.fc8
>
> Robert
> 
> From: Robert Denton [mailto:[EMAIL PROTECTED]
> To: Barry project development discussion
> [mailto:[EMAIL PROTECTED]
> Sent: Thu, 27 Dec 2007 08:33:01 -0800
> Subject: Re: [Barry-devel] RIM desktopmng installs under wine
>
>  Ah!  That may be my problem then.  I thought I had indeed installed
> barry-util but grepping for it in the rpm db I could not find it.  Trying to
> install it I get this:
>
> [EMAIL PROTECTED] 10]# rpm -ivh barry-util-0.11-1.fc7.i386.rpm
> error: Failed dependencies:
> libboost_serialization.so.2 is needed by barry-util-0.11-1.i386
>
> I tried copying my libboost_serialization.so.3 to
> libboost_serialization.so.2 but no love.  Where do you suppose I could grab
> the libboost_serializiation that I need?
>
>
> Robert
> 
> From: Chris Frey [mailto:[EMAIL PROTECTED]
> To: Barry project development discussion
> [mailto:[EMAIL PROTECTED]
> Sent: Fri, 21 Dec 2007 13:11:44 -0800
> Subject: Re: [Barry-devel] RIM desktopmng installs under wine
>
> On Wed, Dec 19, 2007 at 04:49:15PM -0800, Robert Denton wrote:
>  > >It would seem that one has to run modprobe -r usb_storage and bcharge
>  > everytime a bb is plaug into the usb port, no? What's the recommended
>  > way to configure a system to "just work" when the bb is plugged in?
>
>  If you installed the barry-util package, it should have installed a udev
>  rules script as /etc/udev/rules.d/10-blackberry.rules
>
>  This runs bcharge as root whenever your blackberry is plugged in, and
>  if you are running the latest version 0.11, then it should also handle
>  usb_storage automatically.
>
>  If this is not the case, we'll need to do some extra udev logging on your
>  system and see what is really happening.
>
>  - Chris
>
>
> -
>  This SF.net email is sponsored by: Microsoft
>  Defy all challenges. Microsoft(R) Visual Studio 2005.
>  http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
>  ___
>  Barry-devel mailing list
>  Barry-devel@lists.sourceforge.net
>  https://lists.sourceforge.net/lists/listinfo/barry-devel
>
> -
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
> ___
> Barry-devel mailing list
> Barry-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/barry-devel
>
>

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Barry-devel mailing list
Barry-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/barry-devel

Re: [Barry-devel] Barry Outreach Program

[Niels de Vos]

On 11/28/07, Martin Owens <[EMAIL PROTECTED]> wrote:
> Hi, thanks for the log, I need the logs from btool from version 0.9 or
> above because the 0.8 version doesn't record any of the detailed
> information.

Okay, here it is, created with 0.11. Ran the src-rpm for Fedora 7
thrrough "rpmbuild --rebuild .." on CentOS-5.1.

> Oh and let me know what model of phone you have :-)

It's a Pearl (8100).

Cheers,
Niels
device_desc loaded
bLength: 18
bDescriptorType: 1
bcdUSB: 272
bDeviceClass: 255
bDeviceSubClass: 255
bDeviceProtocol: 255
bMaxPacketSize0: 16
idVendor: 4042
idProduct: 1
bcdDevice: 262
iManufacturer: 1
iProduct: 2
iSerialNumber: 0
bNumConfigurations: 1

  config_desc #0 loaded
bLength: 9
bDescriptorType: 2
wTotalLength: 46
bNumInterfaces: 1
bConfigurationValue: 1
iConfiguration: 0
bmAttributes: 128
MaxPower: 250

interface_desc #0 loaded
bLength: 9
bDescriptorType: 4
bInterfaceNumber: 0
bAlternateSetting: 0
bNumEndpoints: 4
bInterfaceClass: 255
bInterfaceSubClass: 1
bInterfaceProtocol: 255
iInterface: 2

  endpoint_desc #0 loaded
bLength: 7
bDescriptorType: 5
bEndpointAddress: 129
bmAttributes: 2
wMaxPacketSize: 64
bInterval: 0
bRefresh: 0
bSynchAddress: 0

  endpoint added to map with bEndpointAddress: 129
pair.read = 129
pair.type = 2
  endpoint_desc #1 loaded
bLength: 7
bDescriptorType: 5
bEndpointAddress: 2
bmAttributes: 2
wMaxPacketSize: 64
bInterval: 0
bRefresh: 0
bSynchAddress: 0

  endpoint added to map with bEndpointAddress: 2
pair.write = 2
pair.type = 2
pair added! (read: 129,write: 2,type: 2)
  endpoint_desc #2 loaded
bLength: 7
bDescriptorType: 5
bEndpointAddress: 131
bmAttributes: 2
wMaxPacketSize: 64
bInterval: 0
bRefresh: 0
bSynchAddress: 0

  endpoint added to map with bEndpointAddress: 131
pair.read = 131
pair.type = 2
  endpoint_desc #3 loaded
bLength: 7
bDescriptorType: 5
bEndpointAddress: 4
bmAttributes: 2
wMaxPacketSize: 64
bInterval: 0
bRefresh: 0
bSynchAddress: 0

  endpoint added to map with bEndpointAddress: 4
pair.write = 4
pair.type = 2
pair added! (read: 131,write: 4,type: 2)
interface added to map with bInterfaceNumber: 0
  config added to map with bConfigurationValue: 1
usb_open(0x9bdbf38)
usb_claim_interface(0x9bcef30,0)
usb_clear_halt(0x9bcef30,131)
usb_clear_halt(0x9bcef30,4)
BulkWrite to endpoint 4:
: 00 00 10 00 01 ff 00 00 a8 18 da 8d 6c 02 00 00  l...

BulkRead (131):
: 00 00 10 00 02 ff 00 00 a8 18 da 8d 6c 02 00 00  l...

BulkWrite to endpoint 4:
: 00 00 0c 00 05 ff 00 00 14 00 01 00  

Socket::Send: Endpoint 131
Received:
: 00 00 20 00 06 ff 00 00 14 00 01 00 4a 7b 6a 02  .. .J{j.
0010: e4 a9 28 15 1a 11 a4 d7 1b 04 90 f7 ba 36 ca 1b  ..(..6..

BulkWrite to endpoint 4:
: 00 00 0c 00 05 ff 00 01 08 00 04 00  

Socket::Send: Endpoint 131
Received:
: 00 00 14 00 06 ff 00 01 08 00 04 00 03 00 00 00  
0010: be 84 4e 20  ..N 

BulkWrite to endpoint 4:
: 00 00 0c 00 05 ff 00 02 08 00 02 00  

Socket::Send: Endpoint 131
Received:
: 00 00 c4 01 06 ff 00 02 b8 01 02 00 0a 00 04 00  
0010: b8 01 00 00 01 17 02 05 03 0d 00 84 52 49 4d 20  RIM 
0020: 38 31 30 30 20 53 65 72 69 65 73 20 43 6f 6c 6f  8100 Series Colo
0030: 75 72 20 47 50 52 53 20 48 61 6e 64 68 65 6c 64  ur GPRS Handheld
0040: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  
0050: 00 00 00 00 00 00 00 00 00 00 00 00 6e 70 61 72  npar
0060: 74 68 69 62 61 6e 00 00 00 00 00 00 4a 75 6c 20  thiban..Jul 
0070: 31 33 20 32 30 30 36 00 00 00 00 00 31 30 3a 32  13 2006.10:2
0080: 37 3a 35 36 00 00 00 00 00 00 00 00 00 01 0f 00  7:56
0090: 00 00 00 00 00 00 00 00 a4 00 00 00 0a 00 00 00  
00a0: b8 00 00 00 40 00 00 00 02 00 00 00 90 65 00 80  [EMAIL PROTECTED]
00b0: 01 05 02 c5 03 01 04 03 07 12 ff ff ff ff ff ff  
00c0: ff ff ff ff 4a 56 be 92 0c 00 01 00 03 0c 00 00  JV..
00d0: 00 00 00 80 ff ff 3f 80 03 0c 00 01 00 00 00 d0  ..?.
00e0: ff ff 07 d0 03 0c 01 00 00 00 40 80 ff ff 3f 82  [EMAIL PROTECTED]
00f0: 03 0c 01 01 00 00 40 82 ff ff 3f 84 0e 10 00 00  [EMAIL PROTECTED]
0100: 00 00 02 80 ff ff 05 80 00 00 01 00 02 08 00 00  
0110: 00 00 06 80 15 14 00 00 00 00 02 00 ff ff 3d 82  ..=.
0120: 00 00 02 00 00 00 42 80 07 14 00 00 00 00 02 00  ..B.
0130: 00 00 42 82 ff ff 33 84 00 00 02 00 0c 0c 00 00  ..B...3.
0140: 00 00 34 84 ff ff 35 84 05 14 00 00 00 00 02 00  ..4...5.
01

Re: [Barry-devel] Barry Outreach Program

[Niels de Vos]

There you go. Actually I'm only using bcharge. Experimenting with
opensync <-> evolution is still on my todo...

btool - Command line USB Blackberry Test Tool
Copyright 2005-2007, Net Direct Inc. (http://www.netdirect.ca/)
Using: Barry library version 0.8 (little endian)

Cheers,
Niels

On 11/25/07, Martin Owens <[EMAIL PROTECTED]> wrote:
> Hey Blackberry People
>
> I'm looking to investigate the data we get with btool so I need
> everyone who has a blackberry device to run the following command and
> email me the log file it generates so I can compare all the data and
> work out more fields than just description and pin. (more docs would
> be good too)
>
> sudo btool -v -l > ~/barry.log
>
> Best Regards, Martin Owens
>
> -
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
> ___
> Barry-devel mailing list
> Barry-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/barry-devel
>
device_desc loaded
bLength: 18
bDescriptorType: 1
bcdUSB: 272
bDeviceClass: 0
bDeviceSubClass: 0
bDeviceProtocol: 0
bMaxPacketSize0: 16
idVendor: 4042
idProduct: 4
bcdDevice: 262
iManufacturer: 1
iProduct: 5
iSerialNumber: 3
bNumConfigurations: 1

  config_desc #0 loaded
bLength: 9
bDescriptorType: 2
wTotalLength: 69
bNumInterfaces: 2
bConfigurationValue: 1
iConfiguration: 0
bmAttributes: 128
MaxPower: 250

interface_desc #0 loaded
bLength: 9
bDescriptorType: 4
bInterfaceNumber: 0
bAlternateSetting: 0
bNumEndpoints: 4
bInterfaceClass: 255
bInterfaceSubClass: 1
bInterfaceProtocol: 255
iInterface: 2

  endpoint_desc #0 loaded
bLength: 7
bDescriptorType: 5
bEndpointAddress: 129
bmAttributes: 2
wMaxPacketSize: 64
bInterval: 0
bRefresh: 0
bSynchAddress: 0

  endpoint added to map with bEndpointAddress: 129
pair.read = 129
pair.type = 2
  endpoint_desc #1 loaded
bLength: 7
bDescriptorType: 5
bEndpointAddress: 2
bmAttributes: 2
wMaxPacketSize: 64
bInterval: 0
bRefresh: 0
bSynchAddress: 0

  endpoint added to map with bEndpointAddress: 2
pair.write = 2
pair.type = 2
pair added! (read: 129,write: 2,type: 2)
  endpoint_desc #2 loaded
bLength: 7
bDescriptorType: 5
bEndpointAddress: 131
bmAttributes: 2
wMaxPacketSize: 64
bInterval: 0
bRefresh: 0
bSynchAddress: 0

  endpoint added to map with bEndpointAddress: 131
pair.read = 131
pair.type = 2
  endpoint_desc #3 loaded
bLength: 7
bDescriptorType: 5
bEndpointAddress: 4
bmAttributes: 2
wMaxPacketSize: 64
bInterval: 0
bRefresh: 0
bSynchAddress: 0

  endpoint added to map with bEndpointAddress: 4
pair.write = 4
pair.type = 2
pair added! (read: 131,write: 4,type: 2)
interface added to map with bInterfaceNumber: 0
interface_desc #0 loaded
bLength: 9
bDescriptorType: 4
bInterfaceNumber: 1
bAlternateSetting: 0
bNumEndpoints: 2
bInterfaceClass: 8
bInterfaceSubClass: 6
bInterfaceProtocol: 80
iInterface: 4

  endpoint_desc #0 loaded
bLength: 7
bDescriptorType: 5
bEndpointAddress: 133
bmAttributes: 2
wMaxPacketSize: 64
bInterval: 0
bRefresh: 0
bSynchAddress: 0

  endpoint added to map with bEndpointAddress: 133
pair.read = 133
pair.type = 2
  endpoint_desc #1 loaded
bLength: 7
bDescriptorType: 5
bEndpointAddress: 6
bmAttributes: 2
wMaxPacketSize: 64
bInterval: 0
bRefresh: 0
bSynchAddress: 0

  endpoint added to map with bEndpointAddress: 6
pair.write = 6
pair.type = 2
pair added! (read: 133,write: 6,type: 2)
interface added to map with bInterfaceNumber: 1
  config added to map with bConfigurationValue: 1
BulkWrite to endpoint 4:
: 00 00 10 00 01 ff 00 00 a8 18 da 8d 6c 02 00 00  l...

BulkRead (131):
: 00 00 10 00 02 ff 00 00 a8 18 da 8d 6c 02 00 00  l...

BulkWrite to endpoint 4:
: 00 00 0c 00 05 ff 00 00 14 00 01 00  

Socket::Send: Endpoint 131
Received:
: 00 00 20 00 06 ff 00 00 14 00 01 00 4a 7b 6a 02  .. .J{j.
0010: e4 a9 28 15 1a 11 a4 d7 1b 04 90 f7 ba 36 ca 1b  ..(..6..

BulkWrite to endpoint 4:
: 00 00 0c 00 05 ff 00 01 08 00 04 00  

Socket::Send: Endpoint 131
Received:
: 00 00 14 00 06 ff 00 01 08 00 04 00 03 00 00 00  
0010: be 84 4e 20  ..N 

BulkWrite to endpoint 4:
: 00 00 0c 00 05 ff 00 02 04 00 05 00  

Socket::Send: Endpoint 131
Received:
: 00 00 0c 00 06 ff 00 02 00 00 00 00  

BulkWrite to endpoint 4:
: 00 00 0c 00 05 ff 00 03 04 00 06 00  

Socket::Send: Endpoint 131
Received:
: 00 00 10 00 06 ff 00 03 

Re: [Barry-devel] Blackberry 8830 on Ubuntu 7.10

[Niels de Vos]

On 11/9/07, Simon Ruggier <[EMAIL PROTECTED]> wrote:
> On 11/9/07, Chris Frey <[EMAIL PROTECTED]> wrote:
> > On Fri, Nov 09, 2007 at 10:11:24AM +0100, Niels De Vos wrote:
> > > On 11/8/07, Chris Frey <[EMAIL PROTECTED]> wrote:
> > > > rmmod is not enough to prevent the conflict.  You need to rename the
> > > > berry_charge module under /lib/modules before plugging in your device.
> > >
> > > Or add the following line to /etc/modprobe.conf:
> > > install berry_charge /bin/true
> > >
> > > This prevents modprobe loading the module. modprobe executes /bin/true 
> > > instead.
> >
> > Thanks!  That's so smooth, I'm tempted to put it right in the binary
> > package.  That would save a lot of trouble.
>
> Err, As far as I know, both of these solutions are hacks, and the
> proper way to do it would be to create a file like
> /etc/modprobe.d/blacklist-berry_charge containing:
>
> # conflicts with barry bcharge utility
> blacklist berry_charge

You're correct, that looks even nicer :)

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
___
Barry-devel mailing list
Barry-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/barry-devel

Re: [Barry-devel] Blackberry 8830 on Ubuntu 7.10

[Niels De Vos]

On 11/8/07, Chris Frey <[EMAIL PROTECTED]> wrote:
> rmmod is not enough to prevent the conflict.  You need to rename the
> berry_charge module under /lib/modules before plugging in your device.

Or add the following line to /etc/modprobe.conf:
install berry_charge /bin/true

This prevents modprobe loading the module. modprobe executes /bin/true instead.

Cheers,
Niels

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
___
Barry-devel mailing list
Barry-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/barry-devel

Re: [Barry-devel] Blackberry 8830 on Ubuntu 7.10

[Niels De Vos]

Hi all,

as far as I know the berry_charge driver/module conflicts with the
bcharge-tool. This might prevent other barry-tools from functioning
too.

Cheers,
Niels

On 11/4/07, Zach Stern <[EMAIL PROTECTED]> wrote:
> I have the same issue, and I can't use the sync tool either. I also have an 
> 8830, ubuntu 7.10.
>
> I had the same issue on 7.04 as well.
> Sent from my Verizon Wireless BlackBerry
>
> -Original Message-
> From: "Arvind Kalyan" <[EMAIL PROTECTED]>
>
> Date: Sat, 3 Nov 2007 17:11:30
> To:barry-devel@lists.sourceforge.net
> Subject: [Barry-devel] Blackberry 8830 on Ubuntu 7.10
>
>
> Hi,
>
>  I have installed barry from cvs (version .10).
>
> When I tried to invoke bcharge the power settings remain at 100mA (the device 
> id doesnt change to 0004. it remains at 0fca:0006).
>
> Here are the details. Please let me know if you would need further 
> information.
>
>
> OS: Ubuntu 7.10
> Ph: Blackberry 8830 / Verizon Wireless
>
> # uname -a
> Linux arvind-r61 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 
> GNU/Linux
>
> # lsusb
> Bus 001 Device 001: ID :
> Bus 005 Device 001: ID :
> Bus 003 Device 008: ID 0fca:0006 Research In Motion, Ltd.
> Bus 003 Device 001: ID :
> Bus 002 Device 001: ID :
> Bus 004 Device 001: ID :
> Bus 006 Device 001: ID :
> Bus 007 Device 001: ID :
> #
>
> # lsusb -v -d 0fca:0006
>
> Bus 003 Device 008: ID 0fca:0006 Research In Motion, Ltd.
> Device Descriptor:
>  bLength 18
>  bDescriptorType 1
>  bcdUSB 1.10
>  bDeviceClass 0 (Defined at Interface level)
>  bDeviceSubClass 0
>  bDeviceProtocol 0
>  bMaxPacketSize0 64
>  idVendor 0x0fca Research In Motion, Ltd.
>  idProduct 0x0006
>  bcdDevice 1.06
>  iManufacturer 1 Research In Motion
>  iProduct 4 RIM Mass Storage Device
>  iSerial 3 5E1615F1623EF31A6519F809EE97BB1
> 607FA0ECD
>  bNumConfigurations 1
>  Configuration Descriptor:
>  bLength 9
>  bDescriptorType 2
>  wTotalLength 32
>  bNumInterfaces 1
>  bConfigurationValue 1
>  iConfiguration 0
>  bmAttributes 0x80
>  (Bus Powered)
>  MaxPower 100mA
>  Interface Descriptor:
>  bLength 9
>  bDescriptorType 4
>  bInterfaceNumber 0
>  bAlternateSetting 0
>  bNumEndpoints 2
>  bInterfaceClass 8 Mass Storage
>  bInterfaceSubClass 6 SCSI
>  bInterfaceProtocol 80 Bulk (Zip)
>  iInterface 4 RIM Mass Storage Device
>  Endpoint Descriptor:
>  bLength 7
>  bDescriptorType 5
>  bEndpointAddress 0x86 EP 6 IN
>  bmAttributes 2
>  Transfer Type Bulk
>  Synch Type None
>  Usage Type Data
>  wMaxPacketSize 0x0040 1x 64 bytes
>  bInterval 0
>   Endpoint Descriptor:
>  bLength 7
>  bDescriptorType 5
>  bEndpointAddress 0x07 EP 7 OUT
>  bmAttributes 2
>  Transfer Type Bulk
>  Synch Type None
>  Usage Type Data
>  wMaxPacketSize 0x0040 1x 64 bytes
>  bInterval 0
> Device Status: 0x
>  (Bus Powered)
>
>
> # grep 0fca /etc/udev/rules.d/*
> /etc/udev/rules.d/10-blackberry.rules:BUS=="usb", SUBSYSTEM=="usb_device", 
> ACTION=="add", SYSFS{idVendor}=="0fca", SYSFS{idProduct}=="0001", 
> SYMLINK+="bb-%k", RUN="/usr/sbin/bcharge -p %p"
>
> /etc/udev/rules.d/10-blackberry.rules:BUS=="usb", SUBSYSTEM=="usb_device", 
> ACTION=="add", SYSFS{idVendor}=="0fca", SYSFS{idProduct}=="0006", 
> RUN="/usr/sbin/bcharge"
>
> /etc/udev/rules.d/10-blackberry.rules:BUS=="usb", SUBSYSTEM=="usb_device", 
> ACTION=="add", SYSFS{idVendor}=="0fca", SYSFS{idProduct}=="0004", 
> SYMLINK+="bb-%k", RUN="/usr/sbin/bcharge -p %p"
>
> /etc/udev/rules.d/99-barry-perms:SYSFS{idVendor}=="0fca", 
> SYSFS{idProduct}=="0006", GROUP="barry", MODE="0660"
>
> /etc/udev/rules.d/99-xmblackberry.rules:SUBSYSTEM=="usb_device", 
> SYSFS{idVendor}=="0fca", SYSFS{idProduct}=="0006", ACTION=="add", 
> RUN+="/bin/chown --reference=/dev/console $env{DEVNAME}"
>
> #
>
> I have tried the following:
>
> 1. Unload usb_storage. connect phone. Run bcharge. Run bcharge -o.
> 2. Unload usb_storage. load berry_charge. Connect phone. Run bcharge.
> 3. Unload usb_storage. load berry_charge. Connect phone. Run bcharge. Run 
> bcharge -o
> 4. Unload usb_storage. load berry_charge. Connect phone. Unload usb_storage. 
> Run bcharge.
> 5. Download 2.6.23 kernel from
> kernel.org   and compile with /boot/config-`uname -r`. 
> Tried 1,2,3,4 as above
> 6. Download ubuntu kernel 2.6.22-9 and used current config, and tried out 
> 1,2,3,4 as above.
>
>
> This is what happens each time:
>
> # dmesg
> [ 4140.328000] usbcore: deregistering interface driver usb-storage
> [ 4150.16] usb 3-1: new full speed USB device using uhci_hcd and address 9
> [ 4150.324000] usb 3-1: configuration #1 chosen from 1 choice
> [ 4150.356000] Initializing USB Mass Storage driver...
> [ 4150.356000 ] scsi10 : SCSI emulation for USB Mass Storage devices
> [ 4150.356000] usb-storage: device found at 9
> [ 4150.356000] usb-storage: waiting for device to settle before scanning
> [ 4150.356000] usbcore: registered new interface driver usb-storage
> [ 4150.356000] USB Mass Storage support regist

Re: [Barry-devel] Specifying required versions in the RPM spec file

[Niels de Vos]

Hi,

Just sommething I noticed with suse9. Are you using "yast -i" to
install the rpm? Try zge GUI after installation, it might complain!
If you install with the rpm-command, you probably get the desired error.

Good luck,
Niels

On 9/22/07, Chris Frey <[EMAIL PROTECTED]> wrote:
> Hi folks,
>
> I'm hoping this is something simple I'm overlooking.  I'm trying to
> craft the barry.spec file to require libopensync version 0.22, using
> this:
>
> Summary: BlackBerry(tm) Desktop for Linux - opensync plugin
> Group: Applications/Productivity
> Requires: libbarry, libopensync >= 0.22
> BuildRequires: libopensync-devel
>
>
> Unfortunately when I test this on OpenSuSE 10.2, with libopensync 0.20
> installed, RPM doesn't complain at all.
>
> Any RPM gurus out there that know the answer off the top of their heads?
>
> Thanks,
> - Chris
>
>
> -
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
> ___
> Barry-devel mailing list
> Barry-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/barry-devel
>

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Barry-devel mailing list
Barry-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/barry-devel

Re: [Barry-devel] MemoPad & Tasks + newbie = ? - take 2

[Niels de Vos]

The only suggestions I can think of is:

1) Download libboost{,-serialization} from Debian and try to install
these packages. You might need their -dev packages too, instead of
Ubuntu's.

2) Download Debians source package and try to build that on Ubuntu. That
might be easier than building from (Ubuntu?) CVS.

Good luck,
Niels

On Fri, 2007-06-08 at 09:12 -0700, Yigal Weinstein wrote:
> There are no "libboost{,serialization}" packages in Ubuntu/Feisty only
> "libboost-dev{,serialization}" packages.
> 
> In Gutsy which won't be ready until October there is a "libboost"
> package.  I downloaded BOOST via CVS but it looks really challenging to
> build.
> 
> If you have any suggestions please let me know.  I might even consider
> making a chroot of Debian and running barry through this.
> 
> Best,
> Yigal
> 
> On Fri, 2007-06-08 at 15:47 +0200, Niels de Vos wrote:
> > On Wed, 2007-06-06 at 20:35 -0700, Yigal Weinstein wrote:
> > > I have installed  
> > >   
> > > libboost-dev   
> > > libboost-serialization-dev
> > 
> > Are
> >  - libboost
> >  - libboost-serialization
> > not available on Ubuntu/Feisty?
> > 
> > Those do the trick on my Debian/Testing.
> > 
> > Thanks for the info you shared about LDIF and Evolution, that's really
> > helpful!
> > 
> > Cheers,
> > Niels
> > -
> > This SF.net email is sponsored by DB2 Express
> > Download DB2 Express C - the FREE version of DB2 express and take
> > control of your XML. No limits. Just data. Click to get it now.
> > http://sourceforge.net/powerbar/db2/
> > ___ Barry-devel mailing list 
> > Barry-devel@lists.sourceforge.net 
> > https://lists.sourceforge.net/lists/listinfo/barry-devel
> 
> 
> -
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> ___
> Barry-devel mailing list
> Barry-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/barry-devel
> 


-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
Barry-devel mailing list
Barry-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/barry-devel

[Barry-devel] [PATCH] Compiling barry on Debian - libtar-dev missing

[Niels de Vos]

Hello,

seems barry (gui?) needs libtar-dev for creating the Debian packages.
Here's the patch which adds this to the Build-Depends.

Cheers,
Niels
Index: debian/control
===
RCS file: /cvsroot/barry/barry/debian/control,v
retrieving revision 1.3
diff -u -p -r1.3 control
--- debian/control	11 May 2007 23:16:06 -	1.3
+++ debian/control	8 Jun 2007 14:04:09 -
@@ -2,7 +2,7 @@ Source: barry
 Section: misc
 Priority: optional
 Maintainer: Chris Frey <[EMAIL PROTECTED]>
-Build-Depends: debhelper (>= 4.0.0), libusb-dev, libssl-dev, libboost-serialization-dev
+Build-Depends: debhelper (>= 4.0.0), libusb-dev, libssl-dev, libboost-serialization-dev, libtar-dev
 Standards-Version: 3.6.1
 
 Package: libbarry


signature.asc
Description: This is a digitally signed message part
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/___
Barry-devel mailing list
Barry-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/barry-devel

Re: [Barry-devel] MemoPad & Tasks + newbie = ? - take 2

[Niels de Vos]

On Wed, 2007-06-06 at 20:35 -0700, Yigal Weinstein wrote:
> I have installed  
>   
> libboost-dev   
> libboost-serialization-dev

Are
 - libboost
 - libboost-serialization
not available on Ubuntu/Feisty?

Those do the trick on my Debian/Testing.

Thanks for the info you shared about LDIF and Evolution, that's really
helpful!

Cheers,
Niels


signature.asc
Description: This is a digitally signed message part
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/___
Barry-devel mailing list
Barry-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/barry-devel

[Barry-devel] Even more users?

[Niels de Vos]

Hi Barry People,

I've just found a note on barry here:

Looks like a more people are interrested than I thought :)

Keep up the good work, and thanks for all that,
Niels



signature.asc
Description: This is a digitally signed message part
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV___
Barry-devel mailing list
Barry-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/barry-devel

[Barry-devel] New udev rules for Pearl in .deb

[Niels de Vos]

Hi,

it seems that the Pearl is not detected by udev in Debian/testing at the
moment. Attached patch should add the required lines to the udev-rules
(taken from udev/10-blackberry.rules).

Cheers,
Niels
Index: debian/postinst
===
RCS file: /cvsroot/barry/barry/debian/postinst,v
retrieving revision 1.1
diff -u -r1.1 postinst
--- debian/postinst	5 Jan 2007 03:47:25 -	1.1
+++ debian/postinst	21 Mar 2007 14:51:33 -
@@ -12,6 +12,10 @@
 #BUS=="usb", SYSFS{idVendor}=="0fca", SYSFS{idProduct}=="0001", SYMLINK+="bb-%k", PROGRAM="/usr/sbin/bcharge"
 # Ubuntu and Fedora:
 BUS=="usb", ACTION=="add", SYSFS{idVendor}=="0fca", SYSFS{idProduct}=="0001", SYMLINK+="bb-%k", RUN="/usr/sbin/bcharge"
+#
+# Newer devices with USB Mass Storage, 0x0006 + 0x0004.
+BUS=="usb", SYSFS{idVendor}=="0fca", SYSFS{idProduct}=="0006", SYMLINK+="bb-%k", PROGRAM="/usr/sbin/bcharge"
+BUS=="usb", SYSFS{idVendor}=="0fca", SYSFS{idProduct}=="0004", SYMLINK+="bb-%k"
 EOF
 
 fi


signature.asc
Description: This is a digitally signed message part
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV___
Barry-devel mailing list
Barry-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/barry-devel