Search Results: "ag"

24 January 2009

Brice Goglin: Debian/X.org notes - Xserver 1.6, Intel 2.6.1, ... what's up in XSF?

It has been a while since my last post here. Not because nothing happened, but mostly because I did not have time to do much for X. Fortunately, Julien is taking good care of X in Debian so we are still close to latest upstream bits. Obviously, due to Lenny's freeze, everything is happening in experimental these days. Xserver 1.6 The release Xserver 1.6 is expected in the near future. 1.6-rc1 (1.5.99.901) entered experimental recently. Both video and input driver ABIs changed and very few drivers have been rebuilt so far. So if you're not running Intel or Radeon, you might not be able to upgrade yet. Please be patient :) You might have heard that many things are happening in X.org these days: DRI2, kernel-modesetting (KMS), RandR 1.3, ... Everything is not ready yet, but it's getting close for real. Radeon 6.10.0 and Intel 2.6.1 Radeon driver 6.10.0 was released in early 2009. As usual, it brings many fixes, and improvements for modern boards (see Alex Deucher's blog for details). However, Radeon is not ready for above DRI2 and KMS yet. Most of the development for these new features is first done in the Intel driver, which got recently bumped to 2.6.1 as well. DRI2 DRI2 is the new Direct Rendering Infrastructure. The most noticeable change from the user point of view is support for Redirect Direct Rendering, which basically means that your 3D application can be wobbly/transparent in Compiz. See Kristian H gsberg's blog for details. If you want to try DRI2 on Intel, you have to enable UXA as the acceleration architecture in xorg.conf (Option "AccelMethod" "UXA" in the Device section). DRI2 will then be enabled automatically. Then, it may or may not work, depending for instance on the hardware. I get a black screen at startup on i865 while i945 works fine until I start Compiz (the server suddenly exits for some reason then). Note that you probably want to upgrade your Mesa packages to experimental as well here (7.3 has been released recently). Of course, running git snapshot of various components (Mesa, libdrm, kernel drm, Intel driver, ...) may help since the released versions seem to not be entirely ready yet. But, things should may be ready to use for everybody in the near future. Kernel Modesetting The other nice feature that makes a lot of noise in X.org these days is Kernel modesetting (KMS). It moves the management of mode (aka resolution+rate) into the kernel. It helps support for switching between different users' sessions, enables reporting of kernel messages (oops, panics, ...) while X is running, and reduces the need to blank the screen during boot (since the kernel can setup the display early and X doesn't have to change it later independently). KMS testing requires a bleeding-edge kernel (2.6.29). Using a git snapshot of the drm stack is probably a good idea as well since I couldn't get KMS to work on 2.6.29-rc2 here. Again only Intel will support KMS soon, but other drivers will follow. Panning is back (aka RandR 1.3) Xserver 1.6 brings support for the 1.3 version of the RandR X extension. Among other improvements, it reintroduces one feature that many users miss since it was removed back in Xserver 1.3 or so. "Panning" (often referred to as "Virtual Desktop") gives the ability to move the display within a larger screen when the mouse approaches from the border. Instead of being configured with the Virtual option in xorg.conf (this option means something else nowadays), it may now be enabled/tuned with xrandr --panning. You'll need the latest libxrandr2 and xrandr utilities to do so (the latter is not uploaded yet).
(Permanent link)

Daniel Burrows: aptitude 0.5.1 released

I've released version 0.5.1 of the aptitude package manager (release notes). Once it has been installed into the archive, you can download it from Debian's experimental distribution, or manually from the aptitude package page. WARNING: This is an unfinished piece of software. Do not install it if you want a package manager that does everything you need perfectly all the time. It is buggy and incomplete. There are no huge user-visible changes in this release, but there are a number of smaller new features and enhancements. Click through to the release notes to see a list of what changed in this release, with screen-shots.

Sami Haahtinen: New tricks

"You never call, you never write. I hardly know you anymore." Yes, I've been meaning to write up on several things. For some time now, I've been a happy VIM user and a while back I ran in to a blog post where someone mentioned a new feature they found in VIM which got me to explore the vim-scripts package. There are a lot of scripts out there that extend VIM far beyond what it can do by default. And it's quite powerful even without the scripts. One of the neat little scripts I decided to install by default was surround, it allows one to easily replace surrounding parenthesis, tags or quotation marks. There are a lot of scripts in the vim-scripts package, but it's not always clear how to enable the scripts. Thats where vim-addon-manager comes to play, it provides a vim-addon command that allows you to easily enable or disable the scripts. I'm still trying to grasp the full potential of all the new commands available, but it certainly appears that I'll be having even more fun writing stuff. It's kind of odd, at first when you start to use vi-like editors, you struggle. But in the end it's just such a convenient way of editing files that it really does grow on you.

Ingo Juergensmann: I did it!

Oh, well... although I said that I'll wait some more time until I upgrade the firmware of my Seagate Barracuda ES.2 ST31000340NS drives, I did it today!

=== START OF INFORMATION SECTION ===
Device Model: ST31000340NS
Serial Number: 9QJ2VT98
Firmware Version: SN06
User Capacity: 1,000,204,886,016 bytes


And well, it still works.

/me happy :-)

