Search Results: "cas"

7 November 2006

Simon Richter: Reusing code

A feature I'd like to see in an SCM is a refactoring aware merge tool. When I have one branch that has had most namespace, class and method names changed (I used to use CamelCase), merging another branch into that doesn't work well, because there are a lot of scattered little changes that each inhibit changes for a few lines before and after. Given enough discipline on behalf of the person doing the refactoring (in my case, me), the commit that introduced these changes can be reduced to a set of substitutions, which then can be applied to the last version in the branch being merged, and this should reduce the conflicts to a small few (mainly whitespace changes, probably).

Adam Rosi-Kessel: Minor Voting Irregularities

We are fortunate in Massachusetts to have fairly simple paper ballot voting machines (rather than electronic touch-screen voting machines, see, e.g. Ed Felten’s comprehensive critiques of electronic voting). When I voted this morning, however, the machines were not feeding the ballots. Instead, the poll workers were piling the ballots up on top of the machines, apparently to be fed into the machines when they figured out how to get them to work. When I left (about 90 minutes after the polls opened), they had gotten to the point of triple-checking whether the machine was plugged in. I felt a bit uneasy leaving my secret ballot in a big open pile. It was somewhat reassuring that a police officer seemed to be in charge of watching the ballots, but I still will always have a slight reservation as to whether or not my vote was actually counted. Don’t they get to work early to test the machines? Perhaps do a few dry runs, kick the tires, etc.? Other industries seem to have figured out most of these problems a long time ago — for example, I can’t remember a single instance in my entire life of encountering a paper jam (cash or receipt) with an ATM. (I’m sure it does happen, just rarely enough that it’s never effected me). If a system is mission critical, it should be possible to get the failure rate down to something more acceptable.

Steve Langasek: alpha day

As a matter of principle, I try to avoid any conflict of interest between my release manager and alpha porter hats, by e.g. deferring to my co-RM when there's a question of whether a particular compromise should be made to benefit alpha's releasability. Where Dunc Tank is concerned, that means some changes in priorities for bugs to work on, since I'm being paid to try to get etch out in a timely manner, not to keep the alpha port afloat. OTOH, alpha is not the only arch that produces RC bugs needing release team attention, and Dunc Tank only dictates how I spend 40-50 hours of my week -- which means another 20-30 hours a week of Debian work that I can set my own priorities for, right? So the theme ingredient over the weekend was: problems on the alpha port. I'll give myself 4/5 points for presentation, 5/5 points for use of the theme ingredient, and 6/10 points for taste (this plastic computer case needs more salt). And of course, waiting for Debian kernel packages to compile on an LX164 alpha gives one time to do other things too, like following through on the RC bugs that the BTS has wrong version-tracking information for, and preparing an NMU here and there. Less than 200 RC bugs left now, and dropping daily!

Stefano Zacchiroli: editing latex the vim way

Editing LaTeX, the Vim way Uwe presented latexmk as its way of previewing LaTeX output while editing in Vim. While I don't know latexmk myself, I'm using quite a lot LaTeX recently (my Ph.D. thesis is getting huuuge) and I'm co-maintaining vim-latexsuite in Debian. With vim-latexsuite what he wants can be achieved quite easily too. I keep on editing in Vim and can exploit the following shortcuts (where <Leader> is usually mapped to backslash):
  1. <Leader>ll compile the current LaTeX source, the generated format depends on the value of g:Tex_DefaultTargetFormat (I use dvi, for a reason explained below);
  2. <Leader>lv fire up a viewer for the compiled format, in my case this runs xdvi;
  3. <Leader>ls move the DVI viewer to the point the cursor is currently at in Vim, highlighting (in xdvi) with a rectangle the current paragraph (believe me, this is amazing);
  4. CTRL+Mouse Click (this in xdvi) do the opposite of (3), i.e. move Vim to the point in the LaTeX source file corresponding to where we clicked in xdvi.
