Search Results: "tar"

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.

David Moreno Garza: Sapo verde soy yo

I’m 23 years old since 2 am on this August, 8th. Thanks for the congratulations messages I’ve received so far :-), resiak even sang happy birthday to me on IRC! Next year (August, 8th, 2008), 08-08-08, I will turn 24! 08+08+08! Something really bad is going to happen because of that :-) Probably that’s gonna be my really lucky year. But how en Earth can I be more lucky than what I am today? :-P In the meantime, I’ve invited my closest local friends to a bar this Friday to celebrate my birthday. Let the rum and tequila flow, baby! Yeah!

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.

MJ Ray: Two Answers for All Serious Free Software Contributors

etbe: Two Questions for All Serious Free Software Contributors asks:
"What do you think is the most important single-sentence of advice that you can offer to someone who wants to contribute to the free software community?"
He who does wins, so don't let the bastards grind you down.
"If you had the opportunity to say one sentence to someone who knows about computers and free software (EG they have used both Linux and Windows and done a small amount of programming) to convince them that they should join the free software team, what would it be?"
Imagine every bug you found could be fixed by you if you want, or a friend, or an enemy, or someone you hire, or the original developer, or whoever and that it's your choice who you ask to do it, with no veto from the copyright holder: that's free software. The second sentence is a bit long, but I found it hard to encapsulate the power of that freedom in one. I use the bug example rather than costs or anything, because I think that's what will be most attractive to someone who has done a bit of programming: the right answer to "why can't I fix this trivial 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.


Joerg Jaspert: Two answers

Russell: What do you think is the most important single-sentence of advice that you can offer to someone who wants to contribute to the free software community? Have a THICK skin. If you had the opportunity to say one sentence to someone who knows about computers and free software (EG they have used both Linux and Windows and done a small amount of programming) to convince them that they should join the free software team, what would it be? Goto free-software related events, get to know the others involved, have fun. Knowing each other in person and to see them every now and then gets you the best motivation to start/continue doing stuff.

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?

Adam Rosi-Kessel: Half Stars Considered Harmful

Fascinating and surprising (at least to me) observation on the Netflix Community Blog about user demand for half-star movie ratings:
So here s what I learned from months of testing this across the country: when we make the star options possible, we get fewer ratings. Significantly fewer ratings. We have argued these results internally for some time, and our best guess is that the complexity of doubling the number of choices from 5 to 10 deters many people from rating, so they just give up. ( 3 stars? No, 3 stars.. no 3 stars no oh forget it )

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.

Sergio Talens-Oliag: Lifestyle, Resignations and the Peter Principle

