Search Results: "ag"

22 November 2006

Gunnar Wolf: AGH! The Devil! The Devil!

Winter is mercilessly arriving in Mexico City. This is the third day we get an average temperature of 10 Celsius (although the first day it happens with a nice, unclouded sky, as Winter is usually offered here). People wear jackets everywhere, and every conversation starts with mention of the cold weather. Of course, remember very few people have any kind of heating here, as the lowest we ever get is close to the freezing point.
In general lines, I enjoy our winter. However, something happened today that made me have apocalyptic visions: Automatic, synthetic and terrible Christmas music. Yes, somebody brought to the office musical Christmas decorations. I have two choices: Listen to my music loud enough to bother other people (and drown the Christmas chimes) or just go nuts. Well, three choices. If they don't stop it, I might just short-circuit it so it goes to hell forever.

Edd Dumbill: Three things I would be doing if we had Thanksgiving in the UK

Working as much with the US as with the UK, Thanksgiving is always a noticeable holiday for me, even if I still have to work. If I had the luxury of the holiday this year, I'd be
  1. Staying up all night to follow The Ashes. Sporting competitions founded in the 1880s don't have much regard for television and radio audience hours, alas.
  2. Going to evensong at York Minster. The intimate and historic choir is an amazing experience at this time of year, as the candles take over from the weak winter sun.
  3. Encouraging people to use the holiday to prepare their submissions for XTech 2007. Springtime in Paris and top technology seems like something to look forward to.
As it happens, I'll do No. 3 anyway and reluctantly miss out on the others. Happy Thanksgiving to my friends and colleagues in the US.

Uwe Hermann: Tagesschau Video Podcast Archive?

Does anybody know about any archive of the Tagesschau Video Podcast (German TV news)? I'm collecting the videos, and I missed the shows from November 8th and November 13th, and they only provide 7 days of "backlog", after a week they seem to remove the videos (which sucks!)... Thanks in advance!

21 November 2006

Erich Schubert: Iceweasel is the latest firefox

Debian unstable now has iceweasel. Running iceweasel presented me with the pretty message
You've Updated To The Latest Version of Firefox
Great. Note: Ubuntu has more patches to firefox than Debian, so if Debian is (or: was) violating Mozillas trademark, so is Ubuntu. And probably Fedora. And Redhat. And Gentoo (well, maybe not; from what I know Gentoo is closed to unmodified upstream usually, and not as anal about LSB and desktop integration etc. as the others), ... you name it. Anyway, go, iceweasel, go.

Daniel Stone: an impenetrable wall of stupid

Kinnison points out a fantastic patent application, in which claim nine makes the attorney, and 'inventor', simultaneously look incredibly stupid (but the attorney in the first place reasonably clever, up to a point).

Funny though that is, it still has nothing on the patent for a circular transportation facilitation device that a Melburnian took out a few years ago. I don't know what's worse: that it got through, or that you just expect it to have gone through.

Benjamin Mako Hill: Writing and Writing Code

Over the years, I've published some of the articles I am most proud of on Advogato. As you can imagine, I was sad to see demise of Advogato announced early September and thrilled to see that by the end of the month, Steve Rainwater had stepped up to save the site. For a belated welcome of Advogato back from the edge of the grave, I've published a short essay about the effectiveness of an analogy of software and writing on the site. In it, I introduce the analogy and argue that it is useful in advocating free software and programming education and in justifying the disproportionately large amount of programming related projects in the free software world. Here's the intro:
Advocates of free and open source software, myself included, like to talk about the "democratizing" effect of free software. Others, especially non-programmers, are quick to point out that the only technical people can take advantage of half of the enumerated freedoms in FOSS. The freedoms to modify and collaborate mean little if you don't know to program. Over time, I have come to the conclusion that the only good solution to this problem -- and one that I was initially quite opposed to -- is to teach everyone to program. In considering this position, the processes of reading and writing provide a useful analogy when considering the processes of using and creating computer software. Additionally, the analogy provides an powerful justification for the fact that FOSS programmers produce a disproportionately large amount of software that is primarily of interest to FOSS programmers.
Please check it out on Advogato and feel free to leave a comment on my blog if you don't have an Advogato account.

