Search Results: "ag"

25 July 2007

Matt Brubeck: 25 Jul 2007

Retiring from Debian In response to the inactive developer ping, I have decided to retire from the Debian project. Between my job and the new baby, my time for hacking on other projects is nonexistent, or possibly negative. I have already passed Audacity maintainership to the debian-multimedia team. I still use and like Debian, and I hope someday I'll return from "emeritus" status to become an active developer again. Cyclone While browsing through some very old backup files, I rediscovered one of my first real software projects, an IRC client for BeOS. This was a neat collaborative effort, but we weren't really on the ball with project hosting or version control. This is from a file I wrote documenting what was left of the project after it stopped:
Cyclone was started in spring 1998 by a group of developers who hung out in the #bedev channel on EFNet. The original Cyclone team included Jason Gosnell (Avatar), Jeff Hamilton (Pyrus), Matt Lewinski (mattl), John Wiggins (prok), and Matt Brubeck (mgb), with contributions from several other #bedev regulars. The Cyclone project produced a small, elegant IRC client. Unfortunately, the team dissolved as several members moved around the country to go to new schools or jobs at the end of summer 1998. Along with the loss of some important pieces of source code, this prevented Cyclone from ever seeing a public release.
I also found some poetry I wrote in middle school, but it's compressed using a version of StuffIt that does not seem to be compatible with any open source tools. This is probably a good thing.

Wouter Verhelst: The iPhone

... sucks. As this page aptly explains. Not that I need an E70 or anything, but it's pretty well done. Well, perhaps not well done. And not G-ratedly done. But still, done.

John Goerzen: OSCon Wednesday

Nat Torkington, program chair, started off the day. He commented that one of the most interesting trends these days is the expansion of the Open Source ideals beyond software.

Tim O'Reilly commented about the FSF's four freedoms, and asked how we maintain them. We have to think about preserving freedoms -- questions such as Free Software that relies on proprietary services, data, or business processes. It's important to remember to pay attention to freedom and not just to the success of businesses. But businesses matter and have enormous power and will always be related.

Tim really pushed expanding the boundaries of Open Source and thinking ahead: wikipedia, OpenID, etc. He also asked: does Congress need a version control system?

He suggested there are four open source success factors: frictionless software distribution, collaborative development, freedom to build/adapt/extend, freedom to fork.

Hadoop is an interesting FLOSS project to build some infrastructure like Google has. Apparently Yahoo is very interested.

Back to Nat... hardware is cheap and everyone keeps buying more of it.

James Reinders from Intel talking about multi-core parallelism. Saying that parallelism is going to be more and more important. Intel released threading building blocks, a series of templates for C++, as GPL'd software at the conference this week. I'm not all that excited about a C++ project, though, since I think languages like Haskell have more promise here anyway.

The other Intel guy mentioned Intel's open source involvement: intellinuxgraphics.org, intellinuxwireless.org, linuxpowertop.org, kernel,org, moblin.org. Linux laptops have the longest runtimes compared to other laptops.

"It's amazing how many people you can make paranoid by showing up with a tie and a suit to do a keynote at OSCON." -- James Reinders

Simon Peyton-Jones is up now, and Nat says he will "stretch your brain until only tiny bits are left."

State of the art in parallelism is really 30 years old with locks and condition variables -- like building a skyscraper out of bananas.

Locks are difficult to do right and have "diabolical error recovery".

Let's do transactions against memory instead of against a database. Implementation can even be similar to databases. The idea is transactional memory, and it sounds very, very slick.

Mark Shuttleworth and Tim for an interview...

Mark was fine, but I wish Tim had more interesting questions for him.

I went up to the front a few minutes after the event to talk to Simon PJ. He was talking to someone, who saw my nametag, and said, "Hi John, nice to meet you." He looked familiar but I couldn't quite place him, so I asked who he was. "Mark Shuttleworth." Yep, I was sitting just far enough back from the stage that I wasn't behind one of the large TV screens and couldn't make out faces real well, and I didn't recognize him. Erg..

Evan Prodromou: 6 Thermidor CCXV

