Search Results: "will"

28 April 2006

Randall Donald: Will you be my Neighbour?

So the company where I work at (Push72) is looking for a few (up to 5) good men (or women) to add to our development team. Currently we are heavily involved in online banking applications and need more people who know Java, have done some web application development and are good team players. Our office is in beautiful Parksville, British Columbia on Vancouver Island and relocation is required. This isn't an official job posting by any means (I don't hire, I just work here) but if you are interested, want to apply or want to know more information let me know at randy@push72.com

27 April 2006

Martin F. Krafft: Almost crying in Bagan

I guess you could say I am now on the verge of tears, or at least have been for a while (and it's wearing off) -- since I came back from a little expedition on a horse cart around Bagan, visiting some of the poorest villages in the area to drop off a good share of the presents I still have with me (like marbles, balloons (latex ones, so biodegradable), soap bubbles, hair pins, fake jewellery, balls, and pens and paper), as well as a bunch of tubes of toothpaste, bars of soap, and bottles of shampoo, which I had picked up on the way just before. My sadness comes from two aspects of this experience. The first, which is minor because I had expected it, was simply to (once again) witness the conditions under which the poorest of the poor live: in bamboo houses together with their cattle and pigs (everyone here seems well aware of bird flu and have taken the appropriate precautions; the government apparently did a good job in educating its people), with trash and feces all over the place, kids with almost no clothing and the elderly obviously sick from a distance. But I've actually seen worse in Laos and expected it, so that wasn't the main source of my tristesse. What almost made my eyes water was rather the fact that in the first village of the two I managed today, my arrival and obvious wish to give out gifts resulted in fights among the kids, and in dishonest behaviour by some, while the mob was almost ready to run me over as everyone (including grownups) was stretching out the hand and grabbing at whatever I pulled out of my bag. Call me naive, but that part I did not expect. It's understandable, as for these people, anything makes a difference, sometime and existential one, but they are Bhuddist after all, and among the teachings of the Bhudda you can find such lines as "do not be dishonest", and its philosophy (which carries throughout many non-Bhuddist Asian countries) includes the rule to never lose one's face, which covers shouting or fighting. On my first trip to Southeast Asia -- Vietnam -- I reached some remote villages in the Tonkinese Alps in the country's north -- villages which where equally poor, but which were also quite detached from civilisation as found around larger cities. While money still served as the main means of exchange, it appears to have a much lesser meaning to the people, who are mostly self-sufficient to a point of independence from the government as far as you can get (I guess). In these villages, I also passed out presents, but never had an experience such as the one today (nor did we experience something of this sort in some of the villages in Laos, equally removed from the main lines of infrastructure). Rather than fighting for the gifts, the kids would share them. Rather than tears, the gifts brought smiles. It thus seems that civilisation as we know it causes the competition even among kids, and that's the part that fills me with sadness at the same time as it disillusions me quite a bit, because that kind of civilisation will inevitably spread. Going off on a tangent (without the intention to return), I have been thinking a lot about my "mission" in Myanmar, which was to bring clothing and medication, as well as gifts to the poor. While one could interpret this mission -- carrying more than 15 kg of "stuff" through the stifling heat -- as an altruistic act, I also cannot deny the selfish component, because I take great joy in helping people. If you recall, dropping off the clothing I had brought in a village a couple of miles outside of Pyin Oo Lwin didn't fill me with the satisfaction I had hoped to gain, mainly because I was obviously misinformed about Myanmar (btw: I am calling it Myanmar again, which is actually what locals use, unless they speak with tourists). Fortunately, however, I quite easily managed to accept that the mission was still a success for the people undoubtedly were helped quite a lot. If there is one thing I have learnt for sure this time around, then it's that I will return, sooner rather than later, and hopefully with a lot more goods than this time around. This trip has been self-funded, which is why I am also (trying to) spend most time on vacation. I could well imagine that the next time might see me just running the goods there and fly back after only a couple of days. Of course, there are no details, but keep this in the back of your heads (and pass it on), just in case you'd be willing to donate funds to finance the trip. This brings me to another, somewhat related topic, which I have been pondering ever since I arrived in Myanmar, and especially so after I met and talked to a Portuguese globetrotter, last night: the topics of beggars and how to support these countries in effective ways. Let me address those in turn, the second one first as it's more closely related to my braindump you just read (thanks for that), and because I am nowhere near a resolution and can thus sum it up in three sentences: even though individual aid trips, like the one I am on, are helping, I would guess their effectiveness to be quite low, and raising this effectiveness certainly requires a lot of effort and infrastructure. Thus, it may be more beneficial if I were to donate my will to help to an existing organisation already established and connected in the Southeast Asian countries. I am not talking Unicef and other, similar large organisations (some of which I do support already, and if only financially), but rather much smaller endeavours that concentrate on this area only -- surely the need for help exists in all developing countries, but I am most interested in helping Southeast Asia, for the people here have taught me so many valuable things that have changed my life. On the first topic -- beggars -- let me say this much: if you've been to developing countries, you know what I am talking about. If you have not, just imagine all sorts of people (but mostly poor-looking) coming up to you with their hand stretched out, saying "money, money" repeatedly and not respecting a "no" in any way. Any guide book advises you not to give any money, because it will increase the "nuisance" these beggars are to future tourists. But at one point during my time here, I was as far as giving a small amount to everyone who came up (unless there were more around, at which point it would just get out of control too fast) by reason that it doesn't hurt me a bit, and that despite the syndicates and other arguments against it, if you are actually helping one out of ten beggars, that's one more than zero. Since then, however, I've found some more compelling arguments, and the one that's been the most persuasive so far is that a beggar's success attracts more beggars, and while the guide books call that a "nuisance", the real problem is that these people come from villages to cities, from places where they are self-sufficient (at least in Myanmar with its vast resources) to places where they'll end up sleeping on the streets. Enough of that for now, you can be sure there will be more another time; on to something completely different: This is the first time I am travelling Southeast Asia while blogging, and I have very mixed feelings about it. First of all, Myanmar isn't the place for easy Internet access, so it's been quite painful to keep publishing (which was only possible thanks to the help of Hanspeter back at home; thanks), nor is it the place where you'd be inclined to spend a couple of pensive hours in front of the screen while serialising your thoughts into writing -- the power keeps coming and going every couple of minutes, and frequently the battery-backed power supplies most people have cannot bridge the downtime. But that's not the reason why I am not really too satisfied with my blog entries so far. I have found it difficult to write even in Thailand, where Internet access was excellent, and I guess it's mainly due to two reasons: first, there is too much going on outside and the fear of losing a minute of "street action" to these godaweful computers just keeps me from taking the time to think before writing. The second reason is related: impressions need time to settle, and I guess in some ways I do prefer very much to just "be", rather than experiencing with the objective to blog about it in the back of your head at all times (I am a geek after all, don't forget that). I guess I'll try it another time since having Aline along for the first part, and then being subjected to Myanmar's suboptimal information infrastructure, may be factors of larger value than I see them right now. By the way: this blog does not contain all of my writings while I am here, for obvious reasons, so there is more to come if you are interested, but not via this channel. I'll let you know. Now, on the boring side: I returned to the temples in the late afternoon yesterday and saw another three or four, before sprawling out on top of another in aspiration of the sunset to be Obscured By Clouds (which is when I talked to the aforementioned globetrotter for an hour or so). I did find that after all, Bagan didn't have much in store for me, having seen some of the temples at Angkor. The scenery is breathtaking, and some temples are really astonishing views, but as soon as you get on the inside, they are mostly walls and Bhuddas, one similar to the others, and thus quite unlike to what I'd seen in Angkor last year. Since I am also not the type of guy to go off meditating for a day in a remote location, or take my book far away to read in peace, I think that this one day between the temples was enough for me. Maybe the temperature did play a role too, but there was no question for me: I was to do something else the next day (which is today), rather than go out again on that horse cart. I thus joined up with some Australian travellers on their overland way to their new home, London, and hired a taxi to Mount Popa, home of the 37 Nats (spirits) which are closely knit into the Burmese culture. After a 25 minute climb up steep stairs, I found myself again disappointed by a somewhat dirty and absolutely non-pretty stupa on the top of the hill. The view (and temperature) was great though, so no hard feelings, but also no time lost to head back to the hotel, to get on with the village hopping I had planned for the afternoon. Tomorrow morning I am leaving for Hohe and Inle Lake, where it'll be much cooler (or so they say). Stay tuned. PS: And of course, Murakami's novel is not called "Kafka at the Beach", as I wrote in yesterday's entry, but "Kafka on the Shore". I guess it must have been yesterday's intense heat causing that Freudian slip. Anyway, the book is truly captivating and I am afraid I'll zoom through those 600 pages faster than I'd like, given that it's the last of the books I brought. Hopefully I'll find something to pick up on the way that's not Agatha Christie, Dan Brown, Jane Austen, or the other wonderful writers of entertainment fiction, which I'd rather not read even if you paid me for it.