Benjamin Seidenberg: How to set up an encrypted filesystem in several easy steps

Introduction: This guide will walk you through the creation of an encrypted filesystem using LUKS. LUKS is the Linux Unified Key Setup and is a standard format for linux hard disk encryption. It has a lot of interesting features such as using a key on a removable disk, keeping multiple keys, and more. This is the technology used by the Debian Installer (since etch beta3) and is quickly becoming a standard in the linux world. Who this guide is for: This guide is for anyone who wants to secure their data using an encrypted partition. While it is tailored to users of Debian, it should apply elsewhere in the linux world. This guide is intended to add an encrypted device to an existing install, if you are contemplating a fresh install, the Debian Installer will configure encrypted filesystems for you. Ready? Then let’s begin Prepare the partition (or other block device) to be used This can be a partition on disk, a logical volume in LVM or some other block device. For this example, I created a 40 GB volume in LVM. Install cryptsetup This utility provides an interface into the code in the linux kernel that handles encrypted block devices. It’s packaged for Debian in both testing and unstable, stable has an older version and I don’t know whether or not it will work in the same manner.
apt-get install cryptsetup Set up encryption on the partition: This initializes the partition for encryption and sets the initial key. People not using LVM will want a path like /dev/hdxY where hdxY is the partition on their hard drive that will be used for encryption. Important! This command will wipe out anything on that partition
cryptsetup luksFormat /dev/mapper/asimov--vol-crypto_test
WARNING!
========
This will overwrite data on /dev/mapper/asimov–vol-crypto_test irrevocably. Are you sure? (Type uppercase yes): YES
Enter LUKS passphrase:
Verify passphrase:
Command successful.
Congratulation! You now have an encrypted block device! However, it’s not quite ready to use. Open and map the device: This opens the device (prompting for a passphrase) and maps it to a block device in /dev/mapper. This can be used like any other block device, and the encryption/decryption is transparent. The first path (/dev/mapper/asimov–vol-crypto_test) is the encrypted partition you set up earlier. The name (crypto_test) is the name of the volume, the block device will be mapped as /dev/mapper/<name>.
cryptsetup luksOpen /dev/mapper/asimov--vol-crypto_test crypto_test
Enter LUKS passphrase:
key slot 0 unlocked.
Command successful.
Create the filesystem of your choice on the device: This is just like setting up any other block device. I use ext3, others may prefer different formats.
mkfs.ext3 /dev/mapper/crypto-test Add the definition to /etc/crypttab: /etc/crypttab is a list of encrypted devices that are mapped on boot. The format is <map name> <path to device> <key file> <options> Since we’re using a passphrase, we don’t have a key file.
crypto_test /dev/mapper/asimov--vol-crypto_test none luks Create a mount point: This is where the encrypted device will be mounted on your filesystem.
mkdir /mnt/crypto_test Add the device to /etc/fstab: /etc/fstab tells the computer where to mount different devices on the filesystem. The format is
<source path> <mount path> <type of filesystem> <options> <mount options options> <dump frequency> <fsck pass> More information can be found by reading man 5 fstab. You will want to add a line like this: /dev/mapper/crypto_test /mnt/crypto_test ext3 defaults 0 2 somewhere in this file. Update the initial ramdisk. The initial ramdisk is used to jumpstart the boot process and load modules for the kernel that it can’t load itself (such as drivers for block devices that contain the modules it uses). I’m not sure if this is needed or not, but I wanted to be on the safe side.
update-initramfs -u -k all Congratulations Now your encrypted filesystem is completely set up! Reboot the system and you will see it prompt you for your passphrase during the boot cycle. Once the password has entered, the encryption is completely transparent. If you want to use your encrypted filesystem before rebooting, simply type mount /path/to/mountpoint.