At DemoCampMontreal3 last night, I quoted Ward Cunningham, who once said that making a wiki link is a great way to ask a question. A year or so ago, I got interested in citizens arrests. What are those, anyways? How do you do it? Is it even really legal? So I started How to Make a Citizen's Arrest on wikiHow. Just a little while ago, it became a featured article on wikiHow. And just a few days ago, it was quoted in an article on Time Magazine's blogs: We Don't Need No Stinkin' Badges. Interesting to see how these memes gather momentum. tags:

Scott James Remnant: Online Desktop

Havoc’s keynote at GUADEC was extremely interesting, especially for how it polarised the people present. Several people seemed very upset with the notion that f-spot should be replaced by flickr, but I think that was a problem with the way that Havoc presented the message, and not the underlying idea. Instead consider f-spot and flickr as sharing the same collection of data, and being two different ways to view and manage it; with changes from one appearing in the other. The mechanism isn’t important. Consider the following: Now, isn’t that cool?

Martin F. Krafft: They could be onto something

The Neue Z rcher Zeitung relayed today the warning by the US American TSA (travel security agency) that terrorists may be practicing attacks on airplanes (in German) (sic), because the USA has recently found loads of highly suspicious substances all over the place. I love the warning, which states that they could be practicing attacks. They could also be tanning on the beach somewhere and laughing their ass off at the idiots in Washington. And the rest of the world, who have not enough guts to stand up against the crap emerging from the White House but instead just shamble along like brainless ducklings. Some have claimed that the terrorists have already won because nothing is as it used to be, and fear and chaos are spreading. I agree. I'll also claim that they're highly successful recruiters: after all, the governments of the Excited States of America and most of the European nations who like to grease up to Washington have long joined their ranks and are now themselves terrorising their people. Yet, if you ask them, they'll deny it. Brilliant recruiters. NP: Dominici: O3 A Trilogy - Part 2

Adam Rosi-Kessel: Netflix Outage

Netflix was offline for nearly 24 hours — almost weeks in Internet time for a business whose entire existence is online. It was astonishing, at least to me, that a major Internet service could be disrupted for so long. According to my people on the ground in San Francisco, a transformer explosion was the cause. It’s a good reminder that the Net is more fragile than we might think. UPDATE: the original source in California recants. The Netflix outage remains a mystery. Explanations are welcome.

24 July 2007

Joey Hess: review: HP t5725 thin client

Today was HP day again. Kinda like Christmas, HP day is when I wake up to some new HP hardware in a box under the mailbox on the porch. For some reason, HP keeps sending me hardware, and this time they shipped me a HP t5725. It's kinda funny what's called a "thin client" these days. This box has 512 mb of flash memory, no moving parts, and is silent. Other than that it's a fullfledged desktop machine in a very nice smallish package. The OS is a very lightly modified Debian sarge. They did a good job at adding their tweaks without getting in the way of Debian. I was able to install whatever additional packages I wanted on the hundred+ megabytes of free space. Most users will probably be perfectly happy with the preinstalled system, you can surf the web, etc. This was one of the few preinstalled systems that I've actually used for more than 10 minutes without wanting to blow it away with my own custom install. If felt sorta silly to do so, but I'm installing testing on it right now via netboot. ... That went fine, no issues whatsoever. Though on a system with this size disk, tasks are useless and every package must be hand-picked right down to the xorg video driver packages. So it really is a thin client for me, NFS root is a good way to go, and means that I have a machine on my desk that I can use as a workstation, and easily reboot to use as a d-i and rootsync testbed, without worrying about preserving the contents of its disk.

Russell Coker: An Ideal Linux Install Process for Xen

