Search Results: "ag"

28 September 2008

Jonathan McDowell: Which data contract?

I bought an EEE 901. More on that later.

For the past few weeks I've been trying to work out which "mobile broadband" provider to go with for my daily commute. It's a train journey from the north coast of Northern Ireland to Belfast and goes through some sparsely populated areas, so I wasn't expecting to get anything that would provide 3G all the way. However I do want a provider that can do their best to keep a session up for the journey, handing over between 2G + 3G as necessary. Coverage maps/checkers aren't too bad if you just want to check a static point, but really even then it's better to actually try the provider in the location yourself. So, armed with a bluetooth GPS (Bl eNEXT BN-909GR), an Option GT 3G Quad PCMCIA card and my laptop I set about measuring signal strength along my train journey for each of the 5 providers available. I also made sure to actually try a session with them for at least one journey, because signal strength is not everything.

I wrote some Perl using Net::GPSD and Device::Gsm to query my current location, signal strength, 2G/3G status and network every 10 seconds. I did this for 3 train journeys (except for O2) and then also produced an "optimistic" file of all the data points combined for that provider.

A second piece of Perl took this data and drew the maps you see below. The graph on the right for each provider is all data points. Red means 2G, blue means 3G, green means "Limited Service" (ie it could see a signal, but not one it was allowed to connect to). White means that we had a GPS location and no signal at all. Click on the maps for bigger versions. You can see the route on OpenStreetMap - my graphs are a little squished horizontally, but the journey is from Castlerock (top left on the coast near Coleraine) to Belfast (bottom right).

3
O2
Orange
T-Mobile
Vodafone

At first glance 3 look to be the best bet. Lots of blue, a reasonably priced data plan. Except they can't hold up a session to save themselves. Not only does a 2G/3G handover almost always seem to result in a drop, but I had periods of failing to get a 2G session up at all and had some random drops while in 3G coverage as well. So strike them off.

O2 and T-Mobile don't manage any 3G outside Belfast (that's the bottom right corner btw). I found that a few periods of 3G along the journey helped a lot; it meant I could do a quick mail sync rather than the long drawn out affair it was on a 2G connection. They can both handle handover between 2G/3G and keep a session up for most of the journey, but the lack of speed counts them out.

Vodafone managed the worst reception, which is disappointing. I found them quite good when I lived in England (my datacard is from a Vodafone Pay as You Use data contract). I did find sessions being dropped during the no signal regions, so they just don't seem to be a good bet.

Which leaves Orange. I've had issues with Orange and data in the past (pre 2004 IIRC) but in testing they were able to keep a session up between Belfast and Castlerock, handling 2G/3G handover fine. Coverage was reasonably good and they manage 3G at several points along the journey (the blue points roughly correspond to Coleraine, Ballymena, Antrim and Belfast). I understand Orange have some EDGE capability, but my card doesn't do EDGE so I've no idea if that'll be an extra gain or not. I had a few issues with getting dud DNS servers but this happened with the other providers too so I was beginning to suspect the datacard of playing up. Manually setting known good servers in resolv.conf worked fine.

So, before I go and sign up to an 18 month Orange contract, what have I forgotten?

27 September 2008

Christine Spang: finally found a decent DAP

