Search Results: "ag"

21 January 2007

Christian Perrier: 99,51%

This is the current translation ratio for French in unstable, after 4 days of "blitz l10n NMU". Many other languages did benefit from this as well, as shown here (for instance, Czech went over 90% for the first time as far as I can tell). All remaining packages with incomplete or missing French translations have prepared NMUs and we can expect reaching the Grail in the next week. If I have enough courage, I'll probably continue this blitz NMU campaign to kill as many debconf l10n bugs as possible. Of course, if maintainers do it themselves as sugegsted by Javier, it will be quicker.

Andreas Metzler: subpixel rendering

Following up on my previous entry there is still no snow. On the bright side it looks like I have managed to find readable settings for the new TFT. XP looked ok after enabling Cleartype however I had some problems on the Debian side. I have stepped through dpkg-reconfigure fontconfig-config a dozen times without much luck. Removing -dpi 100 from /etc/X11/xinit/xserverrc to let the Xserver calculate the real resolution by using info from DDC (i.e. 99 dpi) finally seems to have improved things.

Andrew Pollock: [debian] Whoops, it seems I dropped the ball

Hi Christian, It seems I haven't uploaded a new version of the argus-server package that I prepared back in December some time, which addresses the l10n bugs you speak of. I'll rebuild it today and upload it. Sorry about that. Love, Andrew

Isaac Clerencia: Bluetooth remote

A few days ago Applemania took over Warp HQ and several workmates purchased MacBooks. The MacBooks came with this nice remote thing and I grew jealous. In my way back home I thought that it shouldn’t be very hard to get a kind of remote control working using bluetooth and my Nokia mobile. I had never coded for my mobile so I wasn’t sure about how difficult would it be. In the end it was quite easy to write a simple program that just sent every key press to my laptop via bluetooth, and it only took 113 lines of Java code. Then I spent several hours coding the “receiver” part, in the end I created a little Python app which could load different plugins and created several of these modules: There are loooots of things to improve but it works for me :) , I’ve uploaded the source code (tarball) in case you find it useful.

Adam Rosi-Kessel: Near-Death Experiences

Via the Frontal Cortex (my favorite recently and accidentally discovered blog1), on the cultural relativity of near-death experiences:
Many Africans interpret near-death experiences as somewhat evil, a bad omen or a sign that they were somehow “bewitched.” Among 400 Japanese NDErs that participated in a study, many reported seeing long, dark rivers and beautiful flowers, two common symbols that frequently appear as images in Japanese art. East Indians sometimes see Heaven as a giant bureaucracy, and frequently report being sent back because of clerical errors. Americans and Brits often say they are sent back for love or in order to perform a job or task. Natives of Micronesia often visualize Heaven as a large, brightly lit American city with loud, noisy cars and tall buildings.
I’m not sure what’s worse — returning from death to rectify the inadvertent omission of a certificate of service on a motion for leave to file a reply brief in excess of the ten-page limit (maybe I should have picked a different profession) or getting additional time on Earth because the powers-that-be failed to complete a 27B/6. I really prefer the beautiful flowers, but it’s probably too late for that. 1Is there a term of art for such blogs? E.g., a blog discovered from an unrelated Google search that turns out to be worth adding to the blogroll.

Jan Wagner: Music and Debian

Today I found a way to combine consuming my favorite Radio Station and using my favorite System Distribution.

On working hours and most of the time at home I’m listening to Frisky Radio, founded by Faisal Sultan. But I’m missing it the 3 hours per day, when I’m traveling between work and home town. I did realize, Frisky Radios provides podcasts, but only one per week and the download history isn’t such long. Some days later, I thought stream ripping could be nice. So I did run:
$ apt-cache search stream ripper
goobox - CD player and ripper for GNOME
kstreamripper - kde frontend for streamripper
streamripper - download online streams into audio files
tunapie - Lists audio and video streams from Shoutcast and Icecast
My decision was to use streamripper in combination with screen.
Streamripper can provide a relay server, where you can listen to and save bandwidth and decide, what should happen with already existing tracks. This all seems very nice and I’ll see how lovely it will work together with my player, which name I will not mention in this context. ,

Steve Kemp: Turn another page at the animal bar

