Search Results: "ron"

10 August 2007

Joerg Jaspert: Override changes

While doing lots of override changes lately I noticed that people who reply to the override disparity mails do like to delete the important part of the mail and quote that part thats of no interest for me. Compare the following two: > lalala_0.0.0.0.-0.0+b0_amd64.deb: package says priority is musthave, override says dontuse. > Either the package or the override file is incorrect. If you think > the override is correct and the package wrong please fix the package > so that this disparity is fixed in the next upload. If you feel the > override is incorrect then please reply to this mail and explain why. Can you please change the override, as people should really have the package installed? Thanks. with > Either the package or the override file is incorrect. If you think > the override is correct and the package wrong please fix the package > so that this disparity is fixed in the next upload. If you feel the > override is incorrect then please reply to this mail and explain why. This package is conflicting with other packages, so must be extra. Yes, there is the source package name in the subject line, but hey, a source package can built lots of different binary packages, so - what binary do you want to have changed? Even if the answer is all - quote them, as that saves at least one dak command to run…

9 August 2007

Daniel Jacobowitz: So much for that computer

My desktop seems to have melted something precious in this morning’s lightning storm, despite the recent and rather hefty UPS sitting behind it. I am, to say the least, annoyed. It was a nice self-built Shuttle system from 2005, but now all it is is a machine check generator:
HARDWARE ERROR. This is *NOT* a software problem!
Please contact your hardware vendor
CPU 0 4 northbridge TSC 6eb92ec370b
  Northbridge Watchdog error
       bit57 = processor context corrupt
       bit61 = error uncorrected
  bus error 'generic participation, request timed out
      generic error mem transaction
      generic access, level generic'
STATUS b200000000070f0f MCGSTATUS 4
It’s not even bad RAM or a bad RAM socket, the way most memory errors seem to be; I had two DIMMs in two sockets so I was able to try for both possibilities. Unless it fried both somehow, of course. It seems to boot a little further when left cold for a while, and not as far just after crashing. I am inclined to suspect the motherboard. I think I’m going to have to write it off as a loss. Which means I need a replacement. I can get by with just my laptop for a little while, but not indefinitely. Are there any good options for pre-built Linux systems yet? I was somewhat underwhelmed by Dell’s. I usually build from parts, so looking at pre-built systems always has a certain amount of sticker shock. My main concerns are CPU / memory performance (a lot of compiling here), room for at least three hard drives, and reasonably quiet. Otherwise it’s off to newegg again… Or I could always buy an equivalent computer to my current one, for a fraction of the original price, at a local consumer electronics megastore! How’s that for a different idea.

Michael Janssen: UI Peeves: Locking, Proximity and Purpose

I have had, on occasion in the past, a reason to use the wonderful TortoiseSVN software. It is, by all standards, a really great solution for someone wanting to use SVN in a MS Windows environment, and uses the official svn client in order to leverage open source as much as possible. Recently I have been using it a bit more as I work at Honeywell as a programmer. I've come across a couple things that bug me about the interface.

The first is that some actions inexplicably lock the place that initiates that action. The best example I have of this is when I am looking at the window for an Update, and want to see what happened in the log, I click the button to open the log, and I can't use the window while the log downloads. Sometimes this can be an issue because the server is pretty slow at producing logs for some reason (it's beyond me, and NotMyProblem(tm) because I'm not in charge of the admin). This makes it irritating because I can't inspect other files while the log is downloading. Strangely, the server actually will return other requests quickly, like the request needed to see the diff between the working copy and the tree. It would be much better if the windows were separate - they're not related to each other in effect, so the locking of the initial window is completely useless. I could have called up the log from another action, that would leave the update window perfectly usable, so I know it's possible.

The second problem that I have run across more than once relates to the proximity of actions in the right click menu while committing a change. Take a look at the screenshot of this menu.
TortoiseSVN commit context menu

There have been many times when using this window that I realize that I forgot to add a file that I need to commit, so I right click on the file and move down to the "Add" menu item, only to miss and click on the "Delete" item. "Delete", when used on a unversioned file, performs a windows delete, causing me to curse at the (now missing) entry in the commit log and go running to the recycle bin to retrieve this temporarily lost file. These two options in the context menu are entirely too close to each other. The "Delete" and "Add" actions have completely opposite meanings and effects, and having the program do exactly the opposite of what you expect is what I consider to be a Very Bad Thing. I would move the "Add" action up to the top of the list (it is, by far, the most common reason for me to use the context menu), or at least place another menu item in between.

I'm feeling like I'm being very unhelpful here, complaining about these issues in an open source project and not producing a patch to fix these issues. I may produce one in the near future - unfortunately when I'm not at Honeywell, I don't really have a Windows development environment setup.

Comments: (1) Trackbacks: (0)

Comments
  1. JD: The reason diffs are quick is because svn keeps a copy of the original file in the checkout, so diffs and reverts don't need to hit the server.
Trackbacks
  1. No Trackbacks

Evan Prodromou: 20 Thermidor CCXV