I believe that an ideal installation process for Linux would have the option of performing a Xen install. The basic functionality of installing the Xen versions of the required packages (the kernel and libc), the Xen hypervisor, and the Xen tools is already done well in Fedora and it’s an option to install them in Debian. But more than that is required. Xen has two options for networking, bridging and routing. The bridging option can be confusing to set up and changing a system from routed to bridged networking once it’s running is a risky process. I have documented the basic requirements for running bridging in a previous post, but it would be better if there was an option to have Xenbr0 as the primary device from the initial install - and there are non-Xen reasons for doing this so it would be a more generally useful feature. Another common requirement for a Xen server is to have a DVD image on the local hard drive for creating new DomU’s. If we are going to need a copy of the DVD on the local hard drive for Xen installation and we need data from the DVD for the Dom0 installation then it makes sense to have one of the early installation tasks (immediately after running mkfs) be to copy the contents of the DVD to the hard drive. Hard drives are significantly faster than DVDs - especially for random access. It would also avoid the not uncommon annoyance of getting part way through an install only to encounter a DVD or CD read error… Here are some reasons for running Xen (or an equivalent technology) when not running more than one DomU:
  1. Avoid problems booting. Everyone who has spent any significant amount of time running servers has had problems where machines don’t boot. Even with a capable out of band management option such as the HP ILO it can be unreasonably inconvenient to fix such problems. Separating the base hardware management tasks of the OS from the user process management tasks makes recovery much easier. If a DomU stops booting then it’s easy to mount it on the Dom0 and chroot into it to discovere the problem.

  2. Easier upgrades. Often you have users demand that you install software that only works with a newer version of the OS. You can install the new version under a different DomU, test it, and then replace the old DomU when you think it’ll work - this gives a matter of minutes of down-time instead of hours for the upgrade. If the upgrade doesn’t work then you destroy the DomU and create one for the old version. Running two versions of the OS at the same time with NFS shares for the data files is also possible.

  3. Security. If a DomU gets cracked the Dom0 will not necessarily be compromised, this puts you in a good position to track down what the attackers have done. You can get a dump of the DomU’s memory to enable experts to examine what the attackers were doing. Reinstalling a DomU to replace data potentially corrupted by an attacker is much easier than reinstalling an entire machine.

Even in situations when reason #2 was the motivation for installing Xen I believe that most systems will want to have a Xen DomU running the same version as the Dom0 for the initial install. Therefore integrating the installation process would make things easier. Among other benefits if you have a server with multiple CPUs (the minimum number seems to be two CPUs on all recent machines) and hardware RAID then doing two installations at the same time is likely to give better performance overall. Also I believe that it will often be the case that the Dom0 will exist purely to support DomU’s, therefore if you only install the Dom0 then you have done less than half the installation! For a manual installation there are some reasons for not doing this all at the same time. Having the sys-admin enter configuration data for some DomU’s at the same time as the Dom0 can get confusing. However for an automated install this would be desirable. I would like to boot from a CD and have the installation process take all configuration from the network (either via NFS or HTTP) and then perform the complete installation of the Dom0 and the DomU’s automatically. Let me know what you think of these ideas, it’s just at the conceptual stage at the moment.

Uwe Hermann: Download videos from Youtube, Google Video and others using Linux [Update]

