Search Results: "ron"

8 September 2006

Andre Luis Lopes: Sorry for the noise

Sorry Planet Debian. The last post was intended to appear on Planeta Debian Brasil only, not on Planet Debian. I tend to separate my posts written in english and in portuguese using different categories for each and have both Planet Debian and Planet Debian Brasil being feed from the relevant URL for each category. It was just a mistake from my part giving the last post (written in portuguese) the wrong category. It’s already fixed and I hope not to make the same mistake again in the future.

Andre Luis Lopes: Por qu Debian ?

Tenho aqui comigo um o in cio de um texto antigo, que comecei a escrever h uns dois anos atr s, sobre porque eu uso Debian. Nunca consegui finaliz -lo direito, mas achei que n o seria justo deix -lo aqui jogado em um diret rio empoeirado de meu HD (meu ~/txt tem muita coisa iniciada e n o finalizada). Um dia ainda vou termin -lo e acrescentar mais conte do, s preciso estar num dia inspirado para tirar todas as id ias da cabe a e coloc -las na forma de palavras. De qualquer forma, mesmo inacabado, espero que gostem. E lembrem-se : meu blog aceita coment rios :-)
Por qu Debian ? Eu tamb m ou o esta pergunta quase diariamente. Para que eu n o tenha que respond -la novamente a toda vez que me perguntem, resolvi sentar e escrever uma resposta padr o para a mesma. Assim, toda vez que algu m me faz esta mesma pergunta novamente, eu simplesmente pe o para a pessoa ler este texto. Aspectos t cnicos Qualidade. Sim, qualidade. Erroneamente, a maioria das pessoas que n o utilizam Debian ou que n o o conhecem pensam que o grande motivo pelo qual o Debian se diferencia das outras distribui es GNU/Linux puramente pela exist ncia da ferramenta APT, a qual auxilia na resolu o autom tica de depend ncias, facilitando enormente o gerenciamento de softwares. Realmente, trata-se de uma ferramenta extremamente til. Por m, atualmente, diversas distribui es GNU/Linu baseadas em pacotes no formato RPM (Red Hat, Fedora, Mandriva, etc) utilizam por padr o ou suportam, mesmo que n o oficialmente, mecanismos de resolu o autom tica de depend ncias e gerenciamento de softwares similares ao APT. Algumas at mesmo utilizam um porte do pr prio APT, adaptado para funcionamento com pacotes no formato
RPM. O que diferencia o Debian das demais distribui es GNU/Linux a qualidade. O apt-get a parte vis vel qual o usu rio tem acesso e que parece fazer toda a m gica. Por m, por atr s dele, existe um componente fundamental, frequentemente esquecido pelos usu rios : a pol tica de empacotamento de softwares Debian. O projeto Debian possui um documento extenso e altamente detalhado, que descreve, em cada m nimo detalhe, ao que um pacote de software precisa estar atento para poder ser considerado um pacote oficial e fazer parte da distribui o. A pol tica de empacotamento de softwares o que faz com que o Debian seja altamente superior s outras distribui es. Ela bem definida, clara e aplicada rigorosamente. Ferramentas de apoio aos desenvolvedores auxiliam a refor ar a aplica o das regras ditadas pela pol tica e qualquer pacote de software que n o siga fielmente o que dita o Manual de Pol ticas Debian n o inclu do em uma vers o oficial da distribui o, n o importando o qu o importante seja o componente de software fornecido pelo pacote. Isso, somado s diversas equipes internas existentes dentro do projeto Debian, garante a qualidade da distribui o. Equipes de QA (Quality Assurance), de seguran a, de ger ncia de release, ger ncia de relatos de erros e diversas outras equipes garantem que um sistema operacional funcional e altamente integrado seja criado, em oposi o a mera corre o de problemas em pacotes de softwares isolados. Adicionalmente, cada software passa por um intenso processo de avalia o antes que possa ser aceito oficialmente e adicionado a distribui o. Al m dos in meros detalhes t cnicos, tamb m existe uma equipe de especialistas legais que analisam as licen as de distribui o dos softwares antes de aceit -los como parte da distribui o. O fato do Debian ser atualmente a distribui o GNU/Linux que suporta a maior quantidade de arquiteturas de hardware que o kernel Linux suporta tamb m adiciona qualidade distribui o, uma vez que, como parte do processo de porte das aplica es para uma arquitetura de hardware suportada pelo Debian, in meras falhas s o descobertas e corrigidas, o que contribui
para a qualidade final do software. Logicamente, some a isso tudo o fato do projeto Debian possuir o maior acervo de softwares livres empacotados e prontos para uso existente da atualidade, deixando para tr s todas as outras distribui es GNU/Linux, inclusive as distribui es comerciais. Atualmente, s o mais de 15.000 pacotes de softwares prontos para uso e facilmente instal veis. Aspectos estrat gicos (ou independ ncia tecn logica) Uma das grandes vantagens estrat gicas que se ganha ao utilizar Debian a independ ncia tecnol gica. L gico, a grande maioria das distribui es GNU/Linux atuais s o livres, mas nada garante que continuar o a ser livres por toda sua exist ncia. Claro, sempre existir o grupos de pessoas dispostos a iniciar uma nova distribui o com base em uma vers o livre existente de uma distribui o comercial caso algo aconte a com a empresa que a desenvolveu e que impossibilite a continuidade da distribui o. Mas criar uma comunidade e manter um projeto grande como o de uma distribui o GNU/Linux, com toda a infraestrutura j fornecida pelo projeto Debian, leva tempo, anos. E consome anos de trabalho de milhares de volunt rios. O projeto Debian j tem tudo isso funcionando e uma experi ncia de 13 anos nessa rea. Exemplos de problemas com o envolvimento de interesses privados de empresas no desenvolvimento de distribui es GNU/Linux n o s o somente te ricos e recentemente tivemos provas da exist ncia dos mesmos, com empresas privadas terminando a continuidade do acesso a atualiza es de seguran as para suas distribui es de uso livre e sem custo e, em
muitos casos, praticamente obrigando seus usu rios a migrarem para vers es comerciais de suas distribui es. O projeto Debian criou o Contrato Social Debian. O item n mero 1 desse contrato social diz que o Debian ir sempre permanecer composto de 100% software livre. De igual import ncia, o item n mero 4 desse mesmo documento diz que a prioridade do projeto Debian ser sempre seus usu rios e o software livre, o que, na pr tica, garante que interesses comerciais n o ser o colocados em primeiro plano e que os usu rios n o ser o for ados a migrarem para vers es comerciais da distribui o em momento algum. A Defini o Debian de Software Livre, mais um documento produzido pelo projeto Debian, possui grande import ncia na comunidade de software livre, tendo sido utilizado como base para a cria o do Defini o de C digo Aberto (Open Sorce), a qual individuais e empresas aderentes ao modelo de desenvolvimento aberto de software usam como base para cria o de licen as de softwares que os qualifiquem como software aberto (Open Source).
Ok, isso por enquanto. Um dia ainda termino e acrescento mais conte do. Quem quiser comentar e dar novas id ias, esteja a vontade, nos coment rios ou por e-mail.