MJ Ray: discussion@fsfe: Free Software supporter on TV

Update: Not sure that this is actually going out at noon. See mailing list post for information. - Shane wrote: "Legal TV, a TV channel broadcasting on Sky 885, will have a show at noon tomorrow (Friday) about copyright and the Internet. DRM will also be addressed." Legal TV is on eurobird at 28e 11224 V 27.5Ms/s, and is visible over much of Europe free-to-air [link to mailing list post]

Amaya Rodrigo: In memoriam

She was the hunter, the jumper, the smallest one. She was the first to join me in bed every night. She was the one that sat on my arms when I was at the computer, the reason of all my misspellings on IRC. She was the one that preferred peeing on the bathroom basin than on the litter box. The one completely crazy about getting in the bath after my shower, the one who liked to pour the water out of her drinking dish. The one that purred the loudest, the one that sucked on my clothes, the one that made strange bird noises.

Today I came home from work and bad, terrible, news were there for me. I would have liked to blog about how much certain rubito makes me smile, or the Extremadura Sessions, or any of the wonderful stuff that has happened to me lately.

I was in such a good mood when I arrived home today. Well, I admit I was a bit pissed off. While waiting for a green light to cross the street a stupid pigeon shit on my sweater. But that doesn t matter anymore, because cats die stupids deaths and Emacs had jumped after another stupid pigeon, from a seventh floor, through a window that was open only because the lady that cleans my house was doing the laundry I had been to lazy to do myself. Nobody s fault. But she s gone. And I loved her. She would have turned one year old in July, but cats die such stupid deaths. She had to jump out of that window and I am so angry I want to shoot every pigeon on the face of earth. I was one day late, I was building screens to protect the windows with, and this was the only screen left. I was going to finish that very window today.

     