Y Giridhar Appaji Nag: Movies for the day

I went to watch Slumdog Millionaire this afternoon. The movie is good, but doesn't live up to the hype around it. However, the initial sequence where the kids are chased by the police through the slums of Dharawi was excellent. The movie is very Indian, but one thing that stands out is that Jamal Malik is accused of cheating because he is a boy from the slums, and IMO, India is country where people believe that anything is possible and if someone from a slum wins on a game show, it wouldn't surprise a lot of people let alone make them suspicious.

Pretty much everybody seems to describe SDM as the story of a boy from Mumbai's slums who answers all the questions on who wants to be a millionaire and is suspected of cheating. While that is how the plot goes, I don't know if that was how Danny Boyle intended people to know the movie as. I felt that SDM is the story of a young man who wants to be on the TV game show for as long as possible so that his love can watch him. Neither the money nor the intellectual challenge of being on the show matter to him at all.

I am watching The Mystic Masseur at home right now. Most movies from The Merchant Ivory 'period movie' collection are available at a discounted price in the stores these days :-).

Oh, I finally made myself a Hackergotchi hackergotchi

Steve Kemp: Just some kind of fairytale.

Once upon a time I ran a Valentine-Matching site for Livejournal users. (Actually I did it for about three years in a row, but then got bored.) The basic idea was simple, you'd visit a magical site and it would present you with the usernames of all your friends. You'd tick a few boxes, and that would nominate those users as your potential valentines. Then you'd do nothing until February 14th, at which point you'd discover if you matched. A match being made if you chose bob, and bob chose you in return. (Essentially the site is a big double-blind matching system, albeit with constrained membership, via lj.) The major technical difficulty in early days was preventing spoofed accounts. I didn't want Evil Alice to be able to visit the site and pretend to be Bob. In the couple of years I did this I came up with a couple of fun schemes to minimize the chances of this occuring - anything from using email validation, to requiring that users taking part updated their profiles to include a magic cookie-string, or posting to a specific community which I could later screen-scrape. These days the use of openid allows me to prevent spoofing in a trivial manner - and once I realised that I figured why the hell not?! In short here I am and here we go again: The motivation? Playing with openID and because I still like to "match people up". I am aware of one marriage that resulted from a match on my system back in 2003. There could be more. If you're a long-time reader you might remember ctrl-alt-date - how time flies - I just let the domain name(s) expire this week. The timing is a little bit of a coincidence, but not entirely. The only thing that I'm doing this time is not sending emails on matches, because I just can't. Unless I asked people to volunteer their mail addresses I don't have the data. Still I expect remembering to return for the results won't be a challenge. Now, lets get viral. But not in an icky fashion .. ObFilm: Daywatch

Uwe Hermann: Recovering from a dead disk in a Linux software-RAID5 system using mdadm

RAID5 failure As I wrote quite a while ago, I set up a RAID5 with three
IDE disks at home, which I'm using as backup (yes, I know that
RAID != backup) and storage space. A few days ago, the RAID was put to a real-life test for the first time, as one of the disks died. Here's what that looks like in dmesg:
raid5: raid level 5 set md1 active with 3 out of 3 devices, algorithm 2
RAID5 conf printout:
 --- rd:3 wd:3
 disk 0, o:1, dev:hda2
 disk 1, o:1, dev:hdg2
 disk 2, o:1, dev:hde2