I recently bought a 4GB Sansa Clip to solve the problem where once-a-week or so I want portable music or podcasts and don’t have any: namely, at the gym, occasionally when walking somewhere, and on trains and buses. I’ve been looking for something exactly like this for ages—small, attachable for use during exercise, enough space for a few hours of music/audio, OGG support, and not necessarily much more than that. Basically, an iPod Shuffle that plays OGG and doesn’t involve dealing with Apple. For the longest of time, this was pie-in-the-sky nonexistant. After a few weeks of using the Clip, I’m extremely pleased so far. The battery life is much longer than I’d ever want to listen to music for continuously (they claim 15 hours, and I haven’t gotten it down to less than half charge yet). It’s light in the hand but not too flimsy in feel, the clip makes it easy to attach to e.g. shorts, the interface is easy to use, and the sound quality is good. After upgrading to the latest firmware, it plays OGG as well as MP3. Both Rhymthbox and Banshee work for transferring files to it. I think my biggest complaint so far would be that the audio jack doesn’t fit in as securely as it could, which sometimes manifests as sound skipping and can be fixed by making sure the headphones are completely plugged in. Seriously, it was funny when my Walkman skipped during runs in 2003, but I hope I’m past that phase of life at this point. At any rate, it doesn’t happen all that often, so it’s more of a minor annoyance than anything. And well, the firmware isn’t free—but hey, can’t have everything.

James Morrison: Waves to Wine

Thanks to all that donated to the MS society in my name. Thanks to the generous donations and a match from Google I surpassed my goal and I may even get a cool bike jersey from the event. The actual ride was a lot of fun. The ride was very well supported. It felt more like 8 12 mile rides the first day instead of one 100 mile ride. The second day was even better. I managed to tag along with a group of cyclists from Deloitte who I could draft off of, for the second half of the ride, which made it very fast and a good learning experience. I have not had many opportunities to draft on rolling hills before.

The first day route had 7400ft of climbing over the 100 miles. The second day route had only 3500 over the 75 miles. However, by looking at the routes it is obvious that neither day was exactly the most direct route to the destination. Which is ok, I had all day to do the ride on each day and didn't have to turn around and ride home afterwards.

Speaking of afterwards, when I got back to AT&T park to pick up my stuff, I tried to ride back to my house. That was the slowest riding I have done for a very long time. The bright spot was I passed a couple of people starting on the wiggle, who did comment that everyone seems to be passing them :)

Biella Coleman: Zuing Zotero

I am a big fan of zotero as it has helped me manage my research, especially collect, tag, time stamp, and keep web pages that are likely to vanish. I can’t recommend it enough. I have yet to use its bibliographic functionality and apparently it is this functionality which has made it the subject of what what looks like a pretty questionable law suit. It has been a while since a IP lawsuit has really caught my attention (only in so far as it was the same old thing, not because it was not important) but this one definitely has caught my attention (and caught me off guard as well as I never really associated End Notes with Zotero, in so far as they seem to work pretty distinctly). I am eager to see how an academic institution, George Mason in this case, will react. I just hope they stand firm and also get some great legal team to help out.

Adeodato Sim : A good window manager for me?

For some time now I’ve been wanting to find a window manager that allows me to improve my current “implementation” of my workflow. I currently use KWin. Since I’m a bit overwhelmed by the number of window managers available, some of them being perhaps too flexible, and since what I want is very, very specific, I thought I’d go for a lazy-web post. My workflow is simple: I don’t do tiling, and my sole wish is that a simple key combo (Mod + one letter) can activate the window designated by that combo. Ideally I can statically assign combos to each application (or, in general, window properties) from the configuration file, but I can also use a special combo to change on-the-fly the current keybindings for a particular window. At the moment I’m “faking” this with several methods combined: In my new world, I’d be able to just type Mod+M to activate Minirok, Mod+A to activate Akregator, Mod+B for the browser, and several others keybindings for each instance of my terminal emulator (one for my -release work, one for my ongoing Uni work, another for my ongoing programming work). I really, really want that’s it’s just one Mod plus a key, because I’m convinced that’d work out very well for me (though it should offer a way to cycle among all windows as well). As for the rest, ability to display Kicker (KDE’s panel) gracefully would be a plus. Please mail me with your suggestions, but I’d appreciate if you could include pointers to the relevant parts of the documentation, or even examples, of how to accomplish what I want. I’ve tried eg. awesome 3, and I only managed to get lost in Lua-land.

Lucas Nussbaum: Importing bugs into UDD, faster.