Great day today. It's been beautiful here in the South Bay, and I'm glad to get some regeneration. I miss Amita June and Maj pretty badly, but they're coming to California on Saturday, so the end is near. Tonight I'm heading up to San Francisco for the Creative Commons Salon. Should be really fun. tags:

Planet Nowhere So, I've had some complaints from people that my blog posts on Planet Debian weren't about Debian enough. Although that's not the mission of PD -- it's stuff by Debian developers, not stuff about Debian -- I decided to remove my feed from the list there. Life's too short. So, if you're used to reading my blog there, you'll need to add my feed to your reader directly. tags:

Meanwhile... I just got back from the CC Salon. Excellent time! I hadn't been to one in SF, although I helped to organize the first one in Toronto. The presentations were all by the summer interns from CC. I was shocked and astounded that all the interns were doing cool, important things, like desktop integration, enhancing the CC Wiki, and developing best practices for marking CC-licensed content. These are all things that CC users have actually been asking for and need a lot. I'm concerned that this is breaking with the tradition of summer interns everywhere doing meaningless tasks that help no-one. Is the future of summer internships in jeopardy? One of my favourite pieces of info, of course, was that you can now log into CC Wiki with OpenID. Coolio! tags:

8 August 2007

Eric Warmenhoven: Self portraits are hard.

A few weeks ago, Lisa and I were in Barnes&Noble, and I decided to buy a few photography books: The Digital Photography Book by Scott Kelby: This book is, as advertised, not a book about concepts and theories but rather about practical advice and tips. If you already know some of the theory, it’s pretty easy to see how it plays out in practice in this book. Composition Photo Workshop by Blue Fier: I love the name “Blue Fier”, even though I’m probably pronouncing “Fier” wrong (”Fire”). Anyway, this book started off a little slow for me because he covers things like aperture and depth of field and focus, and shutter speed and ISO and other things I’m already fairly familiar with. When he started getting into framing and rule-of-thirds type stuff it got more interesting. He also covered several different styles of photography (landscape, macro, portrait, etc.) and so it was a pretty good introductory book. Digital Portrait Photography and Lighting by Catherine Jamieson and Sean McCormick: I’m only half way through this book so far, and already it’s prompted me to spend hundreds of dollars on a new flash, and gotten me thinking about getting lights and umbrellas and reflectors and setting up my own miniature studio. I’ve spent the past few days trying to take portraits of Pixel and Lisa and myself, and haven’t had much success, mainly due to poor lighting (hence the flash and the dreams of better lighting equipment). When taking self portraits I’ve had such trouble getting the camera placement and focus and lighting right that I haven’t even gotten to really working on posing much. Which is fine, since I haven’t gotten to that chapter yet anyway. There’s a portrait workshop being held in Los Gatos at the end of September that I think I’m going to enroll in, but I’m worried based on the description that I’ll have already heard most of it from the portrait book I bought. In the spring I may enroll for a photography class at the local community college as well.

Miriam Ruiz: El rei de la casa

