Search Results: "ron"

27 May 2006

Arnaud Fontaine: Google's summer of code has begun

I was really glad to be accepted for Google Summer of Code. My (accepted) proposal was on DWTT (Distribution Wide Tracker Tool) and CRMI (Collaborative Repository of Meta-Informations about source packages) mentored by Raphaël Hertzog. I have worked a bit on DWTT today and have written a webpage on the Debian wiki about the project. I'm currently pondering which is the best python framework to use : Having recently used ZODB (this means Zope Object DataBase) in a project, I think it's a great object database because it's very tightly integrated with Python, which makes it easy to use for programmers. ZODB is python-specific though, whereas SQLObject backends (for MySQL and Postgres) makes it language-independent. In the next weeks i will work on DWTT design. Until june 16, I have a lot of school work, which is why I won't have enough free time to work on the project, hence a slowdown in the project.

Simon Law: Debconf 6, Day 7


Funicular
Originally uploaded by sfllaw.
After the morning talks were over, [info]ze_dinosaur and I decided that Saturday afternoon should be devoted to fun. We rounded up Jesus, Anabelle, Ben and Nattie. And then we set off for the water park. You see, we were actually staying at a huge playground, except we never saw very much of it. Determined to see more, we hike over to the Tower, found the funicular and took a trip down. As we passed over a small wood, I instantly regretted leaving my camera at the hotel. I suppose, however, that I'd regret it more if my camera had taken a swim. We arrived at the bottom and found a flock of geese. This is where I really wanted my camera, because the goslings were oh-so-adorable. Nattie got some photographs while the mother goose hissed furiously at her. We left, found the front gates of the water park, and were told that it was closed. Well, we were quite disappointed. The others went back to the resort, but Ben, Nattie, and I refused to have our afternoon ruined. Instead, we found a washroom, got changed and waded off to the sulphur pools. There's a large spring underneath a big glass dome, which happens to spew out some rather foul smelling water. Much like rotten eggs, really. There, it fed into a series of swimming pools in which vacationers soaked.

Swimming
Originally uploaded by sfllaw.
We waded in to the very cold water and swam a while for a bit. We got used to the smell and temperature, and started having a marvellous time. Then we saw the waterfall. A man was standing beneath a small torrent of water, that beat about his neck and back. In order to stand in place, he hung on to a knotted rope which was tied to the retaining wall. After watching him for a bit, we three decided to give it a go. Swimming up to the fall was the most difficult part, then it was quite relaxing to have water pouring over you like that. I need a bathtub and shower like this, when I build a house. Soon after, we went back to the resort where we dove in the pool and swam a bit. We managed to corrupt Tore's mind and scar him forever. Just then, we were kicked out by the lifeguards because it was 18:00. The air was still scalding and they closed the pool. What are these people thinking? I took a nice shower and then a nap in the front lobby. Since lots of people were leaving on Sunday morning, this was the last night for them to party. So lots of people got quite drunk, including one poor fellow who passed out on the grass. I found a towel for him, so he wasn't so cold. Then, I took plenty of pictures of people, while simultaneously convincing them to wear hats. No really! There are many benefits to hats. And people look great when they have a hat on. I highly encourage you to get one yourself. I stayed up very, very late. Until about 5:00. Then, Eric and I couldn't take it any more and we went to bed.

Erich Schubert: Next generation of office suites

I have the impression that OpenOffice is still busy with cleaning up the code inherited (and e.g. porting to GTK2 and such things). Given the screenshots posted in the much respected Office UI blog by Jensen Harris, I think OpenOffice will run into trouble when Microsoft actually releases their new Office. Microsoft seems to have a really neat and productive UI there - there is only one thing really wrong with it: it's completely different than anything else people are used to (and people have learned to use). While there will obviously be migration issues, companies will probably delay switching to the new office to save licensing costs and such things, marketing people will be all crazy about the new features in there. You might remember the research with the aggressive title "PowerPoint makes you stupid"... actually this will become even more true with the new Office, I fear. It comes with default styles for common diagrams used in presentations, like a flow sequence or a circle sequence. While these aren't particularly smart things, they'll be presented even more prominently (because the gfx is so great), and the actual contents will probably be pushed back even further... Anyway, these new styles look really hip, so people will be eager to use them. And use them. And use them again. And use them really big (eventually forgetting about the contents behind them)... and OpenOffice can't keep up with that so far. Maybe OpenOffice needs a huge scale UI contest. Maybe with some abstraction scheme to be able to run different UIs on the same engine. OpenOffice in particular should try to become a technology leader, and not just try to copy Microsoft as much as possible... the UI changes in Impress are said to be pretty similar to what people expected when they think PowerPoint. There are good reasons to stick with the established UI standards (even when that might mean 'cloning' the UI) since that keeps migration costs low. But I think it's a pity OpenOffice can't show many large technological improvements to put more pressure on Microsoft. Ah, and yes, I guess many people at OOo are well aware of that, and like so many projects (commercial ones probably even more than FLOSS) they're just short on development resources...

26 May 2006

Colin Watson: Google Summer of Code project started (Ubuntu)