[...]
hdg: dma_timer_expiry: dma status == 0x21
hdg: DMA timeout error
hdg: 4 bytes in FIFO
hdg: dma timeout error: status=0x50   DriveReady SeekComplete  
ide: failed opcode was: unknown
hdg: dma_timer_expiry: dma status == 0x21
hdg: DMA timeout error
hdg: 252 bytes in FIFO
hdg: dma timeout error: status=0x50   DriveReady SeekComplete  
ide: failed opcode was: unknown
hdg: dma_timer_expiry: dma status == 0x21
hdg: DMA timeout error
hdg: 252 bytes in FIFO
hdg: dma timeout error: status=0x58   DriveReady SeekComplete DataRequest  
ide: failed opcode was: unknown
hdg: DMA disabled
ide3: reset: success
hdg: dma_timer_expiry: dma status == 0x21
hdg: DMA timeout error
hdg: 252 bytes in FIFO
hdg: dma timeout error: status=0x58   DriveReady SeekComplete DataRequest  
ide: failed opcode was: unknown
hdg: DMA disabled
ide3: reset: success
hdg: status timeout: status=0x80   Busy  
ide: failed opcode was: 0xea
hdg: drive not ready for command
hdg: lost interrupt
hdg: task_out_intr: status=0x50   DriveReady SeekComplete  
ide: failed opcode was: unknown
hdg: lost interrupt
hdg: task_out_intr: status=0x50   DriveReady SeekComplete  
ide: failed opcode was: unknown
That's when I realized that something was horribly wrong. Not long after that, these messages appeared in dmesg. As you can see the software-RAID automatically realized that a drive died and removed the faulty disk from the array. I did not lose any data, and the system did not freeze up; I could continue working as if nothing happened (as it should be).
 md: super_written gets error=-5, uptodate=0
 raid5: Disk failure on hdg2, disabling device.
 raid5: Operation continuing on 2 devices.
 RAID5 conf printout:
  --- rd:3 wd:2
  disk 0, o:1, dev:hda2
  disk 1, o:0, dev:hdg2
  disk 2, o:1, dev:hde2
 RAID5 conf printout:
  --- rd:3 wd:2
  disk 0, o:1, dev:hda2
  disk 2, o:1, dev:hde2
This is how you can check the current RAID status:
 $ cat /proc/mdstat
 Personalities : [raid6] [raid5] [raid4] 
 md1 : active raid5 hda2[0] hde2[2] hdg2[3](F)
       584107136 blocks level 5, 64k chunk, algorithm 2 [3/2] [U_U]
The "U_U" means two of the disks are OK, and one is faulty/removed. The desired state is "UUU", which means all three disks are OK. The next steps are to replace the dead drive with a new one, but first you should know exactly which disk you need to remove (in my case: hda, hde, or hdg). If you remove the wrong one, you're screwed. The RAID will be dead and all your data will be lost (RAID5 can survive only one dead disk at a time). The safest way (IMHO) to know which disk to remove is to write down the serial number of the disk, e.g. using smartctl, and then check the back side of each disk for the matching serial number.
 $ smartctl -i /dev/hda   grep Serial
 $ smartctl -i /dev/hde   grep Serial
 $ smartctl -i /dev/hdg   grep Serial
(ideally you should get the serial numbers before one of the disks dies) Now power down the PC and remove the correct drive. Get a new drive which is at least as big as the one you removed. As this is software-RAID you have quite a lot of flexibility; the new drive doesn't have to be from the same vendor / series, it doesn't even have to be of the same type (e.g. I got a SATA disk instead of another IDE one). Insert the drive into some other PC in order to partition it correctly (e.g. using fdisk or cfdisk). In my case I needed a 1 GB /boot partition for GRUB, and the rest of the drive is another partition of the type "Linux RAID auto", which the software-RAID will then recognize. Then, put the drive into the RAID PC and power it up. After a successful boot (remember, 2 out of 3 disks in RAID5 are sufficient for a working system) you'll have to hook-up the new drive into the RAID:
 $ mdadm --manage /dev/md1 --add /dev/sda2
 mdadm: added /dev/sda2
My new SATA drive ended up being /dev/sda2, which I added using mdadm. The RAID immediately starts restoring/resyncing all data on that drive, which may take a while (2-3 hours, depends on the RAID size and some other factors). You can check the current progress with:
 $ cat /proc/mdstat 
 Personalities : [raid6] [raid5] [raid4] 
 md1 : active raid5 sda2[3] hda2[0] hde2[2]
       584107136 blocks level 5, 64k chunk, algorithm 2 [3/2] [U_U]
       [>....................]  recovery =  0.1% (473692/292053568) finish=92.3min speed=52632K/sec