When I moved to Edinburgh and lived in a student flat we decided we needed pets. Gerbils were chosen as they were small, cute, and easy to hide. (Because we weren’t actually allowed to keep pets ..) After a few years of gerbils we graduated to rats. The king of the rodent world. Rats rock: They are small, cute, agile, incredibly soft, very non-bity and highly intelligent. Time passed and I moved out to live alone and then started to move up the food-chain with my own pet cat. (Tigger). Badnesstm happened, and Tigger was “replaced” by Six. I got hit with a year of illness, mostly, and so I decided to do the decent thing and return Six to somewhere where he could be loved and get the attention he deserved. Since then I’ve been petless, and basically afraid to commit to looking after a cat/dog for the 10+ years that they would (hopefully) live. I want to have a cat. I would love to own a Dog, and after talking about things in a circular fashion for many weeks with my girlfriend we decided to compromise. So … tada .. I have rats again. Two beautiful females. Here is a picture of one of them upon my girl’s shoulder.


Click to see full-size. So two rats, Basil for me, and Moptop for Meg. All being well they will live for the next couple of years, and then we might return to the bigger pets.

Christian Perrier: NMU'ing Andrew Pollock?

Dear Andrew, I'm always an enthusiast reader of your blog and more particularly the "adventures of Aussies in USA-land"...:-) But, I'm about to NMU one of your packages as part of my "blitz l10n NMU" campaign, namely the argus package. I'll of course notify you, but in case you prefer doing this yourself, please just fix the pending l10n bugs in argus. Just yell out loud..:-)

Daniel Burrows: How to Breathe, Functionally (part 2)

In a previous post, I pointed out some ways that you can acheive the "compute this, now save it and compute this, ..." style of coding in a functional language such as Haskell without going mad. This is a continuation of that post.

There's one other purely syntactic feature of Haskell that I rather like for readability: Haskell lets you define variables after you use them.


GoToTheNextTrickyBit someVal
where someVal = DoThisAndThisAndThat...


Although it isn't always appropriate to do this, there are times when I find it extremely intuitive to define my variables after they're used. For instance, to take a "practical" example, compare


mailTo customer =
let customerName = getCustomerName customer
customerAddr = getCustomerAddr customer
in
makeMailingTo customerName customerAddr


with


mailTo customer = makeMailingTo customerName customerAddr
where
customerName = getCustomerName customer
customerAddr = getCustomerAddr customer


I don't know about anyone else, but when I read the first definition I mentally go "huh. Why are we extracting the customer name?", then skip down to where the name gets used, and finally re-parse the name in that context. The "where" form lets me write the code in the same order that I would read it, giving the code a natural flow. It's very important, of course, to keep the number of auxiliary definitions small; otherwise you leave too many "open questions" for the reader of your code to carry around as she works her way down to the definitions.

But it isn't all roses at the low syntactic level. IMO, the biggest practical problem with writing Haskell code is the syntactically significant indentation.

Python, of course, also has significant whitespace -- but it works mainly because it's extremely simple. Any line ending in a ":" introduces a new block, and statements within a block have the same amount of indentation. In contrast, Haskell's rule...well, just read that link above. You can write code that has the same meaning under any indentation, but it's not idiomatic to do so -- and worse, since the statement terminators are not obligatory, a missed terminator might work fine, might change the meaning of your code, or might fail to compile in an obscure way.

A side effect of the complicated indentation rules in Haskell is that the Emacs Haskell mode doesn't work very well at indenting my code. It usually chooses an indentation that I don't want, and often one that doesn't even compile. I'm sure Emacs could do better, but I would be willing to live with a little more punctuation if it meant that the code was easier for programming tools to process correctly. Functional coding advocates assert, correctly IMO, that side-effects are problematic because even smart programmers will write more bugs in their presence. I think the same logic should apply to syntax: making the language harder for humans and machines to parse has negative overall effects, even if it is possible with sufficient effort to parse it correctly.

I think that conceptually, Haskell is a great language -- the problems I see with it are issues of syntax, tool support, libraries and speed (laziness has a high price). Oh, and also the fact that, as with most programming languages that are pleasant to use, you can't get a real paying job writing in it unless you have a PhD. :-(

Julien Blache: ftpmasters slowly implementing source-only uploads ?

A couple of weeks ago, ftpmasters decided to reject arm uploads that aren’t signed by either a buildd or one of the blessed arm porters. Yesterday they decided to do the same thing for alpha. So, dear ftpmasters, are you slowly implementing source-only uploads, or are you only preventing Debian Developers from doing their work (which would obviously violate the Constitution) ?