Importing bugs from the Debian Bug Tracking System into UDD (the Ultimate Debian Database) in a reasonable time is challenging. The BTS uses flat files to store bug information, and importing a bug typically requires reading a ’summary’ file, and a file containing the verisoning information, both of a few hundred bytes. That looks easy, but when you multiply it by ~70000 unarchived bugs, it takes a lot of time (about 40 minutes) to read those ~100k files, because the import process will block on every I/O. The problem is not the amount of data to read (19.8 MB for summary files, 7.4 MB for versioning files), but the number of files (69612 summary files, 17507 versioning files). The obvious solution is to preload all the files into the page cache, so they are there when you need them. But you can’t simply do that with find /org/bugs.debian.org/versions/pkg -type f -exec cat \+ &>/dev/null, because that wouldn’t fix anything: you would still block on each file, and prevent the I/O scheduler to reorder the reads and optimize them (it’s called elevator for a reason). So, how do I tell the kernel “I’m going to read that in the future, please preload it?” readahead(2) is blocking, so it’s not helpful. The right solution is to use posix_fadvise(2), that allows to declare an access pattern. Using fadvise to preload all the files takes less than 5 minutes, and importing the bugs after that takes less than 8 minutes, so it’s really a big win. Does someone know if there’s already an fadvise-based tool that allows to preload a list of files? That’s something that I could need in other contexts as well.

26 September 2008

Jeff Bailey: My employer is SO FUCKING COOL: "No on Prop 8"

Hey - I usually have a personal policy of not talking about my current employer on my blog. It's why I didn't join Planet Ubuntu until after I'd left Canonical, for instance. This blog isn't theirs. I can promise you that no PR department I've ever worked for has approved the gratuitous overuse of the word "fuck".

But FUCK, this is cool: http://googleblog.blogspot.com/2008/09/our-position-on-californias-no-on-8.html

My readers might remember that Angie and I spent a bunch of time writing letters to my Member of Parliament back in Canada in support of gay marriage, donated to egale, attended a church that got intervener status in support of gay marriage, and ultimately attended the senate debates where equal marriage became the law of the land.

And then, a year ago, we moved to this place. A place where this is still considered an issue. A place where people are willing to do what would never be considered back at home: They're willing to take away the rights that people have and are exercising to marry their partner of choice. And I don't have a voice. As a non-citizen, I can't sign a petition, I can't donate money to political campaigns, and I have no representative to contact and inform how important this is to me.

I was pleased to learn this afternoon that Google has decided to publicly make a stand for the rights of people in California. It's just one more thing that makes this the coolest job I've ever had.

Russ Allbery: Things learned from debate

Things you learn from a US Presidential debate: Apparently the solution to the Iranian crisis is to replace the United Nations with the Extraordinary League of Democracies. They need to have a really cool plane. And a secret headquarters.

Junichi Uekawa: Two tips on using ssh for alioth.

Two tips on using ssh for alioth. Just because I currently have sloooow connection to alioth, I looked into making the connection better. Installing pdnsd and improving perceived DNS performance, installing webcaching etc are important too, but there is a ssh improvements which can be done. Using ControlMaster argument for ssh. You can have a master ssh session open, and ssh will reuse that connection, without asking for your password every time, just like using ssh-agent, but faster. I remembered this setting just because someone mentioned alioth -guest login names being a nuisance because they always have to specify it on ssh and scp; you don't. You just set the respective 'User' directive to the -guest names.

Tollef Fog Heen: Things to do on a Friday night

(when your wife/SO is not around) Hurrah! And it only took like six or seven hours. Notes for later: This is an YDL Powerstation, the magic mkofboot invocation is mkofboot -b /dev/sda1 --filesystem raw; the raw bit is needed for IBM hardware. The firmware also cares about whether the partition is marked as bootable or not, so make sure to mark it as such.

Martin Michlmayr: Choosing language during NAS installations

