Search Results: "ag"

19 March 2008

Eddy Petrișor: News from other worlds

I was recently forced to face once more the limitations and quirks of rpm. This is more painful, when looking at a more capable system like .deb.

When building a .deb package, the debian/rules file is pretty much the heart of all things happening, with debian/control and debian/changelog as the lungs and the liver(? maybe) .

Having different files for the maintainer scripts makes possible things like automatic (but repetitive) generation/modifications of those scripts. This can be useful in some situations when the postinst should do stuff depending on the current contents of the released upstream source (sorry, I know I am being vague, but I can't detail too much). The source package is then generated and the resulting package can be rebuilt 1000 times and the resulting postinst will not be different for a given release. But this is always done in the same way, no matter the upstream version.

Fatality one - the spec is fixed, saint, but still can be altered... still, not in due time

So the basic idea is to have postinst.in as a source for postinst, which is created during the configure stage and later removed on clean. This is possible and works on deb.

Try the same on rpm and you will fail. This is because, although the spec file supports file inclusions, the altered files are merged into the spec right at the beginning of the build process, and you end up with no or an outdated postinst. A later rebuild of the same package would do the trick, but that is wrong for more than one reason.

Fatality two - why fatality one was met

All of this is made in order to overcome yet another rpm limitation: rpm can't assist too much on upgrades; you can't simply upgrade packages properly from one version to another, because rpm doesn't have the notion of letting the scripts know which version is installed over which; it only tells that it is an upgrade or not.

This has lead some people believe rpm isn't able to upgrade at all. Glad to tell them they're wrong (still rpm sucks and is brain dead).

Fatality three - why rpm based system fail to have upgrade support today

Want another RPM limitation? RPM has this brain dead idea that on upgrade the "proper" order and way to call the maintainer script(lets) is:
The numbers 1 and 2 are literally what is passed to the scripts and mean "the number of the installed versions of the same package that will exist after the current operation finishes". No versions of any kind, no other parameters, no rollback, no nothing, just 1 or 2.

And by letting the scripts of the old version run AFTER the scripts of the new one means that you have to explicitly prepare the packages for a later upgrade support (and the best idea is to do NOTHING in the old prerm and postrm scripts on upgrades, since nobody is clairvoyant to see what would be the right course of action for upgrade in future releases).

More bad ideas from the rpm land (glad not to be there)

In somewhat related news, the fedora people are discussing now around the rejection of being able to have package names contain non-ascii characters, characters like kanji, kanas, cyrillic characters or any other characters. Even if I am pro-l10n, this wreaks of bad idea scent from a mile afar.

They aren't probably aware that even unicode is broken (if you see the same glyphs in the comparison table, that is proof unicode is broken) but that is their decision and I am glad I am not in that lost land.

Marc 'Zugschlus' Haber: Universal boot stick for Debian, grml and the Debian installer

For various reasons, I have the kernel and the initrd that my notebook needs to boot Linux on an USB stick. I recently added the Debian Installer and grml to the stick to allow additional uses of the stick. Usually, USB sticks are formated with FAT32 and when they’re used to boot Linux, Syslinux or some derivative is used. I do it differently on my boot stick, most prominently because I’d like to have Unixoid privileges on the stick, and because I’d like to continue using grub. So, my stick is formatted as ext3, and feels like an additional hard disk. Booting from an USB stick is sometimes tricky. I have made the best experiences with formatting the USB stick as an USB ZIP, which basically means having 64 heads, 32 sectors and a single partition in the fourth primary partition slot. This can be done using mkdiskimage and is documented on Debian in /usr/share/doc/syslinux/usbkey.doc. Partitioning and generation of the file system is as straightforward as is installing grub using the standard, documented methods for hard disks. I tried using grub 2, but have found it not sufficiently well-documented and stable to be used in this kind of critical environment. I am therefore still using grub-legacy despite the fact that the grub maintainers have ceased fixing grub-legacy bugs some months ago, refering to the pending release of grub 2. I use unison to keep /boot on the stick in sync with /boot of the Linux system, which is on a crypted filesystem on the hard disk and thus unuseable until the system has booted. The hard disk /boot thus serves only as installation target and sync source so that the stick does not need to be plugged in during upgrades. update-grub is configured so that running it creates a menu.lst which can be used from the stick. This concludes booting the production system from the stick. For the other systems, I have decided not to put them in the “default” boot menu from menu.lst, but instead include foo.lst files to the root of the stick, and when I need them, shell out from the grub menu to a command line by pressing “c” and then pulling in the new grub config file with the “configfile /foo.lst” command. grml is my favorite rescue system. I use it all the time once a system starts acting up. One of its biggest advantages is its extremely flexible bootup process. That made it predestined to be the rescue system on my USB boot stick. grml is currently making a transition to a new build environment, which has had the side effect that the boot process has changed in some details. grml-small, the 60 MB variant that I had been using before, has been discontinued and replaced by grml-medium, a 170 MB variant which does definetely not fit any more on a business card CD, but 128 MB USB sticks have become relatively seldom. For both grml flavours, all one needs to do is mount the .iso file loopback, copy the file’s contents to a subdirectory of the boot stick, and to drop this menu file to the stick:

title           grml-small
root            (hd0,3)
kernel          /grml-small/boot/isolinux/linux26 toram grml_dir=/grml-small/GRML/ grml_name=GRML ramdisk_size=100000
init=/etc/init lang=us BOOT_IMAGE=grml
initrd          /grml-small/boot/isolinux/minirt26.gz
title           grml-medium
root            (hd0,3)
kernel          /grml-medium/boot/grmlmedium/linux26 live-media-path=/grml-medium/live/ toram=grml-medium.squashfs
lang=us boot=live noeject noprompt keyboard=de
initrd          /grml-medium/boot/grmlmedium/initrd.gz

Since grml-medium works reasonably well, I do not expect to need grml-small very often any more. The Debian Installer guys have published an initrd which can browse nearly arbitrary media for an debian-installer .iso file, mount it and install from that image. I have made use of that feature to allow Debian to be installed from my boot stick. /d-i holds a current debian-testing-i386-netinst.iso, and vmlinux and initrd.gz from http://ftp.nl.debian.org/debian/dists/testing/main/installer-i386/current/images/hd-media/. With that, this d-i.lst:

title debian installer
root (hd0,3)
kernel /d-i/vmlinuz
initrd /d-i/initrd.gz

does the trick and boots up the Installer, ready to start. I guess that it would be easily possible to include these grub config stanzas to the default menu.lst, including grml and the Installer into the main grub menu, but I deliberately decided not to have these options directly in the menu for the time being. It is always amazing how flexible today’s systems have become when it comes to boot Linux. For both rescue and installation, this is needed, and the respective authors have done a remarkable job.

Peter De Schrijver: Opus Iridium

Opus Iridium finally released ! Especially the downtempo part is very nice.

Pierre Habouzit: [RC-Bug-A-Day] Day 5

Today, I cheated a bit, and used my Release Assistant super powers, and removed from testing 2 packages with long standing RC bugs and no activity from the maintainers: See my hint file:
 #20080319
 # 467096
 remove traverso/0.42.0-1
 # 243363
 remove xcruise/0.30-8
edit: twinkle removal was a bit hasty, I totally missed that the bug wasn't RC from the beginning. And as a second thought I'm not either sure it's really RC.

Kartik Mistry: Raghudixit Project


* Got the album. Enjoying it!

Stefano Zacchiroli: git-buildpackage from debian-only to debian+upstream

Moving a git layout from debian-only to debian+upstream ... and live happily with git-buildpackage Let's say you have a git repository you have used thus far to maintain only the Debian part of some package (i.e. no upstream sources on sight). OK, you're right, that would be quite an uncommon scenario for a git repository. In fact the truth is that you are in such a situation because the git repo was obtained converting from a subversion repo which was using the mergeWithUpstream stuff of svn-buildpackage. Now that you have git's space efficiency you want to change this, import upstream sources, and possibly adhere to a branch layout which is compatible with git-buildpackage (which is very simple in its minimal requirements: an upstream branch containing just upstream sources and a master branch containing a debianized source tree). Out of the box git-import-orig won't work since don't have the upstream branch. Creating it branching from master (or somewhere else) won't work either unfortunately. Indeed after branching you will need to remove the debian/ dir from upstream and when you will merge upstream with master you will be merging the removal as well, bad idea. By myself I've found some horrifying solutions involving using git-filter-branch on the upstream branch merged from master and then squashing all the history of that branch with git-rebase, but they are so horrible that I won't mention them here more than this. The nice solution came from a hint by madduck on the creation of branches without ancestry. Here is the complete recipe (assumed to be run from the master branch of the repo, before creating any upstream branch):
$ git-symbolic-ref HEAD refs/heads/upstream
$ git rm --cached -r .
$ git commit --allow-empty -m 'initial upstream branch'
$ git checkout -f master
$ git merge upstream
$ git-import-orig --no-dch ../foo_1.2.3.orig.tar.gz

In short: you should create an upstream branch without any ancestry, in it you should create an empty commit, then merge it (vacuously) in master, and now you're ready to call git-import-orig to the rescue. Feature request on git-buildpackage to support this out of the box is on the go: bug #471560.

Adrian von Bidder: The Inevitability of Victory

Notwithstanding my recent nod to a sceptical article about Linux on the average user's desktop, I think that Linux has already won the “war” where it's important, namely in the minds of many people. (Yes, this is a response to Russel's posting with the same title.) Why? Because, first, many people do indeed see it as a war where there has to be a winner and a loser, and second, when I talk with people who never have seen Linux, or with people who'd never seriously consider switching to Linux (in business or for their home needs), most of them talk about not having tried it yet or it not being ripe yet. So the general expectation is that they'll only stick with (expensive, buggy, hated, ...) Microsoft software until they feel confident about switching. So the task is not to convince them that they should try Linux, but that they might want to try it now. Or at least that they might want to try Oo.org, the Mozilla family of programs, the Gimp etc. on Windows, so that they have an easy time when it's time to change the chassis underneath (is there a Windows port of Digikam?)

Russell Coker: The Inevitability of Victory

I just read an interesting blog post about Montenegro [1]. Apparently a key to the process of becoming a country was acting like it was inevitable. It seems that this method can be applied to many areas, one of which is the contest between Linux and some proprietary OSs. For many years monopolists have convinced people that it was inevitable that they would monopolise all areas of software development. Why use any other software (even if it is more reliable, faster, has more features, and is cheaper) if a monopolist is about to dominate the market? The monopolist changes sometimes, the monopolist from ~1990 to now is different from the monopolist of the 1970’s, but the tactics of a computer monopolist remain the same. The way to beat this is largely to just ignore them. There is an ongoing debate in some circles about when Linux will be “ready for the desktop“. I’ve been running Linux as my primary desktop environment since about July 1998, it’s almost 10 years of having Linux as my primary desktop environment. It seems inevitable that the Linux will take over the desktop - it’s far better for desktop use than it was 10 years ago when I switched. Some people claim that Linux lacks driver support. Every piece of hardware that I’ve wanted to use over the last 10 years has had adequate support. Often second-hand hardware works best with Linux, hardware vendors have no reason to continue to support their old products on newer operating systems (they make more money if you buy new hardware to run the new OS). Not only is hardware support for Linux adequate, but long-term support is far superior (and I often get to use cheap second-hand hardware). Now that an increasing number of hardware vendors are supporting Linux for their new hardware (Intel, AMD, and most laptop vendors are doing some good work in this regard). It seems that everyone who has tried both says that writing drivers for Linux is easier than writing drivers for proprietary OSs, so it seems inevitable that Linux will end up with better driver support by all metrics. Linux is designed for users. DRM (Digital Restrictions Management) is not something that interests Linux developers. Run Linux and your computer will obey you and give full quality audio and video. It seems inevitable that Linux will dominate the AV section of the market (it already dominates the computer work involved with creating movies). Free software (of which Linux is merely the most famous and popular example) is based on the principles of open design and open standards. When you use a free software program to save a file then you can be reasonably sure that you will be able to read it back again in a few decades. Most free software uses file formats that are well documented and standardised. Sometimes there are bugs in programs and new versions will use files in a different way, this is sometimes a case when you rely on a bug in an old version. Using the older version of the software is sometimes required to properly access old data. Fortunately when you have the source to the older programs they can be compiled on new systems (so different types of CPU won’t matter). Also the lack of DRM means that an OS image can be virtualised. One thing that is on my todo list is to create a set of virtual machine images of some of the most commonly used distributions of Linux so I can easily compare distributions of 10 years ago with modern distributions - it’s not technically challenging and there is no particular technical or legal obstacle to doing this. This would also mean that if someone gave me a file in some strange format from 10 years ago I would have a better chance of reading it. It seems inevitable that as the value of data increases the desire to avoid OSs that prevent people from accessing their own data will also increase, and that will eventually squeeze out most closed software from the market. This doesn’t mean the end of proprietary software, merely the end of software that holds user’s data hostage. The majority of the world’s population does not use computers. The computers that they end up using will be cheap because they can’t afford to waste so much money on new hardware. To make cheap machines means that there will be limited resources in terms of RAM, mass storage, and CPU power which require more efficient software. Also to properly take advantage of machines with small screens and other limitations changes to the design of the software will be required. It seems inevitable that the most open software will be adapted to such environments more readily than proprietary software. Now this doesn’t mean that we can take a break from development. In the free software community there are usually many different programs to perform a particular task with competition between the developers of the various projects. The fact that a monopolist is inevitably going to lose it’s position is of little relevance to the competition between the various free alternatives.

Wouter Verhelst: Generating ogg theora from individual frames

Hello World, When I have absolutely nothing useful to do (which has been quite a while ago now), I sometimes like to play with povray. Not that I'm very good at it—I'm a programmer, not an artist—but it still is good fun. What I usually prefer doing is creating an animation. This is rather easy with povray; you can have it modify certain values in your scene based on some "clock" variable, and then generate a series of different frames based on that one scene description. This creates a large number of image files in the format that you specified (say, .png) in your output directory. Of course a number of frames is not an animation yet. If you want that, you need to do some postprocessing on these images. ImageMagick to the rescue.
convert foo*.png foo.mpg
This works, but I don't like the low quality which the MPEG2 format gives me; and it also requires me to install the non-DFSG-free and slightly buggy MPEG2 reference implementation before it'll work. That's not very nice. What I'd really like is for something similar that will work with Ogg Theora. So, dear lazyweb, is something like that even possible? This would preferably not require me to know too much about Ogg Theora, but just take a bunch of files and output a .ogg file—much like the above convert command line. Thanks,

18 March 2008

Christian Perrier: Debconf localization stats feed on my blog

I just added a blog category in my good old Blosxom blog with gathered stats about the progress of various languages towards the 100% Grail for lenny (NMU campaign in progress...which will last until the lenny release). It is not syndicated in Planet Debian as this could sound boring to others. If you want to follow this, just go there. PS: all this is completely manual. No automation involved...:-). And, yes, it's named "l10n-fr" but all top-leading languages are followed. And, this time, the goal is to bring as many of them as possible to 100% (French, German, Portuguese can make it...I'm unsure for Czech).

