Search Results: "ag"

14 April 2008

Russell Coker: Friends and Adverts

For some time I have been running Google Adsense adverts on my blog. Not long after I started running the adverts the revenue exceeded the amount of money I pay for net access, so it’s worth having. I recently increased the amount of advertising by including an advert in the middle of the post and received one negative comment from a reader who doesn’t like reading content with adverts in the middle. I have just changed my advertising to have that advert spot in question be before the start of the content rather than in the middle (I’m not sure if that will make them more or less happy). It seems expected nowadays that there will be a moderate amount of advertising on all web sites which have good content and don’t charge membership fees, many of my blog posts cite as references pages on web servers run by media companies that have significant amounts of advertising. Chris Samuel is considering implementing advertising [1] and is planning to not display adverts to “friends” (which means people who have commented or who are referred by social media sites). One significant problem with this idea is that sometimes the adverts become part of the blog conversation. Google adverts give an idea of which of the things that people are prepared to pay money for are considered by the Google algorithm to be related to the post in question. In my experience it’s not uncommon for people who comment on blog posts (both through the blog interface and through private correspondence) to reference the contents of adverts. Also while writing this post I updated my post about car sharing because I discovered a third car-share company through the adverts on my own blog [2]. I know one professional journalist who blocks the adverts on his own site so that his writing will not be biased (or be perceived to be biased) by his advertisers (which makes sense given his situation), but for my situation it clearly makes sense to review the advertised offerings of all three companies that compete in this space in Melbourne and there is no potential for bias (incidentally all three of them are advertising on my blog post). A problem with giving a different version of the content for friends (in the more traditional meaning of the word - as opposed to using the word to mean people who have visited your blog in a certain way) is that they will not be able to correctly review your web site. I regularly notify friends and people who do worthy things of deficiencies that I discover in their web sites and occasionally receive such notifications from other people. I don’t want to have bugs in my site concealed from friendly people who would like to help me out and displayed to random people who don’t care and will respond by visiting another site. When such things are discussed one topic that is mentioned is putting advertising in an RSS feed. I have no plans to do this, such RSS advertising would not be acceptable to Planet installations, but it would not be technically challenging to give an advert free feed to Planets but give adverts to everyone else. I think that most people who read my blog through RSS feeds will see adverts when they want to comment on my posts or when they want to forward the URLs or reference them in their own blog posts (always click on the permalink before forwarding - when a blogger messes up their permalinks it’s embarrassing if you forward them without checking). So I encourage Chris to put adverts on his blog and to show them to me.

Christian Perrier: IP over DNS for dummies

Once again, I'm sitting in an airport (CDG) and enjoying the benefits of IP over DNS to bypass the outraegous rates for wireless access (about 10 euros for 1h if that didn't change since last year). Actually, having IP over DNS work is pretty simple. What you need is: "Appropriate software" here is, IMHO, the iodine package in Debian. There's nothing as easy to setup as it is. There is no package for etch, AFAIK, but backporting it is straightforward. You then need to create an entry in your foo.bar domain, such as "tunnel.foo.bar" and have it point to your static address. Then you run iodine on that server, listening to port 53 (with a configured password). That creates a virtual interfaces with something like 10.0.0.1 as address. When you need IP over DNS access with your roaming laptop, all you need is to connect to the expensive network, then launch iodine and provide it two parameters: the "tunnel.foo.bar" address and a local address (for instance 10.0.0.2). If everything works well, you'll be prompted for the password and voil . You have a tunnel between your local 10.0.0.2 address and the remote 10.0.0.1. The rest is a matter of network routing and you can now access the entire Internet through your remote server with no charge. The entire traffic goes through DNS requests to the local DNS server. That can be fairly slow but all a geek needs is receiving/sending mail and remote SSH access, right? This doesn't work in every place, unfortunately. Many wireless providers block such traffic in some way. But, at least in A roports de Paris, I can promise that will work..:-)

13 April 2008

Patrick Winnertz: Spam Contest Update

Some weeks ago I post about a spam contest where I participate. This contest is now running for several weeks. (It will be finished after 5 weeks). The aim is to get as most as possible spam to the emailadress . (My is winnie@qsc218.credativ.com). Atm I'm the second... I've ~140 spam mails and only 1 virus in my mailbox Noel, who is on the first has ~150 spam mails and ~10 viruses in his mailbox :-S The winner of this contest will get a free t-shirt (with a cool text on it). Yeah... it would rock if you can distribute this emailadress a bit more, so that I recieves more spam ;-) Thanks!!

Kartik Mistry: Congratulations Steve!


* Congratulations to Steve McIntyre for winning DPL election.

Pablo Lorenzzoni: e-fisl

I ve been involved in TVSL (Free Software TV a streaming infrastructure for the fisl) since its beginning This time, while searching a way to embed IRC into a webpage for a internal project, I discovered mibbit an interesting IRC widget. Then I thought, It would be interesting to have that for fisl ... this is how I put together e-fisl. e-fisl is just a webpage with an embedded cortado player (via the beautiful MetaVid library ) and mibbit widget. I put it together just a few minutes ago, but I suspect it is going to be interesting to watch how people use it (the mount-points for the rooms are still not available as you ll notice). I am planning to have a bot in the #fisl channel to collect questions from the remote attendees ... I just have to check with the rest of the organizing committee if it will be possible to read these questions for the speaker during the session. It would be great