As soon as this process is finished you'll see this in dmesg:
 md: md1: recovery done.
 RAID5 conf printout:
  --- rd:3 wd:3
  disk 0, o:1, dev:hda2
  disk 1, o:1, dev:sda2
  disk 2, o:1, dev:hde2
In /proc/mdstat you'll see "UUU" again, which means your RAID is fully functional and redundant (with three disks) again. Yay.
 $ cat /proc/mdstat
 Personalities : [raid6] [raid5] [raid4] 
 md1 : active raid5 sda2[1] hda2[0] hde2[2]
       584107136 blocks level 5, 64k chunk, algorithm 2 [3/3] [UUU]
Btw, another nice utility you might find useful is hddtemp, which can check the temperature of the drives. You should take care that they don't get too hot, especially so if the RAID runs 24/7.
 $ hddtemp /dev/hda
 dev/hda: SAMSUNG HD300LD: 38  C
 $ hddtemp /dev/hde
 dev/hde: SAMSUNG HD300LD: 44  C
 $ hddtemp /dev/sda
 dev/sda: SAMSUNG HD322HJ: 32  C

23 January 2009

Josselin Mouette: On the good use of compiler warning flags

The gnome-power-manager developers like clean code. Actually, more than clean code: code that will not generate a single nitpicking warning. The package builds with the following C compiler flags:
-Werror -Wcast-align -Wno-uninitialized -Wall -Wformat-security
Sometimes the compiler is more clever than the coder On the SPARC architecture, -Wcast-align really starts to mean something. Unlike most other architectures, any alignment error on here will leave you gather your teeth spread on the floor after you ve been hit by a SIGBUS. It tries to catch at build time alignment errors resulting from a cast between pointers to different types. Together with -Werror, it triggered a first FTBFS bug. The error occured on the following code:
        if (XRRGetOutputProperty (brightness->priv->dpy, output, brightness->priv->backlight,
                                  0, 4, False, False, None,
                                  &actual_type, &actual_format,
                                  &nitems, &bytes_after,  ) != Success)  
                egg_debug ("failed to get property");
                return FALSE;
         
        if (actual_type == XA_INTEGER && nitems == 1 && actual_format == 32)  
                *cur = *((int *) prop);
                ret = TRUE;
         
        XFree (prop);
        return ret;
More precisely, the error occurs when casting prop (which is an array of pointers) into an int *. The compiler is clearly right. The alignment requirements are different for a pointer and an integer; therefore, casting a pointer to a pointer into a pointer to an integer will always work, but dereferencing the pointer later will possibly cause a crash. Turning this expression into a memcpy leads to code that should always work. Lesson learned: do not design APIs where an array of pointers can actually store integers. Have you ever heard of opaque structures? and sometimes it is not This was not enough and a second FTBFS bug showed up. Here, the error happens in the following code:
static inline GstBuffer *
gst_buffer_ref (GstBuffer * buf)
 
  /* not using a macro here because gcc-4.1 will complain
   * if the return value isn't used (because of the cast) */
  return (GstBuffer *) gst_mini_object_ref (GST_MINI_OBJECT_CAST (buf));
 
GstBuffer is a structure which contains a GstMiniObject at the beginning. Therefore, you conduct operations on the GstMiniObject through a mere cast. The first cast (GstBuffer GstMiniObject) is fine, but in the second cast (GstMiniObject GstBuffer), the compiler suspects a problem, since the alignment requirements on GstBuffer are stronger than those on GstMiniObject. The compiler is wrong because it didn t read the API documentation; otherwise, it would have known that gst_mini_object_ref can only return NULL or its argument, which means there can t be any loss of alignment. Since there are no function attributes to express such complex things, we are still forced to rely on the developer having correctly read the documentation. Way to go, compiler. Lesson learned: there are good reasons why some warnings are not part of -Wall. Especially, it is dubious to use them with -Werror. Does anyone know whether it is possible to apply -Werror only to some of the warnings and not to all of them? It would sound like a useful improvement.

Daniel Kahn Gillmor: target disk mode (sbp-2 mass storage host mode?)

