Search Results: "ag"

3 June 2007

John Goerzen: "FEMA doesn't do levees"

During recent flooding, some levees in Kansas were breached. (Yes, Kansas has levees!) According to the story, there was a quote from a FEMA official saying "FEMA doesn't do levees."

After New Orleans, I think the entire country would agree with that sentiment.

Although after some congressmen got involved, FEMA changed their tune, and now promises to fund 75% of the repair work.

Too bad their initial answer is "no" to anyone from ordinary citizens to county officials.

This small-scale problem gives some people a small idea of what people in New Orleans are still dealing with. It must be really frustrating.

Matthew Palmer: OfflineIMAP and Deleting Folders

(File this under "Reminders for the future Matt") I use, and highly recommend, OfflineIMAP for the synchronisation of your e-mail between your daily working machine and your IMAP server (if you don't have an IMAP server available for your mail, it's high time you got one). You point it at an IMAP server somewhere far, far away, and a local Maildir, and all of your mail and folders magically get synchronised in both directions. New folder on the server? After the next run, it'll be on your local machine. Even more magical, though, is that any new mail or folders you create on your local machine will be uploaded to the server. Woohoo! Offsite Backups! (Before you GUI mail users say "pfft, my client does that all for me", I'll remind you that I don't need to chew several hundred megs of core to delete my spam) I've got some magical procmail rules (specifically, look for "ARTFUL PROCMAIL") that automatically filter list e-mail into individual folders (with automatic creation of the folder if necessary, of course). This makes mailing lists soooo much easier to handle. Of course, when I unsubscribe from the list a couple of weeks later, that folder is still sitting there, empty and forlorn. I don't mind empty directories, except that they slow down the OfflineIMAP sync run, since it asks "any new mail in here?" for every one of them. I'd just delete them from my local machine periodically, except that OfflineIMAP can't delete folders off the server if you remove them from your local Maildir (and vice versa). Instead, the folder gets re-created on the local machine, which is definitely not the result I'm looking for. I'm pretty sure this is an IMAP limitation, so I'm not criticising John Goerzen for not implementing this particular feature. However, the empty folders bother me a bit, so I decided to do something about it. Namely, I hacked up some little shell one-liners. These one-liners are all dependant on you having the same IMAP server (Courier) and folder name mapping (none) as me, otherwise there's a good chance that your file names won't match the patterns I've used. For reference, My folders on the server are dot-directories under $HOME/Maildir, and my folders all start with INBOX. on the client. Also, both sides use periods to separate folder levels. As an example, e-mail to the debian-devel-announce list gets stored in $HOME/Maildir/.lists.debian-devel-announce on the server, and $HOME/Maildir/INBOX.lists.debian-devel-announce on the client. I've got one big before you start warning: this process involves deleting things. If you're not able to verify that what these snippets are doing is correct for your particular situation, then please do not run them. Also, if running them causes all your e-mail to disappear or your cat to fall pregnant (despite being spayed and/or male), then that isn't my fault. The only warranty I give is that It Works For Me. It May Not Work For You. As a first step, make sure that your local and remote mail stores are in sync -- presumably by running OfflineIMAP. Otherwise, a folder which is empty on one side might not be quite-so-empty on the other side, and that would possibly make for sadness. Stopping e-mail from coming into your mailboxes would be good, too -- I just turned off my MTA for a few minutes, because clogging other people's queues is fun. Doing something smart with procmail would also work. On the OfflineIMAP client machine (laptop, home desktop, whatever), cd into your local mail store, and run this to generate a list of IMAP folders that don't have anything in them:
 for i in INBOX.*; do find $i -type f   grep -q $i   \
 (echo $i   sed 's/^INBOX//'); done >/tmp/empties
The contents of /tmp/empties should look something like:
 .Deleted
 .junk
 .lists.debian-devel-announce
 .lists.something-funny
 .spam
Review the list of folders it produced (just to make sure nothing really unpleasant ended up in the list), and then run:
 for i in $(cat /tmp/empties); do rm -rf INBOX$i; done