Gunnar Wolf: Silent soundtracks

Vicm3, you know I'd probably ignore this, as following internet memes goes against my principles. But what are the principles there, if not to break them?
Ok, so what you request is, basically, to get a list of sounds to build my life's soundtrack. Following the list you mentioned, it is quite exhaustive, creative and long.
In my case, some other time, I'd probably jump over some über-sarcastic Leo Masliah and the like. Particularly, I would not ever talk about my life without his Todo as .
But not today.
Today, I'd love my life's movie to be an old-fashioned, mute movie. Yes, quite in line with the nice grey life theme I've had on my blog for several months... I'd love having a nice, quiet, mute movie, just letting me live along, think a bit, work a bit... Settle down on too many things, lead to some peace.
No, this message bears no dedication to any character or person I have or will meet. Just inner my mood and needs.

Jose Luis Rivas Contreras: New XScreenSaver 5.05-2

There are new packages of XScreenSaver from the last upstream release, now with a patch applied for systems with dual-head screens.They're available at my site along with i386 deb binaries.I hope they'll get uploaded to Debian soon. Technorati Tags:

John Goerzen: Backup Software

I think most people reading my blog would agree that backups are extremely important. So much important data is on computers these days: family photos, emails, financial records. So I take backups seriously.
A little while back, I purchased two identical 400GB external hard disks. One is kept at home, and the other at a safe deposit box in a bank in a different town. Every week or two, I swap drives, so that neither one ever becomes too dated. This process is relatively inexpensive (safe deposit boxes big enough to hold the drive go for $25/year), and works well.
I have been using rdiff-backup to make these backups for several years now. (Since at least 2004, when I submitted a patch to make it record all metadata on MacOS X). rdiff-backup is quite nice. It is designed for storage to a hard disk. It stores on the disk a current filesystem mirror along with some metadata files that include permissions information. History is achieved by storing compressed rdiff (rsync) deltas going backwards in time. So restoring "most recent" files is a simple copy plus application of metadata, and restoring older files means reversing history. rdiff-backup does both automatically.
This is a nice system and has served me well for quite some time. But it has its drawbacks. One is that you always have to have the current image, uncompressed, which uses up lots of space. Another is that you can't encrypt these backups with something like gpg for storage on a potentially untrusted hosting service (say, rsync.net). Also, when your backup disk fills up, it takes forever to figure out what to delete, since rdiff-backup --list-increment-sizes must stat tens of thousands of files. So I went looking for alternatives.
The author of rdiff-backup actually wrote one, called duplicity. Duplicity works by, essentially, storing a tarball full backup with its rdiff signature, then storing tarballs of rdiff deltas going forward in time. The reason rdiff-backup must have the full mirror is that it must generate rdiff deltas "backwards", which requires the full prior file available. Duplicity works around this.
However, the problem with duplicity is that if the full backup gets lost or corrupted, nothing newer than it can be restored. You must make new full backups periodically so that you can remove the old history. The other big problem with duplicity is that it doesn't grok hard links at all. That makes it unsuitable for backing up /sbin, /bin, /usr, and my /home, in which I frequently use hard links for preparing CD images, linking DVCS branches, etc.
So I went off searching out other projects and thinking about the problem myself.
One potential solution is to simply store tarballs and rdiff deltas going forward. That would require performing an entire full backup every day, which probably isn't a problem for me now, but I worry about the load that will place on my hard disks and the additional power it would consume to process all that data.
So what other projects are out there? Two caught my attention. The first is Box Backup. It is similar in concept to rdiff-backup. It has its own archive format, and otherwise operates on a similar principle to rdiff-backup. It stores the most recent data in its archive format, compressed, along with the signatures for it. Then it generates reverse deltas similar to rdiff-backup. It supports encryption out of the box, too. It sounded like a perfect solution. Then I realized it doesn't store hard links, device entries, etc., and has a design flaw that causes it to miss some changes to config files in /etc on Gentoo. That's a real bummer, because it sounded so nice otherwise. But I just can't trust my system to a program where I have to be careful not to use certain OS features because they won't be backed up right.
The other interesting one is dar, the Disk ARchive tool, described by its author as the great grandson of tar -- and a pretty legitimate claim at that. Traditionally, if you are going to back up a Unix box, you have to choose between two not-quite-perfect options. You could use something like tar, which backs up all your permissions, special files, hard links, etc, but doesn't support random access. So to extract just one file, tar will read through the 5GB before it in the archive. Or you could use zip, which doesn't handle all the special stuff, but does support random access. Over the years, many backup systems have improved upon this in various ways. Bacula, for instance, is incredibly fast for tapes as it creates new tape "files" every so often and stores the precise tape location of each file in its database.
But none seem quite as nice as dar for disk backups. In addition to supporting all the special stuff out there, dar sports built-in compression and encryption. Unlike tar, compression is applied per-file, and encryption is applied per 10K block, which is really slick. This allows you to extract one file without having to decrypt and decompress the entire archive. dar also maintains a catalog which permits random access, has built-in support for splitting archives across removable media like CD-Rs, has a nice incremental backup feature, and sports a host of tools for tweaking archives -- removing files from them, changing compression schemes, etc.
But dar does not use binary deltas. I thought this would be quite space-inefficient, so I decided I would put it to the test, against a real-world scenario that would probably be pretty much a worst case scenario for it and a best case for rdiff-backup.
I track Debian sid and haven't updated my home box in quite some time. I have over 1GB of .debs downloaded which represent updates. Many of these updates are going to touch tons of files in /usr, though often making small changes, or even none at all. Sounds like rdiff-backup heaven, right?
I ran rdiff-backup to a clean area before applying any updates, and used dar to create a full backup file of the same data. Then I ran apt-get upgrade, and made incrementals with both rdiff-backup and dar. Finally I ran apt-get dist-upgrade, and did the same thing. So I have three backups with each system.
Let's look at how rdiff-backup did first.
According to rdiff-backup --list-increment-sizes, my /usr backup looks like this:
        Time                       Size        Cumulative size