Robert Edmonds: vmware-package 0.22

vmware-package 0.22 was just uploaded, which supports the just-released versions of vmware workstation / player / server. most of the changes went to dealing with the newly sensitive dpkg-shlibdeps(1).

awesome:
Index: trunk/share/vmware/debian/rules
===================================================================
--- trunk/share/vmware/debian/rules     (revision 57)
+++ trunk/share/vmware/debian/rules     (revision 63)
[...]
+       # stupid stupid stupid stupid stupid
+       ln -sf libcrypto.so.4 debian/vmware-server-mui/$(lib_dir)/lib/libcrypto.so.0.9.7
[...]


ugly ugly build logs for 5 upstream packages x two suites x two archs are here:

http://people.debian.org/~edmonds/vmware-package/build-0.22.etch-amd64.txt
http://people.debian.org/~edmonds/vmware-package/build-0.22.etch-i386.txt
http://people.debian.org/~edmonds/vmware-package/build-0.22.sid-amd64.txt
http://people.debian.org/~edmonds/vmware-package/build-0.22.sid-i386.txt

Axel Beckert: MicroClient Sr.

About a year ago, I bought a Norhtec MicroClient Jr., a complete 200 MHz MMX-compatible SoC (“Vortex86”) PC so small that it fits into your hand or onto VESA mountings. Althought thought as thin client, the machine has 128 MB RAM and runs Debian from either netboot, USB stick, CF card or 2.5” harddisk without problems and not even that slow. Later last year, we needed more MicroClient Jrs. at work and since the MicroClient JrSX had a 300 MHz 486SX-compatible SoC processor (“Vortex86SX”) from MSTi and 128 MB DDR RAM instead of SD RAM, we expected them at least in the same performance range and bought a few for ETH and I also bought one for myself. Well, they were about three times slower, since the FPU is missing, not all programs from Debian Etch work fine, e.g. X doesn’t work without patching and recompiling (with Sid, X works, but not the kernel anymore)… BTW: I had both machines with me at FOSDEM ‘08 at the Debian booth and the MMX-compatible machine also at Chemnitzer Linux-Tage (CLT) at the Symlink booth and in Kurt Gramlich’s talk about ecological computers. So if you saw them there, just imagine the same case, with a twice to three times faster CPU and four times the amount of RAM, but with roughly the same carbon foot-print! For our thin client purposes at work we now use ALIX boards from PC Engines (Mini-ITX format) with 500 MHz AMD Geode processors. They’re much faster than the MicroClient Jr. and need even less power. Today, while surfing around on some Mini-ITX shops, I found some computer in obviously MicroClient Jr. case, but with 500 MHz VIA Eden processor and 512 MB of RAM. I first couldn’t believe it. They are selling it as eTC-2500. Since eTC-2300 was one of the brandings of the MicroClient Jr. which is called eBox-2300 officially by the manufacturer DM&P, I searched for eBox-2500, but didn’t find anything useful. Then I looked at the manufacturer’s product page at CompactPC.com.tw and found the eBox-4300 — so it’s really true, they managed to fit a board with 500 MHz VIA processor and half a Gig of RAM into the already fscking small space inside the MicroClient Jr. case, and even without needing more power: Still 15W from the power adaptor. Next stop was Norhtec’s Website. And yes, they also have a new MicroClient product: The MicroClient Sr.. I really need to have one of those for my MicroClient collection! ;-)