to delete all the empty folders. Next, copy the list of folders onto the IMAP server (yes, you need shell access on the server to do all of this; that's why I run a Linode), cd into your Maildir on the server, and run this:
 rm -rf $(cat /tmp/empties)
That removes the folders from the server as well. For some reason, OfflineIMAP doesn't notice that a folder has gone away, and so it doesn't remove the metadata for the deleted folders from it's cache. I'm not sure if that hurts performance or is otherwise injurious to your health. To be ultra-neat, go into $HOME/.offlineimap (or wherever your metadata dir is) on the client machine and run
 for i in $(cat /tmp/empties); do find . -name INBOX$ i ; done  xargs rm -rf
And that makes everything clean and tidy. Now, of course, someone's going to point me to a small script that finds all of your local empty folders and deletes them locally then issues an IMAP "delete folder" command on the server. But I had fun working all this out, so it's not a complete waste.

Miriam Ruiz: Ubuntu Women R00lz!

Sarah Hobbs became an Ubuntu Core Developer this week, becoming AFAIK the first women to enter it. Elizabeth Bevilacqua had her Ubuntu membership approved some days ago. Yay Girls! :)

Matthew Palmer: Project Honeypot

Recently I stumbled across Project Honeypot, an interesting anti-spam system to identify and flag Internet abusers, through the use of honey pots -- systems that look innocent and attractive enough to the passing network abuser, but which actually log and flag the abuser's activity and record it for future reference. It seems cool enough -- anything that aims to stop random assholes from abusing the Internet and making life unpleasant for the rest of us is to be commended -- but I'm wondering if anyone has had any experience with the project, and has any comments? I'm considering joining up and contributing a few resources, but prior experience is always worth listening to. E-mail me at mpalmer@hezmatt.org, and I'll summarise in a future post (possibly with my own experiences, if I do actually join up).

Matthew Palmer: Get Your War On

I've got a number of web comics in my rotation, which I read with varying regularity. I don't know if I'd call "Get Your War On" one of my "favourites" (if only because I don't think it should need to exist), but it does have some viciously biting commentary on the Iraq war. Some of the ones I wish I had on T-shirts: Culturally Sensitive @ Get Your War On Shiite Death Squad Productivity @ Get Your War On The Power of Freedom @ Get Your War On The Writ of Habeus Corpus @ Get Your War On

Joachim Breitner: Spontanious DHCP-Server: Done.

Sitting around at the GPN6 conference in Karlsruhe at the moment, I thought it s time to write the instant DHCP server I blogged about. So I took the code from udhcpd and, instead of parsing an config file, figure out the settings myself. So I can run simpledhcpd eth0 now, and will get a DHCP server that waits for DHCP request and answers them with an IP from eth0 s subnet, the correct netmask, my own IP as the gateway and the first entry of /etc/resolv.conf as the nameserver that s all it needs to quickly connect any other computer to mine and, if routing is enabled, provide it with internet connectivity.I have uploaded the simpledhcpd binary as well as debian binary (.deb) and source packages. It is all very hackish, bad code and comments are welcome.

Bernd Zeimetz: gimp-plugin-registry

gimp-plugin-registry Dear lazyweb, since a few days there s gimp-plugin-registry waiting in unstable. At the moment the package contains several tiny GIMP plugins I like to use and which are not included in the gimp package or in other gimp-* packages. In my opinion a collection like this one was missing in Debian, since there re a lot of very nice plugins/scripts out there, which are too small to package them on their own.
Which plugins would you like to see in the collection? Packaging all plugins from http://registry.gimp.org/ doesn t make sense, so I d like to know which plugins other people are using and put them into the next release of the package. Any feedback is appreciated. P.S.: As I didn t find a real alternative for my needs, I ll stay with Dokuwiki. As far as I remember is a rss feed with proper html on Andi s todo list, and there re more other nice features going to come :-) Although somehow I still would like to rewrite Dokuwiki in python ;-)

Bernd Zeimetz: hi, planet && iso8859-15 to utf8 with netatalk magic

hi, planet && iso8859-15 to utf8 with netatalk magic Hi, Planet!
Welcome to my blog, and thanks to Martin for subscribing me. I m not going to bother you with any details about me, if you have any questions feel free to ask me on freenode or oftc (in case you re wondering: my nick is bzed).