When the Debian installer starts, it will normally ask you what language you want to install in and gives you a really long list of languages to choose from. Unfortunately, that's not how it works when you install on a headless NAS device. The reason for this is that installations on NAS devices are done via SSH and the installer normally brings the network up after asking the user for their language. So we'd simply skip the language question and go with English. When Timo Jyrinki recently mentioned that he couldn't install in Finnish, Frans Pop pointed out that localechooser has changed a lot since etch and that it should now be possible to have the language question after setting up the network. This turned out to be correct and I managed to choose a different language but the installer still showed everything in English. Frans reminded me that the installer drops all translations that are not necessary but unfortunately this happens too early in our case. He pointed me to a variable that determines whether translations will be dropped. So in lenny translations will not be dropped on NAS devices that have enough RAM and users will be asked when they connect to the installer via SSH what language they'd like to install in.

Romain Francoise: Five and counting

Five years ago today, I became a Debian Developer! My account was created just a few weeks after Debian's 10th birthday and we recently celebrated the 15th, so I've been around for about a third of the project's life. In that period, we released sarge and etch, had two compromises, approximately 300,000 bugs were filed in the BTS, Ubuntu was created, three DPLs came and went, dunc-tank was launched and subsequently abandoned, and the Debian Maintainer status was created (among other notable events).

For me personally there have been ups and downs, but mostly it's been fun. I'm still proud of taking part in what is perhaps the largest volunteer project to date, and one that can produce a distribution of outstanding quality and versatility. The Debian community is huge, diverse and sometimes frighteningly technical, but always focused on making Debian (both the product and the project) better for everyone; it's worth being part of it if only for the amazing melting-pot of cultures and (sometimes antagonistic) technological philosophies.

I think that after fifteen years Debian is still relevant both as a basis for derivative distributions, and as a product for end users. I like to think that I've played a part, however insignificant, in Debian's success in the past five years and I hope that I'll be given the chance to continue contributing in the future. Rock on, Debian!

Asheesh Laroia: Load average

sh-3.1 $ uptime
12:10:16 up 20 days, 18:54,  4 users,  load average: 680.29, 656.27, 636.17
Huh.

Kapil Paranjape: Why people write Free Software

Some people troll free software lists with remarks like:
Linux will never be able to displace MacOS/Windows since the latter are much more pretty/user-friendly. You will lose.
Such people assume that hackers write free software because they "hate Microsoft" or "hate capitalism" or have some other pet hates. However, it should be obvious that such a large creative effort cannot be sustained if it is based on such negative emotions.1 There are a number of positive reasons why one works on free software. The software that I like to work on is software2 that I use or want to use. This has some consequences which are worth underlining: Giving others the "four freedoms" results in wider critical examination of these aspects. Bugs must be acknowledged and fixed --- or elevated to features! Moreover, there are parts of the task that are "obvious" to me but I would have to ask others for advice on other parts. So I gain a lot by being part of a larger community. There are other reasons to write free software. For example, someone may pay you to do it. However, this is just deferring the same question to your employer. In most cases, your employer already has a use in mind for the software. The employer has the same concerns as I outlined above except that the job of writing the code is being out-sourced. The usability, portability and long-term maintainability are probably even bigger concerns for your employer. "Last but not the least" (as we always wrote in our school-day essays) free software is fun! You share ideas with people from across the globe and to show them your own clever little tricks. Good code and good themes resonate with people who may not even speak the same language as you do. What could be nicer than that!

  1. One should not ignore the strength of negative emotions. Enormous war machines are built on negative emotions.
  2. I use the term "software" here for computer programs. Most of what is written applies equally well to books, articles and documentation --- which are "software for the brain".

Mark Brown: Whats the standard Linux audio API?