Martin F. Krafft: mutt tagging

Dear lazyweb: I love mutt, my faithful mail client for almost a decade now, but I think I've reached its limits. Not that mutt isn't doing fine, it's more my way of organising mail that's no longer working for me. To give a short overview: I receive all mail in a single account and filter messages to folders in a hierarchy. My filter set spans several thousand lines and has been growing for seven years now, the last "refactoring" was in 1999. When browsing mail, I either delete messages (for list mails mostly) or save them to the read folder when I am done with them. The hierarchy is mostly arranged by field of endeavour, and then subdivided into specific topics. For instance, I have =private/dudes/..., =debian/pkg/mdadm, =ul/phd, and =work/clients/.... I currently face two major problems with this approach:
  1. Folders just don't cut it anymore. For instance: with my job, research, and hobby all somewhat connected to Debian, most messages I receive don't belong into one folder any more than they should be in another. What I want is effectively what gmail and several of the GUI clients do: any given message can have a number of tags, and virtual folders act as filters to display only messages with a certain tag.
  2. Having a single sent and read folder for all worked for a while, but it's long been a major pain. What I really want is for sent and received mail to sit right next to each other in all cases, ideally based on tags as well.
I found mutt's X-Label patch (the Debian mutt package includes it), which seems to go in the right direction, but it's not exactly what I want (yet). For my purpose, it adds a selector ~y to use in searches and when limiting the display of a mailbox. Thus, I could implement virtual folders by saving all mail to a single folder (thanks to the header_cache patch), then executing l~ydebian to see all messages tagged debian. The problem with this approach is that it uses a functionality that I already use extensively: limiting. I like the thought of being able to use tags as filter criteria, but I don't want to depend on them. For instance, if looking at all messages with the debian tag, and then filtering those with mdadm in the subject, I currently have to hit l<space>~s mdadm (taking care to preserve the label limit), and I cannot use the simple_search functionality anymore. In the end, what I'd want is to be able to use the folder syntax for tags. Specifically, I think it would be cool to have folders as they are currently, but if you try to change to a folder that does not exist, or prefix the folder with vfolder (=vfolder/debian/mdadm), it would instead display the main folder with the different path components used as label filters. A syntax for logical OR would also be nice. All this should happen without affecting the limit functionality of mutt. I don't think this is currently possible, but before I start to pretend to plan my intent of eventually thinking about what it would take to have a go at coding a patch, I'd welcome your feedback. I can't imagine that I am the only one wanting mutt with tags... NP: Log / Every Time a Bell Rings, an Angel Gets His Wings Update: people have pointed me to Gnus and Mairix. I'll have to check out Gnus, but I wonder whether it can be used the way I do mail: currently, I use offlineimap (my favourite software award 2004-2006) to synchronise my Maildirs across a total of eight machines, so that it does not matter where I read my mail -- it's totally synchronised. I'll give Gnus a whirl soon though. Manoj already showed it (off) to me, and several other Debian developers seem to swear by it, so it can't be all wrong. With respect to Mairix, I know that tool; it basically populates folders with symlinks according to search criteria. One could say it instantiates virtual folders. The problem I have not been able to solve yet is quite simply that operations such as moving messages to other folders then operates on the symlink, which is not what I want, for obvious reasons. Even just using mutt to edit them results in a copy made, so the symlink association is lost. I'd be happy to be shown how to use the tool to make it do what I want. NP: Led Zeppelin / Led Zeppelin I

Wouter Verhelst: Re: Undelivered Mail Returned to Sender

Dear SMTP Server program at host orange.fr,
It's great if you inform me that my message could not be delivered to
one or more recipients. It's also wonderful if you attach it below, so
that I can verify what's going on.
It's less great if verification shows that the mail you're replying to
was sent by me on 24 july 2005, which is over a year ago.
It's not very interesting if verification also shows that the mails in
question were actually mailing list posts, meaning that you sent the
bounce to the wrong address (it should've gone to the mailing list
bounce address instead).
It's rather annoying if you repeat this behaviour sixteen times. I guess
I should call me lucky that I only sent four mails on that day, and that
only four people on your mailserver were subscribed that day.
No, I did not contact postmaster, since the mails weren't all that
important, and I doubt there's anything they can do about it at this
point. I certainly don't need assistance with these mails.
Also, if I would address your postmaster the way you suggest it to me,
those mails would end up in my own mailbox anyway, rather than in your
postmaster's mailbox.
Your postmaster is, however, welcome to contact me if they so desire.
Love,
Wouter

7 September 2006

MJ Ray: Installation Difficulties

