Older blog entries for bagder (starting at number 169)

So McAfee apparently makes an anti-virus program called Virex, that is using libcURL, and it graciously mention me in the about window.

This has had the minor side-effect that users of Virex find my email address there and mail me for requests and questions regarding Virex.

I hadn't even heard of it when the first mails started to show up in my mailbox this weekend...! ;-)

This is actually one of the more pleasent kinds of problems, at least if it doesn't grow out of proportions.

jhermann, I can only agree with your sentiments on the sourceforge public CVS server status as of lately. It seems it is more dead than alive these days... :-/

Just wanted to mention that Denise is still alive, and that I've started working on it again after it having been idle for a couple of months.

It does work somewhat rudimentary already and I hope to get the example program to build and run fine with asynch one name => ipv4 resolve this week.

I will need help from people to get DNS server information on various platforms, to be able to make a decent gethostbyname() (etc) clone.

I like the fact they went with trio in Glib.

glibc 2.2.93 is the one used in Redhat 8.0

When we use that and call gethostbyname_r() with a too small buffer, it no longer returns ERANGE. It now returns EAGAIN!!!

But, older versions (like the ones in redhat 6.0 or 7.3) of glibc obviously sometimes returns EAGAIN when the lookup fails due to normal resolve failures.

So, what the heck shall I check for when I want to know if I need to enlarge the buffer or if the name just doesn't resolve?


dillo, viewml, konq-e, opera

microwindows, tiny-X, QT/e, GTKfb

All those choices. I need a solid window system with a good enough browser using as little memory as possible on an embedded Linux on ARM...


Phew, this time it took more than three months to produce a new release of cURL. I don't think it has ever taken so long time before... Hm, wrong, it has, but the last time it took this long time I did some pretty major rewrites.

This time it has mostly been an extended period of bug fixes, design decisions and thinking over how things should be done, how they are done and how one might possibly wish that it was done.

Anyway, I need full public releases for people to actually run the code. I fool myself into sometimes believing that releasing pre-releases is enough, but it isn't.


Just kidding. Even if I had any, I bet you wouldn't be the least interested.

I'll continue to call it Linux, without any prefix.

There is this company that build mp3-players with a hard disk inside. Let's for the sake of this discussion call the company Archos.

They write the software for their units themselves, but have more or less stopped the development of upgrades.

In come RockBox and since we started coding back in March/April, we have pretty much(*) surpassed the original software in features and stability.

Now, people have the option of getting our free and open firmware, or getting the closed-source one without development from Archos.

We improve the value of their products. We actually make their units a better deal to people. For free. The software only runs on their products and no one else's.

Do they contact us? Do they offer insights and help on details on how things are to be programmed? No.

Every tiny bit has been researched, reverse-engineered and disassembled by us to be able to figure out how things work. They haven't yet contacted any single person in our project. I'm quite amazed by this fact.

Over at their place, they sit on their slowly fading source code with all the info we could've used before to reach this result faster. Now, we don't even need their help anymore.

Is this a perfect example of opensourcophobia or what?

(*) = we still don't offer all features the original firmware does, but the opposite situation is also true. We'll have them all in time. Just give us time.

The asynchronous name resolver library's project name is now set to Denise.

160 older entries...

New Advogato Features

New HTML Parser: The long-awaited libxml2 based HTML parser code is live. It needs further work but already handles most markup better than the original parser.

Keep up with the latest Advogato features by reading the Advogato status blog.

If you're a C programmer with some spare time, take a look at the mod_virgule project page and help us with one of the tasks on the ToDo list!