I don't really understand why Uwe want to see working previews in PDF format, to me PDF is just the final output. DVI is much better (especially for (3) and (4) above, but also because it takes less time to be generated). Oh, and of course vim-latexsuite is able to do a lot more, like deciding whether LaTeX needs to be run again to fix dangling references, use the quickfix window to jump to compilation error, and so on ... End of the SPAM :-) PS these are my latex-specific vim settings from my ~/.vim/after/ftplugin/tex.vim
setlocal tw=80
setlocal ts=8
setlocal sts=1
setlocal sw=1
setlocal iskeyword+=\\
setlocal makeprg=make
setlocal keywordprg=:help
"setlocal formatoptions+=a
setlocal spell
vmap ,b "zdi\textbf <C-R>z <ESC>
vmap ,e "zdi\emph <C-R>z <ESC>
vmap ,t "zdi\texttt <C-R>z <ESC>
  " Latex-Suite
let g:Tex_CompileRule_dvi = 'latex -interaction=nonstopmode -src-specials $*'
if v:servername != ""
 let g:Tex_ViewRule_dvi = 'xdvi -editor "vim --servername ' . v:servername . ' --remote +\%l \%f"'
endif

6 November 2006

Russell Coker: the death penalty

I have just read the news about Saddam finally receiving the death penalty (it did not seem likely that his case would have any other outcome) and have been thinking about the death penalty in general.

Firstly I think that in a jury based system every jury member should have a hand in the execution. If they vote for the death penalty (if you use a jury then it should decide whether the death penalty is acceptable) then they should all be involved in carrying out the sentence. It would be quite easy to fit a room with a dozen switches that control an electric chair. If the jury members are unable to pull the switch then that should result in the sentence being commuted. I am against people voting for actions which they lack the courage to perform themselves.

One problem I have with the death penalty is the poor quality of justice in most courts. The US is a good example of this where poor people are the ones who get the death sentence. A pre-requisite of having penalties such as the death penalty should be that there is a reasonable chance of convicting the person who committed the crime!

In the case of someone like Saddam Hussein there is an additional problem of creating a martyr. I think that a solution to this would be to give him a life sentence and put him on TV on shows based on the Jerry Springer Show. Show him for what he is and let the audience pass judgement on him, I'm sure that he would not do well on such a show.

Another possibility is to have a glass prison where the lights are always on and web-cams show everything he does (including the toilet and shower). That might fall into the category of cruel and unusual punishment, but really the cruel and unusual stuff is what happens in Abu Ghraib (under the command of Saddam Hussein and more recently under the command of George Bush).

Barry Hawkins: The missing ingredient in commercial desktop OS options; a package management system

Having spent the better part of two days provisioning my new MacBook Pro’s OS X, Debian, and Windows XP instances, I am keenly aware of how much the Debian distribution’s package management system and its volume of packages have spoiled me. In that two days, the amount of time required to provision Debian was negligible, even though it is configured to completely match my Lifebook’s Debian Sid instance. In fact, the sum total of time to set up Debian, including every application I use, was about 45 minutes of my involvement. Those who know Debian (and Ubuntu, Linspire, Xandros, Mepis, or any other Debian derivative) are coolly nodding their heads, while others are probably thinking I am a lying, biased Linux zealot. It’s no lie; here are the steps I had to take: Compare that to what it takes with either Mac OS X or Windows XP to get all of your applications installed and configured. Even if you don’t know a thing about Linux or even the more technical side of those operating systems, you can tell from the brevity of that set of steps that the Debian setup is remarkably simple. Now, some will already be keying in their comment posts with exclamations of “Hey! There’s DarwinPorts/Fink/Cygwin!” Yeah, each of those is a nice start; however, they pale in comparison. Fink at least has the robust apt/dpkg foundation, but even it has a relatively meager package selection. I am sure I’ll be writing more on life with Fink and DarwinPorts in the near future. I still don’t have half the stuff installed on XP that I plan to use. I get tired just thinking about the installs. 8^)