Yesterday, I helped a friend install an Edimax wifi USB stick. I've been using wireless networking lots for a year or two without much trouble, even testing experimental drivers sometimes, so I thought this would be straightforward. How wrong was I? First complication: the target machine is running the latest Windows, but still needed a driver CD-ROM loading. The instructions were quite clear that this must be done before plugging in the stick. What it doesn't tell you is that the stick has to be plugged in at a specific point during installation - cue mad unpacking. Second complication: the autorun program on the driver CD tries to do DNS lookups. Why on Earth? This is part of installing a network device. There is no working connection to the network, else we would probably not be installing this... Third complication: the questions in the install wizard are nonsense. For example: "Do you want to optimize for performance or for wifi operation?" Erm, I'd like it to operate as a wifi device with good performance please. The installation manual didn't explain what the questions meant, but did at least give recommended answers. Final complication: the driver utility has at least two ways of setting which wireless network to use (as well as the target AP, there's a BT Home Hub and some other BT kit somewhere nearby, according to their ESSIDs, although the USB stick only saw the Home Hub). One of them works. One doesn't, with the same settings. The only obvious way to find that out is trial-and-error. There's no useful error message when it fails - just no working network connection. Yes, lots of Linux stuff is harder to install than it needs to be, but at least its questions mostly make sense and most things give proper error output that helps to debug it. Windows is still in the dark ages on these two. I guess it's the lack of peer review: I didn't see any way to send a bug report to the dodgy driver designers. By the way, the Edimax stick works pretty well (although their web site is terrible). I think I'd recommend it, particularly if you're not using the Windows drivers... It says on the box it works on Debian and it looks good on linux-wless, but I've not tested that.

6 September 2006

Gustavo Franco: Debian Desktop Artwork meeting

The Debian Desktop Artwork meeting was a success, some members of pkg-kde, pkg-xfce and pkg-gnome and others were there. Thank you guys!

We focused in 8 (some of them dupes) artwork artifacts - basically login screens, wallpapers and splash, and the 4 items that were previously in our agenda. It was consensus that we need some guidelines and probably we can use one single source package (desktop-base) to build multiple binaries (at least one per desktop environment).

If you want to join this effort, join us at debian-desktop mailing list. I'll post a summary of our meeting there and the full meeting log will be available soon. There will be other meeting where i'll talk about the guidelines status and we will discuss the technical details raised on the list.

I'm living on the Etch...

5 September 2006

Gunnar Wolf: Official: The fraud is a fact.

Today, as it was widely anticipated, the Superior Tribunal of the Judicial Power of the Federation (TEPJF) declared Felipe Calder n, of the currently right-wing governing PAN party, elected as president for the 2006-2012 period.
My regular readers will know that my political views are against his party's, and that I completely oppose him - Of course, being consequent, in June I started, together with some friends, FeCal.org.mx, a site destined to show the incongruencies and incoherences in the official version - and that evolved to a site I am quite fond of, having good and deep analysis of the political situation. Of course, it is time now to redesign and think forward for this site, now that FeCal is no longer a candidate - but lets leave it aside for now.
Today, we are mourning. We are not mourning an electoral loss - Wherever there is democracy, there are losers, and it might be right that we lost this time. Furthermore, in political systems such as ours, it is practically guaranteed that the majority of the citizens will lose (this means, it is terribly hard for any candidate to get over 50% of the votes - If Calder n wins with almost 35% of the votes, or if L pez Obrador wins by a similar amount, we will anyway have 65% of losers). But what we are mourning goes far beyond that: We lost faith in our electoral institutions, which we were so proud of a couple of years ago. They proved not to be serious, not to be adequate for a hard decision. Why am I saying this? Lets analyze a bit.
First of all, the Federal Electoral Institute (IFE)'s main function is to organize the federal elections, and to make sure they are run with neutrality. Since the early months of the formal competition (as the campaigns themselves started way too early and we Mexicans are sick of the eternal electoral climate), the IFE has not acted in time to stop a dirty campaign, made not only by the PAN party but by the nation's President himself and by groups that, being privately owned, are said to be outside the reach of the IFE's regulatory spectrum. The IFE's general council should have been built with representants of all of the main political forces, but only PRI and PAN (which means, center-right and right wing) were represented.
Secondly, over the last six years, President Fox seems to have made constant efforts not only to prove us all he is a complete fool and inept as a statesman (examples abound, there is no rush to prove Vicente Fox just cannot be trusted to run a country), but that his fight for democracy was nothing but a race for personal power. He took every oportunity he could to promote his party - while the Mexican law requires him to remain neutral during the electoral period. There are many proven examples of irregularities and corruption inside his cabinet (most notably those carried out by Josefina V zquez Mota, who was in charge of all of the federal programs to fight poverty, and was the coordinator of Calderon's campaign) leading to inject resources into the campaign. Yes, this should have been stopped by IFE as soon as they were detected - But it was not. And, thank you Mr. Fox, by doing this you severely undermined the respect there should be for the Presidential figure.
Now, IFE's role ends shortly after the elections. After that, it is TEPJF's role to qualify the elections - To ratify they complied to the required equity, legality and certainty. Many of us had more trust in TEPJF than in IFE, mainly because of the series of personal and group connections that came up between IFE and the power groups. Most of us were quite vocal on the voto por voto, casilla por casilla front - Demanding from TEPJF to request to recount all of the votes. Having only 0.58% distance between the top candidates, with lots of statistical anomalities, with tons of reports of illegal tampering of the ballots, having a wide recount would surely make many among us believe and accept the results - Of course, the PAN repeated ad nauseam that the ballots had been counted and we should not go again over the same excercise, quoting all kinds of arguments that came from a too narrow interpretation of the law. And, in the end, too narrow was the response of TEPJF - Only 9% of the booths were reinspected, and not all of them were recounted. In fact, one week ago, they decided to discard over 300 appeals (this means, 300 requests for trial on a specific booth or on a whole district), without yet disclosing which appeals were they, on what basis were they discarded, what geographical areas did they impact, or anything. They nullified about 235,000 votes - And this number is quite scary, as it practically matches the official difference between the two lead candidates (244,000 votes before this partial recount, 233,000 after it). We can now state for certain that the difference between the candidates is smaller than the error margin.
Today, with a very important portion of the country in doubt on whether their decision was legal and correct, TEPJF ratified Felipe Calder n as the elected president. This would be good news. I would like to accept Felipe as my president - Sadly, I cannot, just because all of the TEPJF's principles were violated: So... In short, what comes now? We are exhausted by this long process. As too many people, I just cannot accept the imposition of yet another fraudulent president. I had the hopes that Mexico had changed in the last 18 years - But it has not. We are still in a strong presidentialist regime, and we still don't have hopes of getting a democratic government. If we do have a democraticly elected president, perfect, I will accept it. Of course, criticizing and keeping a close eye on his government, as I don't think the social and economic principles they push, but accepting. But there are too many signs of a fraud, there are too many stinky bits in the decision. The stinkiest of them all, the refusal of their opportunity to shut us up. Is it better to have millions of angry citizens closing important streets and giving Mexico a bad name by writing about our trip back to the stone age than to allow for a legal recount? Is it too much asking giving some certainty to our elections? Is there any doubt we will keep fighting this imposition?

John Goerzen: Another Haskell Solution to Lars' Problem

Yesterday, I posted an 18-line solution to Lars' language problem. One problem with it was that it was not very memory-efficient (or time-efficient, for that matter). In other words, it was optimized for elegance.

Here is a 22-line solution that is much more memory-efficient and works well with his "huge" test case. Note to Planet readers: Planet seems to corrupt code examples at times; click on the original story to see the correct code.

import System.Environment
import Data.List
import Data.Char
import qualified Data.Map as Map
custwords = filter (/= "") . lines . map (conv . toLower)
    where iswordchar x = isAlphaNum x && isAscii x
          conv x = if iswordchar x then x else '\n'
wordfreq inp = Map.toList $ foldl' updmap (Map.empty::Map.Map String Int) inp
    where updmap nm word = case Map.lookup word nm of
                             Nothing -> Map.insert word 1 nm
                             Just x -> (Map.insert word $! x + 1) nm
freqsort (w1, c1) (w2, c2) = if c1 == c2
                                 then compare w1 w2
                                 else compare c2 c1
showit (word, count) = show count ++ " " ++ word
main = do args - getArgs
          interact $ unlines . map showit . take (read . head $ args) .
                     sortBy freqsort . wordfreq . custwords

The main change from the previous example to this one is using a Map to keep track of the frequency of each word.

Wouter Verhelst: Belpic 2.5.9-4~bpo1

Or, BEID of the same version. Oh well. It took me a while, but I finally managed to jump through all the hoops[1] required by backports.org correctly and in the right order for the package of the above version to appear there. So if you're running sarge, have an electronic ID card and a smartcard reader, and want to see what the government knows about you, then go ahead and install them. More info on how that works can be found on the backports.org website. There are two known issues as of now: first, you may get wrong root certificate errors; second, you need to install all packages from the belpic source package, or some things may fail. I intend to properly fix these two bugs Real Soon Now(TM), but I'm having issues reproducing the first one and am trying to wrap my head around being policy-compliant and produce working packages at the same time, which is required to fix the second one. It's slightly ugly; believe me, you don't want to hear the details. Speaking of ugly, SCons is not ugly. It's downright hideous. I'll have autotools any day. If you're not running sarge but are using Ubuntu 6.06 'Dapper Drake', then you will need different backports. Luc Stroobant was kind enough to provide them; use deb http://www.stroobant.be/eid ./ in your sources.list to get them. [1] they are not many, but I managed to break my upload three times or so before it actually worked. And since I don't know about any status page or so, I needed to ask people every time—which I don't want to overdo, so I give them a while before investigating. Next time I probably won't...

Wouter Verhelst: Belpic 2.5.9-4~bpo1

Or, BEID of the same version. Oh well. It took me a while, but I finally managed to jump through all the hoops[1] required by backports.org correctly and in the right order for the package of the above version to appear there. So if you're running sarge, have an electronic ID card and a smartcard reader, and want to see what the government knows about you, then go ahead and install them. More info on how that works can be found on the backports.org website. There are two known issues as of now: first, you may get wrong root certificate errors; second, you need to install all packages from the belpic source package, or some things may fail. I intend to properly fix these two bugs Real Soon Now(TM), but I'm having issues reproducing the first one and am trying to wrap my head around being policy-compliant and produce working packages at the same time. It's slightly ugly; believe me, you don't want to hear the details. Speaking of ugly, SCons is not ugly. It's downright hideous. I'll have autotools any day. If you're not running sarge but are using Ubuntu 6.06 'Dapper Drake', then you will need different backports. Luc Stroobant was kind enough to provide them; use deb http://www.stroobant.be/eid ./ in your sources.list to get them.

4 September 2006

Neil McGovern: Microsoft causes software piracy

Over the past three years, my girlfriend's computer has been running slower and slower. This isn't a huge surprise, as it's running Windows XP, which seemingly becomes bloated as time passes. Thus, it came time for a reinstall, or at least some major clean up.

First, she backed up all her files, and checked there was nothing else needed. She found the original software that came with the laptop, and gave them, an d the laptop itself to me. It didn't come with a Windows XP cd, but being a Toshiba laptop, from PC World, it has a 'System Recovery' CD. So, I duly inserted that, and started the full install. After about an hour, the system rebooted into Win98. I wasn't happy.

This computer has a valid WinXP product key on the base, so I decided to find my own media and install using that. After finally getting hold of a copy, I install, and it states that the product key is invalid when I try and activate windows. I decide that something must be wrong, as it's on a sticker on the bottom of the laptop, so call Microsoft. Microsoft then nicely tell me that the product key is indeed valid, and if the installer isn't accepting it, I should contact the people I bought it from.
For the benefit of non-uk readers, PC World are the lowest of the low (IMO) when it comes to computer services. They really do not know their arse from their elbow. I will not be calling them, as they want to charge £1 per minute to talk to me about fixing their fuckup. Which they won't do, because this is out of warranty. I've been through this before.

So, despite this computer having a LEGAL licence for Windows XP, it now is happily running an ILLEGAL copy of Windows 2000 Pro.

If anyone from PC World, Microsoft or Toshiba read this: congratulations for making the installation of Windows XP so hard to illegally install that legal licences don't work.

Erich Schubert: More on the Debian board

Simon has a similar view of the situation. With the stuff I proposed in my last entry and earlier (e.g. bug masters) - I'm well aware that this means someone needs to write a lot of infrastructure code. But given recent improvements e.g. on our bug tracking (user tags, subscription, version tracking) this seems to be working okay. I've never really used launchpad, so I can't comment on what it offers that we might need and where it sucks. And I've said a dozen of times that I hate bugzilla. Next I'm usually hard to convince that any "infrastructure improvement" will help solving "social" issues. But here it might, if it "weakens" the formal DDs power (isn't god on how the software is packaged and on how patches come in) and strengthens the "occasional contributor" (pending patches repository, DDs can easily approve patches and trigger an upload without being deeply involved with the package, since NMUs are easier to do). And I'm also aware that my point of view isn't consequent. On one hand I'm convinced that any big "steering" won't work anyway, and those who do the job (read: write the code, write patches) will largely be those who set the direction. Linus didn't just pick a VCS and decide that everyone will have to use it, but actually wrote his own to suit his needs. And others liked it, picked it up, improved it. On the other hand I'm asking people to use packaging practises that allow others to easily contribute. I almost suggested to make it policy to use debhelper and CDBS... Well, it's one of the things I've learned myself: make it easy for others to contribute - and you'll enjoy it more, because more people will contribute. If it's hard to contribute, people will complain, will file bugs, will argue. If it's easy to contribute, they are more likely to send patches and enhancements. Read: more fun. It's also one of the reasons I blame for my SELinux work being not too rewarding: it's hard to get going, it's hard to contribute (well, that has improved with the public readable SVN repository for the policy). Less people, less contributions, less fun. Anyway, I don't see the need for any steering or "global picture". We're not lacking the big goals, but the low-level fun at development. That doesn't mean I'm strongly "opposed" to the commitee. I just don't see the benefits (but certain costs for electing it. Do we take group applications and vote among groups? Then we could just have the DPL nominate the steering comitee. Or will we vote on individuals, with the top n becoming the board? Then we'll have lots of platforms to read (=boring, not fun), and we'll probably have the same problems at a different level, different opinions in the board. And, given that the DPL has no real power, will the board have any? We also have a technical comittee. Does it have any power (well, it's supposed to, but was it ever enforced)? Did anyone ask it about something recently?