More on the Google Summer of Code: as well as the project I'm mentoring for Debian, I'm mentoring Evan Dandrea (no blog yet?), writing a migration assistant for Ubiquity. I haven't talked much about Ubiquity, mostly because I've been far too busy writing it. Ubuntu has needed an installer for its live CD for a while, partly because, well, loads of users want it, and partly because it will cut Canonical's costs quite a lot if we only have to send out half the number of CDs in shipit (apparently single-CD packaging is significantly cheaper than double-CD packaging). I'd been resisting doing something from scratch because I love d-i and I think it would be a really bad idea to end up maintaining two installer implementations from the ground up (live CDs are nice, but they don't cut it for everyone). So when I was given the task of doing a shiny live CD installer with a custom-designed UI, while I started with a more-or-less from-scratch implementation put together by Guadalinex (thanks!), I fairly quickly diverged from that and morphed it into something that uses d-i code for as much of the backend operation and logic as it sensibly can. I'd call it a sort of debconf frontend except that its design is almost opposite to how a debconf frontend should work, in that it's highly specialised to react to particular question names. This had a lot of advantages in terms of being fairly quick to write, although in the long term I think I might prefer something closer to cdebconf plugins for the job; we'll see how things turn out. Evan wanted to write an extension to this to automatically migrate settings and documents from an existing Windows installation, which I think would be an absolutely excellent thing to have: automatic migration is a real killer feature in an installer. In fact, d-i already has a start at this, namely os-prober, which in conjunction with some bootloader installer code magically sets up boot menu entries for other operating systems on your disk. So, I suggested to Evan that he might want to put most of the clever logic in a udeb, so that it can be used in d-i too, and to my relief he seemed quite enthused by the idea. He's starting on the preliminary work now and I look forward to seeing his progress. Best of luck, Evan!

Kenshi Muto: Backed from Debconf6 and Canada

I backed home yesterday. After I arrived at home, I went to buy foods to cook, checked bills and snail mails, washed my clothes, took a bath, saw through a bunch of e-mails and gave up to reply to them, met my partner again, cooked for dinner, and slept well. Fortunately I haven't a jet lug at this time. Because I tripped China for 1 week before Debconf6, I was very tired at the beginning of Debconf. Furthermore mixing Spanish/English/Japanese caused me a mental fatigue. I felt better as time went by. Well, I would more enjoy if I wasn't so tired, but I enjoyed BOF, talks, swimming, foods, travelling and so on during Debconf6. 'Gracias, Debconf staff and attendees.' Mexico was an interesting place for me, so I'd like to visit there again in the future with my partner. After Debconf, we - Nobuhiro, Yukiharu, and me - stayed Toronto for 2 days. It was very nice time to see Niagara falls and to walk through Toronto downtown. I uploaded the photos: Debconf6 pictures, Canada picutures. I apologize I couldn't work well for Debian, especially for CUPS during the conference by a network problem. CUPS 1.2.1 is already released and I'm working for it.

Steve Kemp: See if you can spot this one?

Xen-tools now correctly installs CentOS4 installations, complete with OpenSSH access. I’ve not fiddled around with rpmstrap enough to cache intelligently, but otherwise it works. (What this means is that each new installation re-fetches each .rpm package from the network, rather than caching them locally.) This new work does bring my “design decision” into focus though. Originally xen-create-image was a simple system which did two things:
  1. Install a clean version of sid/sarge/etch using debootstrap.
  2. Run a series of shell scripts aftwarwards to customize the new environment install networking, and install openssh. The “hook scripts”.
Hooks were implemented as a directory of shell scripts run in order, much like you’d expect from run-parts. Simple? Neat? Yes. And no. Because each script was based around the idea of tweaking Debian they had a lot of Debian-specific knowlege in them, and so they didn’t do the right thing for CentOS4. There are two (or more!) solutions to this problem:
  1. Have per-distribution hooks: hook.d/debian, hook.d/centos4, etc.
  2. Have each script decide which environment it has and do the right thing.
The first has the advantage that it is simple to understand and adding additional distributions becomes simpler to approach. The second avoids proliferation, and seems neater to me. Anyway the decision is made for the moment to use this approach. I could be swayed the other direction when it comes to time to setup SuSE, Mandriva, etc. However in all honesty I don’t actually expect to do that work myself. If you need those distros you can help, capishe? Now to backport rpmstrap to Sarge, and make a new release…

25 May 2006

Wouter Verhelst: Edge flipping.

So, in my previous blog post, I mentioned that Enlightenment, bug-ridden as it is, is the only application I've seen thus far that implements edge flipping the right way. Since it's been a long time since I last used the only windowmanager that actually implements it the right way, I've been able to give it quite some thought by now. Here's my take at it: The central thing to remember is that the edge flipping interface will trigger accidentally. No matter how well you implement your interface, sometimes a user will accidentally move his or her mouse, or he/she will want to click somethin near the edge of the screen and touch it. Therefore, there are two things an implementer should do:
  1. Make every effort to avoid accidental edge flipping where possible, and
  2. Make it as easy as possible for the user to correct an accidental triggering of the interface.
The best way is to make sure your interface has the following characteristics: Getting the above two right will ensure that accidental edge flipping is reduced to a minimum. This is the first step, and one that only Enlightenment and IceWM got right. The final step, however, is something that IceWM does not get right; and this is what makes Enlightenment's edge flipping implementation such a natural thing to do: Some people will find that last point evil, I'm sure. I'll admit it took me a while to get accustomed to it as well. But it's the only natural thing to do. You should think of your virtual workspaces as one large desktop; if you're using four workspaces next to eachother, that means one large desktop four workspaces wide. When you move the mouse one quarter to the left, it's normal that it ends up about the same place on that same desktop. In other words, warp the mouse. Additionally, the mouse warping will have the effect that it makes recovery from accidental edge flipping easy and fast. If the mouse stays where it was after edge flipping (as in the case of brightside and IceWM), then if I accidentally hit my mouse, by the time I've moved my arm towards the mouse and started moving it back, I've moved away three workspaces from where I was already (because of the second bullet point in this post). If, however, the mouse does warp to the opposite side of the screen (i.e., the side where it was coming from), then going back to where you were is just a matter of moving the mouse a few millimeters in the opposite direction. Very easy to accomplish, that... Oh, and finally, you also shouldn't segfault at random. Again something that brightside did not get right when I used it—did I mention that brightside is crap? Well, I did now. Hopefully it's changed for the better in the mean time. Back in my Enlightenment days, I used workspaces a lot, because Enlightenment made it so natural with its excellent edge flipping implementation, and with the help of the pagers which would always, at any time, give me a snapshot of all my workspaces, helping me to remember where this or that application was running. IceWM doesn't replace that, but it sure gets close.

Uwe Hermann: OS Install Experiences - Part 2: SUSE Linux


Note: This article is part of my OS Install Experiences series.
Next up: a SUSE 10.1 install. It's been a few years since I touched a SUSE distribution (it was something like SUSE Linux 5.3 or so), a lot has happened since then... Here's a rough sketch of the installation and a few superficial remarks and facts related to security. Install
  1. First, I downloaded a SUSE 10.1 CD image, burned it on a CD, and booted from that.
  2. The installer that showed up is graphical, and you can choose between a normal installation, booting a rescue system, or running a memory test (uses memtest86, I presume).
  3. While the installer runs it merely shows a rotating logo, but you can switch to other consoles (ALT+F1, ALT+F3, ALT+F4) for watching log messages passing by.
  4. You can choose the language used in the installer, later also your timezone and keyboard layout. You can also check the installation medium, which verifies the checksum of the CD, I guess.
  5. Next, you'll be asked to accept a license agreement (yeeaah, whatever).
  6. Your hardware will be automatically detected (worked quite well for me), and after that you can choose between a new install or a system upgrade.
  7. As for the desktop, you can use GNOME, KDE, text-mode (no desktop), or a "minimal graphical system" (it turns out that means fvwm, at least that's what I think).
  8. The graphical partitioning tool feels a bit awkward at first, I needed several tries until I figured out how to make it use the layout I wanted it to. The default file system suggested by the tool is ReiserFS.
  9. There's an explicit option which lets you choose the default run-level for the system (run-level 5 is pre-configured).
  10. The bootloader, GRUB, recognized the other partitions (Debian stable + unstable), added an entry for SUSE Linux, and created a working setup. Nice, although more control over the process (e.g. naming of the boot options) would be nice.
  11. Reboot.
  12. I'm asked to insert CDs 2 and 3, which I don't have (or want), as I only burned CD 1. Clicking "abort" a few times does the trick, and I can continue by choosing a hostname and domain name for the box (hydra + local.domain).
  13. Now I must enter the root password. Very nice: I have the choice between DES, MD5, or Blowfish (SUSE default) for the hashing/encryption of user passwords.
  14. Afterwards, the network is configured (automatically, via DHCP). You can enable a firewall at this point, and enable/disable access to the ssh port explicitly. It's also possible to enable "VNC remote administration" (default: off), or configure a proxy.
  15. Authentication methods for users, available from the installer: local (/etc/passwd), LDAP, NIS, Windows Domain.
  16. When adding a new user, there are some options. Per default, the user is in the groups "users" (no per-user groups, it seems), "dialout" and "video", but that can be configured. Password expiration is disabled. The default shell is bash.
  17. And now... another registration message (in the release notes, actually). May I quote (from my head): The registration procedure transfers zmd's unique device identifier to Novell's registration web service. The information sent may also include OS, version, architecture, and the output of uname and hwinfo, according to that text. More on that later, maybe...
  18. Of course, SUSE Linux comes with SUSE's/Novell's AppArmor enabled by default, but I haven't looked into it, yet.
  19. Now some problems appeared. More hardware discovery took place, it seems, then the screen turned black (with only a non-blinking cursor in the upper left), no reaction to any input -> I performed a hard reboot.
  20. After booting, I'm dropped into fvwm (although I chose GNOME in the installer), the reason probably being the forced reboot. After looking around a bit in the menus and stuff, I wanted to start sax2 (to find out what it does), but the screen turned black again -> another hard reboot. Could it be that I don't have enough RAM for this (256 MB)?
  21. Anyways, at this point I lost interest in playing with the system any further, and gathered the below information for comparison reasons...
Security That's it. Comments, suggestions, flames?

Wouter Verhelst: IceWM

I had been an Enlightenment user for a long time—halfway the Summer of 2000 up to the early fall of 2004—before someone finally decided to pick up the pieces where they were left somewhere around 2000 and restart its development. Unfortunately, that also meant causing #219925, which was irritating me more and more each day. Eventually, in the early fall of 2004 (almost a year after I filed that bug), I gave up and started looking for something else. The problem, of course, was that I'd grown so accustomed to using Enlightenment and its way of doing things that I felt at a loss. I wanted to be able to move windows above the upper edge of my screen again. I needed focus-follows-mouse. I was having a hard time without edge-flipping. Eventually I found that there was functionality for all of the above, but it wasn't flawless. Especially not the edge flipping—GNOME implements that in a truly horrible way1. Not to mention the fact that brightside, the application which implements edge-flipping for GNOME, segfaulted on me an annoyingly high number of times, sometimes even taking away my entire session with it. Even Enlightenment never did that; it would just misbehave instead. Apart from that, of course GNOME also had some extra annoyances that I didn't get rid of. The fact that it insists on mucking with my keyboard settings, to name just one example. Even so, I used it for about nine months. Then, slightly after DebConf5 in Helsinki, I realized what the true horror of GNOME is: not the fact that they hide away features or try to make the desktop void of superfluous options; the fact that they remove features that are critical to some of its users. I know I was horrified to find out that something I really used a lot had been removed in that new release. I kept using it for three more months before I threw in the towel and tried something totally different. Ion3. After coming from the mostly mouse-oriented interfaces that GNOME and Enlightenment were, ion3 was truly different. I liked it at first; it was a welcome change from what I'd previously been doing. Eventually, though, I found that the ion way of doing things just wasn't my way. The fact that, by default, it puts new windows right in front of the window you're working on was rather offputting. Any serious attempt at configuring the thing involves learning lua which, though supposedly not hard to do, is not something I ever found the time for. In the end, I discovered that I disliked working with ion, as I often felt that it gave me a fragmented and tunneled view on the world, and that it was working with me instead of the other way around. In short, it was getting the fun out of computing for me. Which wasn't good, at all. So that's when I started looking for something else again. When I'd made the decision to move way from ion3, I didn't want to keep using that "until I'd found something else"; instead, I quickly installed IceWM instead—which I still knew from back when I had a Yopy YP3000—and used that until I had found something better. Little did I know the beaty of IceWM. I've decided, by now, that it does all I need, and more: By default, it tries the best it can to put a window on your screen so that it overlaps with as little other windows as possible. I can have it not focus a new window by default. I does focus-follows-mouse, if enabled. It even does edge-flipping. Of course it's not perfect—the edge-flipping, though not as horrible as the GNOME implementation, can still use some improvement. As if to prove my point, I accidentally closed the window in which I was writing this very post before it had been written to disk, the cause of which could be described as an interface problem in IceWM (though it's more likely an example of PEBMAC (Problem Exists Between Mouse And Chair). But, all in all, using IceWM feels like finally coming home. Thanks, Marko and Mathias, for a truly wonderful piece of software. 1 I know that there are a lot of people who dislike edge-flipping. I am 99% sure that this is because they've never seen it implemented right. Edge-flipping is great, if done right; it's nightmare if done wrong. GNOME does it horribly wrong. IceWM does it better, though not perfect. The implementation in Enlightenment is perfect. I'll discuss the details in another post.

Enrico Zini: Creating a trusted pbuilder environment

I figured out that pbuilder ignores secure apt's verification warnings, and was deeply disappointed. One cannot tell everyone that pbuilder is the preferred build environment when pbuilder is happily using untrusted debs to build. After some digging, however, I found out that it's fairly easy to build a trusted pbuilder environment:
pbuilder create --debootstrap debootstrap --debootstrapopts --keyring=/etc/apt/trusted.gpg
This tells pbuilder to tell debootstrap to check packages using the default apt keyring. In turn, debootstrap will install the keyring in /etc/apt/ in the chroot, and so that the rest of the apt-installing done inside the chroot will verify the packages. Note that I also had to force pbuilder to use debootstrap instead of cdebootstrap, because cdebootstrap doesn't support --keyring. Also, --keyring is not (yet) documented in debootstrap's manpage, although you can find it in debootstrap --help. Note: I put this tip on the Debian Wiki at: http://wiki.debian.org/SecurePbuilder, and that version may in the future become more up to date that this blog entry. Note: pbuilder will still install untrusted packages, although it will warn about it. Check your pbuilder output!

Simon Law: Debconf 6, Day 5


Gorditas
Originally uploaded by sfllaw.
After a very tasty breakfast of gorditas in the market, I sat through talks all of Thursday morning, which were all quite good. They were visionary talks, talks about where Debian was going to go, and what we can do to get it there. After a brief lunch, we returned for the talk of debugging debian-installer. I've been lugging around my laptop, jamaica, through the entire conference. It's an old A20m, which means that it's a rather bulky looking thing, that is quite heavy. What makes it noticable is that it's been epoxied together, after having been dropped one too many times. People marvel that GNOME runs reasonably on it. Anyway, during the talks, my wireless card decided it didn't want to work any more. Pulling it out and letting it cool down seemed to get it responsible again. Strange. After the afternoon talk on how to find security problems within Debian, I went back to the hotel to change. You see, we were going to a Formal Dinner. I had not packed for a formal dinner, thinking that all functions would be casual at the very most. Still, I pulled out a pair of pressed slacks, an ironed shirt and a colourful tie. When I left my room, it became apparent that Formal actually meant "clothes without any holes".

Mariachi band
Originally uploaded by sfllaw.
We all packed into the coach buses from yesterday and drove into town. This was actually quite difficult for the drivers, because the streets were very narrow and the buses were incapable of turning around corners. I think it took us fifteen minutes to park, which mostly consisted of doing a 30-point turn. We disembarked and walked into a large building. Two of the walls were made of stone, the rest were made of stucco. There was a small stage presiding over a floor full of fold-up tables which were arranged in a Debianesque spiral. I decided that I was going to be at the nexus of activity, so I sat down at the central table and reserved a seat for AJ. As people seated themselves and started talking, there was a sudden commotion. Holger was running towards AJ with a plastic crown, deposited it unceremoniously on his head, and continued sprinting past. This drew applause and photographs, along some cheering of "Long Live the DPL!" AJ looked decidedly uncomfortable. It's probably for the best that Debian isn't a monarchy.

Indoor waterfall
Originally uploaded by sfllaw.
Our evening got more and more interesting. A mariachi band came in the door and started playing. Soon after they started singing, rain began to fall. This made lovely sounds on the tin roof above, which made me a little sleepy. Right about now, a brawl sprang up near the front door. There was some shoving involved and quite a bit of yelling. Soon, the combatants were separated and some of them left the building in anger. All this time, the musicians were playing louder and louder. As the music crescendoed, the rain fell harder and the wind blew stronger, until we had to close up the shutters to keep the water from blowing in. And the band kept trying to play over the rain. Then, slowly, the roof began to spring leaks. We were lining up for food then, and by the time I got to the buffet table, water was pouring into the trays. I managed to get something reasonably dry and scurried back to my seat. Which was wet. After I got some food inside of me, I experience the final act that capped our evening. We were chatting a bit about the strange weather we were having indoors when suddenly, water started cascading down one of the walls. It made a tremendous roar and the floor of the building quickly flooded. As I was photographing the events, the lights suddenly went out with a pop. We were plunged into darkness. I made my way back to my seat and someone eventually found the fusebox. The lights were restored, one by one, and it was soon time to leave. I don't know how the organizers of next year's Debconf are going to be able to top this: ceremony, live music, fisticuffs over a woman, an indoor waterfall, and drama. This was a night we're all going to remember.

Martin F. Krafft: Post-Debconf

One thing that never really came to my mind during Debconf6 in Oaxtepec, Mexico, was blogging about what went on. In part, that's because I never had a minute to spare, plenty of other people were blogging about the event on the planet, and definitely also because I developed a dislike to play-by-play blogging, which I certainly do not like to read for my part. But now, sitting in Oaxaca in the Hostel Pochon (which has free wireless, imagine that), I feel like at least jotting down some of the highlights. My favourite non-Debian related happening must have been the descent to Mexico City airport. I am willing to bet that our pilots either had too much to drink or way too much fun, because we literally zig-zagged across this amazing city. It's about 2200 metres above sea level and our inflight information system noted our altitude at 3500m for at least 20 minutes, so glued to the window, I felt in a miniature world, hovering above a city that extends to all sides however far the eyes could see (I conclude that in all miniature worlds I've seen so far, such as the Eisenbahnmuseum Hamburg and Swiss Miniature, trains and cars are generally moving too fast). The population of "la Ciudad de Mexico" (which the locals just call "Mexico") is estimated to be somewhere between 20 and 24 million, which makes it the largest city in the world, and it was not hard to believe that during the descent (and afterwards). I arrived at Oaxtepec, a government-run vacational complex, some three or four hours after touchdown and didn't last very long until the jetlag took me to bed. That was Saturday night. With Sunday morning, the official Debconf conference had started and was to last for seven days. In general, that meant talks and BoF sessions throughout the day, loads of hacking and socialising in between, food, and drinks with more socialising in the evening (and throughout the night in some cases). I really enjoyed seeing many of the folks I had met at last year's conference in Helsinki, while some others' absence was equally prevalent. I spent most of the week hanging out with Biella Coleman, Micah Anderson, Sean Finney, Clint Adams, and a bunch of others, I also managed to make the real-life acquaintance of some people I had known online for a long time. In retrospect though, I should have spent less time with the regular clique (with whom I was to go to the post-Debconf trip anyway) and spent more time getting to know more of the attendants. The vacational complex was interesting, and unlike many others, I didn't get annoyed by the long distances between presentation room, my accomodation, the hacklab, and the place where we were served edible lunches and dinners. Rather, I enjoyed walking with others, engaged in discussions on some of the more prevalent topics filling my life with Debian (such as version control, low-level Debian tools, security issues, and social challenges). The only nuisance was the long walk to the nearby town and its market, from where I would get most of my food and drink throughout the week -- but even that walk I rarely had to manage alone. The massive pool (with a ten metre diving board) that lay in the middle of it all didn't really attract me that much, but then again I've never been much of a pool person. In the interest of various people worrying about my safety in Mexico, as well as some of my clients, I purchased a Mexican prepaid SIM card for my cellphone and linked up with the world (after two attempts and an accumulated 2.5 hour wait). The fun was only short though, when I found out that in Mexico, phone charges are ridiculously expensive, and receiving calls on a mobile phone costs exactly the same as making them. At USD 1/Minute to and from Europe, I ended up limiting my air time to a minimum. I spent most of the first couple days getting mdadm back into shape, bug triaging and uploading a new upstream to experimental, except for Monday, which I spent together with Joey Hess, Micah, and Biella trying to recover files from her wrecked filesystem, which we managed in the end using a simple fsck to at least recover her presentation. I'd be sitting on the terrace in front of the "hacklab" where people kept passing by, so my work certainly wasn't focused and without interruptions, but in the end I was still satisfied with the end result. And in the evenings, it was usually the same terrace, sampling the local beer, enjoying cheese from all over the world at the cheese party on Tuesday night, trying liquors from other parts of the globe, and talking and joking and meeting great people (I truly love the Debian crowd). Out of the large assortment of talks available, I attended several but found that front-up presentations aren't my thing and I would have to let the topic simmer a bit (along with some research) before delivering my questions to the speakers outside of the talk (where I finally got some interesting answers to long-standing questions). Thanks to the awesome work by our video team, which recorded every single presentation to tape, streaming it live and also intending to publish it on a post-conference DVD, I found myself often listening in on talks I wouldn't have gone to, while hacking away on said porch. Noticing, however, that many talk slots were left unfilled at the start of the conference (they did quickly fill with impromptu presentations and BoF sessions once the inertia of the event picked up), I was a little annoyed that my proposal was turned down in the first phase of selection. Wednesday was the day of the day trip. Against my recommendations of an early departure, we left the site at 11:30 with six busses (remarkably on time), heading for Xochicalco for a rather boring tour of the museum, and a vastly more interesting, two hour stroll (in the midday sun) around the actual archeological site, which was quite impressive despite mostly being artificially built or rebuilt by the government. We went on for an excellent buffet-style lunch (which was amazingly well organised), and then headed on for Cuernevaca, a small, romantic town where we had only an hour to spend before heading back home (who recommended starting the day earlier?). When we finally made it back to the conference, most of us were just tired and the evening wasn't as wild as some of the other ones during the week. Come Thursday, my mission was to attack the thinkpad packages, which make Debian on IBM laptops a lot more of a pleasure to use. Unfortunately, I didn't get anywhere (yet) with that work, simply because most of my time was spent battling the weird hacks that make up module-assistant, which actually makes it a lot harder for developers to provide kernel module packages (while really improving the end-user's experience). But of course, there was a positive twist to this issue, as I would now leave my screen in frustration much more frequently and socialise with the others. For the evening, the organisers had prepared the "formal dinner" (which isn't so formal at all). A bunch of busses took us to a nearby shed, where we found all tables arranged in a massive swirl, and when we were all seated, a Mariachi band entered, at the same time as the rain outside picked up -- I thought one of the Mariachis was playing the snare drum but as the rain grew stronger, I concluded it must instead be the drops on the metal roof causing the noise. Generally in love with rain, I made my way to the door while others lined up to fetch dinner and stood in awe for a bunch of minutes at the sight of the marble-sized drops descending from the sky. ... when suddenly I saw one of Debian's troublemakers, Jonathan/Ted Walther, running at me, chased by three developers and found myself amidst their altercation before I could do anything. People screaming, one reaching over my shoulder to push Ted, it was all too much. I told everyone to calm down, to which Jonathan/Ted reacted, vigorously shaking and foaming, with a "get out of my fucking way, you fucking Nazi" and I knew that stuff had gone wrong. I withdrew, and in an attempt to find out what had happened managed to piss off one of the three involved developers, who'd then later refuse to hear me out for an explanation. All that really left me in a depressed state mainly because I simply hadn't expected Debian developers getting physical at each other, and this time it was Erinn Clark who consoled me and turned the night around for the better. I still had no appetite and took the first bus home, sent an apologetic email to the offended developer (who never acknowledged receipt but seemed to have forgotten the incident the next day), and enjoyed beers while the others kept returning to the hacklab. Apparently, people were quite aware of my (passive) involvement during the incident, so I was bombarded with plenty questions, most of which I refused to answer for lack of knowledge of the actual facts. Still, when I saw one girl in another altercation with Jonathan/Ted later that night in response to severe offences he published on his blog, which led her to come close to tears, I decided it was time to pull him off the planet. He re-added himself shortly afterwards by "fixing a typo" (according to the CVS changelog), but by that time, I couldn't care less no more and simply resumed the discussions, which eventually turned into topics of life, intelligence, and the bottom-up vs. top-down debate. I am a strong supporter of bottom-up (as many of you know), and I somehow regret the way I approached the discussion, because in retrospect I see myself as somewhat arrogant during it; fortunately, noone seemed to hold it against me the next day. Throughout the entire week, I built up a reputation of the guy that needs no sleep: staying up until the early morning hours, yet rarely missing any of the first talks at 10 in the morning, and even joining with people for breakfast at the market before. Friday morning, however, I just couldn't get up. We talked until six in the morning, and when my eyelids finally moved after I dropped into bed, it was already noon and I dragged myself to the next talk. after which I simply returned to the hacklab and developed more of my dislike towards module-assistant, before the call for the official Debconf6 group picture rescued me (and those around me). The keysigning party followed and I made the mistake to offer to coordinate it (picking up where Anibal's great preparation left off), without really running the process through my head before. Standing up on the diving tower and screaming to the crowd of 140 participants, it was in part due to Moray Allen's comments that the party went more or less without any complications; I did get to conduct another experiment though. During the keysigning, Mark Shuttleworth invited a bunch of us to join him for dinner to discuss the Debian-Ubuntu situation (no bribes involved; we paid for ourselves). I'll have more on this in a separate post when it's ready. The discussion continued after we arrived back at the hacklab, and once again, I didn't go to bed at a civilised hour... ... but I did get up in time for Biella's talk, during which she employed very effective techniques to get me to actually pay attention (which I would have done anyway): she required my laptop for the presentation. Again, the talk didn't do much to me (which is not Biella's fault), but I am certainly interested in reading the relevant parts of her dissertation. At the same time, however, it made me realise how far from reality the academic world is: big words and complicated concepts just don't count when it comes to getting your hands dirty, and I will try my best not to go down that route when my own dissertation gets more serious. Two other memorable events happened on Saturday: the fun group photos (I was determined to get the participants to line up in a swirl in the pool, and partly succeeded), and the last-night-party on the porch of the hacklab, which was mighty fun, in part because we had speakers blasting tunes for the first time that week (thanks to the dance BoF the night before), and Ryan Murray was playing some of the truly excellent mixes of a close friend of his, which are available from mux.ca. I didn't sleep that night. And then Sunday had arrived, the sad last day of a great conference. I would like to thank all the organisers and helpers for making this event possible! I know some of you had some reservations before and during the event, but in the end it's the result that counts, and I was only one of many who were absolutely satisfied by the week. A great big THANK YOU to you! Following the last bits of socialising and copying Biella's harddrive image to Micah's drive for later rescue of some of her precious videos, we were off to Mexico city for the vacational part of the trip. Some of us went by bus, Vagrant and myself hopped onto the bus to assist one of our developers with his wheelchair at the airport. When the group reconvened in front of our hotel for the night in the centre of Mexico city, the vacation had started (blog post forthcoming sometime...)

Peter Van Eynde: s3cr3t blog message

Tonight we meet some others in front of the Santo Domingo church/museum at 22:00 in Oaxaca.

Jeff Bailey: I just love the smell of latex ...

... paint.

What were you thinking of? =)

I went to the Canonical support office today to attend while the Bell technician installed our ADSL line. It's always neat being on construction sites and watching the trades interact. Onsite there were some painters, cabinet makers, phone, network, and air conditioning. The place is looking quite nice.

As always in construction, nothing's perfect. The only thing horribly wrong so far is that part of the ceiling fell down because whoever put it up hadn't bothered to anchor it to the cement. Repairs will get made, and the guy it hit only got minor scrapes. In another few days, they'll all be finished, the carpets will be cleaned, and the space will be ready for us to move in.

It's going to be weird having an office to attend to again.

Next office steps: Get insurance, hire junior support techs.

Axel Beckert: LinuxTag 2006 Slides are online now

Just uploaded the slides to my two LinuxTag talks: I’ll hold the KISS talk also at FrOSCon, the Free and Open Source Software Conference in the Rhein Sieg Area near Cologne at the end of June. There I’ll also hold my two command line talks: one talk for beginners and one workshop for advanced shell users.

Alex de Landgraaf: Debtags SoC project starts

Still amazed I actually got my proposal accepted. Considering I started writing it 3 hours before the (extended) deadline it was closer than that I'd like to, but lets hope the summer is long and I'll be able to do a lot of Debtags-hacking without too many close calls :) As for most of my recent projects, I've started a Trac environment and SVN repository. Doesn't contain much now besides my SoC proposal and a few links, but I'll get up to speed soon enough...

24 May 2006

Neil McGovern: Wings and Roundabouts

Well, I've finally got back from DebConf6 and am quite nackered, especially considering I've just done a full day at work.

I could amuse you with the usual 'lists-of-memorable-dc6-events', or a 'review-of-each-day', or even a 'bits-from-the-orga-team', but there's pleanty of other posts on planet.d.o about that, so instead, I'll recount my experiences of the return trip, starting in Oaxtepec.

I'm also putting up all my photos, but it'll take a while. They'll be appearing over the next few days at my Fotopic site.

I wake up fairly early-ish (10am. It's early for me, ok? I'm not German :P) and pack my suitcase. I take the padlock keys out of the case and lock it. Except I got the wrong keys. So, the keys are now inside the locked case. Fortunately, I'd already taken everything out of the case I'd needed and put it in my rucksack.

Next, it comes to time to check out. I find out that we need out room checking to ensure that we haven't stolen a wall or ceiling or something. One of the cleaners has a look around and spots a missing lampshade. We (me + Fil Hands) try to explain in broken Spanish that it was missing when we arrived in the room, but she doesn't seem to be having any of it. Mind you, there is the vague possibility that "Si","Fruta","Cafe" and "Hola" isn't quite enough knowledge to explain the situation. Feh.
So, we manage to accost the lovely Amaya to do some translation for us. The cleaner lady calls her boss, who tells us it'll cost 860 pesos (£43). We politely decline. So, she then calls her boss. This all takes some time. Eventually, she opens a huge book, looks inside and sees that the shade was taken away by maintainance. Why this wasn't done before, I don't know.

Anyway, our bus was leaving at 2:00pm, so we had to rush to the reception. The journey was quite pleasent, and we eventually arrived at the airport at 4:20pm. There was a small altercation with the Taxi driver over the tip, as it was already included in the fair, and he said it wasn't. We then pointed out that tolls were also included in the fair, and the driver didn't take a toll road. At this point, he seemed to dissapear quite satified.

I approached the Air France desk, and was told I coudn't check in until 7:30pm (my flight dind't leave until 11:30pm). Bugger. So after waiting around quite a while, and getting something to eat, I went to check in. There was a huge queue, but it didn't really matter, as I was flying under a Flying Blue - Silver level card, so I could use the express queue. They did, however, want to check my luggage. Broken Spanish did work this time, as I wildly gestated towards my suitcase, making key symbols.