Matt Brown: MyVFX first impressions

There has been a lot of interest recently in the VFX VoIP service launched by WorldXchange (WXC), no doubt partly driven by the fact that there is no monthly charge until April 2007. I had a spare Linksys PAP2T so I thought I would try the service out to see how it performed. The signup process didn’t go anywhere near as smoothly as it did when I signed up for my WXC DSL connection. The online signup form tried to force me to select a new WXC DSL Plan (I don’t want to do that, I want to keep my old plan with free National traffic). Despite trying several times and making sure that the only checkbox ticked was VFX each time, it refused to let me go any further. Giving up on the web form, I rang the WXC helpdesk who answered promptly. It is easy to see why WXC won the 2006 award for best call centre. Every time I deal with them over the phone it is a pleasant experience. This time was no exception. The CSR I was talking to explained that the webform was dying because I tried to use a VFX username that differed from my WXC DSL username. There was no mention of this restriction on the website! Anyway, 15 minutes later, with my MAC address taken down and my voice recording completed, I was told we were all done and that I would receive my welcome email and account details with 2 working days! 24 hours later I received the email with the details, followed promptly by a phone call from WXC CSR who was ready to talk me through the process of setting up my PAP2. Configuring the PAP2 was a simple procedure, I had to copy and paste a URL into the Provisioning Rule field of the web interface and reboot the device. It then downloads configuration information directly from WXC (based off the device MAC adddress) and configures itself. I was up and running with dial-tone about 2 minutes after receiving the email. Very smooth. I understand that the process is even easier if you purchase a pre-configured PAP2. The downside to the whole scheme is that in trying to make the process as simple as possible WXC has locked the entire system down very tightly and remove a lot of the flexibility that I would desire. In particular my PAP is now completely locked, I can’t access any of the web interfaces, and even the dial-in prompt on the PAP2 replies with a curt “cancelled” before hanging up. There is no way for me to configure the second line of the device to talk to a second SIP provider. Apparently WXC will create a custom configuration for me so that I can still use the second line, but I imagine this requires giving them all my account details for my second SIP provider, which I’m not sure I’m comfortable doing. It also appears that WXC has an arrangement with Linksys such that every PAP2 now sold in New Zealand comes pre-configured to be used with WXC. I haven’t had a chance to look at one of these PAP2s yet, but if it were to turn out that I had to contact WXC to remove the locking on my PAP2 before I was able to use it with another VoIP provider I would be fairly annoyed. The MyVFX portal is very underwhelming. It insists on opening itself in a new browser window, and isn’t integrated with the rest of the WXC/VFX website. From what I can make out it’s just a branded frontend on to the management system that WXC has purchased. The user interface is reminiscent of the design of the 1990s. I think there is a lot of potential for WXC to improve the experience in this area and I doubt that the average user would be comfortable updating settings via MyVFX in its present state. On the technical side of things the VFX service seems to be fairly well designed and secured. The devices are provisioned and configured using the Linksys/Sipura provisioning tools, which appear to encrypt all conversations with the device. The setup process downloaded two configuration files and a firmware file (v 3.1.10) to my PAP2. Both of the configuration files were binary and appear to be encrypted. Interestingly it appears that WXC downgraded the firmware from 5.1.1 to 3.1.1 during the provisioning process. The MyVFX portal and SIP server appear to be using some sort of BroadWorks device. The device fetches it’s configuration file from the WXC server every time it is powered on, so it will be easy for WXC to push out updates and configuration changes as they desire. The VoIP side of things is performed using SIP, which appears to be using standard HTTP Digest authentication. The username and passsword for this being hidden inside the encrypted configuration files which are downloaded to the device. The voice data uses the G.729 codec inside an RTP stream, and from a few short calls seems to be relatively good quality. Conclusion
Overall, VFX seems like a very easy to use and simple service. Simple being the keyword. By locking down the devices so securely and preventing people from using softphones and devices other than Linksys equipment I imagine many people like myself are excluded from the potential market. I can’t see myself keeping the service after I have to start paying money for it. But I would definitely recommend it to friends and family who are looking for a simple, easy to use VoIP system.