Many online video sites such as Youtube, Google Video, Dailymotion, Metacafe, and others only provide limited or inconvenient access to the videos; either they require you to install the proprietary Flash player (and I surely won't do that), and/or you can only view them online (but not download them). There are some solutions, each with advantages and disadvantages: After the download, you can either view the videos using (e.g.) mplayer, or recode them into a more sane format. For all of the above programs there are Debian packages available, except for VideoDownloader/UnPlug (but you can easily install those from within Firefox). Update 2007-07-26: Added UnPlug and swfdec (thanks Joe Buck and Josh Triplet for the comments).

Martin F. Krafft: A user-space filesystem for mail labeling

I am still looking for a solution that allows me to tag my mails similar to what Gmail offers. Having thought about this for quite a bit now, I can see three solutions, implemented at different levels in the mail flow: as filesystem, patch to the IMAP server (Dovecot), or patch to mutt. Since this post is about the filesystem, I'll concentrate on that, but I'll also touch upon the other two solutions briefly.
A bit of theory First, let's dig into the theory and requirements for a bit. Instead of sorting mails into folders (one mail can only ever live in one folder), I want to tag my mails, such that a single message can have multiple tags and hence be relevant to multiple categories. If you want to think in terms of folders, then a single message could be attached to multiple folders, e.g. via hard links. This is what Mairix approximates. The problem with this approach is that simple operations, such as deleting a message (removing it from the enclosing folder) or marking it as read (renaming the file) only affect the message in the current folder, not its duplicates/clones in the other folders. So it's best to stay with a single file per message and to associate tags with it. Here, two approaches seem plausible: (a) extracting tags from the individual message files, and (b) storing tags/message pairs in a separate database. I have a gut feeling that (a) is the better approach, especially since the files we're dealing with all have the same format. And in fact, there is a semi-standard header for email messages to store such tags: X-Label. One more paragraph of theory: instead of simple tags, like Gmail provides, I want hierarchical tags, for instance:
X-Label: Debian::pkg::mdadm
X-Label: Debian::popcon, PhD::Debian::stats
Hierarchical tags work similar to folders in that any message tagged as Debian::pkg::mdadm also belongs to the Debian::pkg and Debian categories. No rocket science.
mutt Now it would probably be trivial to hack mutt and add a new layer of I mentioned earlier that this could be implemented in various places, and I'll start at the highest level, with mutt, the mail reader. For quite a while now, mutt provides search operators for the X-Label header, such that you can search or limit your mailbox e.g. like so: ~y \\<PhD::Debian\\> ~y \\<popcon\\>. The problem with this approach is that it reuses existing functionality, which I need on a regular basis: searching and limiting. Furthermore, I think this approach is hackish and brittle and exposes too much of the underlying workings. filters, which would be used in addition to the user-specified limit. On a high-level, the user would set a tag expression, like PhD::Debian ::popcon, and may additionally choose to limit the display of messages to those sent from the debian.org domain: ~f debian.org$. mutt would then assemble the pieces and apply the filter (~y \\<PhD::Debian\\> ~y \\<popcon\\>) ~f debian.org$ to the current view. With a reasonable user interface to specify or pick labels, as well as a simple label editor, this would almost cut the mustard. Thanks to the header_cache patch (which also indexes the X-Label header), mutt fares reasonably well on Maildirs with thousands of messages (well, not always), and binding keys like s (save) and d (delete) to appropriate actions to add and remove labels determined from the destination or the current tags filter, would make mutt a force to be reckoned with.
Dovecot Unfortunately, implementing this in mutt would mean that I'd be bound to the mail reader forever (and I like to pretend that's not the case, haha!). An alternative would be to implement this on the IMAP server, which already provides IMAP folders which are not necessarily bound to physical, filesystem folders and can intercept all commands that manipulate messages or their status. But while in theory this works fine, it'll break when offline tools, such as offlineimap come into play, as those (need to) instantiate every message they download, which brings us right back to the problem with duplicate/cloned files discussed before.
A filesystem idea Trying to stay independent of the tools I use, I started playing with the idea of implementing mail message tagging at the filesystem level, using Fuse. The user would run a daemon process against a given Maildir holding all mail (the base store) and export a virtual directory hierarchy in which tags become Maildirs, backed by a cache of X-Label:filename pairs.
  • the root folder contains one Maildir dor every tag present in all messages in the base store.
  • each of those Maildirs, in addition to the new/cur/tmp directories, provides a subdirectory for every tag minus the ones already in the path, recursively. Navigating to /PhD/Debian::pkg would result in a logical-AND query for all messages tagged PhD (and thus PhD::*) and Debian::pkg. I am not sure how to implement OR and NOT queries yet.
  • every Maildir in the entire hierarchy contains the messages satisfying the query inherent in the path.
  • the special directory /INCOMING can be used to write messages to the hierarchy in such a way that the cache gets updated. Alternatively, one could register inotify hooks with the kernel on the base store and let others write to it as usual.
  • the special directory /::UNTAGGED might enumerate all messages without any tags.
The virtual directory hierarchy should also export the familiar filesystem semantics:
  • creating a file automatically adds the tags encoded in the file's path.
  • copying, linking, and symlinking a file within the hierarchy are all equivalent and cause the tag associated with the destination to be added to the file.
  • copying, linking, and symlinking into the hierarchy should probably result in an error, unless the source is clearly an RFC822 message.
  • mkdir creates a new tag in the cache, but without any files associated with it.
  • rmdir removes tags without any associated files.
  • rm on a file removes a tag from a file. rm -r on a directory removes the associated tag from all files (and the cache).
  • moving files is equivalent to copy-remove, but needs to be atomic.