The Proof of the PuddingThis is an updated translation into English of the one-question interview with pjorge (based on Darren Rowse’s one-question interviews idea) in which Javier Candeira (Barrapunto co-founder and editor among many other things, and a good, loved friend of mine) comments about an interesting game of his creation that’s being exhibited in Barcelona and that deals with the fears many parents have towards the Internet and the new enterntainment technologies and videogames. The game code will be released as GPL, even though the game data will have a non-free Creative Commons (with a non-commercial clause). The game has a really interesting approach, and mixes the concept of pinball games with that of graphics generated with “paper dolls” techniques, to try to make people think about the ideas mainstream media are pushing, and the way they try to tell everybody how to raise their kids. You might like it or not, but it will probably won’t leave you indifferent. That’s what art is about, in fact, isn’t it? What is ‘El rei de la casa’? ‘El rei de la casa‘ (an expression that in Catalan and Spanish means “the precious child”) is an exhibition and a videogame. The exhibition deals with the cultural construction of the idea of childhood, and can be visited until September 24 in the Palau de la Virreina in Barcelona. From there. Among other works, in the exhibition there are photos by Loretta Lux and Bego a Egurbide, paintings by Marc Ryden, Kiki Smith and James Reilly… it’s really worth a visit. El rei/la reina de la casa. ( The videogame is a commission from Andr s Hispano and Marc Roig, curators of the exhibition. They wanted to portray Internet and videogame arcades (or cybercafes, which are their modern equivalent) as one of the “new forests”, these places where parents don’t dare allow their children go alone for fear of the dangers (real or imagined) that may lie in ambush. The Internet has entered into the collective imagination, and one of the memetic niches that it has crept into is that of the bogeyman, the scapegoat that bears the brunt of all the evil that happens in society. It is enough to look at the news programmes from right-wing TV stations with their adversative Internet coverage: “it’s good, but…”. All over the media you see headlines like “gang of pedophiles arrested who sold child pornography *on the internet*”. They conveniently skip that pedophiles filmed those poor kids *in a flat*, and that they did it *on a bed* and used *videocameras* just like those used by the reporters now sounding the alarm. But no, what’s bad is *the Internet*.
The other theme that we wanted to touch on with the pinball game is how videogames are presumed to corrupt childhood. When pinball games were introduced, the North American authorities laid down the law: it was an infernal machine that incited gambling and even lust. From the religious right to the secular left, every moral guardian has denounced the supposed harmful effects of videogames on childhood: because of them children and teenagers engage in murder, robbery, truancy, bad school grades and even untidy bedrooms and doubtful personal hygiene. For this reason, the “new forest” of the Internet and videogames had to be a videogame, proving once more that games are cultural vectors, a form of artistic, political or commercial expression like any other. It also had to be a videogame about the a triangle: on one side the children, on the second one the children minders (parents and society at large), and finally the Great Scapegoat: the Internet. After many abandoned and reworked proposals we arrived at the present design for the game: an emulated pinball game presented on a panoramic TV screen, and having two levels: one set in the real world and named after the exhibition, and a second one set in a more or less conventional cyberspace. This second level is called “Prey of the Net”, and portrays the vision of the Internet that a Fox viewer may have: you have Spam, game-playing killers, kids making more money than their parents, S&M gear, dildos… in short, everything that is scary and nothing that is comforting, at least to some.  Presa de la red! (All the illustrations for this pinball, both on the gameplay field and on the scoreboard, are by Mauro Entrialgo. For the scoreboard I asked him to prepare a set of drawings similar to KISS dolls (like the cut-up dolls that kids still played with in the last century). Thanks to these dress-up dolls the scoreboard shows more than the score (which grows randomly anyway); it also portrays the state of the boy or girl protagonist of the game. I say “boy” or “girl” because in the game, just like in real life, you have a 50/50 chance of starting the game of life with either sex. The fist level, ‘El rei de la casa’, portrays the stress that families feel when facing children’s media consumption. The targets trigger lines from the parents: “All day in front of the Idiot Box!” when you hit the tv, or “without a degree, you are nothing” when you hit the school. There are four targets on the right, which can be reached shooting the ball with the left flipper (the one representing the parents): school, museum, church and reading. On the left, and reachable from the right flipper, representing the kids’ id, are the TV, the kid’s peers and the videogame console; at the top of the playing field, towering above it, the internet-enabled computer. As the ball hits the different targets, the scoreboard dresses the kids in a housecoat, a leather jacket, and gives them a mortarboard or a saint’s halo. They are the pride of their parents, kids still not perverted by the Internet. It is cheap symbolism, I confess, two-dimensional sociology, but that was also something we aimed for. After all, pinballs have always been complicated allegories rather than complex ones. In a first design I planned to make computer accessible only under certain conditions, but that is not something that would have work in this exhibition: some people just play and play (which gives me an immense joy), but other people can’t or won’t give it much effort. It’s best to make it easier for everyone, so they can send the ball into the next level even without meaning to. The second level, “Prey of the Net”, is accessed when the player puts the ball through the PC’s screen. Here the character on the scoreboard keeps smiling while the game dresses them in a straightjacket, S&M headgear, or leaves them in their underwear, with their hands full of money, playing cards, bloody knives and sex toys… to their parents’ horror. The player has no fixed goal here, only to make the ball go through the pachinko and the spinning spider. These elements work as an atrocity generator and a rebuke distributor. Parents’ voices scold the player, faced with the horrors of the Internet. But the star is the scoreboard. Mauro rocks. Right now the code and content for downloadable game are done, and the people responsible for the ISO are giving it the final touches. It will be a bootable liveCD with some Debian variant that (hopefully) will run on any PC bought in the last two or three years. We will treat the computer as a games console, which may or may not be symbolic (if you want it symbolic, we can make it symbolic!). The game itself is under the GPL license (the pinball part is based on Henrik Enkvist’s Emilia, which is packaged in Debian), and only the graphic resources will be under a non-commercial Creative Commons license. The music is also under a non-free Creative Commons license because of the status of the original samples, but I recommend you download it and play it because its author is none other than man, the Barrapunto founder and sometimes editor.

Russell Coker: Tactical Voting

In response to a blog conversation on Planet Debian, Wouter Verhelst writes about voting tactics in which he claims that Instant-Runoff (wikipedia) (the method used in Australia to elect members of the house of representatives) is broken. I have read the Wikipedia review and neither it nor my previous understanding of Instant-Runoff leads me to believe that it is broken or prone to tactical voting problems. The main tactical voting issue in Australian elections is to give first preference to a small party (such as The Greens) in a seat where there is almost no chance of the small party winning. The idea is to have the vote effectively be a vote for whichever of the two major parties the voter prefers while also sending a message (by the first-preference votes which are widely publicised) as to their desires. If a major party wins a seat while 20% of the first preferences went to the Greens then they might find it an incentive to try and get some Green policies adopted if they want to win the next election (whether this actually works is debatable but it is a fact that people try it). There are many people who don’t understand how the Australian voting system works and believe that they have to vote for one of the major parties to avoid a “wasted vote”. This is not due to the voting system but due to American media - and ill-educated Australians who can’t work out which parts of the news apply to them. Wouter has an advantage in living in a country where English is not the primary language - English news does not directly concern him and his country-men can probably work out that English-language voting instructions should not be followed! The condorcet.org site has a useful analysis which demonstrates one theoretical flaw in IR, but realistically getting the average voter to use Condorcet would essentially be an IQ test as a pre-requisite to voting (numbering all the candidates in order for IR is difficult enough). The fact that an election system is not theoretically fair is not a valid criticism unless there is a viable alternative which is better. If the lower house is to actually represent the people of each electorate (which is rarely the case nowadays) then IR seems to be the best option. If members of the lower house are not expected to represent geographic regions then Wouter’s advocacy of proportional representation makes sense. As for the Australian Senate, the voting system for that is far too complex and I think that as a matter of principle any voting system which can not be understood by the majority of voters is wrong. A good case could be made for proportional representation in the senate. Update: In response to Wouter’s post - tactical voting that doesn’t change the outcome of the election and merely sends a message to a political party is OK IMHO. But if you convince enough people that tactical voting is the only option in the US then the result may change.

Erich Schubert: Security issue in Serendipity

Yesterday, a friend mentioned that some program had been accessing most of his (s9y) blog, and apparently even manged to access password protected entries.Now I'm not a s9y user myself, but somehow I felt like digging into this. I wouldn't consider myself a web security expert, actually. I'm more interested in data mining and such algorithms these days.It took me 10 minutes to find the problem (despite not having used PHP much in years; I don't trust that programming language; including some searching if it was maybe already reported somewhere). By sending an appropriate POST request, you could override the password used, and that way disabling it.Granted: "locating" a security issue you know it exists is a lot easier than actually discovering new ones...Official announcement in the s9y blog, including a fix for the problem.Memo to the guys who wrote that bot that was accessing the blog of my friend: You messed with the wrong people, guys. We know how to detect your scan, and we'll spoil the fun for you by helping in fixing the bug!

MJ Ray: SPI Elections: Corrections

Well, yesterday I asked
"WTF? There seem to be some 30 or 40 voters who really dislike me, but didn't tell me that straight, preferring to be silent then vote me down. Are you cowards, or what?"
Not the most polite of questions(!), but it's what I was wondering at the time. I had some good replies in the comments and a reply by Pingback that I didn't like, but it turned out to be a very educational reply in the end. A comment from Filipus Klutiero included:
"Sometimes, it's not really possible to explain a bad opinion of someone, because we forget the reasons for that opinion. However, if you think that voting based on reputation is a bad idea, you probably can't understand these "cowards"."
I've mentioned before that I don't seem to fit the debian developers stereotype, so I guess it's not surprising if I don't understand them sometimes. If reputation is always going to be such a big factor, one problem I need to overcome in debian and SPI is that some other participants do make crap up about me. You can usually spot it by phrases like "seems to think" (there are not that many mind-readers out there), but eventually, mud sticks. How to overcome this? Patiently post corrections, or is that futile? Here are posts from Andrew Pollock and Matt Palmer which I think are wrong on several points:- First off, I haven't decided to call anyone cowards - it was a question, albeit a bit "nasty, british and short". The underlying sentiment was continued disappointment and puzzlement at why voters behave like that in a non-secret vote, not rage. It was not really an "outburst," coming a week after the results. I'm not unhappy with the results - I've congratulated the winners by several methods, including the last post, although I mentioned my mixed feelings. Isn't that usual? I think very few non-elected candidates express unbridled joy about the experience. After all, it's not an easy decision to stand, but I did it for two main reasons: shortage of other candidates I really liked, at the time I chose to stand (as I mentioned in my platform); and for practical experience of how Condorcet behaves. I'm not rabid - I've even written against the Rabid Right recently - and I'm not rabidly anti-Google. I had polite chats with various people from Sun, Microsoft and Google at debconf - I don't like those companies, but I don't feel a need to tell their workers that at every point. I think reasons to like and dislike Sun and Microsoft are old and well-known, but a few years ago, I got so bored of explaining why I don't agree that Google is God's Gift to our communities that I posted a FAQ-ish page about it, which I update as I look at its new developments. Let's politely disagree, until Google fix the bugs which brought me to that view. Andrew Pollock's point about debian-legal is vague and maybe fair comment. It's not often a fun or popular thing. But "precious ego"? Ha! Yes, a guy who humiliates himself with cheap stunts for environmental protests is clearly very precious about his ego(!) (Sorry if that's rude, but I find it hilarious.) I don't mind people having different opinions, but it would be nice if their opinions about me were mostly based on reality, instead of misunderstandings. One fair point from Matt Palmer's post and also, I discovered eventually, from Antti-Juhani Kaijanaho's site, is that SPI's elections apparently are meant to be secret, as far as I can tell from the starts of Article Five and Article Seven of the SPI by-laws. I tend to value practice more than theory and the current voting practice is merely confidential, not secret. I think that's part of why I didn't understand the approach taken by some voters - they were treating it as a secret ballot. That's fine and now that I realise it's meant to be secret, I've suggested making it a secret ballot. (2007-08-08: 1 comment)