Lennart Pottering’s post about the sound APIs available for Linux appears to have caused some consternation from people working with the modern out of tree OSS drivers who feel that the current, out of tree, OSS drivers are being unfairly maligned. This rather misses the point of his post. The fact that there are improved versions of the OSS code doesn’t really help developers who are trying to target current Linux distributions which only ship the old OSS drivers. From this point of view the new OSS drivers are probably best looked at as a completely different product. Joss is right, though - most applications should be working with a higher level user space API than either ALSA or OSS. One of the most obvious examples of this is in the embedded space where there are often vast numbers of controls that need to be exported in order to support the complex audio routing that devices like phones can have. Most of these should only be touched very occasionally when changing use case and should therefore be hidden from normal applications where they’re at best irrelevant and at worst confuse end users. They do, however, need to be exposed by the kernel in order to allow user space the flexibility to manage the audio configuration of the system at run time.

Michal Čihař: Gammu test version 1.20.94

In few hours after releasing 1.20.93 it became obvious that I will need another testing release, because number of bug fixes grow too much. So here it comes. Schedule for 1.21.0 is Tuesday next week, so please report any problems you face with this testing version. Full list of changes in 1.20.94: You can download from usual place: http://cihar.com/gammu/, Debian users will find packages in experimental soon.

Josselin Mouette: The ALSA/OSS debate is irrelevant

After Lennart posted his summary of Linux sound APIs, the debate heated up again between ALSA and OSS zealots. Both ALSA and OSS developers think their API is the definitive interface for sound support in Unix and like to bash each other, and tell how the other API sucks and how the others are spreading FUD. This is not only a sterile debate, but it is completely irrelevant. Do you know why? Because neither of them is a suitable sound API. Technical constraints, functional requirements and history make the ideal sound stack on Linux look like the following: Only the last bit should be of interest to application developers. Everything else is plumbing. When you develop a multimedia application or a mixer controller, why would you care of the insanely complex ALSA library or to make ioctls somewhere in /dev when GStreamer and Phonon provide you with high-level functions that can do it in a snap? When you want to insert sounds in your game or application, why would you care of those bits when, with SDL_Mixer or libcanberra, a single line of code is enough to decode and play the sound? If we want to see sound working properly under Linux, we need to keep the stack simple and to clearly separate the roles. In the end, this boils down to very simple things: Please, guys, hold off a minute. You are developing drivers and you must be praised for that. Keep doing that well, and stop trying to invade applications. There are people who may not know how to develop a driver, but who obviously know better what a sound API should look like.

Romain Beauxis: OSS4 and the "guide to sound apis"