Vi looks so lonely, the house feels empty... And she will be so very much missed.

Ranty, ErConde, please take good care of her.

Ross Burton: GUADEC Rejections

Christopher Aillon says:
Well, I just got back from the Desktop Linux Summit to find an email awaiting me telling me that my proposal for a talk on NetworkManager was rejected this year for GUADEC. ... I can see why getting contributors into GNOME is rather difficult. Even though I'm going to continue working on GNOME because I'm paid to, it's rather disheartening to go through this. Looks like it will start to be a work-only thing instead of a work-and-free-time thing. To all you who have somehow made it into the "in crowd", have fun in Catalonia. I probably won't be going.
To be fair there were two Network Manager talks submitted, one by Christopher and another by Robert Love. What is worse: telling one of the two that their talk isn't accepted, or having two talks at GUADEC on the same subject? NP: August and Everything After, Counting Crows

Erich Schubert: AppArmor receiving it's share of critique

By finally coming forward and "applying" for inclusion into the mainline kernel, AppArmor finally has to face critique on it's approach. And it seems that it's being beaten up quite a bit. I don't think there is anything in AppArmor that you can't do with SELinux just as good (Yes, SELinux does use labeled files to work around the hardlink issues, but guess how these labels are assigned initially? By pathname. If you have a hard link with two different labels, only one of them will stick.). You can in fact "learn" your SELinux policies just like AppArmor. That's called audit2allow, and it is frowned upon for good reasons, and only considered to be okay for interim solutions. There are also tools in development to produce meaningful policies, that is where SELinux really sets itself apart from AppArmor. In AppArmor, you specify for each "confined" application which files it access (and which capabilities), usually by learning these. On SELinux, you basically divide your system into meaningful parts (e.g. logfiles, user mail, user web files) and then specify which kind of access an application is to be granted. This manual part, deciding which access is allowed, is a big feature. Apparently the AppArmor thunderbird policy has "learned" the setuid permission for thunderbird, which I consider a very bad idea. You can't just learn everything while application may have bugs (or workarounds, or security nets - e.g. it might try to setuid and quit if it succeeds!). And despite some claims, SELinux does not require you to have a policy for everything on your system. Only in "strict" policy, whereas if you use "targeted" policy, you'll have a so called "unconfined" domain, too. The AppArmor approach reminds me a lot of what grsecurity 1.x ACLs were doing, back with some 2.4.x kernel. It never worked too well for me, that's why I can't say much about newer grsecurity versions... but to me, grsecurity sounds a lot better than AppArmor. Much more mature.