Simon Richter: Why we don't need a steering committee

Debian has always defined itself as "the universal operating system", which to me means that, given two options A and B, each with their own advantages and disadvantages, we will incorporate them both, because there are people for whom A is better, and people for whom B is better. This is one of Debian's greatest strengths, and this is what makes it the "universal" distribution. Now there has been discussion lately about whether Debian needs some sort of central authority to pull the project into a certain direction. The thing is, while everyone seems to agree that we lack direction, we cannot disagree more on which direction it would be if we had one. At present, we have a number of groups pulling in different directions:
The "release" group
Debian's primary goal is/should be to make stable releases. In the time between releases, people should run the release candidate and iron out bugs, so we can release faster; new features are to be added only right after a release.
The "usability" group
Debian does not have any use if we do not support every user. As the admin users can already help themselves, we should focus more on the average user and make the system more simple to use and administer. Integration is a must, as is closed-source firmware.
The "hacker" group
Debian's purpose is essentially to give us a distribution we can use for ourselves, where all the tools that exist are there.
The "freedom" group
Debian is supposed to be only free software so I don't accidentally come into a situation where I'm in breach of a license.
The "large installations" group
It should be as easy as possible to deploy Debian to a set of boxes and remotely administer them. It should be easy to install the software the users need and to customize it for our organization. Users are not supposed to administer machines, and non-free software and drivers need to be clearly marked and easily avoidable so as to not put us at legal risk.
The "supermarket" group
Debian is a repository of packages that makes our lives easier when we build either a system or a distribution, but we don't really care whether stuff is integrated already, because in order to feel comfortable with it, we need to redo it anyway.
The "small but beautiful" group
The system should be as modular as possible, allowing me to leave stuff out that I don't need. I don't mind installing stuff later on.
There are others, and I have represented each only with their most extreme positions. These groups are not usually disjunct, and in some places, some groups share goals. But, for example the "usability" group and the "small but beautiful" group will always disagree on what should be in a base installation. All of this is not new. What is new is that people are asking for a strong leader to strike down the unbelievers rather than discussing stuff on the mailing lists. This is generally a thing I wouldn't like to see happen in Debian, because anyone you pull into the discussion is either uninformed (so not qualified to answer) or already has an opinion (which will most likely conflict with either party's opinion). By forcing a decision, you essentially give one party the right to dismiss arguments with "we've already had this, it has been decided" and do not solve the problem at all, because the other party is still unhappy. You might want to argue that a committee evens things out a bit as more groups are represented there. That is true to a certain extent, however you'd have to have a way to determine who gets to be on the committee, and to do so in a manner that noone is left out (even if there are new groups forming all of the time) and without giving any group too much power. We might just include everybody, which brings us to status quo, except that everyone got a job title now and people might feel more inclined to decide things by majority vote (because that is what committees do after debating, right) instead of based on actual merit. Scott writes that implementing the same thing he just did in Ubuntu would have taken him ages to do in Debian because there are so many more people to coordinate in Debian. I have to disagree here, the number of people to coordinate is probably the same if not higher, except that the Ubuntu model seems to be that every core team member has commit access and is supposed to read up on the changelog when touching a package, making the coordination more implicit. I happily give out Ubuntu CDs, which do have non-free drivers, firmware and documentation, to users. Telling them that they cannot use that driver or have a manual because it's not free will not help anyone, and it is unlikely that they will be taken to court over it. This is all fine and dandy considering Ubuntu's target audience. However, Debian has a much larger target audience, including Ubuntu itself. If Debian were to interpret licenses less strict for some perceived benefit for the users (cdrecord springs to mind here), then all derivers, including Ubuntu, would have to carefully cross-check all of the licenses for possible violations. Thus, I oppose GFDL documentation in Debian main, because when we say "our priorities are our users and free software", that includes all of our users, not just end users. So, what I ask of you people reading this via Planet Debian is the following: Ask your "opponent" whether he'd be interested in finding a common solution that fits both use cases. Present it as a technical challenge. Accept that the outcome of such an endeavour might be that the other person is right. Accept that not everyone shares your views and/or priorities. It is hard to accept for me that a lot of people still think that svn is superior to git, or emacs is superior to vi. So if you have a different opinion on some matter, keep in mind that the other person may be looking at things from a different angle, where his choice is the only "logical" choice. Oh, and that goes for both of you. To conclude: Debian's strength is its lack of a clear direction. If we were to decide that the end users are what matters, we'd become another Ubuntu, which would be quite unnecessary because we already have one, and they are pretty good at being Ubuntu. If we decided only releases mattered, we'd probably release more often, but right after a release, unstable would be really broken (the elders might remember how it was before the "testing" distribution was introduced). In the same way, the release team takes care to include your pet project in the release if at all possible. Every package that is added delays the release because they have to wait for autobuilders and make sure that everything is internally consistent. So, they are already respecting your goals. Are you going to respect theirs, and join the release effort even if all your machines run unstable? So in my opinion it is a good thing that we did not decide on a direction, because there is no right one. We'd always leave some people behind if we had to make a choice. What needs to change is our attitude that software is to be used in one particular way, because the people actually using it would disagree. After all, free software is (also) about being able to do things your own way, and Debian as a whole should be supportive of that.