Neil Williams: GNOME 2.22 and GPE (gpe-filemanager to be exact)

This could be fun - gpe-filemanager is not currently available for Emdebian because it depends on libgnomevfs which in turn brings in a variety of other dependencies ending up with liborbit2 which simply does not (and appears cannot) cross build.
Thankfully, GNOME 2.22 deprecates libgnomevfs in favour of GIO which is already part of libglib2.0-0 and only needs other stuff via plugins.

I need now to port deb-gview to GIO and, in the process, probably see if gpe-filemanager can also be ported to GIO. After all, a GUI without a file manager is going to look a little odd.

I'm still working on libqof2 upstream too so it looks like I won't be doing much on Lenny for a while - not directly at least.

I expect to have deb-gview 2.0.0 depending on GIO and in Lenny and maybe quicklist too. (Typical, no sooner does quicklist migrate from Gtk1 than it also needs to migrate from libgnomevfs.) Then there's all my usual Debian and Emdebian stuff.

Romain Francoise: GNOME 2.22 in sid: check (mostly)


The status page speaks for itself: most of GNOME 2.22 is now available in sid. A few packages are being staged in experimental to avoid breaking too much stuff, and a few of the remaining missing pieces are waiting in NEW. Special thanks to Sebastian Dr ge who's done an incredible work with more than 90 uploads over the past week!