5 November 2006

Brett Parker: Woo! I have a working PyLucene! (Err, and some other stuff about full text indexing).

I've been after a python library to mess with lucene indexes for a bit, we use/write a fair few things that use lucene at the backend at work, and just occasionally it would be very useful to be able to fiddle in them (read: search from the command line) without having to do the "write java, compile, test, recompile because you got something wrong, retest, and again" type loop for simple things. Using X11 Forwarding over ssh over a shared with the rest of the office 2M line to use Luke on the indexes is just not fun at all! So, now that I've got pylucene compiled and know the right options (ish), and it compiles on Debian Sarge (both i386 and amd64 variants), I might just build me a package for installing on our servers so that there's an "easy" option for us sysadmin types that just need stuff that we can use, quickly, without messing about! Semi-planning writing a luke-alike using PyLucene and the ncurses library to make it easier to diagnose/look in to the indexes on remote servers, but that's not going to happen this week! Quite impressed with the speed though - looks *fast* - but then, I suppose if you compile the Java using gcj to get native code, then you can expect it to be a *bit* quicker than running in the vm, right? At least, that's what I'm attributing it to at the moment, well, that and python startup time is likely to be a little bit quicker than java startup time. Also, in my travels, I found Divmod Xapwrap, which is a python library round Xapian which seems to be another (interesting) full text indexing engine. Haven't played with that yet - but could be worth a look in the future. Core library written in C++ so should be reasonably quick. The bit that I like the looks of though is """Xapian can search across several databases as easily as searching across a single one. Simply call Xapian::Database::add_database() for each database that you wish to search through.""" which sounds very useful if you start thinking about distributing indexes across a number of machines. I've not read enough Lucene documentation to know wether you can do a similar thing there. Right - enough of that - time to put things back together in the office and go home (again!). Hopefully tomorrow morning I won't be rudely awoken at 5.30am by someone asking a question that could have been better asked via e-mail (where "better asked" means "wouldn't have woken me up and annoyed the hell out of me because I couldn't get back to sleep", though - I did then play with some things and watched American Pie: The Wedding before heading in to the office the first time round...).

Stefano Zacchiroli: versioning etc w bzr

Versioning /etc with bzr for fun and profit Since mid October I rented a room to Godog, here in Bologna (erm ... Italy :-)). Living with another DD so far has been utterly fun: our lives proceed normally, but when we occasionally met it's like hack time: brainstorming and implementation of the first hackish ideas that come to mind. The first idea we deemed nice to be implemented has been versioning /etc of our server (which we co-administer) with bzr. The requirements we set forth where:
  1. who is changing stuff should be somehow forced to document and commit its changes;
  2. automatic changes performed by package upgrades should be automatically versioned.
Our current solution consists in a couple of hacks: What's next? Well, Enrico already set forth the idea of an housewarming bug squashing party with all DDs living in the Bologna area. Sounds cool!

Christian Perrier: NepaLinux 1.1 released

(this could probably deserve a DWN entry) On Monday, 30 October 2006, Madan Puraskar Pustakalaya (the principal archive of books and periodicals in the nepali language, a non-governmental and non-profit organization based in Nepal) released the 1.1 version of Nepalinux, a entirely localized version of GNU/Linux, based on Debian (and the Morphix installer) for use by Nepali-speaking users. This work is supported by the PAN localization project just like the DzongkhaLinux project is. In the case of Nepalinux, though, the project is supported locally by a NGO rather than the local government During last year, good connections have been developed between the developers of this localized distribution and the Debian project, mostly through work on Debian Installer localization. This confirms Debian as the preferred choice of many CDD developers in the region. The success of NepaLinux can probably be seen by all Debian contributors as a success of the Debian project.

4 November 2006

Clint Adams: You promised me Broadway was waiting for me, a freeborn man of the U.S.A.