Unlike tagfs, which uses an external SQLite database for tags, this filesystem should not use an external database for tags, but rather a run-time cache. That way, tags can be propagated to other machines with IMAP synchronisation tools. Initially, I thought such a fileystem could even be deployed "underneath" the IMAP server, but then we obviously run into the same problems with offline tools as before. Potentially, such a filesystem could be incredibly powerful as it could do its work for any user agent directly dealing with Maildirs (such as mutt), and it could also be used as basis for an IMAP server which is only ever accessed synchronously (in online vs. offline mode). In the latter case, one would have to ensure that filenames don't change across IMAP operations, or use the message IDs instead from the start. But as good as it may sound, getting it to work right will require quite some attention, I think. Especially guaranteeing filesystem atomicity, as required for Maildirs, might be impossible through the Fuse layer.
The sad end Unfortunately, I don't have the time to implement any of the above, but if I did, I would probably try to patch mutt first, even though such a patch may not make it into the upstream source any time soon. The filesystem idea sounds cooler and cleaner, but it does not yet support OR/NOT queries, and it will be quite a task to implement and debug. On the other hand, dealing with Maildirs of several thousand messages in mutt is a bit of a pain if those Maildirs are being updated externally (e.g. mail is delivered to them). At least the idea is out now. If you are interested and want to work on this, please let me know so that I can link you up with other interested people. And if you have any other input, please let me know. And no, I don't really want to install emacs to read my mail. NP: Dream Theater: Train of Thought Update: I've created a mailing list for public discussion of this topic, so please subscribe if you're interested. Thomas Viemann suggested to use IMAP flags for the task, as these are standardised. However, I see two show-stoppers here: first, I am not sure whether it would be possible to set those flags from procmail on delivery (sieve can supposedly do it, but I consider sieve not adequate for my needs). And second, offline tools, such as offlineimap, which map IMAP folders to filesystem Maildirs, would have exactly the same problem with representing affiliation of a single message with multiple tags. You can read up on the discussion in the archives of the offlineimap mailing list, and soon the new mailtags list. Martin Scholl had the idea to extend dbmail with the concepts of virtual folders (or stored searches). Naturally, as database-backed mail system, it would be trivial and fast to implement, but this approach bears two problems for me: first, it also falls short with respect to offline tools (see above), and second it would require me to replace my entire mail infrastructure. I am not even considering the implications of using a database for mail storage.

Neil Williams: Use quilt in emdebian-tools?

I've only taken a quick look at the quilt documentation but the
following thoughts occur to me:
  1. emsource / emdebuild are similar to quilt and in some ways, I have
    reimplemented a subset of quilt in these scripts.

  2. emsource handles 'quilt add' provided that changes are confined to
    files in debian/ (including new patches added to debian/patches).
    However, I was unable to find out how quilt handles unchanged files.
    e.g. emdebuild skips creating the patch if the diff is empty - does
    quilt do the same for files that have been added?

  3. quilt is targetted at "upstream builds" and it will require various
    config settings to get quilt to both keep patches outside the package
    source directory AND handle situations where the package itself uses
    quilt with a different series of patches. emsource and emdebuild are
    completely separate from any existing patch method.

  4. quilt does NOT make autobuilding emdebian packages easier. Conflicts
    are meant to be resolved by hand (e.g. emdebian-changelog.patch). A
    bespoke method can embed specific logic on handling such issues that a
    general method like quilt cannot.

  5. quilt could be *almost* as transparent as the current method (which
    hides nearly all patch management within emsource and emdebuild) but
    would still require a wrapper to add support for keeping the patches in
    SVN.



Hmm. Think I'll stick for now. You can have too many nested tools.

Christian Perrier: Brice so nice

Brice Goglin just announced that he considers the bug triage task on the XSF bugs nearly completed. This graph shows the result of that giant work. So, please, be impressed in case you never noticed that work and just buy Brice a beer next time you meet him. And then go back cleaning out your own packages' bugs, of course..:-)

Evan Prodromou: 5 Thermidor CCXV