-----------------------------------------------------------------------------
Sun Apr 13 18:37:56 2008         5.15 GB           5.15 GB   (current mirror)
Sun Apr 13 08:51:30 2008          405 MB           5.54 GB
Sun Apr 13 03:08:07 2008          471 MB           6.00 GB

So what we see here is that we're using 5.15GB for the mirror of the current state of /usr. The delta between the old state of /usr and the state after apt-get upgrade was 471MB, and the delta representing dist-upgrade was 405MB, for total disk consumption of 6GB.
But if I run du -s over the /usr storage area in rdiff, it says that 7.0GB was used. du -s --apparent-size shows 6.1GB. The difference is that all the tens of thousands of files each waste some space at the end of their blocks, and that adds up to an entire gigabyte. rdiff-backup effectively consumed 7.0GB of space.
Now, for dar:
-rw-r--r-- 1 root root 2.3G Apr 12 22:47 usr-l00.1.dar
-rw-r--r-- 1 root root 826M Apr 13 11:34 usr-l01.1.dar
-rw-r--r-- 1 root root 411M Apr 13 19:05 usr-l02.1.dar

This was using bzip2 compression, and backed up the exact same files and data that rdiff-backup did. The initial mirror was 2.3GB, much smaller than the 5.1GB that rdiff-backup consumes. The apt-get upgrade differential was 826MB compared to the 471MB in rdiff-backup -- not really a surprise. But the dist-upgrade differential -- still a pathologically bad case for dar, but less so -- was only 6MB larger than the 405MB rdiff-backup case. And the total actual disk consumption of dar was only 3.5GB -- half the 7.0GB rdiff-backup claimed!
I still expect that, over an extended time, rdiff-backup could chip away at dar's lead... or maybe not, if lots of small files change.
But this was a completely unexpected result. I am definitely going to give dar a closer look.
Also, before I started all this, I converted my external hard disk from ext3 to XFS because of ext3's terrible performance with rdiff-backup.

Rob Taylor: PackageKit Stop Energy

This should be a reply on Hughsies blog, but I don’t want to create a livejournal account. Richard, please move to blogs.gnome.org! In response to Jason’s comments: Hey. I’m a Debian/Ubuntu kinda guy and I think PackageKit is a hell of a lot better than Ubuntu making ubuntu-only solutions like gnome-app-install. It’s DEFINITELY not a NIH, there was nothing that gave us this kind of capability at all before PackageKit started. Everyone knew what was needed to be written and Richard was the guy that jumped in and got it started. Also Richard wasn’t working at Red Hat when he started PackageKit and has worked with every distro he can on this. Jason, stop the Stop Energy. Update:
I though I might jump in and say a bit more on this problem: It really comes down to the question of whether a backend should ask questions of the user. Richard thinks that they shouldn’t, mainly because every time he’s seen backends ask questions they aren’t ones he knows the answer to and so, by inference, most people don’t know the answer to. These questions shouldn’t be asked in a user-friendly system.
However ‘These questions’ are actually multiple classes of problems and simplistically dismissing these is really just asking for failure in solving the problems correctly. Before I go any further, let me note that debconf has multiple levels of verbosity that it can ask questions at. Most Debian based distros just ask the highest priority questions. It should be noted that a PackageKit backend should allow a central administrator to set default values for any of these setting however. Lets break down some of the kind of questions asked though debconf: Some packages also use stdin/out to really make sure you know what the hell you’re doing, like kernel packages, but i think that’s somewhat outside of this scope of this problem. Those kind of things should just fail unless you’re doing leet-super-admin work ;) So the question really comes down to asking the user sensible questions that they a) know how to answer and b) care about. The point I made to Richard on IRC is that this is actually a difficult and multi-faceted problem and just hiding these problems won’t help in solving them well, so my take is that PackageKit should allow asking of questions, probably via a dbus interface, have a debconf frontend that channels questions by this channel, and then let the Ubuntu and Debian guys get on the case of forming projects and policy to help fix the problem at source. Update 2:Richard pointed me to this FAQ entry which explains why even handling debconf questions is hard.

Joey Hess: secret code