John Goerzen: A Haskell solution to Lars' Problem

Thanks to a little glitch in planet, one of Lars' posts from 2004 came to my attention. In it, he proposes a test for language benchmarking:

Read text from the standard input and count the number of times each word occurs. Convert letters to lower case. Order the words according to frequency, words with the same frequency should be ordered in ascending lexicographic order according to character code. Print out the top N words, where N is a decimal number given on the command line. Each output line must contain the count, a space, and the word (in lower case), and end in an ASCII LINE FEED character. Output must contain exactly N such output lines and no other output lines.

A word contains only ASCII letters A through Z and a through z (convert upper case to lower case) and ASCII digits 0 through 9 and is not empty. All other characters separate words and are ignored except to notice word boundaries. Word boundaries only occur at the beginning and end of the file and at non-word characters. You may not assume a maximum length for the word, line, or input file.


He provides a tarball with sample implementations in C, Python, and Shell.

His C code is 183 lines long, Python 57, and Shell 11. The specs for this test seem particularly suited for shell.

I wrote a version in Haskell, commented and formatted approximately the same as his Python version, but using an algorithm more like the shell version. It comes in at 18 lines. Here it is:

import System.Environment
import Data.List
import Data.Char
custwords = filter (/= "") . lines . map (conv . toLower)
    where iswordchar x = isAlphaNum x && isAscii x
          conv x = if iswordchar x then x else '\n'