I used to write shareware. Some people would just send money with a brief thank-you note. Some people would adopt the attitude that I was beholden to them once I cashed their checks. Since the customer is always right, I was faced with the pressure of customer-directed development. For that and other reasons, I stopped writing shareware. My next mistake was to release everything as postcardware. I did not immediately realize that this was wrong, and I enjoyed the influx of postcards from various places. Never underestimate the power of a simple 53-byte executable to make random people happy. In time, I stopped writing postcardware. Many years later, someone offered me something, with the condition that I do something in Debian that I would have not done otherwise. Another individual was offered the exact same inducement with the exact same condition. We both accepted. I kept my end of the bargain. The other guy reneged. Sometimes I wonder if he inadvertantly did the right thing. Since then I have been paid to work on free software, but never directly on Debian.

Erich Schubert: Turbogears performance

I've been trying some stuff with the Turbogears application I worked on a bit during the last two weeks. First thing was that I looked into using postgres as DB backend for Turbogears. Which turned up a bug in sqlalchemy (an ORM, mapping objects to database rows and back). I was passing a unicode string to the getBy function (to retrieve an object by it's primary key), and it went into the SQL statement without any quoting. Since my keys are all ascii, I could just cast them into regular string objects, and getBy worked then. Performance with postgres is worse than with sqlite; this is not too surprising. However this might change once I enable multithreading. Performance numbers: with SQLite: 8.30 trans/sec, with Postgres: 7.52 trans/sec These performance numbers are still very bad, and I guess we won't be keeping Turbogears on the long run, unless I find some documentation on improving the speed. One of the hints I got was to avoid py:match in kid, the templating engine used. I started by not using turbogears "sitetemplate" default template. This would automatically insert javascript and css files when needed. Since I don't use their widgets and such, I havn't been using this feature anyway. Not using the template - which contains one py:match for the 'head' tag and one for the 'body' tag - improved performance to 9.01 trans/sec (or 8.32 trans/sec) Now I can't explain why the improvements in the postgres run were better; both are a 10 minutes siege run. But 8.5% improvement is a start. I'll look into getting rid of the other py:match instances in our templates. (If I'd only find a good example with py:def - guess I'll instead "precompile" pre-templates into the actual templates or so instead with some self-written tool.) P.S. No, I'll probably not use turbogears for my next similar project. Rapid development is nice, ORMs are fancy and such, but sometimes good old plain SQL can be very easy to use, too. And more performant.

3 November 2006

Simon Richter: Optimisation

The correctness of an optimiser in a conforming C++ implementation is defined by the "volatile" keyword, that is, an optimisation is correct if it does not reorder, add or remove volatile accesses. However, people have come to rely on non-volatile accesses to be finished before a call to a function in another translation unit, even if you hand over a buffer which is then passed on to some external entity (syscall or hardware). Technically, this is undefined behaviour, since the compiler is free to identify the writes to the buffer space as dead stores and optimise them away. The correct way to fix the program is to declare the buffer volatile, but in a lot of cases, this requirement is too strong, for example in the case of TCP checksumming, where it is neither desired to force reading back the data, nor to build up the data in a temporary buffer and write in one go. What we'd need is something in between, that is ordered with respect to volatile accesses, but not internally.

Michael Janssen: Google Experiment: Prelude

I've been using DreamHost to host this blog and most of my persistent online activity for the past 10 months. All in all I have been really happy with them. Others seem to have issues, but I don't have any gripes. I'm only paying a paltry fee, so I don't complain too much if my server isn't five-nines reliable. However, I am starting to have a problem with one of the services available. The email support is somewhat lax. My current situation is that I am using mutt as a reader on the server itself. This requires me to SSH into the server and read the mail on there. Because DreamHost doesn't realy expect that people will have this activity (most people check their mail by IMAP or webmail) it sometimes sees my mutt process as long-running, and decides to kill it with a HUP on the SSH connection. This is pretty annoying. Also, I get a lot of spam. No, really: on a typical day, I receive over 400 spams. Currently I am using SpamBayes for spam filtering, which works reasonably well - it catches most spam at least in the unsure folder. The same problem with mutt shows up with spambayes though: it takes up too much CPU and gets killed by DH's watchdogs.

