Search Results: "ag"

21 February 2008

Chris Lamb: FOSDEM 2008

I’m off to FOSDEM in a few minutes (it’s nearly bedtime, right?), getting the 10:00 Eurostar. Give me a shout if I owe you a beverage or something..

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.

Benjamin Mako Hill: Creative Commons and the Freedom Definition

Creative Common Seal for Free Cultural Works Yesterday witnessed the most important step forward for the Definition of Free Cultural Works (DFCW) since its adoption and endorsement by the Wikimedia Foundation a year ago. Although I might have wished things otherwise, Creative Commons is not a social movement fighting for essential freedom or the essential freedoms at the core of the DFCW in particular. From the movement's perspective, CC is more like a law and advocacy firm that works for us -- a very sympathetic one. CC writes, hosts, and supports a variety of licenses. Some are free. Some are not. Last year they took steps to explicitly limit the extent of restrictions they are willing to tolerate in their licenses. Yet, while CC has resisted taking a stand in favor of the Definition of Free Cultural Works, they continue to produce some of the best free licenses, tools, and metadata available and they seem honestly interested in helping users interested in social movements based around these definitions organize more effectively. In perhaps its most important move to date in this area, Creative Commons announced yesterday that it was placing a seal on each of its licenses that provide the essential freedoms laid out in the Definition of Free Cultural Works. The seal links to the definition over at freedomdefined.org. In Creative Commons' words:
This seal and approval signals an important delineation between less and more restrictive licenses, one that creators and users of content should be aware of. A very practical reason users should be aware of these distinctions is that some important projects accept only freely (as defined) licensed or public domain content, in particular Wikipedia and Wikimedia sites, which use the Definition of Free Cultural Works in their licensing guidelines.
The seal is currently on two CC licenses that provide for essential freedom (Attribution and Attribution-ShareAlike) and their public domain dedication. Thanks go to Erik Moeller at the Wikimedia Foundation and everyone at Creative Commons to helped make this happen.

David Nusinow: Two Fun Things

1. After several years of it sitting on my shelf, I finally read Kernighan and Pike's "The Practice of Programming". I was always a little intimidated by this slender little book. I felt like it was full of wisdom that I couldn't really absorb at the right pace. Now that I've spent some time working on more challenging code and trying to come to grips with at the least the basics of more advanced computing concepts it was the right time to read it. I can't recommend it highly enough, it really is packed with wisdom. I've got Kernighan's "Software Tools" on the way, and I'll post a proper review of this at some point since it's not as well known.

2. I decided to spend a little bit of time poking at the almost-but-not-quite-dead language Dylan. I'd remembered being curious about this language back from when I was a serious Mac child in the mid 90's, since Apple was hinting that it would be the future. While the Gwydion Dylan implementation was removed from Debian, there's binaries for both it and the OpenDylan implementation that can be downloaded and run on both Sid and Ubuntu.