Joey Hess: DWN bits 3

I skipped a week or two due to injury and lack of energy, but here are some more items for dwn. d-i etch RC1 was released, featuring a 2.6.17 kernel, easy setup of encrypted LVM, improved installation automation, and the return of installation floppies for i386, plus many other improvements and bug fixes. The improved NSLU2 support in this release in particular seems to be attacting a lot of attention. An RC2 with 2.6.18 is due soon. A release update was posted by Steve Langasek, it discusses an update of the timeline for release, calls for increased testing of etch, updates the release goals, and last but not least, unveils the codename for etch+1: lenny Changes are afoot to ftp-master.debian.org. While not yet officially announced anywhere, it's moved to a new, much more powerful server with terabytes of disk. Also, a new gpg key has been added that will be used to sign etch's release files for the lifetime of etch. Since this key isn't yet in the debian-archive-keyring package, there might be some minor issues when using apt, and debmirror is known to be broken by the unknown key. For now, the new key (6070D3A1) can be downloaded from subkeys.pgp.net. apt-zeroconf was announced by Franz Pletz. This is a decentralised apt cache that uses avahi to find other instances of itself on the LAN and share packages back and forth. Perhaps this will be useful at the next DebConf, which is now open for registration. The browser generally known as Firefox 2.0 has reached unstable as a new iceweasel package. Bug #354622 contains the sad backstory to this renaming.

Dann Frazier: Debian/ProLiant support active

As announced in August, HP has now gone live with support for ProLiant. More information is available at http://hp.com/go/debian. Admittedly its odd to announce sarge support right before etch releases, but hey - we had to start somewhere. On a similar topic, I started a wiki a while ago to track the status of sarge and etch on various ProLiant models. I think it'd be cool to have similar pages for various vendors. By linking to d-i installation reports, I hope this will reduce duplicate information.

Biella Coleman: A spirited debate on the liberal frame of mind

This morning I came across Michael Berube’s response to Jodi Dean’s critique of Berube’s book What’s Liberal about the Liberal Arts?: Classroom Politics and Bias in Higher Education… It is a fascinating interchange worthy of a close read or two but without first-hand knowledge of the book, I hesitate to pledge my allegiance on either side. But I will hopefully to do so. The only thing that surprised me was that there was no mention of the grand master of the critique of liberalism, Stanely Fish… Not sure why but he seems like an obvious place to start. These ppst happened to really captured my attention this morening given I found them after reading the Chronicle of Higher Education piece Input or Intrusion? which examines the recent attacks against scholars deemed as “anti-Israel/pro-Palestine,” including against Nadia Abu El-Haj who happened to be on my dissertation committee… It will be very interesting to see how this all pans out and I am sure many of us are watching closely. And as an added bonus, here is a student’s thoughtful perspective on the Berube book.

Joachim Breitner: Unicode Hack

(No, this is not security related. Some people call screensavers hacks . But I did get your attention, didn t I?) Whenever I happen to run gucharmap, I like to just browse and have a look at all those weird characters other people, especially asian, are using: A lot of them look really cool. So I thought: This would be a great screensaver.After some API digging I created that screensaver. It uses fontconfig to open the FreeSans and the DejaVu Sans fonts, selects a random glyph from these and display s it full screen. Below, the unicode code point and characer name are printed. After a few seconds, the next character is displayed nothing else, nothing hectic, quite relaxing.When you download the code, you will find a file uncode.c , which is the hack itself, a file unicode-names.h , which is taken from gucharmap and only slightly modified, as well as a buch of files from the xscreensaver distribution. To re-compile the binary, use the script compile , which runs gcc with flags I stole from the xscreensaver Makefile. I know this build system is everything but correct or sensible, but it works for me...Unfortunately I don t think it can be included in xscreensaver, as it depends on libfontconfig. If someone would rewrite it using only libX11, this might be possible, so if you like it, feel free to steal the idea.