I'm still following The Lost Ring, but it got a little too intense today when someone who was not very familiar with what was going on was recruited to pick up an envolope hidden in an umbrella stand at a gallery in Hong Kong became disturbed by the contents and destroyed it. All we're left with is some fuzzy pictures. blur This fragment contains a code. If we can figure out enough of the code, it can be used to download a digital copy of the paper that got torn up. It's a kind of checksum, was written with a typewriter (that writes capital letters a bit higher than the rest of the line, and tends to fade bottoms of numbers), and will look something like "SS71/124P/84JH/HFGS/CEAS". After playing with the gimp, I'm fairly sure that the code starts out "C??L/T4GA/L". enhanced In the movies, this is easy, you just zoom in on the blurry picture until you can see fingerprints. In the "real" world, it's gonna be tricky.

Axel Beckert: New mobile phone and what the Nokia 6310i did better than the E51

Habits control our choice sometimes more than we would like to admit… New mobile phone Since about two weeks ago I’ve a new mobile phone. The Nokia E51 will replace my slowly dying Nokia 6130i. I knew I needed a new mobile phone when my 6310i started to turn off itself shortly after I turned it on. I needed up to about ten times switching it on to make it stay on. Sometimes it already switched itself off before I could enter the PIN. Looks like a loose contact, but I never figured out where it is. Although I know about Nokia’s behaviour in Germany, I still had to buy a Nokia, because after using a 6130 (the GSM 1800 only clone of 6110 and 6150), a 6210i and the already mentioned 6130i over the last decade, I got so used to how Nokia mobile phones are navigated and how you type with Nokia phones (blank on 0, point and comma on 1, case changing on #), everything else (especially those with blank on 0 and case changing on *) would be worse than the half-dead mobile phone, I’m currently using. Spoilt for choice So which Nokia? For a long time I refused to buy a mobile phone with a camera or radio in it. But since the E70 was no more available (and is said to have quite buggy software) and the E61 has been replaced with the E61i, there are no more smartphones without a camera, at least not from Nokia. But I also found some useful uses of camera phones. After a while I could track down the number of choices to four: Communicator E90, E61i, E65 or E51:
Sizeasy Size Comparison: Nokia E90 vs Nokia 6310i vs Nokia E61i vs Nokia E51 vs Nokia E65
The picture above shows that the main differences of those models is size: Although having a QWERTY keyboard on the phone would be nice (for ssh, Jabber, the web, etc.) and the E90 being only slightly bigger than the 6310i on the paper, the size difference to the 6130i is more than only noticeable since the 6310i tapers off at the top. Besides, for the price of an E90, I get an E51 and an EeePC together… (Thanks to maol in whose blog I read about Sizeasy.) The E61i also has a (very small) QWERTY keyboard and is primarily only much wider than any of the other phones. It even has no bigger screen resolution than the E51 or E65. (Only the no more available E60 – a normal monoblock smart phone like the E51 – had a better resolution: 352x416 pixel instead of 240x320 pixels.) And since I usually carry my mobile phone in my trouser pockets, width matters most. So I had the choice to either get a phone which is too big for my trouser pockets or one without a QWERTY keyboard. The I remembered those foldable external keyboards for PDAs. There are at least three different makers of foldable bluetooth keyboards said to be working with Nokia Symbian S60 3rd Edition phones, so a QWERTY keyboard on the phone itself was no more important. (Only passwords will need to be entered over the number keypad since I don’t want to broadcast them… ;-) The choice between E65 and E51 was made easier by their reviews (E65, E51) at Xonio: The E65 seems to have not that good standby and phoning times while the E51 seems to be quite good regarding endurance. I looked through the usual shops around Z¨rich HB: Swisscom Shop, MobileZone, Phonehouse: All had the same prices (about CHF 250 for a two years contract at CHF 25 per month), except that Phonehouse had no E51 available in the shop. Interestingly digitec had a much lower price (CHF 100 for the same contract) and the choice of color (the shops always only offered one color), so I ordered a black one there. Converting a prepaid card to a postpaid contract isn’t that easy I wanted to change from a prepaid card to a postpaid contract, both at Swisscom, so I already own a SIM card. But digitec only offers new contracts including a SIM card or contract renewals, but no switching to a contract with keeping the number. And a new SIM card costs CHF 40 extra in their online shop. So I called their hotline and asked. The answer was: I need a new SIM card since prepaid SIM cards can’t be converted to postpaid SIM cards (but can be used with different providers). When I came to the shop, the employee needed three tries to fill out the Swisscom form for the number migration and still did it wrong somehow. No postpaid contract acknowledgement from Swisscom after two workdays. So I called their hotline. They told me, the wrong SIM card number has been entered and I need to make digitec to enter the correct one. A few days later back at the shop they were overextended. After a while an internal e-mail was on the employee’s screen which clearly stated that in case of prepaid to postpaid conversions (and a few other cases) no new SIM card must be given out and if this happens too often for the same employee he will be charged the CHF 30 a new SIM card costs digitec… (So they have a 25% margin of every sold SIM card…) About one hour after they closed their doors (I was there about ten minutes before shop closing time) Swisscom had accepted the contract changes and I had a credit note of CHF 40 for the erroneously sold SIM card. And the mobile phone became even cheaper than in all the other shops. :-) New gadget, new features So after a week, I can say that in general I’m quite happy with the new phone. It has a nice web browser, an IMAP over SSL capable mail reader and a feed reader, it can connect to the internet via WLAN and the 240x320 resolution isn’t as bad as I expected. I already have a Symbian port of PuTTY on it and sshing into my workstation works fine, even if I currently only have the phone keyboard and T9 as input device and helper. I also have Opera and Opera Mini installed, but to my own surprise the included web browser from Nokia (said to be based on Apple’s HTML rendering engine WebKit which itself is based on KDE’s HTML rendering engine KHTML) is way better, especially in navigation, even although Opera Mini 4.1 caught up a little bit in comparison to Opera Mini 4.0. (Hey, and you hear that from a web browser fetishist and Opera fan!) The only thing which currently really bugs me on the builtin web browser is that even an enforced updating of my feeds sometimes just results in nothing. Maybe a firmware upgrade can help… As barcode reader, I have installed the i-nigma Reader. (The Quickmark QR Code Reader download just showed the content of something which seems to be a Windows DLL instead of downloading it. *plonk*) It’s amazing how fast the i-nigma Reader recognizes a 2D barcode from Semapedia on my laptop screen. Of course I also have ScummVM on my new Symbian phone. I will also play around with Amora which turns your Symbian S60 mobile phone into a remote control for your presentations on Linux (or any other unixoid operating system) running laptop as soon as I managed to get an amd64 Debian package of it. (Currently there seems only i386 packages and no source packages available, but this may be due to the “Show all downloads” link gives a server error…) Oh, and many thanks to foosel since I found Amora in her blog. BTW: Any recommendations for a free (preferably free as in DFSG) Jabber and/or IRC client for Symbian S60 3rd Edition? I already downloaded and installed Gizmo5, but somehow it refuses to work each time I try to create an Gizmo account. Accessories Since the E51 has no QWERTY keyboard, I ordered a Nokia SU-8W Foldable Bluetooth Keyboard at Brack. It was a little bit bigger and thicker than expected, but OTOH the metal case seems to be very stable and robust. Since this keyboard is designed to fit on Nokia mobile phones it also has the two Nokia typical soft keys and the middle select key. So nearly all phone functions can be used with the external keyboard, even turning off the phone’s key lock. Only locking the phone’s keys again doesn’t work via the external keyboard. Additionally I equipped my E51 with a 2GB microSD card. Probably a bluetooth headset for driving will come once, too. What the Nokia 6310i did better than the E51 There are a few things which are annoying regarding Nokia’s UI consistency over the years. That the backspace key is no more the right soft-key is ok. It took me only five tries to get my e-mail account setup without hitting the abort key (no “Do you really want to abort?” questions ;-) instead of backspace key. But what’s really annoying is that the menu navigation via number keys only works for the first level and no more for all levels. So no more “menu 4 4 4” to switch to manual network selection. It’s also annoying that you (or at least I ;-) can’t enter phone numbers as the recipient of SMS directly anymore, at least those SMS never reach their receipient neither do I get an error message. Same counts for the missing acoustic acknowledgment of locking the keypad. You only hear pressing the first key but not even the second key anymore. And if you press the volume keys on the side of the phone, you also have neither acoustic nor visual feedback if you pressed them hard enough so that the volume changed. The 6310i had visual and acoustic feedback. The alarm clock in the E51 seems to be artifically castrated: After having pressed the snooze button two or three times there is no more snooze button on the right the soft key anymore. With the 6310i you could press snooze as often as you want. Only disadvantage with the 6310i in regards of the alarm clock: the snooze time was much too long (10 minutes)… Oh, and what’s also annoying is that I can’t move over the whole addressbook of my 6310i in one piece but have to send each contact via bluetooth or infrared and then the E51 even get’s the contact names mixed up: ‘Beckert, Axel’ becomes ‘Firstname: “Beckert,” Lastname: “Axel”’… Great! I have to edit nearly all contacts manually… The cut and paste feature helps here, but it takes about one to two dozens of key clicks to copy the whole content of a filed into the clipboard… The E51 can run several applications at the same time and that you can switch between them any time. While that’s generally a nice feature I started using quite soon, it’s sometimes annoying that you have to wait up to a second or so after you’ve chosen some menu entry until you can do anything further. Also the screen often flickers while loading applications, showing them, then showing only the background, showing them again, etc. … but finally I already got used to the new mobile phone so much that I already have the feeling that my old 6310i became more thick since I have the E51. (Won’t think about how thick the about ten years old 6130 feels now compared to the slim E51… :-)