What I can grasp of the language is interesting. It's sorta like what little I know of scheme, except that it's got an object system that is apparently like CLOS from Common LISP, which I also don't know. Most notably though, is that even though Dylan is considered a LISP it doesn't look like one at all. There's no parentheses except what you'd expect, and things are infix rather than prefix, so it looks more like algol-derived languages like C. It's strikingly easy to read, and while the object system is very different from C++-style, it's fairly easy to grasp because it relies on familiar concepts like multiple dispatch to work. It's optionally typed, which is something I've been after (give me safety when I want it, but don't force me!) and provides all sorts of cool things like closures. Additionally, it does allow hygienic macros, which are apparently LISP's claim to power and fame, although I don't understand such things yet even in Dylan. Despite all this, the language appears to be relatively simple, which seems nice. It seems to be a very well designed language that was allowed to languish in obscurity because Apple abandoned it*.

Unfortunately the implementations aren't really all there yet. I ran in to obscure compiler bugs in gwydion writing something as simple as quicksort, and gwydion doesn't really have much of a standard library yet, although it can apparently bind to C quite well and fairly easily (this is something I haven't tried). In addition, there's OpenDylan, which is even less there on Linux, because it was an opened commercial compiler (derived from the original Apple one I believe) and it's had fewer people working on it. It seems to have a very large library, but documentation is sparse on it and I haven't had any time to really go after it. I've really been using gwydion exclusively, although I'd love to see OpenDylan get up to speed. While I have no time to really work on anything outside of X right now, this seems like a good language that deserves some attention.

* This is a familiar story to all of us who lived through Apple's mid-90's

David Nusinow: Where I've Been, Where I'm Going

After about two weeks I'm finally able to come back to Debian, which feels good. After my last package upload was botched (and gracefully recovered by my teammates) I realized that I needed to step away for a little bit.

I'm currently in my fifth year of my PhD program. For those who don't know how such things work in the US, I have a small committee of people (my thesis committee) who act as advisors and gatekeepers on my work. They're the ones who gauge my progress, and ultimately give me permission to write my thesis and receive my doctorate. I'm supposed to meet with them every 6 months, and it had been over a year since my last meeting. Because I'd like to actually graduate one day, I was rather nervous about having the meeting. I was more nervous than I realized, and the botched upload reflected that.

Anyway, to make a long story short, the meeting went as well as I could have hoped for and my committee seems to be happy with my progress. I'm looking to get a paper out in the spring, and they'd like to meet with me again in three months time (which will absolutely fly by) to assess where that paper is at, and how things are going. At that point, I wouldn't be surprised if they tell me to write my thesis and graduate.

What I do after my dissertation work has been weighing on my mind for years and years, and it's obviously coming to a head. My boss will let me stay on as a post-doc in the lab for a while, which I may do depending on other job opportunities and progress on my projects. Ultimately though I need to make a decision that's familiar to a few others in my position. Do I stay in science or go try and work on free software for a living? I honestly don't have an answer yet, because I love them both.

I see tons of incredible opportunities in my field right now, and while I'm not the only coder interested in synthetic biology, I'm one who's positioned to get in on the ground floor of the science in a very real way and have a significant hand in shaping its future. On the other hand I spend my free time devouring computing literature, not biology literature, as well as producing software and things related to it. I do this because I enjoy it, and I know I enjoy it on a deeper level than the biology. Would I enjoy it this way if I did it for a living? I've got no idea, since I've never coded professionally.

I'm coming up to the fork quite fast now, and I'll have to choose soon. I know I'm lucky because I do have the chance to choose for myself, but that doesn't make it any easier.

Tore S. Bekkedal: A very cute bug

Today, in a fit of fool-Hardy-ness, I upgraded one of my computers to the most recent Ubuntu development release, codename Hardy Heron. Amongst the several other bugs I encountered (the kernel not booting was a rather noticable one…) was this adorable little bug in tracker. (Some background info: Tracker is a file alteration monitor - like Apple’s Spotlight, and …whatever the Vista knockoff is called. ImageMagick is an image processing utility, invoked with the command “convert”.) So - picture this situation: Tracker is searching along, and encounters a graphics file. Being a graphics file, Tracker realizes it wants a thumbnail. Tracker calls convert. Convert creates a temporary file. Tracker notices a file has been created. It notices that this file is an image file, and therefore wants a thumbnail. Tracker calls convert… You can guess what happens from here on. :) This lovely bug reminds me quite a lot of a story I read a while ago which had been uploaded by Eric Smith to his wonderful PDP-6/PDP-10 resource and folklore website, “I/O Deja Vu, A Farce in One Act“. Worth a read. Update: Within ten minutes, the very helpful Saleem Abdulrasool (”compnerd” on IRC) helped me debug it and comitted a change to upstream, so it’s fixed in the next release (expected in a few days). Filed a bug on the Ubuntu package. I love FOSS. :)

Dirk Eddelbuettel: Time flies ...

... when you're having fun. This blog turned five a few days ago.

Marc 'Zugschlus' Haber: Debian Installer from an USB stick

For various reasons, I usually carry an USB stick with me that holds a single ext2fs and has grub installed. This blog entry quickly documents how to copy a Debian-Installer to it to be able to quickly install Debian without the need to burn a CD. I had tried this stunt last year already, but without success. I don’t know whether Debian Installer was not able to boot from an USB stick back then or if I was just too stupid to do things right. This procedure was done with today’s d-i daily image, so I guess that it will work this way in the future. I’d like the USB stick to be useable for other things even if d-i is available on it as well. So I would have liked d-i to be confined to a single subdirectory, which is possible with today’s code. The Installation Manual is rather verbose about booting from USB stick. The only challenge is to find the Kernel and the initrd files that are needed to actually boot. The exact path to these two files is not in the manual, but the nice people on #debian-boot confirmed that these are the correct ones. The second challenge was a non-issue for me since grub was already installed and functional on the USB Stick (its installation was also surprisingly straightforward). Next step: Create a directory on the USB stick and copy vmlinuz, initrd.gz and an arbitrary Debian CD image there. I used the daily netinst image. root (hd0,3); kernel /d-i/vmlinuz expert; initrd /d-i/initrd.gz and boot That’s it. The installer boots, finds the CD image, mounts it and pulls its components from there. The rest is a normal, stock Debian installation. Debian Installer rocks. It nearly always does the right thing.