After a longer time of planning we ve upgraded our main file server at work: New machine, new storage (7TB - woohoo!), Etch instead of Sarge and UTF-8 for file names instead of ISO8859-15. Everything not a too complicated thing, except for renaming the about 10,000,000 files from ISO8859-15 to UTF-8 in a proper way.
In theory this is easy, as convmv happily takes care of the problem. But this did not work for us unfortunately, as we re not only providing NFS and Samba services, but also AFP (Apple_Filing_Protocol) via netatalk. Years ago you had to choose ISO8859-15 if you wanted to allow your Apple and Windows users to see the same, non-broken file names - not only because AFP didn t support UTF8 before version 3, which came out with OSX1). Normally you d think that a server would not allow a client to write a file with a file name which includes not supported characters - again, OSX and netatalk go their own way here:
Characters which are not supported by the underlying file system are character(!)-wise encoded using the CAP encoding. So we had to find a way to Luckily netatalk ships the uniconv(1) util2) which is able to take care of this problem. It also updates the CNID3) Database at the same time. There s two things you need to take care of in case you re using the dbd CNID backend: Be careful: uniconv assumes that all colons in a file name are part of a CAP encoded character. That s not a problem as long as you have only Mac and Windows clients accessing your server, as both systems do not allow colons in file names. In our case we found a number of cache files from Nautilus (which is running on our sunray/Solaris web-surf terminals as default browser) with colons in the file name. I hope no user will miss them ;-) Including a final synchronisation of all files to the new storage, about two hours it took uniconv to convert the file names and a aunch break, we were finished after about 14 hours of work. Until now it seems that our users didn t notice the change at all, except for those who realized that they have much more free space now. Looks like a successful weekend so far! :-D 1) and uses a NFD variant of Unicode normalization (UTF-8#Mac_OS_X), but netatalk takes care of this and translates it into the NFC form, which is used on most other platforms 2) it s called netatalk-uniconv in Debian and shipped with netatalk 3) Catalog Node ID, another crust from old Mac OS versions

2 June 2007

Frank Lichtenheld: packages.debian.org status and development

Copy of a mail I sent to debian-www earlier today. I don't think it warrants posting to -devel-announce, but I post it here to make it visible to people not usually following debian-www. Since I seem to sense an increased stream of offers to help out with packages.d.o coming my way (but maybe that is just wishful thinking ;) I wanted to give a short update on the development of the current code and the status of the infrastructure so that nobody can claim he wanted to help but failed due to lack of information.

Alexander Schmehl: Report from the LinuxTag -- Part I (A bit of DebianDay and my talk)

Before I start with my report I need to fulfill my promise for those who stumble here from kushaldas.in: The URL of the web interface for the package description translation framework is for now: ddtp.debian.net (It's easy: Debian Description translation pproject). There might be some changes after DebConf, our annual conference, which will take place this month. So keep an eye on your language's team mailing list. But more about Kushal Das later. The first part of my report will cover a bit of our DebianDay and of course especially my talk ;) More will follow later. Friday was DebianDay and I attended Holger's talk about debian-community. It's a quite interesting project, trying to solve the problem, that there's not much between real DDs and the rest of the world. It's more low level than the Debian maintainers idea floating around for a while: Look around, you'll see much contributors to Debian, who are not maintaining any package. The idea is basically to have kind of bonuses for contributing to Debian, as a more direct way to say Thanks!. Have look at the website, and think how you could help to get things rolling. After his talk it was my turn. I did a Debian package building for beginners talk... Well, actually it's a workshop stripped down by the practical part leaving only the slides of the introduction. But who cares ;) Again I was surprised how many people where interested in that topic. I always thought it's kind of special and not that interesting, but the room was quite stuffed. Some people where even sitting on the floor. I neither counted how many people attended my talk, nor how many seats where available. I guess I had something between 80 and 120? Perhaps Wolfgang Borgert, who moderated DebianDay, can correct me, if I'm wrong. Since I stripped down a workshop to a talk, I needed to take special care about the timing. Well... I didn't work perfectly. I took a bit too long while answering questions, but I think all in all it was quite right. As usual I took gnujump as example; easy package, works without much tweaking of the templates created by dh_make, and if you have some time left at the end, you can show some additional stuff, like splitting of a -data package. After the talk I got some quite interesting questions; the three most interesting ones were the following: So much for now; I'll write some more about the event in general, a goodie from an old friend from Treuchtlingen (rather short; the german entry is longer), and a small talk I had with an other J rg later... I'm kind of tired right now.

Romain Francoise: Emacs 22.1 released

No announcement yet, but you can read about it on the homepage, and get it here.

2054 days have passed since the previous non-bugfix release (Emacs 21.1, on October 18th 2001). The next release, Emacs 23.1, is thus expected around January 15th, 2013.