Neil Williams: Requesting adoption of glipper

RFA: glipper -- A clipboard manager for GNOME #436550.

Glipper is currently my package in Debian at 0.95.1-3 and that version
is written in C and uses a binary data file which has raised one bug
(#436078 - wishlist severity). It currently has no other bugs.

There is now a
new release
that closes this bug, my problem is that
v1.0 is a ground-up rewrite in Python! Essentially, glipper v1.0 is a
completely different package internally. (Previous translations have
also been lost.)

I have no python experience, no python packages and no ability to do
anything if (when) python code goes wrong. I don't want to have to
learn python just for glipper (don't have time).

So - I don't see what I can do except request adoption of glipper, it
just seems so weird to leave a package which is active while I am also
active.

Anyone fancy taking on glipper?

I don't think there's any point retaining the old C package - that code
is already dead upstream.

Currently, there is no RCS for the debian packaging for glipper - I was
using CDBS and the current watch file needs editing to look for a
tar.bz2 instead of the previous tar.gz.

There are two issues with migrating from 0.95.1 to 1.0:
  1. the ~/.glipper directory needs to be removed.

  2. Glipper v1.0 is also now GNOME only, support for other window managers
    has not been implemented in the python version.


Adrian von Bidder: Free Software Contributors

In answer to Russel's recent “tips for new contributors” posting, I give you the answer to the ultimate question about life, the universe and “How can I contribute?”: Find an area that you really care about. Or, rephrased in a less friendly way: “If you have to ask, don't.” And answering Russel's real question (one sentence to give to somebody who wants to contribute): “Know the community. Respect the people who are in the project much longer than you.” Knowing the technology isn't important - it's always possible to learn technology. But not knowing the community leads to frustration very quickly, and the new contributor will possibly not even have the chance of having the technical side of things even seriously looked at. (Of course, you may still come to the conclusion that you know more than “them” and that the people running the project right now are morons. If this sentiment persists, perhaps it's time to fork the project?) Ganneff's reply is also worth thinking on.

Andrew Pollock: [life] Oh, baby!

Today we went to see our new obstetrician. Ironically, he was our second preference (our current, third preference, who hasn't been all that endearing anyway, is going to be out on sabbatical when the baby's due). I think we'd already decided we liked him better before we even met him, but he did come across as a bit more calm and less alarmist. That said, he is currently of the opinion that the baby should be delivered at 36 weeks, which is September 14, which is a few weeks earlier than the date we were throwing around, of October 8 (Sarah's Mum and Aunty arrive on October 6). So that's going to make things interesting. We're seeing him again next week, which is after Sarah's had another echo-cardiogram to see if her aneurysm is still stable. The results of that will help firm up the delivery date. He also said that because the 28-32 week mark is when the heart's working the hardest, we're really in the danger zone now. It looks like we won't be going camping next week after all. The doctor didn't think being 6 hours by car away from home was a terribly good idea.