MJ Ray: The Myth Of Deregulation

Russ Nelson: The Influence of Government writes:
"Larry Lessig proposes to lessen the influence of money on legislators. Unfortunately for him, he is trying to hide a symptom without curing the disease. The disease is that governments regulate businesses. The symptom is that businesses then have a profit motive in regulating governments. If you want a government which is free of corruption, you have to eliminate the motive for corrupting them."
which looks like utter bovine excrement to me. Corporations - and the overpowering profit motive of some corporations - are artificial things, created purely by regulations. If you free corporations from all regulations, you destroy them. If you only free them from taxes, you remove some of the few restraints on their bad behaviour in pursuit of profit. See Joel Bakan: The Corporation for a better approach. In summary:- Some of those may seem surprising, but if you read the book, you'll see why those conclusions make sense.

MJ Ray: Finance & Business / Where would you shop ethically?

Where would you shop ethically?  It's a simple question, but is there a simple answer? 

Tescos systematically dominate small traders, as might happen again in Mill Road Cambridge.  Sainsburys are currently trying to remove delivery time restrictions in Worle which is just going to disrupt and devalue neighbouring homes.

It's very hard to avoid supermarkets and the leaders in ethical supermarkets are probably the Cooperative Food stores and M+S (with their Plan A) but you probably can't get a full shop from them, at least in Weston.  Would you accept missing a few items (and maybe buying them elsewhere or online), or would you pick one of the others?

Or is all this ethical consumerism stuff nonsense for some reason anyway?

Simon Richter: Lazyweb: not hogging the event loop

I'm (again) writing a library that is supposed to be cross-platform, but needs sort of an event loop, which I'd rather leave in the main program and just give them a bunch of file descriptors to watch and a timeout. Problem is, file descriptors are platform dependent. There are a few approaches to this. The mighty ASIO simply annexes the entire loop, and just tells people to hook into it if they need anything -- it works, but on the downside you get threads for free when you didn't want or need them. Simply spawning a new thread for everyone isn't a solution either, as it requires me to do lots of synchronised inter-thread communication -- and on Windows, file handles are thread affine, so I cannot even call into the same library from different threads. I will probably go with ASIO for this project, but I'm fairly certain that there are better solutions out there.

Amaya Rodrigo: Where is Wally?

Can you find Holger in this pic?

Where is Holger?

And BTW, I am going to Fosdem.

FOSDEM, the Free and Open Source Software Developers' European Meeting

Edit: If you don't understand this post's title, find out about Wally

David Welton: Android - commercial meets open source