Wouter Verhelst: Film: the story of the weeping camel

Just now, a movie was on TV. This was a non-fiction film, but it was still a story, rather than just a simple documentary or something; it only wasn't scripted or anything similar. The film is about a group of shepherds in Mongolia, who not only own sheep, but also camels, for transport. One of these camels gave birth to a rare white camel; however, the mother does not accept the young for some reason, despite the shepherds' best efforts. Eventually, however, they did succeed in calming the mother, and persuading her to accept the young. What really blew me away, however, is how they did that: By using music. Incredible. So, next time you need to calm down a camel, here is the procedure:
  1. Go by camel to the nearest town, and fetch a violinist.
  2. By way of a blue piece of cloth, attach the violin to the camel's side, and allow the wind to blow against the snares, so that it makes sound. The camel will start to make sound too, the tone of which will sound suspiciously close to the tone produced by the violin.
  3. Get a soprano to sing, while having her gently touch the camel's side. Preferably one who can sing incredibly beautiful. No, really.
  4. After half a minute or so, have the violinist join in.
  5. After yet a few more minutes, slowly and gently bring the young to the mother. Have the young drink some of the milk.
  6. The mother will now accept the young, while she was aggressive if you even brought the young anywhere near her.
Words cannot express how incredible this is. I mean, sure, music can have an effect on one's emotions; and if this is true for human beings, I'm sure the same can be said for animals. But this? Whoa.