Christian Perrier: Back from my annual German samba break

As usually every year, I went this year to the Samba eXPerience conference in G ttingen, Germany. That conference is the only existing conference entirely devoted to the Samba project. It is a unique opportunity to meet with other users of samba, as well as nearly all member of the Samba development team (which is "only" made of 10-15 people, which always seem to surprise attendants when one knows about the quality of Samba over the years). This year, we were missing Tridge who was busy in European Commission hearings about the Microsoft case, if I got the explanations correctly. But most of others were around and I'm glad I had a few really interesting talks with several key people in the Samba project. The small samba maintenance team in Debian will probably take advantage of this as well. There were two of us over there, No l K the and myself. It's always a pleasure to spend some time with No l. We've been able to lower the number of bugs for samba in Debian a little bit as well as prepare the next release (3.0.23) packages...finding a few bugs in the upstream builds..:-) We also initiated some discussions with upstream about possible backports of the current samba code to sarge. Upstream policy is to encourage users to upgrade to the last version in the samba3 releases, so our policy in Debian does not fit well with these goals. We'll try to work closely with people who maintain the Debian packaging in the Samba Team... Of course, we also talked and listened to numerous talks about Samba 4, the Active Directory killer. In short they can be summarized to: nothing will be released "production ready" in 2006. So, we won't have samba4 in Debian etch. Steinar Gundersson and Jelmer Vernooj (member of the Samba Team AND in the Debian NM queue) will continue to maintain samba4 package in experimental (to test them, just install samba from experimental...beware, this *will* break File and Print services on your host). Also important were talk about evolutions in Samba3, the current production code. My vote goes to Jeremy Allison's talk about "Delegating administration of samba servers", introducing what I consider a killer features: user shares, ie the possibility to allow some users to create their own share on Samba server. Believe me, that feature will rock and it *will* be in 3.0.23 due out in a few weeks. I already have tons of plans for my production server at work in ONERA where the days of my NT4 domains are counted. For this, Jerry Carter tutorial about Samba 3 and Active Directory will be incredibly useful, even if I don't have any AD servers (and don't plan to). In short, great time as usual in G ttingen. I'm also very happy that I had the opportunity to visit Meike and have such long and interesting hours talking together while eating noodles. Tsch ss!

26 April 2006

Martin F. Krafft: Mandalay to Bagan, and 2700 temples

