Search Results: "will"

29 May 2006

Jordi Mallach: Sevilla

I arrived in Sevilla this morning to attend tecnimap 2006, and I will be staying in the city until Friday evening. I'd love to hook up with the Sevillan Free Software community after the show ends during the week, so if you're in the area, please contact me by phone (there's plenty of Debian people who know my number) or by email and we can try to make up some plans. I'm staying in the Sevilla Congresos hotel in the outskirts, so going out to the city involves taxis, busses or other non-trivial means of transportation, so have that in mind! Getting here has been quite stressful, but that's no news anymore. At 00:00 last night, not only I had not packed at all, but all my clothes were scattered around thre different flats in the city, and I had no car to go pick the stuff up. Luckily, this morning my sister could give me a lift to pick things up and then took me to the airport. The flight revealed a very dry landscape as we headed south, and some irrigated areas in the middle of pure desert. There are also some very characteristic circular fields that show very cool patterns when looked from the heights. It's pretty hot in here, but still bearable. I don't want to imagine August around the place. Anyway, if you're in Sevilla, I hope to be able to meet you any of the four evenings or nights I'll be around. I need some natives to walk me around the place, and in some cases, translate the very special Andalusian spoken here. :) Momona people, I also mean you!

28 May 2006

Ian Murdock: Picasa: Why not a native Linux port?

Robert Love: “In Google’s calculation, the cost of a native port outweighed the benefit of a native [port] v s-a-v s a WINE-fueled Picasa. Is that really unexpected? Our development platform is no shining star. We have two toolkits, poor binary compatibility, and unclear direction. To be sure, vendors such as Novell are devoting increasing effort toward improving the Linux ISV and platform story. But the community must make it a priority as well, from the kernel up through the highest levels of the graphical desktop.” That’s part of it (and certainly an accurate assessment of the kind of thinking we need as a community to make Linux a better platform). I think there’s another part of it, though, and that’s that operating systems in general are fundamentally uninteresting to Google as platforms in themselves, as well they should be—after all, the web is Google’s platform, and they dominate there, so why should they promote an alternative where they are much weaker? In my view, the (fat) client bits merely exist to ease the transition from the current, predominantly desktop centric world to a new web centric world where Google naturally thrives. After all, such paradigm shifts are always gradual. There’s the offline question too—if all your data is in the cloud, how do you get to it when you’re not online?—though I suspect over time the browser will provide offline capabilities of some sort, so this is largely a temporary problem too. So, using Wine in ports not only minimizes the incremental cost of building out a foothold on the client (which, again, is a necessity for Google, given that Google’s biggest competitor is between them and 90% of their customers), but it raises the fat client platform up a level too. In other words, it builds a fat client platform with a consistent look and feel across desktop environments; and with this, the operating system underneath rapidly becomes irrelevant. The real question is when Google will hook Picasa into a photo sharing service of its own. I already keep my photos in the cloud, and I’d love to organize and edit them in Picasa (Organizr is nice, but nowhere near as nice as a desktop application, and it doesn’t have some basic functionality, like import from camera and red eye repair). Of course, this is just one example of Google having some platform thinking issues of its own, though that’ll have to be a rant for another day.

27 May 2006

Robert Pickel: First Post

This is my first post since starting the project.

I am working with the live-debian project, but I think I will continue on with my original proposal.

Bascially that is to write an extention of debootstrap for creating live images.

Of cource this will work with the releases supported by Debootstrap includeing Ubuntu.

Right now I am looking at supporting a debian scheme which uses init scripts that closely resemble the INIT scripts from a normal debootstrap install. The other will take advantage of KNOPPIX technology, which is has been noted as having some the best hardware detection.

For now I will focus on researching the types of hardware detection.
This will probobly require me to create my own repository that contains both Kudzu (KNOPPIX) and Discover2 based hw detection.

There is a lot more to be looked into in terms of bootloaders, and types of read-only filesystems (cloop, squash file system, etc.)

There are no immediate plan to focus on incorperating any X-windows system or desktop into debootstrap-live.

Essesntially the core of this project is to identify the best tools for creating a working live version of the releases supported by debootstrap.

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.

Junichi Uekawa: cowdancer and its limitations.

I've been expecting a fewdesign problems with cowdancer; and I was hoping that theseproblems are going to be minimal that normal packagebuilding isn't affected.One thing that cowdancer cannothandle is that because it plays tricks with replacingi-nodes when writing to a file, any application that expectssame i-nodes before and after 'open' syscall will fail.Apparently, this is a popular behavior to avoid symlinkattacks. So, if an application does lstat, open, fstat, insequence, and checks the dev/inode number of the lstat/fstatresult, the application will be confused when running undercowdancer, which will change the inode number hooking'open'.For cowdancer with pbuilder, if dpkg/apt andpreinst/postinst works, that's fine, and it seems to befunctioning; which is good.

Joachim Breitner: little subversion helper script: svn-ignorer

Hi subversion-using world. I always had the problem that setting svn:ignores is quite tedious, especially since svn refuses to read the list from standard input, and specifying multiple line values on the command line is not very convenient. So I wrote a little shell script, here is the usage:
Usage: Just run in your svn directory. It will fire up your favourite $EDITOR and lets you edit the list of files unknown to subversion. Erase those that you don’t want to ignore, and add wildcard patterns at will. When you close the editor, the files left in the list will be added as svn:ignore properties to their directories, amending the present list of svn:ignores
If you think this of any use to you, grab it here. Comments welcome.

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!

Raphaël Hertzog: Improving Debian as a whole

I have to agree with Joey, I have the feeling that we’re not doing many “transversal” improvements and that we’re busy enough simply trying to keep up with new upstream version of software. That’s not completely true but I also wouldn’t want Debian to evolve in that direction. I think that less people are interested in doing large scale changes because the coordination with 1000 maintainers and 10000 packages is simply too complicated and taking too much time. Luckily we had significant improvements recently that should ease that coordination work. I’m thinking mainly of the usertags that allow us to use the BTS as big TODO list. But usertags are obscure to many people and not well documented yet. So there’s room for improvements: that’s why I proposed a project for Google’s Summer of code called “Distribution-wide tracker tools” (see list of accepted projects here). Check the project proposal of Arnaud Fontaine to have a more precise idea of what it could give. I want this infrastructure because I think it may help Utnubu to effectively coordinate the integration of Ubuntu improvements and because it may help Debian be more on the leading edge (instead of trying to catchup with derivatives). And last but not least, I believe many more people (with different level of skills) will be able to effectively work on some projects once the work to do has been clearly identified and registered in such a system. The project is about to start, so all ideas/comments are welcome of course!

David Pashley: Makes you look big *and* clever

To the anonymous Texan that thought it would be a good idea to point out a Perl module in response to my date parsing class in Java: I'm well aware of date parsing modules in other languages. In fact I've used them for similar tasks. But the post wasn't asking "How do I parse dates in Perl?" It was giving some code that some people might find useful. Commenting with "man Date::Parse" doesn't make you look clever; it just makes you look like a twat and the kind of person people are relucant to invite to parties. You may be a geek and you may know stuff, but that doesn't mean you have to try to look clever, because you will invariably fail. </rant> Oh and Erich, I've got some more date formats I want to add support for, so I'll add german dates and post the updated code. :)

Andrew Pollock: [life] Another massive road trip coming up

It's not a Holiday Weekend unless it involves us putting heaps of miles on the car. This time, we're going to Kirkland, where I'll work from for the week. The route outlined on this image isn't quite the route we're going to take, we're going to camp amongst the redwoods on Saturday night, and stop off in Portland on Sunday night. On Friday night we'll stop where we drop, which we expect will be Ukiah. The following weekend, on the way back, we'll take a more direct route, which will probably be closer to what's on the map. Rough idea of the trip

Carlos Parra Camargo: debian-cd-ng (Application accepted!)

I've just read that my project debian-cd-ng has been accepted in Google Summer of Code :-D
Summer Of Code

Like one spanish president said when he wons the elections:
Now, it's time to work
I'm a litte busy right now, i will post here more info as soon as possible.

Carlos Parra Camargo: Powered by debian sarge

This weekend, i've been thinking about debian-cd and also, as you can see the debian logo at the right bar, i've installed a debian sarge in my personal server. In two days i will know if i've been selected to participate in Google Summer Of Code. I send two applications: rewrite debian-cd and a graphical tool to compile debian packages. I have to confess that i've already been working in debian-cd-ng (i call it debian-cd next generation, idea stolen from bzr) because i'm really interested in. For many years, i've been really interested in the debian world, it was a time that i was really interested in become a DD but i was afraid of the process. I'm looking forward a great piece of software to package it to debian, if i found it this summer, surely i will package it and try to upload to debian i hope that it's just a matter of time. Well, i've many exams in a week so i've to study a little harder for this week. The friday i've an exam about informatic rights, it's really interesting and it's greatful to have a subject that it isn't relationed with maths or programming. Pleasy notify me any bug on my english, thanks :-)