wordfreq = map (\x -> (head x, length x)) . group . sort
freqsort (w1, c1) (w2, c2) = if c1 == c2
                                 then compare w1 w2
                                 else compare c2 c1
showit (word, count) = show count ++ " " ++ word
main = do args - getArgs
          interact $ unlines . map showit . take (read . head $ args) .
                     sortBy freqsort . wordfreq . custwords

Taking a look at this, one thing that might strike you is the function composition in main. This takes the output from one function and feeds it into the next -- and the Haskell syntactic sugar for this makes it look a lot like pipes in the shell version. The interact call takes, as a parameter, a function that takes a string and returns a string. interact supplies stdin as the input and prints the output to stdout. Note that, since Haskell is lazily, this does not mean buffering up the entire input or output -- it is read and written on demand.

The rest of the functions are also standard in Haskell, and you can find them in the index to the library reference if you want to learn more.

I understand and agree that short code doesn't necessarily mean good code, but I think that Haskell provides a very elegant and expressive solution to many problems -- one that also happens to be remarkably concise.

Updated 9/4: Changed isLower to isAlphaNum to fix a bug, and removed unnecessary Data.Map import

Biella Coleman: On Mole-ville, a Public Service Announcement, and the Internet.

In a recent post I mentioned that my scalp is adorned with 14 titanium staples. While some may think that I have them because an odd accident incurred during my recent move, I have them because I live in mole-ville and some of them were causing a small disturbance in the hood. Living here means I have a lot of moles on my body and well, these little masses of brown pigment, while they can be somewhat attractive, and unproblematic, can be unruly creatures that can change on short notice and cause a lot of problems. Now I usually don’t blog about personal things like my moles, but I thought it is worth writing about this as a public service announcement… So if there are any other readers who live in a crowded mole-ville, this is little reminder to check up on your moles, sooner than later. I have never had a problem with my moles and there is no history of problems in my family but I do have more than the average number of them. In fact, anyone who has met me knows this because they are all over my face, and there is one distinct one, under my left eye that is shaped like a tear, and often mistaken for dirt, more graciously as a tattoo, and most oddly as that black stuff that football players smear under their eyes. About a year ago, after one of my friends was diagnosed with melanoma (thankfully he is ok), I started checking my moles more frequently and did a full check at the dermatologist. All was ok and when I went to another dermatologist in February, all looked good. Then this summer, as I was running my hands through my hair, I felt a mole and started obsessing over it. I was pretty sure I did not have it a year ago as it was not on my chart and if was, it was probably flat and since I could feel it, it had changed, which is not a good sign… I was traveling most of the summer and it was first in South Africa where I had it checked in a fancy dermatological office in Durban. They dermatologist took a close look and said, looks fine but have it removed because you can’t track it. That made me feel a lot better so I enjoyed the rest of my time there and then as soon as I got back I saw a RN at a dermatology office in NJ (it is near to impossible to get a derm appointment without a month’s wait in the US but since they had RNs, I could see someone quick.. More on this in a second). This person also confirmed what the dermatologists in SA had said but also decided to remove it because I could not track it. A week later a pathology report came back that showed it was dysplastic and that the cells were changing, and thus considered abnormal. Some dermatologists consider this as pre-cancerous, some don’t, but it seems to be that there is more likelihood that this type of mole can turn into cancer. So the “treatment” is a full excision where they remove 1cm all around the mole. I got word of the report around the 8th of August and the only time they could fit me in for surgery was the 25th, a day after I was supposed to leave for Edmonton, which changed my moving plans (and explains why I arrived here so late, making getting my stuff complicated given school is in session and parking is tight). I then scheduled an appointment for a a full body check and removed another mole that once biposed was confirmed as dysplastic and though not as abnormal as the other, the recommendation was to also remove the surrounding dermis. Now, when I called the surgical coordinators, they could not fit me in another time slot to expand my appointment for 2 surgeries because they were “full” even though I explained I was moving away from the U.S. They said that it was up to the surgeon to decide whether to operate on the second area and since I was leaving to Canada the NEXT day, he would probably agree but no guarantees.
So of course, I wanted the stuff out because I was not sure how to go about getting the procedure done in Canada. My insurance does kick in the second I sign up and there is no Bull-Sh*t pre-existing clause stuff here but because I could not get an appointment in time, I would probably have to go to a medicenter that performed these operations and not all do. Though I was confident I could get it done eventually, it would take a lot of inquiring and after a 7 day drive and all that follows a big move, I decided it was not the thing I wanted to do. So I got to the office early on the 25th and one of the first things that comes out of my mouth when I saw the nurse was that I was leaving the next day to Canada and I did not know when I could get care there. Of course the first phrase that pops to mind for many Americans when you say Canada and health care is “socialized medicine” which most people in the U.S. associate with bad healthcare and long waits. Now on the one hand, I have to admit I, to some degree, share those fears, which is one of the reasons I wanted the extra dermis removed asap. On the other hand, I think that the claim is a big fat red herring because in fact for many Americans, they *do* have to wait a long time for many procedures (dermatology is classic for this, and even my first procedure took a 3 week wait and if I wanted to schedule the second one, it would have taken 5 weeks) or worse, they have no insurance, which KEEPS many people from going to a doctor in the first place. So American medicine is not necessarily “fast track” and in a dual sense: in the literal sense because HMO healthcare is like socialized medicine with capitalist prices, and because many people without insurance also probably avoid the doctors until they are in bad shape… And even though I have insurance, they would not pre-approve anything as I am in some awful pre-existing clauses because my insurance had lapsed for 2 months this year. And even though I have never had a problem with a mole in my life and did not even see one doctor in the 6 months before I got my insurance (which is when the pre-existing diagnosis would pertain to) and even saw a dermatologist in my HMO network in February who found nothing wrong, the insurance wants to make sure to add as many roadblocks as possible in the hopes of never paying up. Great. Now I am very grateful the nurse at the derm office proceeded to get the doctor to perform the 2nd surgery and he also was more than ok to do it. I wanted to give them big fat hugs after the procedure but you know, you just don’t do that type of move in your blue robe after the surgery. Before the surgery I naturally “hit” the net to gather a lot of information on moles, cancer etc… I join the millions around the world who–for better or for worse–use the Internet to supplement (some I am sure supplant) their doctor’s medical advice. In fact, a key part of my second project on psychiatric survivors looks at how patient communities are building a sphere of amateur but expert medical knowledge exchange. It is an enormous sphere of vibrant peer-to-peer knowledge production but one that many are uncomfortable portraying as such because it involves a lot more risks and ambiguities than exchange knowledge about, you know, how to get your blue tooth working…. But if we bracket the realm of alternative remedies (which admittedly is a HUGE part of this type of exchange), I think in fact, patients are pretty savvy and are engaging in risk-averse behavior by going on the net and illness forums. A lot of what is exchanged are warnings about side-effects, detailed accounts of experiences with procedures, and yet a lot of red flag raising that one’s experience may not match another persons but may be still helpful. It is a lot of information that often may be missed during the exchange with the doctor and derives from what is another type of expert knowledge: one’s bodily experiences with medicine, illness, and other related procedures. But I have to say that when researching melanoma and moles on the Internet, I was somewhat stumped. There is just too much variation out there to make informed judgments and abnormal but non-malignant moles have the same characteristics as melanomas. The Internet, in this case, seemed helpful to provide some baseline information and then just served to freak me out more than necessary so I turned away for the time being. For now I am just adjusting to the staples, which come out in another week. The procedure did not hurt much but the first week after the removal my head was much more sore than I had expected. Not so fun when on a marathon road trip, which is finally over!