Leaving the computer centre in Mandalay, I decided to settle my further itineraries and headed to an Internet shop in the hope to arrange some online bookings, using Aline's credit card (because mine was lost and I would rather preserve the cash dollars I have, given that there is no way to get more money in this country. I managed to book myself hotel rooms for the One Night in Bangkok I have before returning home, as well as the five days of Yangon before. Other than that, however, I could not get any flights; Myanmar-internal flights cannot be booked online, and Thai Airways refuses to take passengers when the name on the credit card does not match the passenger's. Given that my plans for the evening where set, I had to leave the place with my mission unaccomplished and headed for the Green Elephant restaurant, which the Lonely Planet describes as up-scale. For a whopping $7, I treated myself to beer, pickled ginger and green tea leaves, and butter fish in a tomato curry. Very delicious. Afterwards I attended the Mandalay Marionette & Culture Show, which was quite lovely despite the atonal music that came with it. Mandalay marionettes (or Myanmar marionettes in general) are very elaborately made, and the style to guide them is very unique to the country, the art having been the popular art back in the days when kings ruled the land. The artists are devoted to keeping this art alive, and you could really feel their enjoyment as they showed fights between ogres, princes and snakes, riding horses and trolling monkeys, princes engaging in "hackysack"-style football artistics (which is very popular over here, and people are rather good), as well as synchronised dances between marionettes and real dancers. I can recommend this show to anyone visiting (as I recommend to anyone visiting Hanoi to see the water puppet theatre) and am glad I chose this option over the "Moustache Brothers" performance, which is political satire and slapstick on the edge of legality. I ended the evening talking to some other travellers, most of which had no interest in listening to others but to tell their stories instead. The next morning saw me rising at 4:30 to catch the ferry to Bagan at 6:00 o'clock. The boat had comfortable seats and a restaurant, and only a handful passengers, so the 10 hours went by reasonably fast (no comparison to the ride we took on the Mekhong last year to get from Chiang Khong in Thailand to Luang Phrabang in Laos). We arrived in Bagan on time and together with some Australians I found the May Kha Lar guesthouse (following again the Lonely Planet), which is a rather pleasant place with a lovely, elderly, English-speaking lady running it. SHe also arranged my further air travel for me and wanted about $30 less than the official booking offices. I decided to spend an additional day in Bagan, so I am heading out from here by plane on the 28th, going to Heho, then spending two and a half days at Inle Lake, and flying to Yangon on the 30th. From there, I am leaving for Bangkok on 4 May. With the tickets in my pocket, I felt relieved, showered, and went for a traditional Burmese massage, which turns out to be completely different from the Thai style (which Laos and Vietnam copied more or less) and was rather painful, both because the lady literally tormented my legs far too long and spent only a very short time on my pained shoulders, and because neither the mosquito coils nor my repellents warded off the beasts as I was lying there out in the darkening sky right at dusk. No Malaria in this region, fortunately. Following a very traditional Burmese dinner (goat meat curry), I went to bed because... ... the next day I rose again at 4:30 to meet a guide, and left the hotel at 5:00 o'clock on a horse cart for a tour of the temples. Bagan is what could be called the heart of Myanmar, and on a 42 square kilometre area, you can find 2700 temples (of the 4500 originally built), dating back to the 10th century AD. Unfortunately, the wall carvings and paintings in most temples has been washed away, and it was nowhere near as fascinating to stroll along the endless corridors as it had been in Angkor Wat or Bayon Wat in Cambodia, but from the outside, these temples still look spectacular and are well preserved or restored. Also, climbing up on one or the other, the sight was almost overwhelming: a vast landscape of strupas and temples as far as the eye would reach, and all that under a lovely sunny sky. Haha. The "sunny" bit is what made me get up so early, because the temperatures are bearable only up until 11 o'clock or so. Between noon and 16:00 o'clock today, the thermometre measured 46 degrees Celsius -- I don't think I've ever been in a place so hot (if you leave out our trip to Death Valley in an airconditioned van. So in order to escape the heat, I went to the archaeological museum at noon, then back to the city and into the swimming pool of one of the nicer hotels in town, which cost me $3 for a pool that was green (they don't have the money for chemicals), and the water about the temperature of my bathtub at home. I did not swim, but fortunately, the showers there were pleasantly cold, so I lay in the shade to read ("Kafka on the Short" by Haruki Murakami), taking a shower every ten minutes to cool down. Going back to the hotel, I find the electricity to be gone once again. I think that this town (and Mandalay as well) has maybe 4 hours of electricity a day, it coming and going every few minutes (which makes computer use quite unpleasant). This also means that there is no aircondition most of the day, at least in the budget hotels which don't have their own generator. I am meeting my guide again at 16:00 hours for another 2-3 hours, then will follow the hotel owner's suggestion for a "back massage expert", eat, sleep, and climb Mount Popa tomorrow morning. I'll try to get online again in the afternoon. Thanks for reading along.

Ross Burton: Die Evolution Die

This may well be en_GB sucking really badly (until recently in Ubuntu it didn't have 24-hour time either), but this is really bad form for a birthday field: Birthday field in Evolution Someone will be first up against the wall, mark my words. A bug is filed, fingers crossed it gets fixed soon. Update: Richard "bork bork" Hult, running in sv_SE, has a four digit year field. en_GB sucks. NP: Gonzo Jazz, Margin of Safety

Wouter Verhelst: EMILE: tomorrow

Today I 'ave mostly been eating... EMILE. Or my IIci, pick one. I came very close. Anyway. It's been almost a year since the first WNPP bug about EMILE was filed, but today I finished the work. The main reason that I haven't uploaded it earlier is that my previous attempts at building a working package did not succeed; the package got built, but did not work. Today's package, however, is one that finally works on my IIci. Hence, I think the time to upload has come. Except that lintian isn't too happy about it yet, but that's being fixed now. Well, now... it takes a few hours to build the package on a IIci. I could probably do it 'somewhere else', but then I need to compile a new crosscompiler first. Which is going to take too long to my taste. I could probably also pick one of my faster m68k machines (the IIci really is the slowest one I have), but they're all busy doing other stuff right now. That is, except for the Quadra 700, but that one is still at home, shut down, and with a hard disk that I rendered unbootable on a previous EMILE attempt. I guess now that it boots with EMILE, I'll take the MacOS disk out of barok (the IIci), and take it home to fix the Quadra 700. Some time soon. Anyway, EMILE will be uploaded into NEW once the build is complete; I'll announce here when it's ready. This should be tomorrow by the latest. In the mean time, I'll let you know that I created a wiki page to list the hardware that EMILE does support. That's certainly not all of them, but I guess we'll see. Update: here for the impatient, but it's also been uploaded to incoming.d.o—where it awaits NEW processing.

Christine Spang: Side Effects

Today, I witnessed somebody attempting to read a magazine on a dark bus via the light of their cell phone. Makes me wonder what OLPC will end up causing.

Alexander Schmehl: [DebConf] Sometimes I like my job

It is for example fun to be one of the first who heard about a new award Debian got, and add it to our website (should be up there soon, thanks again to Cyril Brulebois from the french language team for translating). The not fun part of my job seems to be to try to write polite mails, asking people for something without stepping on their toes. Well, let's not talk about that; after having spend several hours on writing an other mail I just feld like blow my stack but deleted the stuff I just wrote... so let's go one. Another not that funny part of my work were the proceedings I just finished. After I lost somehow last years work (I had a very nice system of texing all those papers, creating a big PDF for printing and several small ones for download), I needed to do a complete rewrite, which got complicated by people submitting their papers in neither LaTeX nor plain text as we asked to do. Some could be fixed by some sed magic, but I'm impressed what ugly code some automated conversion tools can create. But that's done, too, and we even had the great idea of adding a credits section for all the volunteers helping to make DebConf become reality. Having that done, I couldn't resist and added a small joke. One of those insiders not everyone will get... Forgive me :) While talking about jokes: Did anyone noticed our quite new DebConf fortunes section? Feel free to submitt new ones. Some other news: No, Gustavo, we didn't decided yet where DebConf7 will take place, but one thing is for sure: Since DebConf6 will be in Latin America the next one won't. We have several offers, including (but maybe not limited to, I might have forgot one or the other) Edinburgh, Brixen, somewhere in Greece, Sarajevo and... uhm... some people would like to have one in Germany but don't think we could afford that, so it's quite sure DebConf7 won't be here. But as said, decision has not been made (but it looks like it will be in Europe ;) and currently we don't have the time to think much about that. Let's try to get DebConf6 done first ;) PS: Civilization has reached me! But they marked the wrong house! It is the one to the south east, the one with the empty parking lot.

PPS: No, this blog entry has no deeper meaning; I just feld like bloging.

John Goerzen: Small-Town Banks

Last year, I wrote about a small town funeral home.

Today it's time to write about small town banks.

So last Saturday, Terah and I went to the bank in the town we're going to be closest to (population 590, compared population 3500 town we live close to now). We were discussing financing for the house and renovations.

The loan officer at the bank is also the city mayor. She's lived in the area for years. I don't know her well, but I know of her and she has heard of me too.

So some of the questions we got were:

"Are you still working the same place I heard about awhile ago?"

"Now should the seller's copy of this example contract go to your aunt or your dad?"

"So the place you're buying -- just a couple of miles from your great uncle then, right?"

Unlike the large nationwide bank we talked to, we were NOT asked:

The person at the small-town bank also actually returned my calls, answered my e-mails, and kept appointments. She also provided all sorts of help for us along the way. It's as if the bank would actually like to have our business and would work to get it.

Guess which bank we're going to use.

25 April 2006

Guilherme de S. Pastore: New blog about Debian stuff

After long, and quite too long, and several disappointments (the few people involved know pretty well what this is about), I finally got my Debian account, and all of a sudden felt motivated to work on Debian stuff again. Just created this new blog so I could syndicate something on Planet Debian (as I gave up Advogato long ago, and my GNOME blog on blogs.gnome.org - which is supposedly about GNOME - would probably not fit). Let's see how well that turns out to work.

On some more interesting fronts, it seems we will finally be able to push evolution 2.6 into unstable, releasing gnome-panel 2.14 (and consequently gnome-applets), which are kind of the final bits missing in the transition. Yay!

Wouter Verhelst: EMILE: tomorrow

Today I 'ave mostly been eating... EMILE. Or my IIci, pick one. I came very close. Anyway. It's been almost a year since the first WNPP bug about EMILE was filed, but today I finished the work. The main reason that I haven't uploaded it earlier is that my previous attempts at building a working package did not succeed; the package got built, but did not work. Today's package, however, is one that finally works on my IIci. Hence, I think the time to upload has come. Except that lintian isn't too happy about it yet, but that's being fixed now. Well, now... it takes a few hours to build the package on a IIci. I could probably do it 'somewhere else', but then I need to compile a new crosscompiler first. Which is going to take too long to my taste. I could probably also pick one of my faster m68k machines (the IIci really is the slowest one I have), but they're all busy doing other stuff right now. That is, except for the Quadra 700, but that one is still at home, shut down, and with a hard disk that I rendered unbootable on a previous EMILE attempt. I guess now that it boots with EMILE, I'll take the MacOS disk out of barok (the IIci), and take it home to fix the Quadra 700. Some time soon. Anyway, EMILE will be uploaded into NEW once the build is complete; I'll announce here when it's ready. This should be tomorrow by the latest. In the mean time, I'll let you know that I created a wiki page to list the hardware that EMILE does support. That's certainly not all of them, but I guess we'll see.

Eric Dorland: mozilla-firefox sarge 1.0.8 backport

Packages have been built backporting the security fixes from 1.0.8 into sarge's package. This package has gone to the security team and there should be a DSA soon. All the fixes were backported throught the tireless efforts of Alexander Sack. If anyone sees him, buy him a beverage. In other news, the 1.0.8 release is the end of life for the 1.0.x series. With etch at least 8 months away (wouldn't it be great if we released etch in 8 months?) doing security releases for firefox will likely increase in pain.

Dirk Eddelbuettel: RGtk2 packages in Debian

As previously mentioned, I had built local packages of Michael Lawrence's RGtk2 port of the Gtk v2 widgets / toolkit to the R language and environment. This package, along with the related cairoDevice package, is now in Debian's main archive. RGtk2 extends and replaces the older r-omegahat-rgtk package. For an two interesting applications using RGtk2, look at Graham William's rattle, a glade-based data-mining user-interface to several R functions, and at John Verzani's PMG (aka Poor Man's GUI) generic GUI for R.

Joey Hess: html sanitisation

Now that I've finished adding email subscriptions to ikiwiki the only thing blocking me finally making an official release of it is html sanitization. This is the part I've put off till last because it's the part I hate. Somehow the web has evolved a backwards security model that wants sites with dynamic content to be responsible for policing that content for things that could cause security issues, instead of just making browsers actually secure so that no possible html can be a security issue. Which is of course absurd, but the various types of potential cross site scripting attacks that users of your wiki will be vulnerable to if it doesn't try to sanitise its html are nothing to laugh at. So everyone is left having to sanitise any untrusted content that they put up on the web. In my experience, almost everyone does it poorly, I've even found XSS holes in well-designed websites like Advogato. It doesn't help that browser coders are busy adding new features^Wholes to their web browsers, which everyone then has to update their sanitisers to block. I don't like participating in security arms races, so while I am evaluating various html sanitisers right now, adding html sanitisation to ikiwiki is not a pleasant idea, and I am tempted to punt on it, document the issue, and refer anyone experiencing problems to the authors of their web browsers. Sigh.

Uwe Hermann: Mafia Boss Secures His Data with Caesar Cipher

This is just too funny not to blog about it... You might have heard that the mafia boss Bernardo Provenzano has been arrested recently. Now people found out that he used some "cryptography" in his messages to relatives and so on. They were decrypted pretty fast: Mafia Boss's Encrypted Messages Deciphered.
"Looks like kindergarten cryptography to me. It will keep your kid sister out, but it won't keep the police out. But what do you expect from someone who is computer illiterate?" security guru Bruce Schneier, author of several books on cryptography, told Discovery News.
(via Bruce Schneier)

Erich Schubert: More thoughts on XML differencing

Last year, I gave a talk on XML differencing at the Extreme Markup Languages 2005 conference in Montr al. Since then I didn't have much time to work on that project. The prototype app is opensource, and available at ssddiff.alioth.debian.org. The slides are there, too, and so is a link to the article. XML differencing is actually a two phase process; I've been mostly working on the first phase. Traditional approaches intertwine the two phases. In the first phase, you build a mapping between the two documents. I called this a "nodeset correspondence" in the slides. Basically you decide which node from the first document corresponds to which node in the second document. When you have found this mapping (the "marked" output writer of ssddiff will output this information in form of two XML documents marked with numbers in a certain attribute), the actual differencing is done. But much of the work remains. When doing a diff, the output (format) is just as important as the actual result. While the "marked" output explained above is very precise, it doesn't give the user an overview of what has changed in the document. That's why I added two more output writers, the "xupdate" writer and the "merged" writer. The "xupdate" writer does obviously produce an XUpdate script. It goes a long way to optimizing the output (read: minimizing the number of operations), and employs a longest-common-subsequence algorithm for that (LCS is what regular diff uses on lines!). Fortunately we already have a 1:1 mapping, so this boils down to a longest-increasing-subsequence which can be computed very efficiently. Then the writer employs some XUpdate tricks to do real moves (by storing parts of the tree in variables to be inserted later), and avoids collapsing of text nodes (it will eventually insert dummy nodes for that). But all this gives just a glimpse of the complexity I've encountered in what I considered to be a "remote" part of my project. It isn't even described in the paper, because I just hacked this code together to work somewhat (attribute handling is incomplete IIRC). The "merged" writer turned out to be much more powerful than I had imagined and actually rather easy. After "merging" two version of an HTML document, I could add some CSS rules and have a visual presentation of the changes in my browser. Very cool. I'd love to add this html merge functionality to the prototype, but I didn't have enough time yet (you'll find some refactoring of the merged writer in SVN though to get there someday). But let me get back to the difficulties in the "XUpdate" writer. Not all of these difficulties are actually of technical nature. It is (like with the semantics of differencing) a matter of the intended data model and use. When you are doing a diff to be applied by a computer (e.g. via XUpdate), you may have the requirement, that the resulting document is identical to the original document. In that case, the diff is likely to have to restore whitespace. If you are interested in analyzing the differences, you will want to skip any irrelevant information. Let's assume we have an address book:
<abook><entry name="tom" /><entry name="jerry" /></abook>
Ordering of the entry nodes is likely to be irrelevant. You address book applications will sort the entries on demand. So a "semantic diff" shouldn't include any changes to the ordering of "entry" nodes, should it? The XUpdate writer doesn't have any functionality in place to skip such changes from being written to the output file. This will likely be not possible without some DTD magic and extra user information. However, to have the benefits of the "-u" context option of good old "diffutils" - fuzzy matches, and somewhat reliable merging of changes without having all revisions available - such semantics are needed, too. But this will even further increase complexity of the output writer, which for example would need to detect somehow that the "name" attribute in my address book is a unique key, and therefore xpath expressions like /abook/entry[@name='tom'] are preferrable to expressions such as /abook/entry[1], which will easily break when merging. The specification of an "XUpdate-replacement with context information" is probably a whole thesis in itself, I guess. P.S. I'm occasionally asked about a Java version of ssddiff. Sorry that I have to disappoint you there. First of all, I'm very short of time. Then I'm not too comfortable in Java, and I estimated that the Java version would need at least twice as much memory, because of certain optimizations I can't easily access in Java that I can just hide in a template in C++. And memory is the key limiting factor at least in exact mode.

Next.

Previous.