One very convenient feature of Apple's hardware is the ability for their workstations to enter target disk mode. This effectively transforms the machine into a glorified ieee1394 (firewire) block device, which can then be manipulated from outside the machine using the standard SBP-2 protocol. Is there a way to provide this same functionality from a running GNU/Linux machine? For example, i have a GNU/Linux system with a block device attached to it. I would prefer if the block device was available to a neighboring machine, but (for whatever reason) i'm unable to physically move it. However, i'm able to link the two machines via a simple ieee1394 connection. A "virtual target disk mode" server (or would it be better to say "an SBP-2 mass storage target service over an ieee1394 link"?) would be really useful. One thing that occurs to me is that i could do some sort of networking abstraction over the link (using eth1394?), and then use something like vblade (an ATA-over-Ethernet target service) to provide a virtual block device to the remote host. However, this requires the remote host to run an operating system capable of dealing with these (more obscure) protocols, and i'd like this to work for any remote machine that knows how to deal with generic SBP-2 ieee1394 mass storage. I know that in general GNU/Linux is at least as powerful and capable as the firmware that Apple ships ;) But it's possible that our community just hasn't gotten around to implementing something like this. Is this the case? My attempts to search for it haven't turned up anything, but it's entirely possible that i'm reading the wrong docs (or reading the docs wrong). Any pointers?Tags: firewire, ieee1394, sbp2, vblade

Ingo Juergensmann: Seagate Firmware Problems

Some time ago I've blogged about the downside of large disks being long the huge amount of time that it needs to check them with badblocks for medium errors.

As I told there, I bought two Seagate Barracuda ES.2 ST31000340NS and most of you might have heard about the firmware problems of those disks from Seagate. Seagate writes:

*Please email discsupport@seagate.com to request a firmware upgrade if your drive is on a release earlier than SN06.

Please include "ES.2" in the subject line of your email request for proper routing.


Well, I did write last week already, but haven't got any reply yet. This morning I mailed Seagate again, but no reaction so far until afternoon. Not even an automated "We got your mail and will answer it!" mail.
So, if you're in a similar situation you might ask yourself: "How can I get those firmware updates for my ES.2 drives then?"

Well, for me this trick worked quite fast:

  1. Go to the Seagate Contact Page
  2. Choose your region and country of Technical Support
  3. Click on "Chat" and wait...
  4. ... and wait...
  5. ... and wait...
  6. ... and wait...
  7. Request your firmware update from the friendly support staff that appeared somewhen
  8. Check your emails
  9. Follow the instructions in that mail



Yes, I've had to wait nearly one hour until someone showed up in that chat window, but then it worked quite nicely: I've got my email, downloaded that ZIP file and ... no! I didn't updat the firmware yet. I think I'll wait some more days, maybe until next week, and see if this firmware update is now working properly for others.
Maybe some will call me a coward, but I'm just following those friendly letters on that specific book you all know:

Don't Panic!

My disks are still working and my UPS does so as well. So, no need to hurry... But it's good to know that I could upgrade if I would like to... :->

Sylvain Le Gall: OCaml meeting 2009, subscription about to end

The subscription will end on January the 25th, for people willing to come to this unique OCaml event, this is your last chance !!!! We have 40 participants for now. I am quite happy with this number because it is almost the same as last year -- except that we do it in Grenoble rather than Paris. Anyway, I see that a lot of people who were there last year, will come back to this year events. There is also a few more people, in particular more from CAML consortium members. I have stepped down from the first talk about OCamlCore.org in favor of Stefano Zacchiroli. Zack has really helped me on this project since the begin (with Pietro Abate and Romain Beauxis). I am very happy that he can do the talk. I will do myself, a talk about my last project for Talend. This was a great project targeting to be as fast as a standard C application but in OCaml. The point is that OCaml helped me to do quickly a working prototype and then optimize it for speed. All in all, after 6 months I was able to deliver Talend with a working and fast application. This kind of release cycle is harder to achieve in other programming language. OCaml compile time verification helped me a lot. I hope that in the last remaining 2 days, some more people will subscribe. Wiki Subscription

Y Giridhar Appaji Nag: Gurudwara Tarn Taran Sahib

About 25KM from Amritsar is Tarn Taran. Tarn Taran was founded by the fifth Sikh Guru, Guru Arjun Dev who also built a Gurudwara there and named it after the town. The Gurudwara has the largest Sarovar (lake) among all the Sarovar's across all Gurudwaras. The place is calm, peaceful and a treat to the senses. I was there one winter morning and took some pictures.