Gunnar Wolf: A chapter has ended

Last Friday, a long chapter ended in my family's history: The last person of the immigrant generation, my great-aunt Tere, passed away, 99 years old.
My family is fully made from immigrants. From my mother's side, Polish. From my father's, Austro-hungarian. Tere, sister of my grandfather was born in December 1906 in Felszoviso, M ramaros, Transilvania (then Hungary, today Romania). Most of her family had spread over different countries by 1925 (I know my grandfather chose to become a Czechoslowak to continue his studies in Stakcin, while she and her parents moved to Budapest) left Europe by 1930 - My grandfather lived for some years in Monterrey, northern Mexico, where he met my grandmother. My great-aunt's husband had a good, stable job as a lawyer in Hungary, so she stayed in Budapest, even during the war, under Horthy's regime. She worked carrying false documents and information to help partisans and other resistence people communicate and move in the Nazi-occupied territory. She always downplayed her work during those years, but we all know she often put her life at risk for this. Her husband was detained and later killed in a concentration camp, but she was able to hide her parents.
In 1947 she was approved to get a Mexican visa, and -after 18 years of having little contact, and almost 10 years of having no contact at all- she came to Mexico, together with her parents and her second husband (who died shortly later, because of the wounds he got at another German detention center).
Anyway... My great-aunt never had any children (we all refered to her as "la t a", the aunt), but she was up to now the thread that kept together a small but very disperse family. She lived in Mexico City, as an independent woman until she was 82 years old. She moved to Cuernavaca, first as my father's neighbour, and then to the Eishel old-age home, where her brother and sister lived - and lived in Eishel for over 15 years. She didn't die of any specific illness, but as we know, living too much is bad for your health. She was a talkative woman until very recently, always very lucid. In mid April, however, she got an infection which had to be treated by strong antibiotics - the antibiotics didn't help much, and keeping them on for too long would only make it more painful. In early May, my father and his cousins decided the antibiotics should be stopped - and to let nature work. Four months later, she went away, closing a very long chapter in the family.

Gunnar Wolf: What does a DPL lead mean?

Rapha l: I mostly agree with your post. Having something closer to a steering committee seems saner than having a single leader for projects such as Debian, due to a single person not able to fully follow everything such a large and diverse mass of people works on. I was among the supporters of Project Cabal^W^Wthe DPL team experiment, and of our 2IC role.
However, you state that a release should determine the time a DPL team (call it committee, cabal or whatnot. I like the title, in fact: "I am an Elected Member of the Whatnot of Debian". Whee!) - I disagree on this one. Like the fact DPL is not chosen for technical but for political work - The DPL (and so should the team) mediates between parties, brings order (controversial, sometimes) to discussions, pushes forward some controversial decisions, reports on the general status of the project - That should be the Whatnot Team work (hmmm... Should I file for trademark on that name?).
In any case... Were we to change our model towards this formal DPL team thingie, I advocate slow changes over strong ones - I prefer a board like this one to be replaced one person at a time, at rates not more frequent than one month, and having them there for a fixed amount of time.
Of course, this would lead to a mess on managing the voting, and each vote being less important for the developers. Besides, we have had DPL elections with as little as two candidates, and topping at seven IIRC - Do we have enough people interested in being responsable for our administrative chores? Would this scheme work? Or would it lead us closer to administrative stagnation? Quoting our not-very-beloved-but-anyways-wise dictator (for the 1876-1910 period) Porfirio D az: "If I want something done, I do it myself. If I want it to take some time, I appoint a delegate to do it. If I don't want it ever done, I form a committee".

Ross Burton: Poseable Action Figures

Last Friday was Vicky's last day at the OU, as next month she hopes to be accepted onto a teacher training course for A-level Psychology. On Friday her desk was covered in fairy lights, cards and presents, including a Teacher Startup Kit: pain killers, an apple, a diary, and a poseable action figure of Sigmund Freud. Freud I'm not sure what worries me more: that someone at the OU found a poseable action figure of Freud, or that somewhere in Cambridge there is a store that sells Freud action figures, and probably more... NP: Piss Frond, Dead Voices on Air