Dear Adrian, I can only but complain about the "Guide Through The Linux Sound API Jungle" that you mention in your last post. All that is said there about OSS is pure FUD and only reflects a deep ignorance of the current project. It is a pitty to spread misinformations that deprecate the work of others without even trying to understand it. Here is what is said about OSS in this document:
The Open Sound System is a low-level PCM API supported by a variety of Unixes including Linux. It started out as the standard Linux audio system and is supported on current Linux kernels in the API version 3 as OSS3. OSS3 is considered obsolete and has been fully replaced by ALSA. A successor to OSS3 called OSS4 is available but plays virtually no role on Linux and is not supported in standard kernels or by any of the relevant distributions. The OSS API is very low-level, based around direct kernel interfacing using ioctl()s. It it is hence awkward to use and can practically not be virtualized for usage on non-kernel audio systems like sound servers (such as PulseAudio) or user-space sound drivers (such as Bluetooth or FireWire audio). OSS3's timing model cannot properly be mapped to software sound servers at all, and is also problematic on non-PCI hardware such as USB audio. Also, OSS does not do sample type conversion, remapping or resampling if necessary. This means that clients that properly want to support OSS need to include a complete set of converters/remappers/resamplers for the case when the hardware does not natively support the requested sampling parameters. With modern sound cards it is very common to support only S32LE samples at 48KHz and nothing else. If an OSS client assumes it can always play back S16LE samples at 44.1KHz it will thus fail. OSS3 is portable to other Unix-like systems, various differences however apply. OSS also doesn't support surround sound and other functionality of modern sounds systems properly. OSS should be considered obsolete and not be used in new applications. ALSA and PulseAudio have limited LD_PRELOAD-based compatibility with OSS.
And here is what one of the devs from OSS answered to this [1]:
It's pretty inaccurate FUD (From the URL address - it's Pulseaudio's author, right? I'd have expected him to know better). He's basically judging OSS per the old OSS/Free drivers, which is like 5 years ago, and even that he does wrong. First, *all* current implementations/emulations of OSSv3 do sample conversion. It's not even a property defined by the API but by the underlying drivers. Second, even OSSv3 supported surround, USB cards, etc. Third, arguing that "it cannot be virtualized" is disproven by the amount of emulations and alternative implementations existing out there and working in practice. (The main difficulty is mmap() API, which is very rarely used anyway, and even that can be done with, say, oss2pulse). Fourth, complaining about OSS API being awkward, is... well, awkward when you compare it to ALSA API, if you could compare it, since most ALSA API isn't documented. It's kinda funny he advocates using ALSA API (not in the quoted part above, but last time I read his blog he suggested it). Actual ALSA devs advocate against it, but using a sound library with multiple backends [2].
If you read some documentation, you can understand that OSS has been the target of some kernel developpers that didn't like it to be reused in a commercial product, back in the 90s. Hence, ALSA was launched, and OSS was progressively discarded, while constantly being the target of FUD like this. OSS has then lived for almost 10 years in the dark side of the force, but eventually did the way back in July 2007. Ironically, now most of the developpement in the linux kernel is driven by commercial interests. Most of the original complains about OSS are now fixed, including all the FUD written in this guide. In particular, software mixing is now supported. Being also part of a project that writes code to handle sound input and output, I can only but complain about the mess in the area of sound APIs in linux. However, OSS should really be reconsidered. In particular, its API is designed in order to abstract as much as possible access to the sound card, so that application writers have as less as possible to do with sound conversion and the like Those who have tried to use ALSA may for instance compare that to the "set rate near" call in its API: this call will set the rate to what the hardware support and let you handle the conversion... For each application... Also, OSS API is available across all unices, except OSX, and there is even a BeOS port going on. Finally, OSS API is POSIX oriented, reading and writing on the sound card, being a matter of calling few ioctls and then reading from the device file. In the future, OSS developpement will most probably be done as a community project, and I believe it is now time to stop spreading false ideas about the project, and give it as much attention as the other projects. For the debian users who want to try OSS4, a package is available in the packaging team's svn repository. It has been sitting in NEW for some time, I hope it gets accepted at some point.

25 September 2008

Cyril Brulebois: /proc/self/mem(e)

No picture
0. Thou shalt not take part in memes.

David Welton: Language Geekery: Reia Programming Language

This looks kind of interesting: http://wiki.reia-lang.org/wiki/Reia_Programming_Language In short: it's a Ruby/Python type of language on top of Erlang. It has a mishmash of Ruby and Python syntax, and also does objects, implemented as Erlang processes. Funny quote:
Reia uses an indentation-sensitive syntax. This allows Reia to look similar to Erlang without relying on "ant turd" tokens (i.e. , ; and .) to structure relationships between forms.
That made me laugh, and is in all seriousness, something that I do find to be a bit annoying in Erlang, especially when refactoring code. You can't just move a line of code from one place to another; you move it, then change the line endings in both places. My preference would be to do something more Ruby style rather than Python style for the following reason: the indentation thing makes it harder to use straight-up Python for templating purposes, whereas Ruby can be used as-is. Templates are something that I wouldn't particularly want to do in Erlang, either, so doing them with this language might be a very nice alternative. Anyway, it looks to be in its infancy. Unfortunately, it seems to require a more recent version of Erlang than what ships with Ubuntu Hardy. Maybe Intrepid will have something recent enough to run it. It's a little known fact that I originally wrote Hecl in Erlang, although, sadly, I can't find the code any more.

Next.

Previous.