So, after another long wait, we (me and Daniel Baumann, we're on the same flight, and indeed sitting next to each other by some freak coincidence) wander off through to the gate. I manage to find some free wireless (ESSID: co_admeralty_club) and surf for a bit. Flight ends up being delayed for 30 mins, but it didn't matter too much.

Then, I hear an annoucement over the intercom, that a group of passengers should contact the gate staff, and my name is mentioned. A little worried, I approach.
"Hello, I'm Mr McGovern. My name was called on the intercom."
"Can I have your boarding pass please?"
"Sure..." *worry*
"Thank you.... ok, we'd like to invite you to fly business class with us today sir."
"Thank you very much"
I then proceed to whistle the 'Kill Bill' tune, as for some reason, it's following me everywhere I go in the airport, be it a cleaner, or another passenger. I think it's like some sort of virus, infecting one person and moving on to the next host.

We still had a little while, so we popped back to the waiting area to, well, wait. We saw some of the Brixen gang, and one of them had his laptop stolen : That's the second laptop down then. The first was run over by a car in Oaxtepec.

So, I board the plane, and am immediately offered lots of alcohol and other free thingstm. Which was nice. Unfortunately, the plane was further delayed. This means that on arriving in CDG, my connecting flight was already boarding. It was at this point that I had dounts about my luggage arriving in MAN at the same time as me.

So, I board the plane in Paris, and it's a straightforward flight. But lo and behold, at the other end, no baggage. No suprises there then.

Today, my luggage arrived at 8:00pm, just after I've got home from work. I'd also got a nice letter from the Inland Revenue, with a £215.67 tax rebate \o/

As my subject: S^HWings and Roundabouts.

Joey Hess: the supermarket thing

At DebConf I whined at Mark Shuttleworth about my fears that Ubuntu is reducing Debian to a supermarket of components (an analogy that was introduced entirely innocently by someone else during an unrelated talk). At least, that seems to be the kind of comment that I later heard some Ubuntu people characterize as whining. Anyway, NewsForge ran an article about DebConf that included a mention of that, and I had to follow up with a comment explaining a bit more about the problem. I'll reproduce it here:
The problem with everyone treating Debian as a supermarket is that it ends up with Debian == sunsite^Wmetalab. Giant un-integrated collections of software are not particularly interesting in a lot of ways. My main motive for contributing to Debian is to make Debian the best distro I can; I don't mind if others use that work, especially if stuff gets contributed back. But it's long been clear to me that the most important added value to Debian is not adding another package to the shelf, but finding new ways to integrate our software together. When you're working mostly above the level of individual software packages, to have your work mostly appreciated on the basis of "component contained in Ubuntu" is not very motivating. If that motive goes away I fear Debian could be left with mostly developers who are happily motivated with just packaging another peice of software. While there's nothing wrong with feeling that way and working on that basis, we don't want to lose the people who want to work on things that cut across sets of packages, like speeding up the boot time, improving the installation experience, making the distribution attractive for speakers of $language, making sure Debian supports as much hardware as best it can, porting Debian to interesting new architectures, integrating Xen and SE Linux with Debian, making a useful default desktop install, etc. Some of these are exactly the areas in which Ubuntu is apparently better than Debian, and in most of those cases, contributing individual patches back to Debian is simply not enough for Debian to share Ubuntu's improvements. It puts Debian at best in the position of wasting a lot of time trying to play catch-up and figure out how a collection of patches to different packages fits together into a coherent overall improvement.

Baruch Even: Debian in Google Summer of Code 2006

Congratulations to all whose projects were accepted, Debian received 60 eligible proposals, many of those were great projects which we would have loved to accept but we only had 10 slots that are paid for by Google so the competition was tough. The accepted projects are: All the accepted projects received email to them and their mentor, if you are a student whose project wasn't accepted, we'd still be happy if you will do the project even without the funding, if you need a helping hand or a mentor we will surely be happy to help you out, contact me at baruch@debian.org. The plan is that students who have a blog or setup one for the Summer of Code will be added to Planet Debian so everyone can follow their progress on their quest to help Debian improve. Cheers and thanks to everyone who helped make this happen!
Baruch Even
Debian SoC coordinator

Adam Rosi-Kessel: Cell Phones and Search Costs

I am one of the unfortunate hundreds of thousands of Verizon customers who eagerly ran out to buy the Motorola v710 Bluetooth phone when it first came out a couple of years ago. (For a short period of time, I could really turn heads with my wireless earpiece—now you look like an antiquarian if you don’t have a Bluetooth headset). It turns out that Verizon disabled all of the most useful Bluetooth features on the phone, and a class action lawsuit ensued, which predictably settled on terms quite beneficial to counsel, but less so to the affected class. The settlement provided several options for Verizon subscribers who had purchased the v710, only one of which had a substantial monetary value—namely, a $200 credit toward a new phone (or whatever the actual price we paid for the phone, assuming we still have receipts). The settlement period expires at the end of the month, so tonight I finally got around to cashing in on the victory. I was quickly reminded of how much I hate shopping for cell phone technology. Verizon provides more than a dozen options for cell phones, each of them mediocre in its own different way. (I should also mention that the Verizon Wireless website is, itself, mediocre in many different ways.) Cell phones have been around for long enough that it ought to be fairly mature technology; instead, you have to figure out which annoying shortcoming bothers you the least. The most expensive of the non-Pocket PC models, the Samsung SCH-a630, despite having a 2 megapixel built-in camera, has a lower image quality than the cheaper “LG the V” (better known as the LG VX9800), as well as crippled Bluetooth like the v710. I ended up settling on “LG the V,” despite its silly name and hefty form factor, because it seems to be the one model that Verizon decided not to cripple Bluetooth on. Apparently, it has complete OBEX support, and works quite well with Linux. It gets worse shopping for Bluetooth headsets. None of the top headsets recommended by cnet are even offered by Verizon. So instead you’re stuck perusing endless message board postings for threads with names like Which Bluetooth Headset is best for VX9800? trying to figure out which, in fact, is the best Bluetooth Headset for the VX9800. While some aspects of a Bluetooth headset are obviously personal preferences based on, for example, the shape of your earlobe, how often you drive in a convertible with the top down while talking on your cell, and whether you like to wear your headset to bed, I would really appreciate some objective metrics and brand uniformity. There’s no way to predict, for example, whether a particular model of Motorola, Jabra, or Logitech headset will be any good—some seem to be well received, while others have glaring design flaws. As a trademark lawyer, I’m disappointed by this state of affairs. I’d like to be able to identify a brand that I can trust and just go with it. This is especially true where it’s difficult to evaluate the quality of an item on first inspection (or over the Internet) and it’s an item you’ll keep for at least a while (two or three years for cell equipment). As things stand, there seem to be few real winners, and the search costs are inordinately high. Hopefully the invisible hand will eventually fix this situation, but I’m not going to bet on it.

Next.

Previous.