Branden Robinson: Sometimes You Hear the Tires

I was in a multiple-car accident yesterday. I've been having to tell this story a fair amount in person and on IRC, so I thought I'd blog about it. Short version: it was a fender-bender. I'm doing fine, nobody was hurt, Michelle wasn't in the car, and 75% of the cars involved were driven away from the scene — including mine, by me. Want the long version? Well, I'm gonna tell it anyway. I had just pulled to a stop at a traffic light, heading northbound on Keystone Avenue where it intersects 106th Street, in Hamilton County. The line of cars at the light was pretty long, and people love to try hauling ass on the stretch between 96th Street and 106th. Apparently the person behind me was one of them. The line of cars stopped in the left lane (where I was) at the light was pretty long, and much shorter in the right — the cars over there were still moving at a good clip. I looked in my rearview mirror, thinking "if someone's trying to match pace with the cars in the right-hand lane, they're gonna need to brake pretty hard to stop." It was about 1815, so it was starting to get dark. A pair of headlights approach. Fast. Oh boy. I don't stop right up on people's tails, so if I'm hit, hopefully I won't go into the car ahead. I look forward again. Yeah, there's some room here. Screech. I didn't tense up; I felt a strange sense of calm and curiosity, as I'd never been in a car accident before. I bought my car, a Volkswagen Golf, in part because of its fairly good safety ratings. It has lots of air bags, and I always use a seat belt. Plus, in this instance I figured I wouldn't get hit a high speed. "Strange Deja Vu" by Dream Theater, from the Scenes from a Memory CD, was playing. Normally I listen to All Things Considered while commuting home, but I was annoyed because when I got in the car, I heard Nina Totenberg signing off a report, which means I'd just missed some Supreme Court coverage. Damn. Anyway. BONK. I got hit. Ouch. My teeth had chomped together too hard. Maybe they should install rubber mouthpieces in the doors of cars so you can grab them right before a crash. You know, car crashes never sound like the stock sound effects that have been around for about 50 years. I guess that's because they build cars to crumple these days instead of act like steel shrapnel bombs. Damn that Ralph Nader. My wreck doesn't sound cool and stuff. And I get to walk away, well, get back in the car and drive away, instead of my wife collecting on my life insurance policy. But I digress again. A middle-aged woman in a Honda Civic skidded into me, and knocked me into the Buick Park Avenue ahead of me, which in turn tapped the minivan ahead of him. I blinked a bit and tried to reorient myself, and then turned off the CD player. We all got out of our cars. The woman in back was very distressed, and immediately and repeatedly said the thing your insurance card tells you never to say after an accident. Oh well. Being a middle-aged woman, she'd probably have to wreck a school bus full of children — twice — before her premium would go up. Mine, on the other hand — we'll see. Called 911. Reported the incident. Tried to call my wife, but she decided not to answer. I later found out she was gabbing it up with my mom. Isn't it nice when your wife gets along with your mother? I COULD BE BLEEDING OUT ON THE COLD ASPHALT, BUT YOU TWO JUST KEEP ON TALKING. Michelle and I have the same model of cell phone, and we have call waiting with caller ID, so I know she knew it was me. Anyway, I try a couple of times, then give up and leave voice mail. Turns out the guy in front, in the minivan, was a Deputy Prosecutor for Hamilton County. He said something about being experienced in car wrecks, but I don't clearly remember it. Anyway, perhaps in part because he decided he was only "tapped" and didn't need to file an insurance claim, and perhaps in part out of professional courtesy, when the cops showed up, they let him go very quickly, so I didn't get any of his information. Everybody was fine, polite, and decent about the whole thing. The couple ahead of me, whom I got knocked into, didn't have their insurance info on them (or maybe this is a euphemism for "don't have insurance"). But, except for the deputy prosecutor guy, who was outta there, we all traded names, addresses, and phone numbers. I hope the Debian Project doesn't mind that I used my Debian Project Leader business cards for this purpose. These people (and the Carmel Police Department) now have my GPG key fingerprint. Uh oh. Anyway, that's about it. Appointment tomorrow with the insurance agent, to get help filling out INDIANA OPERATOR'S VEHICLE CRASH REPORT, State Form 38656 (R6/7-91) Stock 301 Effective 1-92, which has to be filed with the Indiana State Police within ten business days, or my driver's license will be suspended. Aww, yeah. Gotta move fast, because on Friday I leave for Mérida, Spain, to attend the 2nd Annual Open Source World Conference in Extremadura. Also have an appointment with the claims adjustor tomorrow. Then I'm hoping to just leave my car at the dealership so they can work on it over the week when I'm gone. My wife and my mom, those talkative two from a couple of paragraphs ago, will be coming along with me. My mom's got a jones to visit Spain, and I've had a jones to take my wife to Europe. We'll have a couple of extra days to see what Spain is like — I'll be there from 22 October to 28 October. I hope one day to visit Barcelona and hang out with some proper anarcho-syndicalists.

Branden Robinson: A good day to make World

make World is what you type when you want to do a full build of the X Window System sample implementation. With significant embroidery, it's also the heart of the xfree86 and xorg-x11 source packages' debian/rules files. Today, I got a successful package build of the xorg-x11 SVN trunk. One needs new versions of the render-dev and libxrender-dev packages to do so; the former has been accepted into unstable, and the latter is currently in queue/NEW. There's a bit of housecleaning and QA still to do before uploading to experimental, but the worst of the hurdles are cleared, and that's a mighty good feeling. Hopefully David Nusinow returns from his "forced vacation" soon. :-) There are many things to catch up on on the DPL front (and a few others), and I owe everybody an explanation of why I've been so quiet lately. Strapping on my boots to give xorg-x11 a kick in the ass has been part of it, arena-style bureaucratic combat with the Brazilian Consulate General's office in Chicago was another, and my wife's recent re-hospitalization was the most worrisome. I lost out on my trip to FISL 6.0 in Brazil, but kept my wife, which is, I think, the preferable outcome if I could only have one of the two. (Those of you who are members of SPI can also check out a report from me on recent donations and bank activity.) It's satisfying to make progress on a couple of fronts even when you're fightning an n-front war — it beats the hell out of losing ground. Yup, today was a good day to make World.

Next.

Previous.