These problems lead me to this experiment. The hassle with my mail is just too large, and I hear that GMail's spam filters are reasonably aggressive and work well after you train them slightly. I have decided that I will run an experiment. Starting with November 1st, all of my mail will forward to my GMail account. I will document the spam filtering (or lack of) abilities here on Base Zero, and I'll see how it works out. I have years of data from other methods of spam filtering so I can compare.

However, this experiment isn't only going to be about spam filtering. GMail also employs some different mail models than what I am used to. The first that I am interested in is tags. GMail uses tags instead of folders, the normal way of organizing mail. This is touted as better because you can have more than one tag assigned to a email at once, and therefore orgniaze mail which should be in two categories better. For messages which are in an Inbox you just use a Inbox tag. Spam messages get a Spam tag. So I will be orgnaizing my email with tags as much as possible. The second thing which intrigues me is the idea of emails being conversations instead of threads. GMail puts related emails together, but uses a flat structure as opposed to the tree structure that I am used to. I wonder if this will confuse me because I am on a number of lists which tend to use the tree structure a lot, with many branches. I may not like some of the things that GMail does -- in these cases I will look for hacks or build ones myself which attempt to solve these problems. I am also probably going to try and do some user interface critique.

Some people are concerned about GMail and scanning emails. This doesn't concern me that much: most ISPs can scan your emails for viruses and spam nowadays anyway, webmail particularly so. I can understand the effect that this could have on some people however. If anyone reading this message would like to be excluded from the email going to GMail, just reply to this post or email me. I will oblidge by filtering your following emails to a special folder on my server. Just realize that I will only read those emails weekly at best.

GMail will not be the only Google service which gets tested by me this month. Stay tuned for more information. Until then, hail to Google, our dear and glorious leader.

Ross Burton: Leaves

Yesterday lunchtime after walking Henry Vicky went into our driveway armed with lots of fallen leaves, the SLR, and the bright afternoon winter sun. 20 minutes later and lots of technically dubious photography (one handed grip on camera, leaf at arms length, click and hope) she had some fantastic Autumnal leaf shots. Treasure Embers On fire Autumn's Beauty Update: of course a Javascript library to turn image links into magic floating popups won't work in RSS feeds, so if you want to see them in Flickr go to Vicky's Nature set. Yesterday I ordered a cheap lightbox so we'll hopefully be able to take similar shots in a more controlled environment without wind and camera shake getting in the way. Obviously they won't be as good, I've found that often the first casual attempt at a shot is the best, and the harder you try, the worse the shots get. NP: Protection, Massive Attack

Bernhard R. Link: again compiler arguments

I know I repeat myself, but given current discusion, I simply feel the need to do so:

Please do not hide the arguments given to the compiler from me.

I cannot fix what I do not know if wrong. Maybe you can.

Keep the argument list tidy.

Many argument lists are longer than necessary. If there is some -I/<whatever> in the argument list on a Debian system, there is something fishy. (It&aposs not the universial collection of different stuff all going whereever it wants, after all). Common cases are:

- buggy scripts to add -I/usr/include - packages working around upstreams breaking compatibility - plainly broken upstreams - oversight

In short: if the line is too long, that is normaly a bug causing more pain than only a long line. Do something against those bugs, please. There is no need at all for a proper made library to give -I for stuff installed. It&aposs installed in the system, the default search path for /usr/include should suffice. It often does not, but that is simply bad design of that libraries interface. Do something against that, please! Also for stuff not installed, why do you need more than one -I? Are you embedding other libraries into your code? Why are they libraries if noone else uses them? If someone else uses them, why are they not made to proper library packages? If it is all intern stuff, why does it need so many include parts instead just a single include/ dir? Anf if it only needs one include dir why is it added a dozen times? What do you need -D for anything but paths? Ever heared of AM_CONFIG_HEADER?