Daniel Burrows: How to Breathe, Functionally (part 1)

David Welton writes that the problem with functional languages is that you don't get to mentally "catch your breath" between computations; piling function invocations on function invocations makes it hard to understand what's actually being calculated. He has an amusing summary of how functional code can become unreadable:


Do this with the result of this with what this produces when given this input that is derived from this function which takes the result of this other thing after calculating the result of something that is derived from the output of a function that ...


Indeed, I've seen functional code like this (much of it written by myself). Here's a particular gem:


f splitPoints = map fst $ tail $ scanl (flip ($) . snd) ([], toSplit) $
map splitAt splitPoints


I wrote this code a year ago, and I don't know what it does! It's hard to read and hard to understand. So, however, is imperative code that says


Add 5 to A, now if B is not zero we jump to where we subtract one from B and if C is less than 3 we add 4 to C otherwise we divide C by 2 and then add it to A, then we ...


The reason both pieces of pseudocode are hard to understand is that they don't use the abstraction features built into the language. Good imperative code uses meaningful variable names, uses the structured-programming primitives the language provides, and abstracts complex operations into functions.

My rule of thumb (which is, heh, not always religiously followed) is that a piece of program structure that does more than about 3-6 things is probably too complicated; it seems like that's about as much local context as I can hold in my head comfortably (and the number is more 3 than 6 these days, if you get my drift). As David puts it,


If you'll bear with a poor comparison, sometimes programming is like a song. You do the tricky section, then you go back to an easier section and catch your breath for a bit.


The problem seems to be that people trained on imperative languages, when they're tossed into the ocean of functional coding, can't find the guideposts and landmarks that would help them impose some structure on the water. Should I put this complicated expression inside a "let", or break it out into another function? When do I use a higher-order function to unify two dissimilar pieces of code? Should I write this code in terms of higher-order library functions or directly? It's easy to wander off down a chain of nested invocations of anonymous higher-order functions, or composed partially applied library functions, just "because you can" and end up forgetting what you were trying to do in the first place.

Luckily, some of the basic rules of keeping your code readable remain more or less the same: assign intermediate results to variables with meaningful names, and abstract complicated operations into separate functions. To tackle David's example:


You get sections with DoThisAndThisAndThatWithTheResultsOfSelectThisFromTableXYZ that you have to slow down to think through.

...

GoToTheNextTrickyBit where ManyThingsHappen.

All in all, you wind up with a sort of ebb and flow that works out pretty well if you're in tune with the code being written, going from intense calculations, to a line or two where you do no more than store things in a variable, take a breather, and prepare for the next important stanza.


The way to "take a breath" in a functional language is generally to assign an intermediate result to a variable, or to extract a complicated operation into a function and give it a meaningful name. One Haskell approximation to David's example is


do DoThis
AndThis
results - SelectThisFromTableXYZ
someVal - AndThat results
GoToTheNextTrickyBit someval


If you're writing pure functional code, you might write


let
results = SelectThisFromTableXYZ
someVal = AndThat results
in
GoToTheNextTrickyBit someVal


Of course, this will become unreadable if you write a huge complicated nested "let" expression in place of "AndThat". For a truly dreadful example of this kind of coding, check out the Gnucash Scheme code that generates the "Cash Flow" report (warning: read this in short bursts, or you WILL go blind). This is exactly analogous to writing too many nested loops and conditionals in imperative code, and the fix is the same: find logically distinct bits of code and extract them into separate functions.

I have a few more thoughts, but this post is getting too long, so I'll inflict them on the world in another post. The rule that short things are easier to understand applies to blog posts as well as code. :-)

Daniel Burrows: Via C7: it goes fast AND slow!

The low-powered system I assembled recently is based on a Via Epia board and a C7 CPU. I spent quite a bit of time when I was setting it up trying to get the C7's speed stepping to work. I loaded a number of cpufreq modules without luck; crawling around on the Web only led me to discussions about how the C7 couldn't be speed-stepped in Linux and maybe the centrino cpufreq driver would work.

Well, yesterday I randomly searched again -- and poof! There was a discussion from early January about how maybe the ACPI cpufreq driver would work. I loaded it, set up powernowd, and was rewarded with