John Goerzen: Disasters happen

It's been one of those days.

It started with me forgetting my laptop bag at home. Then I had to work with an attorney on some things. He's a nice guy, and does a good job, but you know, it's not what I'd really like to spend my day doing.

Then in the middle of the afternoon, I hung up the phone and checked my email. About 50 messages from Samba telling me that processes with various PIDs had crashed unexpectedly. Uh-oh. I think we still have some 80ish people using that.

About a minute later, a coworker says, "John, I've been bad." "Is that why I just got 50 emails from Samba?" "No. Well, yes. Well, maybe. I don't know."

It turned out he was working on a restore from tape that, out of necessity, grabbed more data than he needed. He meant to type rm -r ./var but typed rm -r /var instead. Oops. He hit Ctrl-C halfway through, so /var was still there enough to send email but not enough for Samba (or, apparently, NFS) to work.

As he dashed off to pull yesterday's tapes from offsite storage, I prepared the restore and made a plan. We hadn't installed any software since yesterday, so I restored var to a temporary location, took the server down into single-user mode, overwrote the /var that still existed, and rebooted the Xen instance in question. Everything back to normal. Except, that is, for the potentially dozens of users that will require assistance running SCANPST.EXE because their Outlook PST, being the fragile heap of garbage that it is, will have somehow been corrupted by this little incident.

So, what did we learn from this?

Pete Nuttall: Playing the system

Neil McGovern recently blogged about the SPI election results - namely the outcomes using different election systems. While it is an interesting exersise, a point to note is that people know the rules for the elction and vote tactically. So to make the assumption that if SPI used a given system, then the outcome would be Neil's results is wrong. This point also applies to discussions of the use of secret ballots - changing this will change the election result.

Matthew Palmer: Just so I'm not accused of being a coward...