24 July 2007 is the fourth birthday of Wikitravel, the free travel guide that I and my wife Michele Ann Jenkins started on July 24, 2003. It's been a long and complicated road, but I'm really proud of all the work Wikitravellers have done over these last four years. The project has gone from being a pretty-good idea to being one of the definitive travel resources on the Web. Winning the Webby Award for Best Travel Site this year was a real recognition of that trajectory. I'm wondering what 24 July 2008 will bring... it will be interesting to see. tags:

Vinismo It's only partly a coincidence, then, that today I'm launching, with my friend Niko, a new Open Content project dedicated to demystifying an even more complex and byzantine world: wine. Tonight we're demoing the site at DemoCampMontreal3, so it's as good a time as any to throw open the doors:
        http://vinismo.com/
We don't pretend to be wine experts or even connoisseurs. We're just two guys who like to drink wine and want to learn more about it. Ward Cunningham once said that wiki link is a great way to ask a question. We want to share the learning experience with people of all levels of expertise. We think that working together with our friends and family, with other Internet users, and with the public at large, we can create a detailed, readable, useful wine guide for people at any level of expertise. Our liberal Creative Commons license means that the guide is Free -- free for anyone to copy, modify, or publish in any medium. I need your help to make this project a success. If you can, I'd really appreciate if you could help us out with one or more of the following tasks:
  • Please sign up to use our site at, and create a user page describing yourself.
  • Drop us a note in the Wine Bar letting us know what you like and don't like about the site.
  • Try adding some information about your favorite wines, wineries, wine regions or wine styles! It doesn't have to be perfect -- every little bit counts!
  • Please forward this info to people you know who might be interested in Vinismo. They don't have to be experts to be interested in wine.
  • If you have a blog, please post a link to our new site on it!
  • If you use a social bookmarking tool, like del.icio.us, please add us to your list!
  • If you use digg.com, please vote for our site there: http://digg.com/software/Open_Content_wine_guide_launches
  • If you use reddit.com, please vote for our site there: http://freeculture.reddit.com/info/296au/comments
tags:

Alastair McKinstry: Quote of the Day

"It is unlikely that Xoce is larger than Xatm , because the ocean initially exists below the atmosphere". From Enhanced atmospheric loss on protoplanets at the giant impact phase in the presence of oceans, Genda et. al, Nature, 2005. Tags ,

MJ Ray: Preface to FSF Radio Interviewee Promotes Skype

Preface to the last post: I'm aware that my surprise at FSF using Skype does raise the old question "where do you draw the line?" - For example, do you refuse to use the fixed-line telephone system if your exchanges are not running free software? Me, I use the telephone system because it's effectively a monopoly and we don't have an alternative that works for me. I sometimes try to nibble at the system with the Phone Co-op and more VoIP use, but it's no fun banging my head against a wall. However, I boycott Skype because I can't tell what it's doing, there have been enough bad reports that I don't trust it and the alternatives of SIP and IAX work for me, but I expected FSF not to use Skype for idealistic reasons. FSF leaders like RMS have promoted things like Why schools should exclusively use free software [by Richard Stallman], carefully corrected inaccurate claims about free software and refused to mention some proprietary software products. They were often criticised for it, but they continued to do it (for good reasons IMO, even when I disagreed with them). So, FSF's Controller giving an interview over Skype seemed a rather surprising about-face. Then the interviewer claimed "Skype is free" and it went unchallenged. After the show, I sent the email...

Adeodato Sim : On becoming $something

One and not uncommon way of granting privileges or positions to somebody else is waiting until it’s obvious it’s time to. As in, for example: “Oh, you don’t have commit access already? Here, let’s fix that.” Or: “Oh, you’re not a release assistant already? Here, have fun.” It’s not useful, however, when there aren’t any people spontaneously jumping into doing some of the required work. Anyway, the point of this post was to say that I can imagine myself applying this method in some non-free-software areas of my life as well: “Oh, we’re not married already? Here, let’s fix that… tomorrow.”

MJ Ray: FSF Radio Interviewee Promotes Skype