Patrick Winnertz: switched from kde3 to kde4

Yesterday I made the switch from kde3 to kde4. But before I dumped all installed packages into a file ( if I have to restore) and backuped my configuration files for kde. After some fiddeling with kde4 and the dependencies I had a full kde4 installed. My problem was that:
apt-get -t experimental install kde4

won't resolve all dependencies... So my apt-get line was quite long. (After I was finished, I thought that maybe pinning would be a better idea). In general kde4 is usable, but there are some quite annoying things: But of course there are quite many improvements, I'll list here only those which I consider very useful :) Some things which are definitly missing in kde4 (which have to be ported to qt4) are kpowersave and knetworkmanager. Furthermore kontact and amarok, but there is work in progress.

Adam Rosi-Kessel: Bridge Year

This, from my alma mater, is a good idea:
Group to explore creation of ‘bridge year’ program
Princeton President Shirley M. Tilghman has appointed a working group to explore the creation of a “bridge year” program that would allow newly admitted undergraduates to spend a year of public service abroad before beginning their freshman year. The program would enable students to pursue a tuition-free, pre-collegiate enrichment year outside their home country with support from the University.
I finished my high school requirements early and spent a year abroad before college in Li ge, Belgium. It was an excellent decision. There would have been practically no benefit to starting college early, and having living abroad without my parents for a year was as important to my university experience as most of what I learned in high school. I propose that some sort of “bridge year” become something like a default option before higher education. This is much more common outside the United States. Indeed, depending on whom you believe, only seven to twenty-five percent of Americans own passports. My completely unscientific survey of Australians, by contrast, suggests that every last one of them travels abroad as young adults. (I have to admit that this survey is not only unscientific but fatally biased, inasmuch as I’ve only met Australians traveling abroad, not having been there myself). While I’m praising Princeton, this, too, is good news:
Aggressive goals set for sustainability initiatives
Princeton has committed to reduce its carbon dioxide emissions to 1990 levels by 2020 as part of a comprehensive Sustainability Plan that sets ambitious goals in the areas of greenhouse gas emissions reduction, resource conservation, and research, education and civic engagement.
I’ve a big fan of Shirley Tilghman, Princeton’s first non-male non-alum president. She has been working to fix a lot of what was wrong when I was student, despite some stiff resistance from the old guard. Technorati Tags: , , ,