And yes, I know many modern libraries are written by people never looked at anything but Windows when designing their headers. (Even some seem to have never looked at unixoid systems even after using them for decades). That is a problem, not something to be worked around with even more kludges. Kludges working around kludges are there to stay. So do not add them.

Adrian von Bidder: Microsoft and Novell

Joint press release from Novell and Microsoft. Took me by surprise, thanks for the link, Dani. Diagnosis: Microsoft is very afraid. It lost Massachusetts on the Office front, it lost M nchen on the Desktop front (financially, both cases are no big deal. But they created quite a media stir.), and Xen is the big buzzword in the server rooms, while I can't even remember if Microsoft has a similar offering... What will happen? Microsoft will remember that selling MS Office licenses, even if they run on their arch-enemy-OS, is better than not selling MS Office licenses. Dito for Xen. If played right, I think Novell might be in a very good position here. On the other hand, there are many, many companies who did business with Microsoft once and don't exist anymore. And probably Novell needs the money. Disclaimer: I can call myself Industry Analyst if I want to. Others do, and probably know less than I. Others don't but know a lot more. Update: After reading the coverage on Groklaw: Novell is a business, and it's their business decision. Maybe they end up as roadkill. And I'm not talking about the Linux market, but about Linux as a piece of software. And Microsoft officially investing in Linux technology (even with the goal to embrace and extend it) will still lead to wider Linux adaptation and the eventual breaking of the Microsoft monopoly.

Adrian von Bidder: Microsoft and Novell

Joint press release from Novell and Microsoft. Took me by surprise, thanks for the link, Dani. Diagnosis: Microsoft is very afraid. It lost Massachusetts on the Office front, it lost M nchen on the Desktop front (financially, both cases are no big deal. But they created quite a media stir.), and Xen is the big buzzword in the server rooms, while I can't even remember if Microsoft has a similar offering... What will happen? Microsoft will remember that selling MS Office licenses, even if they run on their arch-enemy-OS, is better than not selling MS Office licenses. Dito for Xen. If played right, I think Novell might be in a very good position here. On the other hand, there are many, many companies who did business with Microsoft once and don't exist anymore. And probably Novell needs the money. Disclaimer: I can call myself Industry Analyst if I want to. Others do, and probably know less than I. Others don't but know a lot more. Update: After reading the coverage on Groklaw: Novell is a business, and it's their business decision. Maybe they end up as roadkill. And I'm not talking about the Linux market, but about Linux as a piece of software. And Microsoft officially investing in Linux technology (even with the goal to embrace and extend it) will still lead to wider Linux adaptation and the eventual breaking of the Microsoft monopoly.

2 November 2006

Gunnar Wolf: Oaxaca on fire