I just sent this: Dear FSF, On the Radio New Internationalist show "Up in Smoke", during an interview with Peter Brown of FSF (about 43 minutes in), I was surprised to hear the following revelation that FSF uses Skype and the failure to challenge the claim that Skype is free software:
"Peter Brown: ... This interview today is being transmitted through Skype. We're talking through Skype. Now, that obviously is a direct threat to the entrenched telecoms and they would like to restrict that, to lower the quality of the voice connection and they want to do that with lots of other types of transmission. Rachel Maher: And can they do that? Because Skype of course is free and there's a really direct benefit for organisations like ours, which is a non-profit organisation using Skype technology. Will they be able to do that? Peter Brown: Yes, so what they can do is easily identify types of information being passed, so what they can typically do is downgrade the service that you're using, so that - for instance, voice communication - those packets of data can be slowed down, effectively making voice communciation more difficult. Now this can only really be achieved if they're able to manipulate legislation. Unfortunately, they have a long history of being very successful at this. I mentioned earlier on that Digital Restrictions Management are a threat to our freedoms because it's allowing them to erect gateways and to control what it is that we can view and do with our computers. ..."
I was disappointed not to find much on the FSF web site about the need for free VoIP software, building on GNU oSIP and other free software, instead of Skype's proprietary software, which has contained spyware and worms already. Will you be adding such information soon? What is the official FSF view of Skype and similar proprietary VoIP systems? Nevertheless, well done for covering DRM, net neutrality and the privacy problems of Google, Yahoo! and Microsoft in a relatively short interview. Regards, MJR

Rapha&#235;l Hertzog: Assembling bits of history with git

The dpkg team has a nice history of changing VCS over time. At the beginning, Ian Jackson simply uploaded new tarballs, then CVS was used during a few years, then Arch got used and up to now Subversion was used. When the subversion repository got created, the arch history has not been integrated as somehow the conversion tools didn’t work. Now we’re likely to move over git for various reasons and we wanted to get back the various bits of history stored in the different VCS. Unfortunately we lost the arch repository. So we have disjoints bits of history and we want to put them all in a single nice git branch… git comes with git-cvsimport, git-archimport and git-svnimport, so converting CVS/SVN/Arch repositories is relatively easy. But you end up with several repositories and several branches. Git comes with a nice feature called “git rebase” which is able to replay history over another branch, but for this to work you need to have a common ancestor in the branch used for the rebase. That’s not the case… so let’s try to create that common ancestor! Extracting the first tree from the newest branch and committing it on top on the oldest branch will give that common ancestor because two identical trees will have the same identifier. Using git_load_dirs you can easily load a tree in your git repository, and “git archive” will let you extract the first tree too. In short, let’s see how I attach the “master” branch of my “git-svn” repository to the “master” branch of my “git-cvs” repository:
$ cd git-svn
$ git-rev-list --all   tail -1
0d6ec86c5d05f7e60a484c68d37fb5fc31146c40
$ git-archive --prefix=dpkg-1.13.11/ 0d6ec86c5d05f7e60a484c68d37fb5fc31146c40   (cd /tmp && tar xf -)
$ cd ../git-cvs
$ git checkout master
$ git_load_dirs -L"Fake commit to link SVN to older CVS history" /tmp/dpkg-1.13.11
[...]
$ git fetch ../git-svn master:svn
$ git checkout svn
$ git rebase master
That’s it, your svn branch now contains the old cvs history. Repeat as many times as necessary…

Marc 'Zugschlus' Haber: co-maintainer sought for torrus

Recently, Jurij Smakov resigned from maintenance of the Debian torrus packages. This leaves me as the sole maintainer, and I need help. torrus is an extremely powerful framework to collect and display round-robin data. It can do much more than mrtg, is cricket “done right”, but is not configurable via the web as cacti is. Its upstream is busy with their work, but active. It is written in perl and uses XML as configuration file format. It is mainly used to collect operational data from SNMP hosts and network components. It would be great if any co-maintainers offering to help would have knowledge in perl, XML and SNMP. I am currently in the process of fixing the RC bugs and, in a next upload round, other bugs that are pending. torrus is team maintained (but I am the only active team member at the moment). Its maintainer address will be set to a mailing list with the next upload. If you want to help, just subscribe to pkg-torrus-general and/or pkg-torrus-maintainers and say hello. Your help is appreciated.

Next.

Previous.