I did a count back in August, and it seems the downloads counter is growing. During October 2007, Rockbox was downloaded 102127 times from build.rockbox.org, split up on 26 different zip files. This is a 43% increase since my last count! (New since last count is the SanDisk Sansa C200 package)
Here’s the list, with the August results on the right side of the slash (position, count, share of total).
- ipodvideo 20721 (20.3%) / #1 17829 (25.1%)
- sansae200 18788 (18.4%) / #2 9909 (13.9%)
- ipodnano 13228 (13.0%) / #3 9110 (12.8%)
- ipodvideo64mb 12780 (12.5%) / #4 7649 (10.7%)
- h300 3614 (3.5%) / #5 3153 (4.4%)
- gigabeatf 3522 (3.4%) / #6 3113 (4.4%)
- iaudiox5 3340 (3.3%) / #8 2712 (3.8%)
- ipodcolor 3287 (3.2%) / #9 2400 (3.4%)
- ipodmini2g 3083 (3.0%) / #10 2286 (3.2%)
- h120 2924 (2.9%) / #7 2720 (3.8%)
- ipod4gray 2896 (2.8%) / #11 2098 (2.9%)
- sansac200 2841 (2.8%) / NEW!
- ipodmini1g 1647 (1.6%) / #14 1191 (1.7%)
- ipod3g 1624 (1.6%) / #15 984 (1.4%)
- h10 1624 (1.6%) / #13 1322 (1.9%)
- h10_5gb 1524 (1.5%) / #12 1380 (1.9%)
- ipod1g2g 1384 (1.4%) / #17 606 (0.9%)
- player 834 (0.8%) / #18 551 (0.8%)
- recorder 692 (0.7%) / #16 615 (0.9%)
- iaudiom5 422 (0.4%) / #19 341 (0.5%)
- recorder8mb 354 (0.3%) / #21 256 (0.4%)
- h100 345 (0.3%) / #20 299 (0.4%)
- recorderv2 222 (0.2%) / #22 227 (0.3%)
- fmrecorder 222 (0.2%) / #23 207 (0.3%)
- ondiofm 113 (0.1%) / #24 105 (0.1%)
- ondiosp 96 (0.1%) / #25 101 (0.1%)
As you can see, the recorderv2 and ondiosp packages are the only ones downloaded less than before. Sansa e200 has taken a big bite of the share since last, and the newcomer c200 gets almost 3% at once. The h120 build dropped 3 steps.
The top-4 targets are portalplayer based. The top-8 targets have color displays.
The downloads split on main architecture is interesting (the previous count to the right of the slashes):
- portalplayer 85427 downloads (83.6%) / 56764 (79.7%)
- coldfire 10645 downloads (10.4%) / 9225 (12.9%)
- samsung 3522 downloads (3.4%) / 3113 (4.3%)
- sh1 2533 downloads (2.5%) / 2062 (2.8%)
So while all gained downloads by number, the portalplayer targets increased their share…
Another split on properties is to separate the targets on solid state (flash) memory and hard drives:
- HDD 67061 downloads 65.7%
- flash 35066 downloads 34.5%
Like last time, this doesn’t include custom builds, builds from download.rockbox.org nor release builds from www.rockbox.org. Take all this as indications, not absolute facts.
The guys working on the Rockbox port for the Olympus M:Robe 500 player have now reached a state where adding mrobe 500 builds to the Rockbox build table makes sense and there will soon also be zip files provided for download for ordinary mortals.
The only thing left before that will happen is some basic documentations adapted for this target for user.
I was just told about it by zivan56, and my mi4 page was just updated: the SanDisk Sansa View uses the mi4 file format and it is clearly PortalPlayer based. mi4code can find the crypto key, so decrypting it for disassembly is easy.
In fact, the zip contains two mi4 files and the second one is called “mediaproc.mi4” seems to be for a separate processor or similar, and it makes sense since the PP can’t do the movie playback etc with the specs that they boast for this player.
That media processor might very well be a “nv6110“, referred to many times in the firmware image.
Go crazy in the Rockbox forum thread about it!
I found this article by Jungle Dave titled Leopard DNS Issues (and work-around), which explains how libcurl built with IPv6 support may cause trouble on MacOS X 10.5 (Leopard).
According to him, that’s because getaddrinfo() causes a SRV lookup to be made and that may be either slow or get discarded completely and thus cause trouble.
This just adds another problem to getaddrinfo() resolves then, since we already have the problem with it when resolving round-robin DNSes since more or less every machine has a bad /etc/gai.conf setup that makes getaddrinfo() return a sorted list instead of the “random” one DNS admins in the wild would prefer the users to use…
As you should know, we maintain this curl comparison table on the curl web site, and it lists a set of free tools and how they compare against curl and each other in various aspects. If you want more features compared or other tools included, please tell. Also if you disagree with any of the facts stated there, just shout!
The other day I got an email asking me to add aget to the table, and since it is a free tool (original BSD licensed) with a similar purpose it would indeed fit.
So I downloaded aget 0.4 and had a go at it.
- The “stable” 0.4 version doesn’t build out of the tarball. It does wrong assumptions on “errno” and thus I had to manually poke on 3 source files to make it generate a fine binary! While this error is claimed to be fixed in the “devel” version, the devel version fails to build on compiler errors instead!
- My first test was to download aget’s own home page with aget… and it failed. It says the page is 0 bytes and it doesn’t download anything and outputs something about a bad seek 0 bytes!
- This really turned me off, but then I thought I should report this back to the guys rather than just blog it… but there’s no email address in the package that seems suitable, and when checking on the site I find a reference to a mailing list but when trying to read the list’s archive it just redirects back to the main page! So blogging it is.
- aget 0.4 from 2002, the aget devel version is from June 2004. Development seems to have stopped.
- I decided aget isn’t going to be added to the table by me at this time. It’ll have to mature some more first (and given the age of the tarballs I doubt that’ll happen…). I also read through the source code a bit and it really gives the impression of being a young project that hasn’t yet have time to settle since there are numerous of suspicious conclusions and source code doing “funny” things.
I’m open for and interested in ideas around how we should celebrate the curl ten year anniversary around March 20 2008.
Participating in and maintaining open source projects is great fun, much rewarding and very educating. One thing you always want is bug reports from users who suffer from problems, as you cannot fix problems unless you know they exist!
Yet there are several obstacles along the way that can prevent users’ reports from reaching your project. These obstacles include:
Eager to announce a new problem, a new revealed leak or exploit, people (often) submit security- related problems directly to sites and forums dealing with security. These sites (of course) don’t forward the reports onwards, they simply assume the projects are informed as well…
People who use Linux Distributions very often feel like a user of that distro (no surprise there really!) and they therefore primarily report bugs and problems to the distro’s bug tracker. Unless the people in the distro are keen and interested enough, those reports sit there rotting away and people in the upstream project who would like to know about it are never told and thus the bug isn’t fixed…
Sometimes the bug is even fixed by the distro people and they make a newly built version available, featuring that patch, but the patch isn’t forwarded upstream either!
Related forums/mailing lists
People discussing the project in another list or forum where they are users of it. They talk about workarounds etc and sometimes even talk about “known bugs” and “existing flaws” but without ever reporting them to the originating project so they aren’t fixed. They may thus be known to the subgroup there but not upstream.
Please report upstream!
This is my cry for how this situation can be fixed: make sure that problems you know of are reported upstream to the actual project working on the project. Don’t assume that reporting it to your distro or to your neighbor is enough!
(I could easily point out examples for all these cases for projects I am involved in, but I don’t think pointing fingers will gain us anything.)
7.17.1 – the 102nd release of curl is out, with less than 5 months left to our ten year anniversary!
The previous release (7.17.0) included a few larger internal changes and unfortunately that had the backside that it brought a whole array of new bugs in, that we now have spent almost two months polishing off.
Apart from the twenty or so bug fixes, a range of new things are introduced as well, including improved NSS support, –proxy-negotiate, –post301 (to make curl act more standards compliant on HTTP 301 responses), –hostpubmd.
libcurl hackers will appreciate CURLOPT_OPENSOCKETFUNCTION and CURLOPT_COPYPOSTFIELDS (the latter a complement to the existing CURLOPT_POSTFIELDS that got broken in 7.17.0 if you posted binary data that contains a zero byte).
7.17.1 contains contributions by at least 16 different people (me not included).
Well, not really but at least the recent “jailbreak” for it opens up the possibility…
The jailbreak seems to open up the ability to run apps on the target that are built for it, so I figure it can then theoretically be used to run whatever, and that’s why I say it is an opening for an eager and dedicated person to get Rockbox going on it.
I amuse myself by occasionally reading up on articles and posts “out there” that talk about curl and libcurl, and I often find interesting snippets and data well worth reading. Here’s a few of the ones I’ve stumbled upon recently:
- Tony G wrote a post to a u2 database mailing list and did an indirect praise of curl.
- magnetk.com writes about how to build a recent libcurl with visual studio 2005