I'll be 0x24 (hex) or pow(6,2) (dec) years old next Sunday and it is becoming obvious that I need to change my lifestyle. On the physical side I'm sure that I have to loose between 20 and 30 Kg. if I don't want to have health problems in the future. The plan is to change my eating habits and do sport regularly. The basic idea is to do a diet seriously and keep part of the rules more or less forever (that's the habits change); the other important thing is to do some exercise, I've never liked sports too much, but I'm sure I can try to walk some days and swim others (I've been going once a week to the swimming pool during the last months and I'll be doing it twice a week starting this September). On the mental side, I need to reduce my obligations and care less about the work problems in and out of the office. To reduce my obligations and have more free time I decided a couple of months ago that I was going to leave the Uni, as it was taking away a lot of time that I can use for more important things; I notified it and after this September I won't be working for the Universitat de Val ncia anymore. Initially my idea was to keep my main work and use some hours each week to work on my PhD Thesis, but the truth is that I'm not interested anymore; I don't have anything specially interesting to say and my main motivation for getting a PhD has also disappeared (at some point I thought about becoming a full time University professor, but after three and a half years I've had enough, at least for a looong while). This leaves me with my work at the ITI as my main and only work, but after some months I'm seriously considering leaving it also. My main problem there is that I believe that I'm starting to suffer the Peter Principle or something similar; almost all my professional career I've been working as a technician, first as a programmer and sysadmin and lately as analyst and team leader or technical manager, but now, as it seems to happen always in the Spanish IT companies, I'm being forced to move to a pure project management work and, to be fair, I don't like it. I don't know if that means that I'll get to my level of incompetence, but if that is the case I think I'll have to try the Peter's Parry, that basically means to refuse a promotion (I've already done it asking to get a place under my theoretical level, although not on a convincing manner, it seems) or use the Creative Incompetence technique, that is, give the impression that you have already arrived to your incompetence level (probably it is too late to do that at my current place, but maybe on the next one I'll be able to do it). Maybe this is not the last level of the Peter Principle, as I'm sure that I can and will do this work (I'm thinking about moving, but I will not do it until I have a plan for the future, and that will probably mean a new job), but I'm also sure that I will never do it as well as I can do technical tasks because I don't have any real motivation to do it and while I plan to get the skills needed, they are not attractive to me. I understand that on the current IT world we need to have project managers, and I really hate bad managers, but that does not mean I like to become one, I prefer to be a team leader and work only on one or two projects at a time, instead of having more than five and not do real work in any of them; my main problem is that the challenges and tasks a manager has to do have nothing in common with the things I like from computer science and I'm too perfectionist to handle people that does not care about how things are done in a lazy way (a team leader with a couple of projects can handle technical people, when you are a manager with multiple projects you miss the day to day perspective and problematic people is more difficult to handle). Oh well, we will see how things evolve. The good thing is that I believe that one way or another I'll end up having a better life and, if I'm able to care less about my own work (and the one done by others) maybe I'll be able to stay at an acceptable level on the hierarchy without getting burn out and maybe some day I'll be able to work again on the things I like and keep my promises.

Miriam Ruiz: How to make a Debian package without using a helper reviewed

My old tutorial “How to make a Debian package without using a helper” seems to be getting a lot of clicks, so I’ve decided to upgrade it a bit and put it up to date. There are not many changes anyway, but just in case someone is interested in downloading it: roaddemo_1.0.1-2.dsc, roaddemo_1.0.1-2.diff.gz and roaddemo_1.0.1.orig.tar.gz are available.

Lars Wirzenius: Random thought: Productivity fear

Every time I do a "Getting Things Done" weekly review, I am amazed at how easy it is, and also how much it energizes me. Yet every time it is time to start one, I fear it, and procrastinate, sometimes for several weeks. Obviously I have a deep-set fear of being productive.

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.

Jeff Bailey: ... and the packers descended

Our place this morning was so calm and peaceful. Angie was cooking muffins. Then the packers showed up at 8am. It's 2.5 hours later, and we're now surrounded by boxes. In another 24 hours, the computers will be shut down, the cable modem returned, and the moving trucks will show up.

Two weeks ago when we left Montr al for visiting family and going to UbuntuLive, we knew that we only had a couple days left back here, but the reality is now setting in. From here we'll go to Opus, the Unitarian Universalist young adult conference at which we're two of the four cooks. From there, we head south, fetch a rental car, and start our one-way drive out to California.

Crazyness!

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.

Andrew McMillan: Really Simple CalDAV Store - August 2007 Status

Having taken time out to go to the other side of the world to attend DebConf 7 in Edinburgh, and then after spending some time with my family, I have been somewhat distracted from things CalDAV for a wee while now. There are signs that I will be able to put a few more evenings and weekends into it in coming months. Current Status With the release of 0.8.0 I believe it is quite a usable application for shared group calendars. We use it at Catalyst for about 80 staff and, while we're not heavy calendar users, it manages without any noticeable performance problems. There have been an impressive number of downloads from Sourceforge, as well as substantial downloads from my Debian repository, and I believe that the program is in tens, if not hundreds, of installations. Future Plans In the immediate future I want to get the basic framework for querying properties about the owner of a calendar or a set of calendars. This will be used by Mozilla soon during their configuration of a new CalDAV source, and I think that Apple iCal probably uses them already. This is partly done, but it's implementation has been slowed by the necessity to refactor the handling of the REPORT method in general to make the code more modular and readable, and to support queries and properties in a more general manner. The refactoring of the REPORT method handling is in place now, so moving on to the handling of DAV:principal objects should become fairly straightforward. I may end up with a fair bit of quiet, undistracted time over the coming weekend so if I can get in the 'zone', it may get done, and we can start rolling towards a release 0.9. Release 0.9 will have a new name. One from the cast of thousands that have been submitted to me so far, or one that I will hastily think up in between, but the next released version will not be called RSCDS any longer. The main goals for further into the future are: Interoperability I think that RSCDS does fairly well on the interoperability front. Unfortunately I have no access to the preview of OS 10.5, with it's native CalDAV client (though I have been told that it works with RSCDS). Likewise, other commercial CalDAV clients aren't available to me for testing either, so I have concentrated my efforts on supporting the featureset used by the various free CalDAV clients. My initial work focused around supporting Evolution, in particular, but with the recent effort put in by the Mozilla Calendar team the primary interoperability challenge is to enhance RSCDS to support their areas of development. If I could see how the OS 10.5 client behaves, too, I believe that would help identify a few points to extend, as well as suggesting some future directions. The best place to review interoperability would probably be at the CalConnect Roundtable 10 but I think that without some sponsorship for airfares I probably won't be able to make that. Maybe next time. Specifications Compliance As I read, and reread, the CalDAV (and DAV, and HTTP, and ...) RFCs the compliance with the various specifications improves. Recently I have put a lot of work into the calendar-query report, in particular, which means it now supports querying against arbitrary properties much more comprehensively. This is important because some of the client software is starting to do arbitrary queries also, and it is inevitable that queries for the classification of events, or the percentage completion of todo items will become more common. And now I notice that there is a new version of DAV in RFC4918, though not too many changes as far as I can see. The intent of this release is mostly to clarify, and slightly to extend, primarily in order to improve client interoperability. Coverage of Related Specifications In terms of general calendaring activities, the biggest hole in the CalDAV specification at present is standardisation around the location of other people's schedules. The current draft of the Scheduling Extensions to CalDAV appears to address that, and a lot more besides. I expect to start working on parts of this at some point, but perhaps not sooner than I see a client which starts using it, or when it is ratified, whichever occurs soonest. Documentation The documentation is OK. The wiki, in particular, is a reasonable resource for resolving problems (I believe), but it would be good to have some documentation of other things. One area that could do with enhancement is some documentation of how to check out a copy of the code, and how to provide patches back to me. Even better if other people can maintain their own trees which I could pull patches from, since we're using a distributed version control system (Git) to start with. Configuration The administration interface for RSCDS is OK, but could do with a few improvements to make it more usable. Really there are not a lot of reasons to be in the administrative interface, so these improvements should be relatively few, and relatively easy. This would be a good area for someone interested in helping out to become involved, because it does not entail reading large reams of RFCs, or watching tcpdumps scroll past for the debugging. Installation One thing that I have done right, I believe, was to provide the software from the beginning in a packaged form to make the installation easier. Although the software is packaged for Debian, however, it has not yet been uploaded to the archive because I have been waiting for the webapps-common package to enter Debian so I can use that for configuration. I think I have waited long enough though, so I will upload the next version to Debian for use by a wider audience. Security Security has always been a focus for me and I have had the code reviewed for any obvious security flaws. If any particular vulnerabilities are found they will be addressed with appropriate haste. Retrospective I've been working on this for a little over a year now, and I think I have largely met my goals for the project. It has certainly been an educational experience for me, and the effect of this work on other projects that I also participate in has also been valuable. Any new open-source project is always at risk of the developer losing energy and interest, but I believe this one has made it to a state where the bulk of the infrastructure effort has been done, and there are enough interesting challenges in the future to continue to keep me (at least) working on it into the future. The scope of this project is good, in that it is not at risk of expanding to take over the world. The intention behind this is simply to provide a back-end service for client software which should be very much Someone Else's Problem. In reality there have been times when I have had to get to grips with some of that client software in order to resolve problems, but those have by and large been good experiences.

MJ Ray: SPI Election Results

I wasn't elected to SPI's board. I didn't think I would be once I saw all the other candidates (I nominated before all declared), but it looks like I would have been elected with those votes under some other common systems. I think both first-past-the-post and alternative vote (also known as instant run-off voting, reportedly recommended by Robert's Rules for election-by-mail) would have resulted in this same board:
  1. Bdale Garbee
  2. David Graham
  3. Joshua D. Drake
  4. Martin 'Joey' Schulze
  5. Luk Claes
  6. MJ Ray
Instead, the results were:
  1. Bdale Garbee
  2. David Graham
  3. Luk Claes
  4. Joshua D. Drake
  5. Joerg Jaspert
  6. Martin Zobel-Helas
Nevertheless, well done to the new members. On one hand, I'm happier, because there's still two of my top four there and now I've less required work. On the other hand, I would have liked a crack at it myself and both boards are disappointing because there's no Ian Jackson. An interesting thing is how many times I appear in each position in voting lists: (5, 1, 2, 1, 9, 6, 6, 3, 3, 4, 2, 9, 37), or as a bar chart:
  1. st
  2. nd
  3. rd
  4. th
  5. th
  6. th
  7. th
  8. th
  9. th
  10. th
  11. th
  12. th
  13. th
A fairly acceptable middle-of-road candidate for most of it, but then a huge spike at the low end. Note that a majority of voters put me in positions 11-13. There wasn't much warning of that one coming during hustings. 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? More generally, is this type of Condorcet ever likely to elect someone who polarises views, or who many inexplicably dislike? What does this say for any plan to use a Condorcet for debian's social committee? Could majorities always prevent minority reps? Update: Neil McGovern posted a few comparisons of more complex systems (I only did the easy ones) and AJ posted STV results which completes the main systems, I think. It seems Condorcet-SPI wasn't as unusual as I first thought. Finally, as I understand it, turn-out was 25% of voting members (not the 25% of SPI members that some press reported). Why was turn-out so low? (2007-08-08: 1 pingback, 3 comments)

Andrew Pollock: [tech] Squid 2.6 redirector API change pain

So it seems that Squid changed its redirector API with 2.6. This pissed me off no end once I got to the bottom of a problem related to it at work last week. Squid's had redirector functionality since, oh, last century, and it's a really handy feature, if you want to intercept URLs that Squid's handling, and change them to something else. I've used it in a past life at an ISP to force people to use a local mirror for various things, regardless of where they think they want to go. So for the longest time, the API has been documented that an external program, which Squid will attach to the stdin and stdout of, will receive on stdin four words on a line, pertaining to the URL being requested: the IP address/FQDN of the client requesting it, the username of the user, if they've authenticated to the cache, and the HTTP method being used. All good. So we had an in-house redirector script, which used a regex (^(\S+) \S+ \S+ \S+)$) to determine if it should apply any logic to the URL at all, or just output a newline, meaning no redirection should occur. So along comes Squid 2.6, which changes that API. It now passes in five things on stdin. The changelog has an innocuous "Added to the redirectors interface the support for SSL client certificate" entry, so I presume on a good day, that's what is passed in as the fifth word instead of a hyphen. Anyway, our redirector script started not rewriting anything at all, which made some other stuff break spectacularly. It was most fun in one location, where we had four proxy servers behind a load balancer, and two were running Squid 2.5 and two were running Squid 2.6. Yay for non-deterministic behaviour. So once I'd tracked down the problem, I swore a lot, and changed the regex to be ^(\S+) \S+ \S+ \S+( \S+)?$ and proceeded to rant at anyone and everyone within earshot on how messed up this whole situation was. The thing that is irritating me the most is that this seems to have been a fairly poorly communicated change, as best I can determine. It happened between Squid.2.6.STABLE1 and Squid.2.6.STABLE2 (hmm, stable?). I mean, the FAQ hasn't even been updated. This clearly caught out other projects like jesred that provide generic extensible Squid redirectors, looking at #381984. I wonder if SquidGuard in Debian Etch is busted? So, whilst Squid 2.6 (the release that changed this behaviour anyway) is just over 12 months old, if you haven't upgraded yet, and you have custom redirectors, consider this rant a head's up.

Next.

Previous.