Re: [usbip-devel] usbip.sourceforge.net page is not current

[Benjamin D. <ben...@gm...>]

Yes lets please move to github as most people seem to prefer it as a
platform. Just clearing out the already moved linux host side would be
beneficial. Maybe it would get more visibility on github as well. Then we
can clarify on the sourceforge page where development has moved to; linux
kernel staging drivers for the linux host side (it is on the page already,
but not obvious to someone who just wants to use the project), and to
github for the windows and future OS clients.

You're right about the driver not being "stable" but it is certainly
functional for basic usage once you get the pre-reqs correct. Although
personally I had to spend few hours getting it to work at all with windows.
But when I did get it to work, how happy I was, and pleased with the
project progress overall. I'd love to begin bug-fixing the windows driver
as well since that is my primary background. Most open source dev's seem to
migrate towards the linux host portion now which is much more mature than
the windows side. I feel like this mailing list is only read by the windows
dev's anyway. The ReactOS team has USBIP still listed as a sponsored
project on their site so I'm sure they will support us if we request
another signed driver as development continues.

My biggest concern is that we may have some talented people look at the
project as it sits, attempt to use it, then write it off since it takes so
long to even begin to use it. When in fact its a quite usable project if
all the pieces and workarounds are presented clearly. Also to make visible
how active the linux host driver side has become.  I'd love to share my
basic writeup on how to make an environment to test the project with a
linux host and windows client. I think that is a very common (500+
downloads per week) scenario for end-users.

So lets fix-up the front page text just a little to indicate the current
status of the project. Let me know if this is something I can do for the
project and team. Since most of the original dev's aren't involved anymore
who can make the decision to move to github and to update the current
"homepage" on sourceforge? If no one objects I suppose anyone could upload
the code to github and call it the official home. I just wouldn't want to
do that without updating the current home with a link or redirect since
that could cause even more fragmentation of project info and code.

-Benjamin



On Tue, Feb 11, 2014 at 2:22 AM, Ricardo Gomes da Silva
<ca...@gm...>wrote:

> Hi Benjamin,
>
> Sounds good to me, but first I think we should check all the patches
> people sent over the last two years of non-development. I was thinking
> about personally moving the code to github and leaving sourceforge idle.
> This is just because I prefer it ;)
>
> But anyway, I don't think the driver is stable, and I remember applying
> some patches to it (mostly overflow protections as far as I can remember).
> This requires the driver to be signed again, which is a problem - we have
> access only to the testing certificate, not the real one. As far as I know
> it was signed by the people on ReactOS, but I might be wrong, so we might
> have to contact them as well.
>
> Right now I'm quite busy with some exams and my thesis at the university,
> but as soon as I have some free hours I might boot my testing VMs again and
> setup a new and proper development environment (last time I checked mine
> was terrible to work with).
>
>
> Best regards,
>
> Ricardo
>
>
> 2014-02-11 Benjamin DeCamp <ben...@gm...>:
>
>> I'd like to fixup the main web page for the project to update the fact
>> that no further linux development is happening at sourceforge. And to
>> clarify how to make the windows client actually work with modern linux
>> versions.
>>
>> Currently the data on where development is happening is in the message
>> boards and mailing list. But for people getting exposed to the project for
>> the first time it looks quite dead. However the opposite is true because it
>> has been merged into the staging area of the linux kernel itself.
>>
>> The first quote on the page says "Download the latest version" with a
>> link to the long dead repo on sourceforge instead of to the staging area of
>> the linux kernel.
>>
>> We also need to fix the current "latest version" of the windows client. A
>> fix has been contributed (commit r191) that allows usbip.exe to work with
>> modern linux versions without re-compiling the driver (which is signed and
>> quite stable). This would be a simple update to one file in the released
>> .zip that would allow the 500+ people/week downloading to be able to
>> actually use it without modifying the linux version strings as found here:
>> http://jaxlucky.blogspot.com/2013/10/sharing-usb-devices-between-beaglebone.html
>>
>> Someone has also contributed a fix in the forums for a BSOD in windows,
>> this needs to be committed to the windows driver so we can start testing
>> the fix. I would love to become a contributor and keep this side of the
>> project alive.
>>
>> -Ben
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Android apps run on BlackBerry 10
>> Introducing the new BlackBerry 10.2.1 Runtime for Android apps.
>> Now with support for Jelly Bean, Bluetooth, Mapview and more.
>> Get your Android app in front of a whole new audience.  Start now.
>>
>> http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk
>> _______________________________________________
>> usbip-devel mailing list
>> usb...@li...
>> https://lists.sourceforge.net/lists/listinfo/usbip-devel
>>
>>
>
>
> ------------------------------------------------------------------------------
> Android apps run on BlackBerry 10
> Introducing the new BlackBerry 10.2.1 Runtime for Android apps.
> Now with support for Jelly Bean, Bluetooth, Mapview and more.
> Get your Android app in front of a whole new audience.  Start now.
>
> http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk
> _______________________________________________
> usbip-devel mailing list
> usb...@li...
> https://lists.sourceforge.net/lists/listinfo/usbip-devel
>
>