Adam Rosi-Kessel: Climate Dread

Via mariuss’ weblog (discovered accidentally, provides an unusually high signal-to-noise ratio for a random blog), this Canadian article entitled Coping with Climate Dread. Read it. Then read Elizabeth Kolbert’s article, “The Darkening Sea: Carbon Emissions and the Ocean” in last week’s New Yorker Magazine. (Sadly, the content does not appear to be online — if the New Yorker put only one article online, it should have been that one. As a consolation, there’s a short excerpt here, and a related article is available from last year.) It’s become a lot harder to think about this problem since I had a kid.

Steve Langasek: midterm report

This is the first of my two formal reports to the Dunc-Tank board on the release management funding experiment. Although submitted to the board some time earlier, I've delayed publishing it to the wider community until a release update could be sent out with more concrete information on timeline adjustments as Debian developers are wont to demand.
I'm supposing that I don't need to give you any more specific details on what I've been working on than what's already been posted in my blog. There has certainly been plenty to keep me busy the past three weeks, including a lot of triage work on the state of bug reports in the BTS, managing the last of the major package transitions into testing for etch, removing packages and NMUing them, and it has indeed kept me busy. Busy enough that I've been lax when it comes to talking about it, either here or in my blog. :) Has the hard work paid off? Well, http://bugs.debian.org/release-critical/ shows a sharp decline in release critical bugs affecting testing over the same time period, following the peak resulting from Dunc Bank's successful campaign of identifying latent release-critical bugs in etch. Unfortunately, we have no statistics that track the number of RC bugs closed or opened over time, which makes it hard to judge how large of a dent my own work has made in the overall bug count. It's also totally guesswork to try to judge whether Dunc-Tank has encouraged others to help with the release overall, or discouraged them from doing so. What I can say is that, even though the past month coincides both with the tail-end of the Dunc Bank mass bug filings and multiple archive-wide rebuild efforts, the bug count is moving in the right direction, and I am seeing many maintainers being responsive to bugs in their packages and a number of active NMUers. If not for the buzz-kill of Lucas Nussbaum's latest round of build failure reports :), we would be down from over 300 RC bugs to less than 200 right now, which probably represents at least twice that many RC bugs closed. In terms of how the time I'm putting into this release compares with the sarge release, I'd say it's pretty comparable. That's actually quite a positive statement about Dunc Tank's role, IMHO; getting a Debian release out is uphill all the way, and whereas the sarge release came at a time when I was in a position to work more or less full time on it without compensation, my availability this time around would have been greatly reduced, and progress would have been much more heavily dependent on individual maintainers and semi-periodic bugsquashing parties, which I'm not sure is any longer enough to offset the rate at which new RC bugs are created in the distribution by uploaders. As it stands, I do find myself trying to consciously avoid a hero complex of needing to fix every bug personally, but there are after all only so many options for getting bugs fixed for release. A lot of maintainers respond positively to gentle nudging about their RC bugs, but there are still bugs that the maintainers can't or don't fix and that no NMUers take on, which does leave it more or less up to the release managers to address -- which is why one of my tasks for this week is to try get the count of RC bugs over 20 days old down from 90 to around 20-30, as these are the bugs that really do need more attention to get them resolved. So yes, Dunc-Tank is making a positive difference. Andi and I have reviewed the status, and while we don't think we'll be able to hit the Dec 4 deadline (even if we get the bug count down immediately we're waiting on the debian-installer to release, which needs at least one more release candidate with the 2.6.18 kernel), we do believe that a release before the end of the year is very possible and I'm looking forward to starting the full freeze in the next few weeks.

Ben Hutchings: Interface checking

Robert Collins writes: "Added to my list of 'things we need'... a version of icheck that requires less configuration to hook into package builds. Ideally one that we can get running automatically on any package build." There's only so much you can do without having debug information from both versions, which of course we don't keep at present. However, Steve Langasek implemented some basic checks on exported symbols in the unixodbc package which you can find in its debian directory. I'm slowly starting to work on a more comprehensive ABI checker that would use debug information. This would require someone to keep or rebuild debug information from the previous version (and to delay stripping it from the new version) so I don't think it could be automatic.

Piotr Roszatycki: Lost and Found in NEW packages

Yesterday I uploaded new ossp-uuid packages. Today I was worried why they weren't in incoming.debian.org nor archived in sid... I forgot that new upstream brought new binary package (libossp-uuid15), so it came to NEW and BYHAND packages queue. The Iceweasel stucked there for 90 minutes. My package is still in queue for 15 hours. All packages are equal, but some packages are more equal than others :)

Andreas Barth: RC bug p0rn, bugsquashing

Monday morning started with setting up two more graphical stats about the number of Release Critical bugs. They contain how many RC bugs affect etch currently, how many affect only etch (i.e. usually untransitioned fixes), how many affect both suites, and how many affect both suites after 20 days. Both graphs are available for the last 3 weeks and 3 months, respectively at http://bts.turmzimmer.net/graph-small.png and http://bts.turmzimmer.net/graph-large.png. As you can see with the large graph, we did some important progress. As the small graphs show, we should try to get better again. :) So, let's work together on that, and let all three curves go down again. After that was done, some normal RC bug squashing started - nothing special about, just "another few bugs gone".

Biella Coleman: These two services I am prepared to acknoweldge, but I do not know of any others

So I am housed in University of Alberta Department of Philosophy as my supervisor is a philosopher and there is no seperate STS department. And this “academic housing” certainly has its advantages, like for example, learning about probably one of the most audacious (and frankly amusing) statments on religion ever… by Bertrand Russell:
My own view on religion is that of Lucretius. I regard it as a diseaese born of fear and and as a source of untold misery to the human race. I cannot, however, deny that it has made some contributions to civilizaion. It helped in early days to fix the calendar, and it caused Egyptian priests to chronicle eclipses with such care that in time they became able to predict them. These two services I am prepared to acknoweldge, but I do not know of any others. Bertand Russel. “Why I am not a Christian” p. 24
I am sure he turned over in his grave when his daughter said:
“He was the most fascinating man I have ever known, the only man I ever loved, the greatest man I shall ever meet, the wittiest, the gayest, the most charming. It was a privilege to know him, and I thank God he was my father.” Katharine Tait, My Father Bertrand Russell, NY: Harcourt Brace Jovanovich, 1975, p. 202.

Evan Prodromou: 29 Brumaire CCXV

Well, I finally got around to doing it -- I signed up for an i-name on 2idi. i-names are a universal identification format for the Internet -- kind of like OpenID, but a lot more centralized and a lot more authoritative. My i-name, for example, is =evan.prodromou -- a brief little string that doesn't really say that much. But you can make it an URI with an "xri:" prefix, and it can be resolved at http://xri.net/=evan.prodromou is the canonical link to my blog, and =evan.prodromou/(+work) is the canonical link to my work. I can change the forwarding when I change blogs (or work, or whatever). It's a neat system, and I guess it's pretty complimentary with OpenID. OpenID 2.0 will support i-names for login, although I'm not sure how well it works. I'm going to be upgrading Wikitravel to use the new OpenID libraries soon, so it'll be i-names capable... and I'll need a testing account, of course. tags:

ikiwiki supports OpenID Ikiwiki is a wiki/blog/CMS engine by the unstoppable hacker Joey Hess. He just announced that he's made an OpenID plugin for ikiwiki. I think that's pretty cool. tags:

Robert Collins: 20 Nov 2006

Added to my list of 'things we need'... a version of icheck that requires less configuration to hook into package builds. Ideally one that we can get running automatically on any package build. Yes, its sci-fi, but avoiding ABI breaks across all libraries would be fantastic.

Next.

Previous.