Enrico Zini: make distcheck and LaTeX

make distcheck and LaTeX When building LaTeX documentation on a VPATH build, if your .tex file includes other files in the same directory, LaTeX will complain that it cannot find them. The reason is because in a VPATH build, latex is invoked like this:
latex ../../doc/manual.tex

What we need here is an equivalent to cc's -Idir for latex. latex --help doesn't mention of such an option, nor of useful environment variables. Googling a bit seems to suggest --include-directory=dir, but that gives me: unrecognized option '--include-directory=../../doc' The manpage doesn't list commandline options. It however says:
The complete documentation for this version of TeX can be found in the info file or manual Web2C: A TeX implementation.
Without saying where that manual is, if it's installed and where, or what package installs it, or if instead should I look it up on the web. info latex gives the manpage itself, of course. Googling the title of that manual finds it, and it's a long one. Reading through, it points at the kpathsea manual, which then mentions you can set TEXINPUTS_latex, which however doesn't add but overrides, so your document will find the includes maybe, but not the LaTeX styles and other stuff. But then later on it mentions that in the env variable you can use "default expansion", and it's another page of manual to read which tells you to put an extra colon in the end of the env var. After half an hour of googling and trying things and cursing loud, here is the solution, which I hope will save others from this ugly search.
%.aux: %.tex
    TEXINPUTS="$(srcdir):" latex $<