Since MJ Ray seems to think that anyone who doesn't vote for him but doesn't tell him why is a coward, I'm going to be up-front about it so I can't be accused of cowardice. Elections are all about everyone making their own decision, for their own reasons, in the hope that the aggregate of those decisions will produce a useful and workable result. (Whether that happens in reality is a whole other issue). The individual's decision is a statement of their opinion, nothing more. Adding confidentiality to the voting process is meant to remove any pressure from the voter to make a decision on any basis other than their own opinion. Complaints about it like this from a candidate is pretty weak:
There seem to be some 30 or 40 voters who really dislike me, but didn't tell me that straight, preferring to be silent then vote me down. Are you cowards, or what?
Given this outburst, I'm hardly surprised that people weren't keen on telling Mark upfront that they weren't going to vote for him. (As a disclaimer, I didn't vote in the SPI election, because I don't have a specific opinion on any of the candidiates' suitability for office on the SPI board.)

7 August 2007

Evan Prodromou: 19 Thermidor CCXV

I'm on the plane down from Vancouver to San Francisco this morning. My flight from Taipei hit Vancouver around 8PM last night, so I stayed at the Fairmont Hotel at the airport. It was definitely a special treat -- the Fairmont's pretty pricey -- but this trip has been really low-budget and I needed a lot of rest and recharge. I had a good room with a view of the airport and the city beyond. My flight over was uneventful -- sleep, eat, Spiderman 3 -- which was good since I'd had such a big last day in Taipei. In the morning, I'd gone out to see Taipei 101, which claims to be the tallest building in the world by some standards. I think there are lots of ways to slice the "tallest building" category -- the CN Tower has a strong claim, but that's only counting the huge antenna on top. And there's an unfinished tower in Dubai that's already close to, or taller than, Taipei 101. Regardless, Taipei 101 is a real interesting site. The elevators are the fastest in the world -- 38 seconds to go from floor 5 to floor 87. The windowed observation deck is interesting, and there's an outdoor deck two flights above it. The outdoor deck is racked by Taipei's scorching heat -- when I was there, it was 31C, up above the city's protective smog belt. The sun and empty sky make for an otherworldly experience. After 101, I took Taipei's local subway, the MRT, to the National Palace Museum. I've found the MRT easy to get around on -- most of the information was available in English as well as Chinese -- but I got a little lost looking for the museum. I was disappointed that the information booth in the Taiwan Main Station had so little tourism information, and all of it in Chinese. (Yeah, I forgot to print out the Wikitravel Taipei guide before leaving the hotel. My bad.) But I managed to wend my way out to Shilin Station and took a cab to the museum. It was worth the search. When the Chinese Nationalists left the mainland for Taiwan, they took with them many of the treasures of the Imperial Palace (much to the chagrin of the victorious Communists). These form the core of the museum's collection, and they're really quite amazing -- articles in bronze, ivory and gold from the Neolithic era to the modern day. While Western culture has gone through so many distinct and discontinuous phases -- Egypt and Mesopotamia, Greco-Roman, Medieval and Modern -- China's has varied much more smoothly and continuously. It's a little disconcerting to see artistic themes from 4000BC that are echoed in items for sale in the stores today. I had to get back to the Wikimania site -- by then almost empty -- to do a GChat conference with Niko. There were a passel of Wikimaniacs still around after the conference looking around Taiwan like I was, and after consulting Wikitravel we decided to go to Taipei's most famous restaurant, Din Something Something. It's got a short menu of delicious steamed dumplings -- pork, veggie, crab and shrimp. The shop's claim to fame is the elastic skin that keeps a pocket of hot broth inside the dumplings. Hey: if you do something well, why vary the menu? It was the best meal I've had in a long time. The dumplings themselves were incredibly good -- moist and rich with complex flavors. But the company was even better -- about 14 Wikimedians from all continents and walks of life, some of the most fascinating and important people on the planet. We were a big enough group to be stowed in our own party room, and with basket after basket of steamed dumplings piled onto the table, washed down with shared bottles of the ubiquitous Taiwan Beer, we had a crazy chaotic and fun time. I'm so glad I took an extra day after the conference to see a bit of the city. I think there's a lot more that I missed, but I'm glad that I got a taste. tags:

Wikimania 2008 Inevitably the conversation at Din Something Something turned to Wikimania 2008 and possible venues for it. Right now, the only serious bid is from Alexandria, Egypt, home of the Biblioteca Alexandrina. This is a modern reconstruction of the famous Library of Alexandria, centre of learning for the ancient world and repository of all of its knowledge. The bid is to use the sleek, glamourous conference centre attached to the Biblioteca -- offered to us free of charge. You couldn't put together a more powerful metaphor -- Wikimedia being itself a project to capture the world's knowledge and share it with all humanity. Having our event on the African continent would also send a great message about the Foundation's commitment to making free information accessible to the developing world. North Africa is definitely the most accessible part of the continent for Europeans and North Americans -- many of whom balked at the price and distance of travel to Taipei. The big problem with planning Wikimanias (Wikimaniae?) in the past has been the short time-frame. Typically bids for the event don't start until after the previous one, and the bidding process takes several months. By the time a venue is selected, there may be only 6-8 months of planning time available. For an international conference of several hundred people, this is a stressful, breakneck schedule. The idea was floated to do a little stutter-step and put Wikimania on a more long-term planning schedule. The event committee would short-circuit the bidding process this year, and declare Alexandria the site for Wikimania 2008 unless other groups insisted on bids for other cities. Then, bidding for Wikimania 2009 would start in September or October, with a decision made by the end of 2007. This would give 20 months for the Wikimania 2009 organizing team to prepare. Most importantly, they'd be able to shadow the 2008 team, learn how the job is done, attend the 2008 conference, and present about their venue for the next year. I think this is a really good idea. The Biblioteca conference centre staff will be able to provide us some professional services, making the shorter schedule (still about 11 months) a lot easier. There are some concerns about fairness of the process, or appearance of same, but my guess is that if the 2009 bid process starts soon after, people won't have a big beef. There are two major concerns with going to Alexandria, though. First is Egypt's worrying problem with human rights -- specifically gay rights. Homosexual Egyptian men are subject to arrest, and the laws are occasionally enforced. One foreigner was arrested in 2002. That's enough to put Egypt on a no-visit list with some gay-rights groups. Depressing as it is, I think it might be too much to hope for a venue in a country with an absolutely spotless human rights record. Maybe parts of Scandinavia...? There's a cruel calculus needed to evaluate which national human rights abuses can be reluctantly overlooked, and which are unacceptable. It's also clear that my personal judgment might be clouded, since this particular human rights issue is not one I would be directly targeted by. My hope is that an official statement by the Foundation would make it clear to the Egyptian government that this kind of policy is not conducive to attracting overseas business and tourism. The second concern is that Egypt and the Arab world in general have only embryonic local Wikimedian communities. While there are many people who contribute to Arabic Wikipedia, there is not a Wikimedia chapter in Egypt, nor are there regular meetups in the country or region. This might be a chicken-and-egg problem: choosing Alexandria would probably kick-start local groups. I hope that ar: Wikimedians pick up the mantle of leadership that the world Wikimedia community is offering them. tags:

Adrian von Bidder: Fun with virtualisation