Russell Coker: Debian Work and Upstream

Steve Kemp writes about security issues with C programs [1]. It seems obvious that if you are going to do something that is overly tricky (such as anything related to setuid programs) then you should have a good knowledge of what you are doing. Steve goes a little further and suggests that anyone who doesn’t know C should not package a C program. Andrew Pollock is a Debian developer who doesn’t program in C and yet packages some C programs, he explains why he thinks that it’s correct to forward C coding bugs upstream [2]. In this debate I have more sympathy for Steve’s position. Security is one of the most important things in software that we develop, if you can’t develop secure software then IMHO you shouldn’t distribute any software. Although it should be noted that the two posts in question don’t directly conflict. Steve’s main point (your should know the code well to do something relevant to security) does not directly conflict with Andrew’s main point that a non-C coder can maintain the Debian packaging files and forward bug reports related to C code upstream. In the more general case it’s often impossible to know all languages used in a project. It’s not uncommon for a single project to have core code written in C, a configuration file format (which is a programming language), a Makefile (GNU Make is a fairly complex interpreter), Autoconf/Automake (even more complex tools for creating complex Makefiles, and then some Perl or Python to manipulate input or output data. The SE Linux project has code in all those languages plus the M4 macro language. It seems obvious that in a large project the number of people who are capable of understanding all languages which are used is going to be a small sub-set of all Debian Developers. It also seems likely that someone who knows some of the languages really well may be capable of doing a better job than someone who has a passable knowledge of all of them. For the vast majority of my work in Debian I have been a member of the upstream project in question (for Bonnie++, Postal, Portslave, Maildir-bulletin, and logtools I’m the sole upstream developer). Often I start maintaining a package with the intent of doing the minimum needed to keep it maintained in Debian but then end up doing upstream work, for example I briefly had write access to the CVS repository for pppd when I was maintaining it and I had write access to the KDE CVS repository when I was working on KDE packages (which incidentally was before I became an official DD). When I first started working on the SE Linux project I aimed to merely package the code in question for Debian. I was not planning on spending seven years doing upstream work! When I’m working on a project I spend my time working on the things that most need attention. That often means that I get diverted from Debian packaging bugs (which are often minor issues) to work on upstream bugs. In many ways my work practices make me a Debian user and upstream developer who also does Debian packaging rather than a dedicated DD. This of course does have a detrimental affect on the quality of my Debian packaging work - but overall I believe that it’s best for the users! As an upstream developer who is focussed on Debian there are significant advantages in being a DD. I can immediately upload a new package to Unstable without any delay, and there is the potential to take over a related package (either be given the package or NMU) if it’s the best way to get around a roadblock. Another benefit is that in certain limited situations I can speak on behalf of Debian (in terms of packages I “own”). When it comes to upstream development of SE Linux I can make decisions about how things will be done in Debian and work with other upstream developers to ensure that cross-distribution compatibility works reasonably well. It seems to me that a fairly ideal process for managing Debian development would have the people who are capable of the hard coding doing so and some people who haven’t got specific coding skills working on the packaging. I would be very interested in receiving patches related to the Debian packaging of the packages I “own” (in Debian it’s widely regarded that a man’s package is his castle) so that I can spend more of my time on the C coding. I’m not bothered about NMUs (a Non-Maintainer Upload - is when someone else uploads a new version of one of my packages to fix a bug). If anyone would like to NMU one of my packages they are welcome to do so as long as there is a suitable combination of bug urgency, simplicity of the fix, and lack of response from me. If someone wants to start NMUing my packages to fix bugs reported by the latest version of Lintian in Unstable (Lintian is the Debian tool to automatically check for packaging bugs) then that’s OK. Of course there are a variety of other situations that DDs sometimes find themselves in. There have been situations of overtly hostile upstream developers. I try and avoid associating with people who have certain difficulties in interacting with others. If someone is going to change their license and try to back-date the change or create a license that makes it difficult to distribute modified versions of the code then I’m inclined to avoid even using the software, let alone being involved in developing it. This means that the software that I use in any serious way has reasonable people doing upstream development who welcome new people to join their work.

Clint Adams: The Legend of Bagger Baggs

One day the Stranger arrived. He was a tall and lanky teen, his face peppered with acne and sparse pubescent hair. He wore a wide-brimmed hat, a long coat, a scarf, and he was Strange. Some newcomers prefer to observe, to gauge the breadth and nuance of Social Custom, and to keep low profiles until they are comfortable enough to risk a misstep. This newcomer preferred to wield a bean bag, and to go door to door, knocking, introducing himself, and asking if there might be any nice conversation lurking inside in which he might join. Predictably, most people were horrified, frightened, and offended. They responded in a hostile fashion, and branded him Bean Bag Boy, or Bag Boy for short. A few others viewed him instead as a free spirit, a visionary, a unique character, and a Cool Guy. Perhaps they bought into the crap that society spews forth as part of its Campaign for Cognitive Dissonance. Perhaps they were just confused. Those that admired him branded him Doctor Who, a moniker of affection and respect. I will never understand this, even though I know which drugs they were on (Prozac, Zoloft, LSD, THC, psylocybin, and PCP, respectively). Bag Boy learned to keep mostly to those who appreciated his insane ramblings. Had he been motivated and competent, he probably could have been a minor cult leader. Instead, he fell out of public view for a while. When he returned, he had two younger companions: a boy and a girl. It became immediately obvious what to call them. The female, whose name, eerily enough, was Baggs, would be Bag Girl. Since Bag Boy already possessed that name, the male would have to be Little Bag. Little Bag was an enigma unto himself, and went on to have many adventures of his own. Once he called me a Zenmaster, so I will refrain from mentioning him for a long time. Bag Girl was no less a character. She detested being called by either her given name or her surname, and instead preferred to brandish an agglutinative designation of her own choosing: one part temporal adjective, one part finite act of performance. This contrasted delightfully with her appearance, which was not dissimilar to a three-foot-tall chinchilla. Most were content to call her by her chosen appellation, though some would add her real surname (to which she fumed bitterly), and one insisted on calling her by her given name, as a hostile act of hatred. Bag Girl's main hobby was a menagerie of characters that she explained were her multiple personalities. Unlike persons suffering from dissociative identity disorder, Bag Girl had full knowledge of her personalities and their doings. One of these personalities was a 90-year-old elf named Galiganda Dulin. Another was a man named Sayjon, who bore a suspicious resemblance to Pink Floyd's fascist alter ego from The Wall. In fact, Bag Girl had been profoundly affected by The Wall, although she had watched it while on LSD, so interpolation based on these data may be tainted.

Clint Adams: Administrivia

As part of a long overdue move to ikiwiki, this blog now lives here. Kindly update your subscriptions to the RSS and Atom feeds. I have attempted to convert all entries and preserve all but 4 permalinks. I apologize if any links or HTML broke in the process. If you do not see this entry at all, your aggregator likely does not understand HTTP redirects, and you should update your subscription with great haste.

Clint Adams: Mojado en ti

You sweep your toes across the sand as you stare at the ebb tide. Your gaze is focused but your mind is elsewhere. To be more precise, your mind is hopping somewhat rapidly between several different elsewheres. Your companion is standing nearby, blissfully oblivious. You muse that he is in the and you are in the . It is clear that you have been pretentious since you were young. You would prefer to call it precocious, but that term is no longer applicable. Your friends think that you have a sweet deal and would be a fool to throw it away. He treats you well, mostly. At least he spends lots of money on you and lavishes you with attention. Of course he does get a bit possessive. He thinks that with all the effort he puts into wooing you, he has earned some high status. Maybe he has. Of course, you hate him a little for putting you on a pedestal. Is it really you whom he sees, or some imaginary creature of his fantasies, some ideal to which you can never approach? Your ex treated you quite poorly by comparison. He was a liar, but in some ways he, if not his words, was more honest with you. There was something else that drew you to him, some reason you kept having affairs with him even though it upset your other boyfriends. The guy who treats you the worst, though, is the one you have been in love with for ten years. You are unaware of what has caused him to lash out at you, what unleashes his venom every time you sneak away to make yourself vulnerable to him. He acts like it is obvious, but your reasoning cannot produce a reasonable hypothesis. At last your consciousness lands on the man you secretly crave the most, so much that you never tell your friends about him. You think you would give up everything if he only asked, but he never asks. You have never been involved with him, and you fear that he would reject you cruelly if you let him know you were interested. You think that that would destroy you. You are perhaps a bit prone to melodrama. At any rate, you need to make the smart choices, and do the things that you would do if you were normal. So when your beau leans in for a moonlight kiss, you tell him how happy you are. Maybe someday you will be.

Clint Adams: Write-in campaign

Since Ari was too incompetent to successfully complete a self-nomination this year, I have taken the liberty of writing his platform for him against his will.
Ari's Platform What follows is a grassroots movement for positive social change through fostering and giving voice to initiatives and local activism, civic engagement, volunteerism, taking trendy Whole Foods tote bags to supermarkets that are not Whole Foods, and the broader motif of green, eco-friendly, environmentally-sound, community-based, issue-driven, civic-minded focus on saving the environment through awareness of energy and power. Even though recycling consumes lots of energy and pollutes the ground and water, do it anyway. You can make up for it by buying carbon offsets. You don't need to buy carbon offsets for aluminum can recycling, since that is actually good for the environment on a long-term basis, but you should, since it's Fun. Always recycle!
The worst team dynamics can be found in appointed teams. The best team dynamics can be found in self-selecting teams.
Give some thought to the teams (Small or otherwise) you observe. The self-selecting teams are well-oiled machines, competent and effective in every way. In stark contrast, the appointed teams are vulnerable to cronyism, acceptance of bribes, poor communication, pettiness, abuse of power, tunnel vision, xenophobia, and egomania. Who is appointing these teams? It should be stopped, and all teams should be self-selecting to avoid these problems. Face-to-face meetings and events are very important, but we are being terribly irresponsible by using planes, trains, and automobiles. We need to reduce our carbon footprint, so bicycles should be the preferred tool of transportation, and therefore travel sponsorship should be allocated according to these categories: Spandex, Chamois, and Mudflap.
  • Self-nomination
Currently, too many people nominate others for tasks. This leads to an unfortunate mix of egoists and people that no one believes can do the job. Even the nominators have no faith; the only reason they are nominating others is that they know it would be necessary to nominate themselves otherwise. Instead, everyone should take it upon themselves to self-nominate for any position they can, whether they are qualified or not, as it will look good on college transcripts. Only this can ensure that we get the most qualified applicants. Remember, if you do not claim to know better than everyone else, no one can trust you. Relations with SPI have been strained for quite some time, probably because their routine operations resemble a bad episode of The Simpsons. This can be fixed by delegating five hundred people to show up to each month's meeting and bikeshed about American politics and modern fashions.
  • Conservation of power and hats
There have been many attempts to defang concentrations of power and influence and all this does is prevent things from getting done. The proper solution is to give as many hats as possible to the people who get things done. They have already demonstrated that they are trustworthy by getting things done and by having hats, so there is no problem with giving them more hats. Ideally the hats would be fashionable. In order to prevent territorialism and cabals, each person with a hat should be able to give hats to anyone else, but only if the recipient already has a hat. If anyone collects 15 or more hats, he may crown himself High Milliner and proceed to award himself additional hats. Since women do not, as a rule, wear hats, they cannot participate in the hat exchange.
I do not agree with Ari's platform; therefore I will not be writing him into my ballot.

Clint Adams: Right between the eyes

Sometimes creepy shit happens, like a gay black man eating quiche and talking on the phone about The Prestige or a British man sending me a box of strozzapreti and a colander almost a year after I wrote this, then turning out to be the same man who is rumored to buy Laranejeira Prateada because of the suffusion of e's.

Clint Adams: The dysthm of the night

I was walking under Union Square, listening to Hank Williams, when suddenly Hank was completely drowned out by the blaring of Hypnotic Brass Ensemble. You have no idea how sad I am that I can identify Chicago street musicians.

Christian Perrier: lenny l10n NMU campaign continued...

In mid-February, I started the lenny l10n NMU campaign, to tackle down pending debconf l10n bug reports. This page give the list of targets. I'm currently down to "isdnutils" in that list and, this week-end, I launched several NMU processes (a full NMU process lasts for 27 days). I'll now do my best to sustain a rhythm of 2 packages a day. Of course, several "NMU intent" mails end up with an upload by the package's regular maintainer, which is the best that can happen. I also fix many little QA issues in such process, most of the time trivial errors reported by Lintian (which was a lot improved recently, particularly about doc-base sections, menu sections, empty maintainer scripts and a lot of such things. As of now, 45 packages have been done (either by me or their maintainer) and 38 are in the pipe. As a result, all languages statistics are improving a lot. Four languages are now over 90% and 12 are over 50%!
fr   : 9507/9720,  213 missing, 97.80%
de   : 9349/9720,  371 missing, 96.18%
cs   : 8971/9720,  749 missing, 92.29%
pt   : 8757/9720,  963 missing, 90.09%
vi   : 7731/9720,  1989 missing, 79.53%
nl   : 7394/9720,  2326 missing, 76.06%
es   : 6562/9720,  3158 missing, 67.51%
sv   : 6547/9720,  3173 missing, 67.35%
ru   : 6213/9720,  3507 missing, 63.91%
gl   : 5870/9720,  3850 missing, 60.39%
ja   : 5836/9720,  3884 missing, 60.04%
pt_BR   : 5095/9720,  4625 missing, 52.41%
it   : 4538/9720,  5182 missing, 46.68%
fi   : 4589/9720,  5131 missing, 47.21%
ca   : 3954/9720,  5766 missing, 40.67%
eu   : 3942/9720,  5778 missing, 40.55%
da   : 3435/9720,  6285 missing, 35.33%
nb   : 3129/9720,  6591 missing, 32.19%
ml   : 2876/9720,  6844 missing, 29.58%
bg   : 2808/9720,  6912 missing, 28.88%
hu   : 2684/9720,  7036 missing, 27.61%
ro   : 2636/9720,  7084 missing, 27.11%
ta   : 2612/9720,  7108 missing, 26.87%
lt   : 2603/9720,  7117 missing, 26.77%
sk   : 2576/9720,  7144 missing, 26.50%
tr   : 2527/9720,  7193 missing, 25.99%

Next.

Previous.