The Sarovar:

Tarn Taran Sahib Sarovar

And a few more pictures from the Gurudwara:

Tarn Taran Sahib Tarn Taran Sahib Tarn Taran Sahib Tarn Taran Sahib

Michal Čihař: ICQ fun

For legacy reasons (it's still most used IM in Czechia), I still use ICQ. Few days ago AOL again started to block some users (especially in Russia) and disconnected time to time others using non official clients. They do such things quite regularly, however the problems are usually quite easy to fix once somebody figures out what exactly do they check. So it just forces all clients to adjust some bits in the protocol initiation and it works again. Does it really make sense to complicate things this way? How about finally opening it? Or providing Jabber gateway?

Axel Beckert: MBC09: The Day Before

Helped my parents moving the first half of the week. Left there at Thurdays around 9am. Drove 45min to Zurich. Removed everything bicycle related from my daypack. Left the TomTom at home. (Google Maps on the E51 has to sufficed and sufficed so far.) Crammed cloths for three days in. Was at Zurich Main Station around 11:40am. My plan was to take the direct ICE train from Zurich to Hamburg Dammtor. Bought a Rivella for the journey. First suprise at the platform: No ICE train. Instead a Swiss InterCity. The staff told us due to a defect in the ICE train, we have to go to Basel SBB with this train, then switch trains there. No carriage numbers and reservations valid here. Hrmpf. For luck, there where not that many people in the train. No power sockets though. Next surprise at Basel SBB: No ICE train here either. We re advised to switch to a German InterCity and then switch again a few kilometers later at Basel Badischer Bahnhof (aka Basel, German Station ). There then finally waited an ICE labelled as the initially expected ICE 72 from Zurich to Hamburg Altona. Even the reservations were displayed, departure was though 20min later than the original ICE 72. The voice from the speakers told us that this is a replacement train which came empty from Zurich. WTF? The next time the voice explained the situation, it was a replacement train coming from Interlaken Ok, DB is not as insane as I believed for about half an hour. ;-) Worked though the git tutorial and the git glossary on the train since in future I ll use git in some of the OSS project I m working together with Conkeror beyond others. Also had a conversation with some doctor from University Hospital Zurich who has chasing as hobby. (WTF?) The train arrived about 45 minutes late at Dammtor, so I first checked in in my hotel ( Hotel am Dammtor , very close to the MBC09 venue) and then walked to Hamburger Botschaft where the twitter reading was already running, hoping to meet someone I know and having dinner afterwards. Guided by Google Maps on my Nokia E51 it took longer than expected to walk there. And it was windy and raining. The twitter reading venue was quite full, but I still found a place where I saw most of the screen. At least the reminder of reading was quite funny: #famouslasttweets. They closed with a tweet similar to And then there s also identi.ca . :-) I was told it wasn t that funny at the beginning. Didn t find anyone I really knew, just sticked to a group talking about being hungry. When we met @igorette on our way to some restaurant and he recognised me, I found out that @muhh was also in the group I m heading though Hamburg. We had a nice dinner at Schmitt Foxyfood, I had GrillGold (Pommes Frites) with WuchtBrumme (Currywurst) and Fritz Cola. After dinner, @moeffju drove me and some other guy to our hotels. So the first evening was already very interesting despite the usual lateness of Deutsche Bahn.

MJ Ray: I m not going to FOSDEM 2009

FOSDEM is a place where free and open source software really means open source software and the F in FOSDEM is a token gesture to the free software movement if you believe FOSDEM organiser Philip Paeps. If that s so, I m amazed they can claim to promote the awareness of free software with a straight face. I m not going to FOSDEM again because there are better value-for-money events around now, but I do understand the motives of the various anti-Novell campaigners. The Boycott Novell site linked to my explanation of Boycotts a few years back. I really don t agree that A conference just is not complete without corporate schwag and presence. Presence? I don t really enjoy being jumped by salesmen. Schwag? There was one long-term useful item in my last conference pack, that was from an association and I would probably have bought a slightly better one if I hadn t been given it. So, I really don t understsand why FOSDEM are annoying people in part because they like branded cheap junk. I suspect most of it ends up in the bins before long. I mean, who needs a non-obvious bottle-opener? I have one on the waiters friend, another with a nice handle, one on my penknife, one on my wife s penknife and even one on the can opener s handle. There are probably a few more in my home and bottles aren t even so hard to open without a special tool anyway! Anyway, if you re going, I hope you have a safe journey. Maybe you could mention Glyn Moody s summary of the FOSDEM controversy to some people there. Call me when you re organising a trip to something like a drupalcon, wordcamp or LUGRadio Live.