Since I seem to be the last person these days who doesn't run his servers inside Xen, Vserver, kvm, lguest or whatever, I decided to finally evaluate Xen. Not having spare hardware and not wanting to really touch my main workhorse, I started with Qemu. Installing etch inside a Qemu (why can't qemu have working tun/tap setup scripts by default?), then xenifying this according to Ganneff's excellent slides, I was stopped while booting into the Xen kernel with a hard freeze in the boot process (Inside Qemu, so no harm done.) Talking to some people in #xen resulted in me disabling kqemu, and a few minutes later I had a working dom0. Debootstrap is slooooooowwww (well, inside a non-accelerated Qemu machine...)! So I decided to use cdebootstrap instead. Sadly, xen-create-image has debootstrap hardcoded, so I had to "ln -sf /usr/bin/cdebootstrap debootstrap". (I decided to do this when debootstrap was still calculating dependencies after several minutes.) After that, creating and booting a domU Just Worked(tm). Having a running Xen environment, I finally wanted to play around with live migration (mostly I was just curious how robust this Qemu + Xen setup is...) So, just clone the qemu disk and boot them both. Whereupon the two qemu machines have the same MAC address, hence networking is not reliable. Change the MAC of the second Xen dom0, curse udev for thinking that now the network interface should be eth1 (persistent device naming is a good thing, generally. I'm not sure there is a sane solution possible that can cover all/most cases. Computers with only one network interface might warrant some special logic ... Oh well.) Having restored the networking setup, enabling the relocation service in the Xen configuration is trivial. After thinking about using plain files on NFS and seeing a Novell tutorial which uses iSCSI, I decided that I should try AoE because it should be much simpler to set up. And by installing the 'vblade' package, it is indeed possible to have an AoE server running within a few minutes (the vbladed command doesn't take the -m option, though.) And the client side is just as simple, just install the aoetools package, and /dev/etherd is automagically created and lists all available devices. That's how SANs should work! (Note: I had the AoE devices in the dom0 and passed them to the domU. A next experiment would obviously be to pass AoE directly to the domU as root devices. Not sure what the implications would be, though.) Ok, after all this, I have two dom0 machines and a domU. Just for fun, I've installed xdaliclock inside the domU and started a live migration. Result: it works stable (modulo some scary kernel messages popping up when booting the domU. I didn't experience any crashes in this light test), xdaliclock stops for a mere 20s (yes, seconds, not milliseconds. Remember, this is two layers of virtualisation without hardware support.) Normal migration (pausing the domU), the migration takes roughly 2 min (both dom0 have 384M RAM assigned in Qemu, the domU has 128M in Xen, the host is a 3GHz P4 with 1G physical ram. There is some swapping going on (I use KDE, so some of the RAM is lost there. I also didn't stop beagle for this experiment.) The full live migration takes about twice as much time. But this said, if you're using Xen inside qemu, timing values are not what you're after... I was, frankly, astonished at how well this worked. Hmmm. I wonder, if I can stack some other virtualisation layer somewhere in there? Just to see how silly it might get.

Wouter Verhelst: Blog slightly fixed

I spent some time fixing some outstanding issues with my blog. The LiveJournal import on my blog had the wrong timestamp. I had some old ruby script that I'd written two years ago when I still believed ruby would someday become my language of choice (it didn't) which converted the livejournal XML exports into something that blosxom would grok, but it didn't work anymore. Apparently ruby's XML library API changed slightly between then and now. Read /usr/share/doc/libxml-ruby/README, updated the script, ran it again, and it worked. So now the blog items are dated on the date they were actually written, rather than 2005-02-17. Since a few weeks, I've been offering a myrss version of my blog feed, which contains a saner version of a link to the item (linking to the path that I wrote it in, rather than some date-based ugly stuff). Liferea choked on it, though, as did the feed validator. Turns out I managed to enter a few minor typos. Fixed those. Apparently the typos weren't of the magnitude that planet would choke on them, but still. So now my blog is slightly improved. Isn't that great. I still wonder why I have this blosxom-writing-php-scripts-with-home-grown-comment-system rather than, say, drupal, but that's for another day. OTOH, drupal doesn't allow me to write a blog entry using a simple svn commit, with magic commit hooks fixing everything. Let's keep things as they are.

Eddy Petrișor: tilting at windmills - the NSLU2 issues

It turns out I was playing Don Quijote when I was trying to fix the reset issues I had with my slug.

Of course, I was suspecting the USB rack for the issues, but the issues never showed up on the laptop... until now.

I decied to temporary use a USB stick for the FS and started copying files over to the stick. During the copying the rack disconnected and everything became more clear. I was tilting at the windmills all the time.

BTW, be smarter than myself and just change the UUID to mach the old one instead of regenerating the initrd and reflashing it:

tune2fs -U the_uuid_of_the_previous_root_partition /dev/sda1


Oh, next on the agenda will be to use my ipod mini as a hdd for the slug in order to prevent ruining the stick... And another thing, total silence is really nice, even if the rack was not that noisy.

Russell Coker: Blog Memes

A common pattern in blog communication is referred to as a Meme. Here is one example of the commonly used definition of the term as applied to blogs. One common factor that doesn’t seem to get directly mentioned much when people define the term (but which always seems to be mentioned in passing) is the idea of tagging people. So the definition of a meme as applied to blogs seems to be a silly question that you answer in a blog post and then request that some other bloggers (usually 5) answer as well. At the end of this post I have included the dictionary definition of the term (here is the Wikipedia definition). I believe that it is incorrect to call a question such as “which superhero do you most identify with” a meme. Instead I think that there is a Memeplex associated with such posts. One meme is that when someone “tags” you (requests that you answer a question) it should be considered an honour (someone in the blog-sphere likes you enough to ask you random questions in a public forum). Another meme is that such discussion is a good thing (although an increasing number of people in the more serious part of the blog-sphere oppose this). A final one that is apparent to me (I’m sure that there are others) is that so-called memes and lazyweb posts are the same thing (I believe this to be wrong). I believe that lazyweb posts if written about interesting topics can contribute significantly to the community knowledge base. I also believe that chain lazyweb posts (here is a link to the only such post I’ve made so far) can also contribute if created in a sensible manner. Chain posts that don’t require any thought or input from the person re-posting them (EG “please post this message to all your friends so that they can know of the terrible war/famine/earthquake/whatever in some foreign part of the world”) are of course quite useless (you can make a post of links once a month if you want to spread the news about such things). Now I agree that some amount of conversation among bloggers in a community that is personal and not directly related to the main topics of discussion is good for building the community. From Jargon File (4.4.4, 14 Aug 2003) [jargon]: meme
/meem/, n. [coined by analogy with gene’, by Richard Dawkins] An idea considered as a replicator , esp. with the connotation that memes parasitize people into propagating them much as viruses do. Used esp. in the phrase meme complex denoting a group of mutually supporting memes that form an organized belief system, such as a religion. This lexicon is an (epidemiological) vector of the hacker subculture’ meme complex; each entry might be considered a meme. However, meme is often misused to mean meme complex. Use of the term connotes acceptance of the idea that in humans (and presumably other tool- and language-using sophonts) cultural evolution by selection of adaptive ideas has superseded biological evolution by selection of hereditary traits. Hackers find this idea congenial for tolerably obvious reasons. PS This evening I had planned to go to a LUV meeting and see my friend Andy Fitzsimon (blog) give a talk about Inkscape (for which he is famous). I also had a day off work, so it was going to be a day of non-stop fun. But instead I got some sort of cold/flu, stayed in bed for much of the day, missed the meeting, and was late in my blog post. This sucks.

Next.

Previous.