One of the interesting things about Google's Android project is the mix of cultures. There are a number of people like me, firmly grounded in the open source world, who are happy to get something that 1) works, 2) looks to have legs in terms of popularity, and 3) will be open source. Think of a lot of your favorite open source projects when they first launched. "Polished" isn't a word you would probably use to describe them, although it usually happens in later releases (Ubuntu looks better and better, for example). There are also a lot of people who come from a 'commercial' background, who expect to see everything ready and waiting on a plate for them, which isn't a mistaken expectation if you're used to using products from big companies who are staking their reputations on them. They want nice, thorough docs for everything, almost all bugs worked out, and lots of easy to use tools. Android lies in a middle ground somewhere between these two camps, which I think at times makes people uneasy. It's not open source yet. You can't hack it as much as you may want. You can't rebuild it from the ground up. You don't get access to the communication between the developers working on it, and cannot participate in that development. However, there is a promise to open source it that would reflect very, very poorly on Google were it not met and is therefore pretty credible. The developers and many people involved with it certainly seem to "get" open source, and are taking good steps to create a community around Android (a few even hang out in the #android IRC channel on Freenode) that will most likely not take too long to start assimilating interested outsiders once the code is open. In terms of quality, it wasn't bad when it came out, but it was very definitely an "early look", put out there to solicit feedback and change according to it, something that's part and parcel of a release early, release often open source model. On the other side, Android looks to be a big effort from a big company to get into a big market in a big way - it's not a "under the radar" type of strategy that the open source world is often constrained to follow for lack of monetary and marketing resources to do it any other way. This has attracted a number of developers who either don't see or don't really get some of the "open source" aspects of what we have so far: it's still changing! The docs aren't complete! The emulator is still ugly in places! And from their point of view, it must seem odd to getting something that's obviously not a finished product, without crystal clear direction and goals and a roadmap, and without actual hardware only available in the distant (well, in internet terms! - 8 months or so) future. That kind of thing probably isn't done very often in their world, or where it's done, is certainly kept quieter and perhaps restricted to registered developers. They came over to have a look at something that was ready to go, and it isn't, yet. This has caused some disappointment for people who expected to see something ready to go out of the box. Perhaps Google needed to manage their initial communications slightly better in order to manage the second group's expectations more carefully. In terms of us open source folks, I think that what we want is more access, as soon as Google is willing to hand it out. More source code access, but also access to the development process and people. "Real" open source isn't just about the code, it's about being more or less equal participants in a community. Luckily, I think the people at Google get this, which is one of the reasons I'm enthusiastic about Android, even if I wish we didn't have to wait so long for the source code.

Davide Viti: Font tips #2: comparing fonts

Being able to compare images can be really useful sometimes; I found it extremely helpful when I wanted to know what changed between two releases of the same font. Imagemagick does the trick via a set of really powerful command line tools. Here's a very simple demonstration:
  
pango-view --font="DejaVu Sans Mono" -t "Hello World" -w 180 -q -o a.png
pango-view --font="DejaVu Sans Mono" -t "Hello world" -w 180 -q -o b.png
compare a.png b.png hello_diff.png
which results in the following output: We can now apply the previous tip to something more useful; let's say we want to know how the glyphs in a font changed from a release to another. In a previous post I've explained how to render all the glyphs into a nice PDF using fntsample; we just need to create PDFs for both releases and compare them... ain't that easy?
# Let's suppose you have already created PDF files inside the following dirs
a=dejavu-2.22
b=dejavu-2.23

vsdir="$ a _vs_$ b "
mkdir $vsdir

for f in $(find $a -name '*.pdf') ; do
f=$(basename $f)
apng=$ a /$ f/.pdf/
bpng=$ b /$ f/.pdf/
mkdir $ apng $ bpng

echo "*** $ f ***"

# pdf -> pngs
convert $ a /$ f $ apng /$ f/.pdf/ .png
convert $ b /$ f $ bpng /$ f/.pdf/ .png

# compare pngs and, if different, show whre they differ in a png
for p in $(find $ apng -name '*.png') ; do
p=$(basename $p)
meas=$(compare -metric AE $ apng /$ p $ bpng /$ p $ vsdir /$ p 2>&1)
if [ $ meas -eq 0 ] ; then
rm $ vsdir /$ p $ apng /$ p $ bpng /$ p
else
echo " - $ p "
fi
done
done
This is what you get when a glyph was modified: In case of newly introduced glyphs you get the following:

Martin F. Krafft: Logitech product lines and how they still screw over the customer

After a failed attempt to fix Penny s car speakers taking apart the interior of a Ford is way harder than it should be, and of course we came out of the quest with the obligatory screw which wouldn t fit anywhere I bought a pair of portable speakers. The Logitech PureFi Anywhere convinced in terms of sound quality, and we greatly enjoyed them on our roadtrip. Having bought them in New Zealand, the speakers of course came with a type I power plug, while most of Europe uses a type-C-compatible plug. The design is modular, allowing for the actual plug to be swapped, so I bought it anyway: Modular Logitech power plug with type I adapter Back home, I contacted Logitech and asked them how to get the adapter swapped. Their response? It is not possible to obtain the modular plug separate from the speakers. Logitech uses a modular approach to optimise their product lines and ultimately, their profit, but they don t deem it necessary to leverage the power from this approach to serve their clients. Guess who won t be buying Logitech products again! If you are considering their stuff, please think twice. If anyone knows of a way to get at such an adapter, or has one to trade, or can help otherwise, please get in touch with me. Thanks! NP: The Pineapple Thief: 137

MJ Ray: Local Strategic Partnerships and Strategic Economic Partnerships

Are any worker cooperatives reading this involved in any Local Strategic Partnerships or Strategic Economic Partnerships? If so, please contact me (use the contact form on the page for this post and mark it "not for publication"). I've some questions about it from a Regional Cooperative Council. Any other comments about LSPs and SEPs can be fed back if you want to send them to me. As an example, our local LSP is http://www.northsomersetpartnership.co.uk/

Russell Coker: Athlon Memory Problems

I had an old Compaq Athlon 1GHz system that seemed to be broken. It would display random things on the screen from the BIOS and fail the boot, it looked like a motherboard problem. Fortunately before I gave it away (I give away all my broken machines to members of my local LUG who want spare parts) I remembered that the machine uses main memory for video. I removed and reinstalled one of the DIMMs and it then worked perfectly, presumably it was making a poor contact. The next task was to put it back in service, I had a bunch of spare RAM and I decided to upgrade it to 768M (it previously had 384M). With the new RAM it would fail to boot, sometimes it would give a kernel message “soft lockup detected“, and sometimes it would just hang. The hangs typically occurred when running the initramfs (the first non-kernel code). I tested this with a Fedora install (what the machine used to run when it had 384M), a Debian install (the aim was to use a hard drive with Debian installed for the new purpose of the machine), and with CentOS and Debian installation CDs. The CentOS and Debian installation CDs got a little further but still crashed. Memtest86+ however reported all the RAM as good. I then tried reducing the RAM to 256M which worked perfectly. It seemed that increasing RAM above 384M would cause the problem. The next thing I tried was the mem= kernel option. As a first experiment I tried mem=400m which worked perfectly. I then tried mem=759m which allowed the boot process to proceed a little further but it still crashed. The system supposedly has 760M available (8M used for video). Further testing revealed that mem=750m seemed to work well. Being cautious (and not short of RAM) I have configured the machine to use mem=740m, and it is now working well.

Wouter Verhelst: my FOSDEM TODO list

I'm going to FOSDEM In less than two days, and I still have loads to do Most of this has to be done this evening. And all this while feeling horrible; I think I'm sick again. If I didn't have to give this perl training, I'd have stayed at home today. Here's for hoping I'll feel better during the weekend. And that I'll get everything done by tonight.

John Goerzen: Death sure is cost-effective, isn't it?

I just read Death Be Not Proud (But It Is Cost-Effective) by Chez Pazienza. In his story, Chez talks about his stay in the hospital to have a marble-sized brain tumor removed. Across the room during his stay in neuro ICU, he saw a person far worse off than himself: staples all around his head, barely able to stay conscious, unable to speak. After a few days of this, Chez asked the nurse what had happened to the other person.

It was the same thing.

The difference? Chez had good insurance, and the other person didn't. So Chez got the modern surgery with the latest technology, and the other guy got the Neolithic version. The other patient's family came to visit, clearly heartbroken at his condition, not knowing whether he'd ever be the same. And knowing that even if he'd survive, he'd have years of physical therapy ahead of him.

Then there was the story of the girl whose insurance company denied a liver transplant, calling it "experimental", sending her to her death. He says:

Regardless of what Fox business-creature Neil Cavuto may have to say on the subject, healthcare and profit are two thoroughly antithetical concepts. Giving CEOs the authority to stand on the edge of the arena and issue a final thumbs-up or down while we lay incapacitated or dying is like charging a lion with protecting the Christians.


I entirely agree.

20 February 2008

Ben Hutchings: My day job

I'm employed at Solarflare Communications in the test group, supporting the work of testers and developers by developing test frameworks. (We actually have very few pure testers and a whole lot of automation.). In a major break from my previous jobs, I've been working mostly in Python on applications for use in-house. More recently I've become involved in maintenance of our network driver for Linux, starting with updating it to use current kernel coding conventions, and submitting for inclusion in the kernel. This has become a bit frustrating because while there are a lot of people prepared to run checkpatch and pick nits, there are not so many who will do a thorough review of a driver that's 20,000-odd lines long. And without someone doing that, it won't go in. Meanwhile some of my colleagues have done some great work to accelerate Linux networking on Xen by having drivers in dom0 and domU cooperate to expose hardware resources directly to domU. Our hardware architecture supports many virtual NICs with their own packet queues and set of buffers, so this does not compromise the security of the physical machine and dom0. The results are very impressive. The original motivation for the virtual NIC architecture was as a basis for a user-level networking stack, which can provide very low latency and reduced CPU usage. This software was originally proprietary but has now been released under GPLv2 as OpenOnload. Google invited two of my senior colleagues to talk about this - here's a video of their talk about user-level networking.

Next.

Previous.