# Oh, yes, and bibtex requires BIBINPUTS instead
%.bbl: %.aux
    BIBINPUTS="$(srcdir):" bibtex  basename $< .aux 

Julien Danjou: Are chickens hacking?

I was just taking a look at #awesome IRC stats, and I saw that there was a huge traffic 2 days ago. That was weird, so I did take a look in my log files. And yes, in fact, something happened. At 03:26 GMT+1, suddenly, several hundreds of users joined the channel in somethng like 1-2 minutes, and then just left in same timeline. Some minutes after that, some guys began to talk with one of the real awesome user who was hanging out there. It seems that these guys describe themselves as a "Turkey Hack Team". I've seen a lot of hacked box in my (short) sysadmin life. Many of my customers have no idea of what security is, and this week I'm still working for a customer with an hacked box. And one of the thing I never got was why all these "hackers" were downloading and installing IRC bot or IRC proxy on these compromised boxes. I say "hackers" with big quotes, because when I see in their command line history somethings like "rm .bash_history; logout" or "./exploit_of_dead_to_become_root" when the user they got the password has sudo right, I must laugh. Now, I understand: it seems there are doing some sort of "parade", making all their bots joining an IRC channel and then left. That's so amazing. that I can say for sure: if I'd be a chick, I'll be stripping my shirt vehemently. But the thing is that so far I've no idea if a turkey hack team is somehow related to chickens.

17 March 2008

Dirk Eddelbuettel: Google Summer of Code 2008 projects are up

For the past few years, Google has been running their Summer of Code events where Google offers $5000 for college students who are asked to code for a summer for the benefit of various Open Source efforts. And just like in 2006 and 2007, I put up proposals and offered to act as a mentor. The first one is up at both Debian and R: an opportunity to help with the ongoing efforts of 'turning more CRAN package into Debian packages'. The second one is only at the R page: a proposal to fill the missing link of DBI database interface modules with a matching one for PostgreSQL. More details for either idea are at the respective pages. Anybody interested should ping me by email.

Dirk Eddelbuettel: 2008 March Madness Half Marathon in Cary

Yesterday was the annual March Madness Half Marathon in Cary, IL -- and this year marked the 30th anniversary of the race. The race is getting more and more popular as the start to the running season, and an early race for those in Spring marathon training. This year, and it had sold out in a matter of days. As for the race, I wasn't running it all that well. My legs already felt heavy when I was doing a casual four-miler the day before with our local running group. Similarly, I didn't feel all that loose yesterday. By mile four or five I was getting into a decent rhythm, and I was then running fairly steady 7:15s until about mile 11 when I ran out of gas and had to slow down. Final time was 1:36:38.15 -- not only several minutes slower than last year's but also slower than two years ago.

Next.

Previous.