Before anything else: Please excuse some grammatical mistakes I've made in this post. You should understand the topic is really upsetting, and typing while searching for links, listening to news, and gathering the basic information for a five month old conflict is not exactly compatible with me spewing out proper English ;-)
Just to re-state the obvious: Mexico is, once again, on fire. This posting is mainly written with the Debian people in mind - An important number of them, after Debconf 6, went to visit Oaxaca - In late May, during the first weeks of this incredible, stupid and scary conflict we are now facing.
I've written in my blog every now and then about our political situation. Many of us had high hopes on our current government. We thought that the authoritarian regimes were a thing of the past, we hoped for real democracy, we hoped for a government that would honor human rights and solve long-standing topics for our society - Yes, we all knew president Fox came from a right-wing party, and didn't expect much advance in the social agenda -which many of us perceive as the real problem in Mexico- but still, hoped for openness and reconciliation with the past.
I won't repeat what I've extensively said over and over - The thing is, Fox's government continues to amaze us with its stupidity, with its near-sightedness, with its hypocresy. Fox's term is really close to an end - In one more month, the govt. will change hands to the first de-facto president since Carlos Salinas (going over another story we hoped to forget).
As some of you wittnessed, there was a popular protest taking place mainly in Oaxaca - Basically, the State's public elementary school teachers demanding better payment for their work. Such a protest is already a common occurrence in Mexico, as public school teachers are among the worstly paid workers (no wonder, then, our country is still undeveloped - Make public education worse, and you have the warranty of an unprepared, ignorant population). The teachers went on strike in early May, briefly returned to classes on late June to properly close the 2005-2006 lective year, but went back on strike afterwards.
Of course, the local government (Mexico is a federative republic, each state is autonomous and makes decisions independently) took a very long time to act - and acted the worst way possible: By sending policemen to forcefully throw the teachers from their camps in the downtown streets, with no negotiation, no answer, not a drop of common sense.
That led to the formation of the (pleonasmicaly named) APPO: Popular Assembly of Oaxaca's People - A group of people, partly formed by the unhappy teachers, mainly demanding the Oaxaca state governor to step down, after he proved he is inept for his office. And yes, I'm oversimplifying here, but I don't want to dig too much - There is fortunately plenty of available information in this regard.
That happened over four months ago. APPO kept control of the city. Nobody denies that this has caused Oaxaca, a city that attracts national and international tourism like few others in the country, a great deal of economic damage - Oaxacan people are, however, still sympathetic to APPO's demands. Governor Ulises Ruiz (from PRI, the party that ruled the country for over 70 years) has not been able to be seen in public in his state for some months already. The legislative power has also been unable to work properly, and the judicial power is half-dead, doing only its most basic tasks. Renowned jurists, such as Miguel ngel Granados Chapa, have repeatedly stated that this is enough for the Federal Senate to declare the governing powers in Oaxaca have disappeared - This would put an end to the conflict, leading to immediate elections, but the Senate has denied taking this course of action. Not only that, but the Federal government took the command of the local security forces, tacitly recognizing the local government is unable to coherently excersise their authority. After almost five months, last week they issued an unanymous -but mild- exhort, asking Ulises Ruiz to consider stepping down.
So far, 15 people have been killed in the different represive actions taken, first by the local police under local command, later by the local police under federal command, and starting last week, by the federal police. Today, it seems the army is getting in the conflict as well, despite promises of not doing so by the federal authorities - Of course, they have become masters in the art of breaking promises.
Why is the federal government upholding Ulises Ruiz? Simple: After the undeniable electoral fraud we had some months ago, there are too many indicatives pointing out that our (supposedly) elected president Felipe Calder n (FeCal, as he is better known as) will have a hard time becoming the president, and many people doubt he will be able to hold the authority for the six years. So far, he has shown no better aptitude as a statesman than Vicente Fox: Instead of boldly facing the claims of fraud, he just chickened out and has spent many months hiding from the public, appearing only for selected, friendly audiences. For many months already we have heard "Ulises ya cay , le sigue Calder n" (Ulises has fallen, Calder n is next). This country has not been so badly shaken in decades - Of course, Great Statesman Vicente Fox insists the country is in peace and there are no red spots. Fox even was stupid/blind enough to state that the problems in Oaxaca would be dealt with easily and successfully, just as the problems in Chiapas and Atenco were doing his term. During Fox's campaign, he promised to solve the centuries-old Chiapas problem (that resulted in the EZLN uprising in 1994) in just 15 minutes - He just has not had time to do so. Atenco? Yes, in 2002 an angry people made him step back from the most important project of his term (a new airport for Mexico City). In May 2006, Atenco sprang again to the news because of a massive repression - I'm not going into details on Atenco right now, as it would be off-topic, but you can look at my article in FeCal.org.mx or watch a very strong video by Canal Seis de Julio (both in Spanish only) for further details.
Last Friday, however, something was different. In a repressive action, a USA citizen, the Indymedia reporter and cameraman Brad Will was killed by a paramilitary group. Even more, he was killed while doing his work, and we can clearly see this evidence on his last tape. Of course, the US ambassador issued a warning, asking the US citizens not to go to Oaxaca. And, as Lorenzo Mayer says, hay de muertos and muertos - There are different categories of dead people. A highly visible US citizen is more important than the other 14 dead Mexicans, and now the Federal Preventive Police is clashing in Oaxaca.
What should be shocking, but is not so much to those of us who know this beaten country, is the attitude of the authority when taking the city. After five months of occupation, the Oaxacan people have got used to living with APPO - be it for good or for bad. Tourism has diminished, but the people's living sources have not been attacked. Of course, as soon as the Federal Police took the downtown areas, all sorts of reports of looting have been reported. The policemen are robbing even sodas and chips, and up to TVs and microwaves. As many people state, this is a very Kafkian country.
Of course, we don't know what will come next. Most of the city has been "freed", and the APPO is holding at the University. The University is autonomous, and the PFP commands have promised not to break its autonomy - but we don't believe that. There are fights very close to the University. The Rector himself spoke a couple of hours ago at Radio Universidad, the main broadcasting point for real news on this subject (I am following on the news thanks to KeHuelga, 102.9MHz FM in Southern Mexico City, or at their webpage, from where they link to many other underground or Internet radio stations joining in the broadcast), and the reports are dramatic. Dramatic, as well, is the way all of the commercial news sources are ignoring the facts.
I want to keep you updated, as one of the very few reasons things are not worse is the public opinion and, even more, the international pressure. I'm sorry I'm not giving more links right now, but I will soon. I don't want, of course, to flood people that read my blog through the different syndications with a technical profile, so updates via my blog will be quite sparse. If you can read Spanish, we have posted many articles at FeCal, and many other individual sites are also joining in. A couple of links, and I'm off for now.