Jos Parrella: News from the KSP

After reading this thread in debconf-discuss, I think we all agree in the following items: Now seriously, I think the whole point behind key signing is, as Holger philosophed about and Vorlon answered, to know who is the guy behind the key. If I sign your key, I won’t trust you and give you my money for you to keep it, but if I had to do this and you steal me, I can blame you. And the whole point behind a party is to have fun. So it’s a time to take profit of a useful tool while having fun, so please don’t panic.

Zak B. Elep: For those who still care about CVS, here s one for you :)

Heh, almost the end of May and I’ve not a post. Well, that’s going to change :P There’s a new version of cvs in unstable, courtesy of Steve McIntyre and Yours Truly, responding to the RFH posted earlier. As a new upstream version, it is supposed to fix a lot of bugs, but it seems that a duo of grave and normal have been found :/ Hopefully those wouldn’t be there for long :) Along with fixing those bugs, I’ll be checking out the rest of the bugs list and start pinging submitters… Hopefully a good few of the old outstanding bugs will get done. As for my other packages, gtklp got updated (thanks Nutmeg!) to fix Catalan l10n (thanks Lluis!) and updated the autotools update, as well as its (borked) touch-fu. I also got the new gnome-ppp in, thanks to Paul Cupis. Updates to libungif4 and lua50 will follow shortly.

25 May 2006

Junichi Uekawa: cowdancer and pbuilder.

I've uploaded a new version of cowdancer and pbuilder, which work with each other.The two new extensiosn, cowbuilder command, and --pbuilder option (PDEBUILD_PBUILDER configuration option) to pdebuild, will allow cowdancing with pbuilder.Result of hacking at Debconf and in the plane back home.Enjoy.

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?

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!

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...)

Next.

Previous.