Wouter Verhelst: Thecus N2100 arrived

Last saturday, I fetched the N2100 which I had on order since quite a while, put in the two 500G hard disks, and powered it on. Installing Debian to a machine with no console is pretty fun, but luckily the installer makes it all rather easy (there's this thing that allows you to ssh into the running installer and from there start the installation menu; they originally wrote that for installing to an s390 box, but obviously it works for any architecture...). After installing the box, I upgraded the base system against security.debian.org and removed some software that I didn't need, and rebooted the thing. And then... ... nothing. It didn't seem to come up. As it turned out, the stuff which I removed (a horrible solution to a problem that doesn't exist) just hapepned to be responsible for loading the NIC driver module; so after reboot, the box didn't have a network interface anymore as far as the kernel was concerned. Pretty stupid, that. Luckily, fixing that wasn't too hard. Remove the hard disks, put them in another box, edit some files in /etc, put the disk back in the Thecus, boot. There. I now have a wonderfully small system that I'll use as home server, and which will replace rock in that function. Seen as how rock is a power-hungry desktop with five power-hungry hard disks, whereas goa, the new box, is an economic ARM-based system, that'll be good for the environment as well. Isn't that nice. The only downside to this is that I'll now have to do some configuration and migration work, since you can't just put a disk with Debian/i386 on it in an arm box and hope it'll work. But that's okay.

Holger Levsen: linuxtag was harmless fun

I wrote this 15h ago:

It's midnight, the sun is shining, below me are beautiful montains, partly covered in snow. In less than 48h I will be home again.

1 June 2007

Joachim Breitner: Unicode against Smileys

You probably all know how some IM clients convert text smileys like :-) to some more or less funny graphics. The problem with these is that every client has it s own graphics, and there are themes, so what looks like a secretly smiling face here might be laughing naughtily laughing grimace there. That s why I prefer text smilieys But my girlfriend uses one of those bad clients, so I tried to hack around it, using funny unicode characters. My first try was to add a zero-width space character like (U+200B) inside the smiley, so that it would be : -) instead of :-) . Indeed, her client was not replacing the text with an image, but it did not know the special character, so my girlfriend saw something like : -) (It was a square, in case your font looks different). The next best try was to replace the nose with a different character. Interestingly, while using the EN-DASH (U+2013) instead of the normal hyphen - (U+002D), the minus character (U+2212) worked, so now my girlfriend sees text smileys with a slightly longer nose but that s ok, after all they are from me : ). And thanks to a pidgin plugin, I can just type :-) and : ) will be sent.

Matthew Garrett: Further stories of customer service despair

Orange have a fairly decent offer for "unlimited" (1GB a month or so) 3G access. I'm a pay monthly customer on an old tariff that's no longer offered, but there's no mention of any sort of limitations there and they seemed happy to add 3G access to my account. Cue two days of repeated phone calls trying to find out why my entirely 3G phone was refusing to connect to their 3G network. After going through being told it was my phone settings, poor reception, something that I could get fixed at my local Orange store or that it was because they'd entered the wrong start date(!), I finally got through to someone who was actually genuinely friendly and helpful and told that I needed a 3G sim[1]. Oh, and that they wouldn't provide me with one because of the tariff I'm on.

Fucking useless telco.

[1] Something that's clearly documented on their website. Oh, wait.

Antti-Juhani Kaijanaho: Everybody has their own conference management software

… or at least it feels that way. I just ran into Edd Dumbill’s post on Expectnation, and I just last week helped grade a master’s thesis on the application of Petri Nets to investigating the correctness of another conference management software written at my University (a thesis that I had co-advised). I seem to recall reading about a couple of others.

Edd Dumbill: Launching Expectnation

I'm very pleased to announce the launch of Expectnation, a web application for managing conferences. Expectnation logo What does it do? Expectnation is intended to replace the ad-hoc collection of emails, spreadsheets, documents and hacks that hold together the organization of most conferences. The aim is to improve the quality and reliability of communication between the organizers, speakers and attendees. But it doesn't stop there. What I'm really excited about is the chance to enhance the conference experience through the web. Expectnation is capable of managing the complete web site for a conference, which provides many opportunities for bringing the best of the social software world to augment events. Our tagline is "build your conference into a community", which underpins a key aim: to help organizers make events more relevant and useful to attendees, and to live on beyond the event itself. We do this in two ways: saving time, so you can spend it on improving your conference, and providing online tools to support community building.
Right now Expectnation is able to manage the proposal, review, scheduling and publication of presentations, along with the conference web site and smart emailing to speakers, reviewers and chairs. Over the next two months we'll be introducing our registration module, with optional online payments, and working on extending the social software features available for attendees. Take a look  I'm really excited about letting users get started with Expectnation, and seeing the uses it gets put to. We believe Expectnation will be just as handy for organizing events inside an organization as for traditional conferences. So, if you organize, speak at, or attend conferences of any sort, please check out Expectnation and recommend it to a conference organizer near you!Related links