Kartik Mistry: Breaker


* I have started breaking commitments so often. It really hurts when you do it often and I am very depressed by myself at moment. But, good things in life so far: + My new digital photoframe has arrived. Thanks to Chintan for it. + We have started to make some furniture for home (ie my longterm pending thing: Computer Table!) + Kavin is becoming so smart, he has started speaking some random words and identify and duplicate things I do (no, not Debian packaging yet!) + My macbook has 4 GB RAM now. The incident is here (Sorry, its in Gujarati only!).

Daniel Burrows: A report from the technological present.

Today I had the occasion to do something I normally don't do: send a text message. I can report that it's a lot like writing an email. If all the bones in one of your hands are broken, that is.

Robert McQueen: Auctions, Beards, Conferences and Devils

Tuz, coming soon to a Linux kernel near you
It s the last day of the most awesome linux.conf.au 2009 conference in Hobart, Tasmania. I ve just witnessed the a room full of 500 people sit with baited breath as Linus wielded a set of clippers to shave Bdale Garbee s beard, followed by Bdale (with a razor with 3 more blades than last time he shaved, a tiny bowl of water and a hand-mirror) trying to make it look neater. The LCA twitter feed was up on the projector, and someone rightly observed this whole event was actually pretty weird. There are already pictures on flickr too. However, well done to Bdale for being such a good sport, but it looks like his wife Karen will accompany him next year to make sure he doesn t agree to anything else like this, and supervise the waxing of Rusty s chest :) What s this all in aid of? After the incredible auction for this beautiful picture from Karen, and generous donations at the Penguin Dinner on Wednesday night, the conference has now raised between AU$ 35k and 40k towards the Save the Tasmanian Devil appeal. Around AU$ 1.3k of the nonsensical winning consortium s AU $10.6k bid came from the Collabora folks who were at the dinner, and AU$ 1.2k from Collabora and Collabora Multimedia directly. We were all set to place a winning AU$ 3k bid but then Matthew and Daniel came up with the Bdale shaving scheme, and then things really picked up. I m glad we took part - the lead scientist from the project was really grateful, and I hope the money can make a real difference to their great work.
Telepathy
On more mundane matters, I also gave my talk this morning, and my slides (Telepathy slides v2.0 thanks to Marco) are online. I also made a few demos of new awesome stuff you can do with Telepathy (most of the patches are already merged upstream or well on the way): On that note, these were just the five that I picked to try and fit into my talk. There are a load more demos in the pipeline from the other guys in Collabora of doing stuff with Telepathy, so keep a close look on Planet Collabora for the next cool thing.

Joey Hess: a hairy tale

When I was a kid, I had a daddy with this moustache. One day, he shaved it off. I looked at the pale, exposed strip of lip, and demanded he grow it back. There are no images of this event, besides those burned into my brain. It was in simpler times. Dad did grow it back, and a beard too, and and now he's (great)-Grandpa Hess. Who, come to think, looks similar to my tie-died friend Bdale. Bdale is one of the Debian grandfathers, those old guys who the young ones in the project look up to. And today, he scarred all their minds. The collective shout of "grow it back!" is gonna be huge. Did I mention that it all involves Tasmanian devils, charity, and the mean razor of Linus Torvalds? These are not simple times.

Andrew McMillan: Summary of Paul's Perl talk

For the benefit of Debian users, here's a quick summary of Paul Fenwick's talk about cool stuff in recent Perl versions.

apt-get install libmoose-perl
apt-get install libpar-packer-perl
apt-get install libdevel-nytprof-perl
apt-get install libautodie-perl
apt-get install libperl-critic-perl
Now I have to integrate all that into my writing of Perl programs, which doesn't really happen frequently enough for such changes to become easily ingrained... Great fun, and it's tempting to install Windows just so I could run some of that stuff, but perhaps Paul hasn't realised that you can run Minesweeper under Wine?

Next.

Previous.