Martin F. Krafft: The Edgy Dance?

Scott, could you please provide a video of how to do the Edgy dance? If I try, the beat makes me stumble rather than groove. The bass line does sound a little like someone falling down the stairs after trying, don't you think? ;-) NP: Porcupine Tree / Staircase Infinities

Julien Blache: Fixing the debian-installer/Sven Luther situation

[For background information on the whole debian-installer/Sven Luther situation, please read the Debian wiki.] The whole debian-installer/Sven Luther issue has been running for months now, and has seen little to no progress. A number of DPL mediation attempts have utterly failed, and there’s just no authority whatsoever above the debian-installer people that could help settle the issue. I’m just not interested in discussing who’s at fault, as both sides are at fault for something or something else. Now, looking back, there is something that bothers me. It makes me sick, even. At the end of march this year, Sven lost his mother in very difficult circumstances, in the middle of the flamewar opposing him to the debian-installer team. He sent a private mail to Frans Pop which you can read on this wiki page explaining what was happening to him, and asking him to give him a break. Reading this mail, it’s pretty clear that Sven was in shock when he wrote it. It’s so obvious that you can’t miss it, it doesn’t take a psychologist to tell you that. Nonetheless, the bashing went on, and nobody cared about what was happening to him. Now, compare to what happened to dato. How did the DDs react to that ? They rushed to debian-private, both the mailing-list and the IRC channel, to get an update on his condition, for something like two weeks. In both cases, some people knew what was happening (in Sven’s case, others DDs knew what was going on too, Frans Pop wasn’t the only one). I just can’t explain why the reaction was different, and it really bothers me. I spoke IRL with Sven about the debian-installer situation. We rehashed most of what had been told already, and he mentionned the death of his mother just as he did mention it on the mailing-lists. He has been and still is very affected by what happened to his mother. Reading his mail to Frans Pop, it’s pretty easy to understand I think. The behaviour of some DDs in this flamewar, knowing that Sven was deeply affected by this event, is inexcusable. You really should be ashamed of what you’ve done to him. He needed the kind words from the Debian family, the same kind words the Debian family told to dato, his friends and family. It’s time to clear up the mess, folks.

Next.

Previous.