Matthew Garrett

Dear IBM,

I appreciate that laptops are awkward to disassemble, something that's even more true of ultraportables. As a result I don't feel especially surprised that you managed to make a hole in my laptop while working on the screen, and I appreciate your offer to reexamine the hardware. What I appreciate less is your requirement that I pay for it to be sent to Scotland for another fortnight so that you can correct your mistake, you cretins.

No love,

Matthew

Cameron Dale: May-31-2007: HTTP Range Requests

I wasn't sure if some/many/all Debian mirrors responded correctly to HTTP/1.1 range requests for only part of a file, so I ran a test on them (download part of the etch Release file). These type of requests will be useful for downloading missing pieces from packages in the BitTorrent-like downloader that I'm writing. Here are the results of my test on the 221 HTTP mirrors:
Status Description Count
200 Full Data 1
206 Partial Data 208
302 Document has moved 2
404 Not Found 2
Couldn't Connect 8
Total 221
So only one mirror (debian.csie.nctu.edu.tw) was unable to support the range request and instead returned the entire file. It seems like using range requests will be fine, though I'll have to think about some kind of error checking for that one lonely mirror that's not like the others. There was also one mirror that responded with an old Release file. It seems like debian.ihug.co.nz has not been updated since etch was released.

Matthew Garrett

This thread on the Sun initiative to produce a more Linux-like distribution of OpenSolaris is interesting not so much for the technical goals, but as an insight into the community. The immediate response to the proposal? A set of complaints that it hasn't followed the correct process.

Now, to be fair, there have been other threads discussing the technical and social desirability of such a distribution already and some are still ongoing - it's not like the OpenSolaris community has ignored it entirely in favour of process fetishising. However, it's indicative of a community that's more concerned with procedure than it is with producing high quality software. What I suspect has happened is that Sun felt it was important to ensure that procedures were put in place before creating a community in order to avoid the problem of it immediately turning into low-grade anarchy. The problem with this is that if you create procedures before you create community, the people who end up enforcing the procedures tend to be the sort of people who find enforcing procedures to be the interesting part of the job rather than the ones who see them as necessary evils to enforce moderately sensible community development.

Sun's clearly stuck between a rock and a hard place here. They don't want to be seen to be directing the community too strongly, or they'd end up like Red Hat did with Fedora - you alienate your community by giving them the impression that they have no influence over the direction of the distribution. On the other hand, the rapid growth of the Ubuntu community strongly suggests that having a strong leader can ensure that people don't get too bogged down in procedure at the cost of technical progress.

I suspect that Sun made the wrong call here. Having more corporate influence to begin with might have put off some contributors, but it would also have allowed the development of a functional community at an earlier stage. Sun could then gradually withdraw (as Red Hat have been doing with Fedora) and let the community play a larger role. Perhaps that way we'd hear more about the technical contributions coming out of OpenSolaris and they wouldn't be left with just the same two cards they've been playing for a couple of years now - dtrace and ZFS.

On something of a tangent, I don't think their choice of license has helped a great deal here. Two of the areas where OpenSolaris is most behind Linux are hardware support and desktop/kernel integration. The choice of a GPL-incompatible license strongly discourages any Linux developers from working with the low-level code of OpenSolaris due to the perceived risk of contaminating the Linux codebase at some later point. That rules out a huge pool of skilled developers (I'm going to be potentially controversial here and say that I suspect Linux has a larger skillset here than all the BSDs put together, and quite possibly Solaris added to that) who are writing a good deal of advanced code. Meanwhile we're left with OpenSolaris having even worse laptop support than FreeBSD. These are people who could have added to the community socially as well as technically. Instead you've got a community led by a set of Sun staff who are paranoid about doing anything that might make it look like Sun controls the community. Score.

Next.

Previous.