daniel@jeeves:~$ cat /proc/cpuinfo
processor : 0
vendor_id : CentaurHauls
cpu family : 6
model : 10
model name : VIA Esther processor 1200MHz
stepping : 9
cpu MHz : 400.000


Sweet. Now all I need is for the Debian kernel folks to package a version with a vt1211 lmsensors driver so I can shut down or slow the fans, and I'll be all set. (I could probably hack it in myself, but according to what I've read on the Web, the next kernel release will have a working driver)

[UPDATE: I disabled cpufreq after only a day or so, because Linux got horribly crashy with CPU scaling turned on. Hopefully the kernel will be fixed sometime in the future :-/ ]

20 January 2007

Erich Schubert: The end of the world 2.0 is near.

I'm convinced the Web 2.0 bubble will impact soon. Granted, some will survive, some will struggle - but some will just blow up. Time to sell for these. There are several reasons why I believe this will happen "soon": Many people have been keeping an hungry eye on YouTube, Rapidshare and others. It's just a matter of time until some of these predators goes for the kill. My predictions for the post-web2.0-bubble time:

Adam Rosi-Kessel: Quotes on Signs

Does anyone have any idea why this phenomenon is so common? What is the hidden message implied by the quotation marks? A nudge and a wink? Captured (by cell phone) at Butterfly World in Coconut Creek, Florida.

Eddy Petrișor: HOWTO test PPPoE without having PPPoE (long)

I don't have an ISP which uses PPPoE or more than a laptop on my desk, but still, thanks to free software, I can test PPPoE installations (to some degree).

I have set up with qemu machines a virtual LAN that is made totally in user space via a TCP socket on port 1234. I needed this in order to test the changes I am working on for the ppp-udeb Debian installer module that supports (or should I say, should support) configuration of PPPoE connections.

These are the tools whose authors and maintainers deserve kudos:


This is the tutorial I followed to configure the PPPoE server http://www.freeantennas.com/PPPoE-Server-HOWTO.html, but until then I had to make the network.

In case someone is interested, here's how I did it (these are Debian centric instructions, but I don't see anything that would stop someone to do the same even on a windows machine).
I won't repeat that tutorial, but now I can create a virtual machine (well, I'll use an existing virtual machine) and test my custom D-I images and test the changes done in ppp-udeb.

Rock on!

Julien Blache: Once again, XFS saves the day

The server hosting this blog just suffered what can only be described as catastrophic hardware failure, thanks to the crap that are Maxtor hard drives, Dell CERC 1.5 RAID controllers and the Linux driver for those (aacraid). So, the machine got shut down for a moment on thursday night, just the time to move the rack around in the datacenter, and one of the disks did not come back in one piece. But it did come back online after a reboot, prompting an array rebuild by the controller which took 12.5 hours for 250 GB (RAID 1). And the drive failed again 10 minutes after the rebuild was completed, confusing both the controller and the driver. At that point I could still log into the machine, but any command would trigger nice I/O errors all over the place. Fortunately, the FS got shut down by XFS automatically on I/O errors and I haven’t lost a single bit of data. The machine came back just fine with the faulty drive removed. And you thought a RAID controller would help in this case. Obviously this one doesn’t. I need to mention that we’ve observed this behaviour on another machine before this incident, we have another machine suffering from a faulty drive in just the same way, so this isn’t an isolated case and it’s reproducible.

Evan Prodromou: 30 Niv se CCXV

I just got the Free Your Phone announcement from the OpenMoKo announce list. Looks like they'll have preview versions of the new Linux-based, Open Source phone platform available Feb 11, generally available March 11, and ready for public distribution September 11 (!). FIC is under a lot of pressure to make this product the Open Source answer to the iPhone, and I think they have a very good story. At this point I think the success of the platform is going to depend on three things. First, FIC's execution in getting developer versions out the door and ready to use. If the OpenMoKo platform stays vapourware for much past the first part of 2007, it won't be able to capitalize on the iPhone hype and current excitement. Second, FIC is going to have to resist the temptation to hold back parts of the OS or the application stack as proprietary software. Credibility in the Free Software fanatic community is going to be key for its first wave of usage, and "free enough" isn't going to be good enough for this product. A good cautionary case would be Trolltech's Qtopia. Trolltech's reputation for holding back parts of its stack has probably been the main reason this platform hasn't been taken up by Linux aficionados. Third, and perhaps most importantly, support from more hardware vendors. "Open Source" is sometimes a synonym for "second source" -- it gives customers and developers the security of knowing that the success of a platform is not tied to the success of a particular company. OpenMoKo can take the Free Software niche in the smartphone OS market -- making a place among Symbian, Pocket PC, and Palm OS that appeals to hackers. I think if they can get the hackers, they can get the kind of UI quality and application availability that will get the rest of the population interested. Firefox is an example of an Open Source project that has done this recently. All in all, I think FIC has a lot of challenges ahead -- mostly internal. But I also think that if this is played right, OpenMoKo or something like it could change smartphones the way Linux and the *BSD family have changed servers. tags:

Hillary's In News bulletin: Hillary's In. She's in to win. She's in to win the Big Spin. She's in up to her chin. She's in and so is her twin. She's in with a grin and a tin of aspirin. Hillary's in by the skin of her shin. She's in with the thin fin of an elfin dolphin. So it begins. tags:

Martin F. Krafft: No-fly list to be scrubbed?

Nori points me to this article by Bruce Schneier, which seems like good news for me. Does it mean I'll be able to visit the US again sometime in the future? I don't think so; travel to the US is among the most unattractive things I can currently think of. I might reconsider when the US stops treating visitors like terrorists, taking their fingerprints and requiring so-called "Passenger Name Records" to be made available by the airline companies transporting passengers into the US, with the sole purpose to build a criminal file for everyone entering the country, just in case they become a threat to national security or an obstacle in the path of the neo-conservatives to forge ahead. In addition, I'd fear for my laptop, which US immigration officers can now seize without reasons and scrutinise; I do not own a laptop because I can do without one for weeks on end. Furthermore, all my data are encrypted for good reasons. As the old saying goes: "only the guilty have something to hide", I'd surely make it into their prisons as a suspected terrorist (which has happened to people before). What the US doesn't understand is that even though I may be guilty and therefore hiding something, it doesn't mean I am hiding it from them. So no, I don't think I'll enter the US anytime soon. NP: I Love You but I've Chosen Darkness / Fear Is on Our Side

Bernhard R. Link: please add mime-types

Enrico blogged about translating the mime-types of file to a debtags, stating "I&aposm not sure it&aposs a good idea to encode mime types in debtags".

I just want to throw my two cent in here and state that I only once looked into debtooks and gave up because it does not list mime-types but some obscure other specification.

Getting suggested programs that support formats which have the same type of content like the one I want to show, to convert or to create does not help me. I most of the time do not want to edit "a video" or "a spreadsheet", but I first of all have a very specific file I want to do something with, or a specific set of formats I want to create something in. If I have a AbiWord file, Openoffice.org will not help me, and with video or audio formats it is even worse.

So after turning away disappointetly from debtags, I had to do a full mirror scan for /usr/lib/mime/packages/ files and their contents. Having that data cached in debtags would be something that really makes debtags usefull in my eyes. (And the more direct and verbatim the mime-type is encoded, the more useful it would be for me).

Eddy Petrișor: RC bugs, what about important ones?

I was wondering if is right to our users that we are following only the RC bugs before a release. I think not. Don't get me wrong, I don't want important bugs count to be 0, or something similar; that would be insane to have as a goal.

I am thinking that we should (during the freeze) poke more of those important bugs that our and/or others' packages have. If you are like me, you will feel that you can't do anything/too much to improve the quality of the release during the freeze since some of the RC bugs are corner cases, not reproducible on your arch, already taken or you don't have the knowledge to fix them.

Many of the important bugs are broken functionalities that affect the users on a daily basis, and living 2 years with the same set of bugs is a pain. I don't know how that would feel, but I can imagine. I used Woody for only a half an year and after 2 months I started using backports. After 3, I started pulling things from Sarge (at the time it was testing). At the end of that half of year I was using mostly Sarge stuff and decided to go entirely into testing.


So, what do I propose? Maybe we should make some pages in the style of the RC bugs count pages which follow the important bugs.

As a bonus we might see some interesting things like bugs which were downgraded from RC - the RC graph would go down, while the important graph would rise. Of course, that wouldn't mean too much since that would be the product of badly assigned severities or downgraded and judged as non-RC bugs, but it would interesting to follow such tendencies.

Next.

Previous.