Search Results: "ag"

31 August 2007

Erinn Clark: My new furniture

Pink. Victorian. Vulvacious.

I have the most emasculating living room ever.

John Goerzen: The Story of One Barn

img_2575

About 80 years ago, a Kansas family -- the Janzens -- built this barn.

About 60 years ago, my grandparents moved onto the farm. Their cattle were kept right here. I remember Grandpa's red tractor being parked in the barn.

So many memories have this barn in the background. We had a visit from one of the Janzens that lived here as a child. He had fond memories of this building. My dad and his siblings once played in the deep snow in front of this barn.

Here's one memory from those times:

078.jpg

That's my grandma and grandpa on their 25th anniversary in 1970. It was a working barn back then, so they probably weren't standing right next to it for this picture, if you get my drift. But they were on the yard.

About 25 years ago, Grandma lost her battle with cancer. At some point or another, Grandpa had eased out of farming, so the barn had a lot less activity. I remember exploring his outbuildings when I got bored at family gatherings. And I used to mow the lawn next to it every summer when Grandpa went off to be a cook at a camp. I didn't mind mowing next to the barn. But I always tried to go past one corner of the house as fast as I could, because there were wasp and hornet nests right there.

About 7 years ago, it was time for Grandpa to move off the farm. It was getting to be too much to keep up the old house, the barn, the yard, and deal with things like freezing water pipes and water getting in through the windows. He moved to an independent-living duplex in town. He was always worried about what would happen to the farm. Over the next few years, the farm would sometimes be vacant, sometimes have renters. Some renters did some work on the house, but the barn sat. Grandpa would eventually move into the nursing home because of his Parkinson's.

Two and a half years ago, Grandpa passed away. I shared some memories from Grandpa's place at the funeral.

But what of the house, the farm now? Renters went, and it sat empty. Nothing was in great shape, and the house needed a lot of work. Perhaps the whole place would be leveled and turned back into the prairie that it once was, or used as farmland. Perhaps someone would have an interest someday.

A year and a half ago, Jacob was on the way. Terah and I had occasionally thought of buying Grandpa's place, but we never talked about it seriously. We figured that we better finally decide what we're doing, before we have a baby around, or a child in school. So in April 2006, we went out to the farm and checked it out. The picture at the top of this post is from that visit. Terah and I checked out the house, the barns, the granary, the pasture, and the creek. As we walked past one of the barns, a pigeon flew out. Terah jumped with a shout. I grew up around barns and didn't really notice it. In the big red barn, besides Grandpa's tractor, we found some remnants from years ago: some old bales, corn cobs that raccoons had found long ago, several generations of electric fencers, old appliances.

And we decided to go for it and buy the farm. This was right at a year after Grandpa died.

The family always liked to get together for Easter. What would happen for 2006? Well, they decided to have a picnic out at the farm. It was vacant, and a bit eerie. Yet they knew that we were working on buying the place and moving in. All but one took a last look through the house before our renovations began. The one person who didn't was my great aunt, Grandma's sister. She said, "I haven't been in this house for years. I remember how it looked back then. I don't want to remember how it looks now, run down like this. So I'm not going in. But once you have it all fixed up, THEN I'll go in!"

In June of 2006, we bought the farm.

One month later, we lost this barn, and two other buildings, to a fire at our yard. This is what the beautiful red barn looked like that sad afternoon last year:

IMG_3630.JPG

As I wrote back then, nobody got hurt, the barn was insured, but "somehow, despite all these things, it still feels like we lost a little bit of Grandpa today."

2006 was a hot, dry summer. We had a patch of debris, then a patch of dirt, where the barn once stood.

7 months ago, Terah, Jacob, and I moved out to the farm. For the first time in 80 years, someone could stand in the farmhouse in the evening, look to the west, and see the colorful Kansas sunset over the pasture; the trees down by the creek; and even the neighbor's barn off in the distance. It was a beautiful sight, but it was also sad; that's not the view we had expected.

But then a surprise. This spring and summer, plants started coming up where none had grown for 80 years. But only where this barn stood -- not where the other two buildings were.

We watched as they grew tall. I'm sure decades of animals hanging out there were well appreciated by the plants.

As they grew, it looked like we might be seeing Terah's favorite flower: wild Kansas sunflowers.

And sure enough, they were.

Last weekend, Terah, Jacob, and I went out to the old barn. I took some pictures of its new appearance.

img_3429.jpg

This one stands where Grandpa's tractor used to be parked.

img_3401.jpg

And here we see a lifetime of flowers, from the old and withering, to the young just about ready to bloom.

img_3462.jpg

At the edge of the sunflowers, there's an old plow next to them. Though you might think it's barn-colored.

img_3411.jpg

Animals continue to be attracted to the area. Here's one of the smaller visitors.

img_3447.jpg

And here's a picture of almost the whole patch, right where the barn used to stand. I still mow right up to it.

I still miss the old barn. But somehow it still seems to be full of surprises and worth exploring. I wonder what next year will bring.

And I wonder if, a few years from now, Jacob will tell his friends about mowing right up to the sunflower patch, going fast to try to avoid any trouble with the bees.

30 August 2007

Steve Kemp: I gotta be cool relax, get hip

Fighting Spam Lots of people get spam and don't want to fight it themselves. Many of those people elect to use a service such as Google Mail, which does an adequate job of filtering most of the time. For people who wish to host their own mailservers, and off-load their anti-spam support to another entity, there are big companies such as MessageLabs. But if you can't/won't pay for somebody else how would you handle it? Right now I run my own mailserver and mostly it rocks. However I also manage a couple of servers for other people, and this mostly means that I have identical configuration(s) scattered across other machines. (Or as I recently discovered "mostly identical" setups scattered across N hosts.) After viewing a recent thread upon the forums of my employers I'm wondering how hard it would be to setup an anti-spam mail host. The idea being that users of domain example.org would continue to run their own mailserver (+optional POP/IMAP server). However this server wouldn't be listed in an MX record. Instead the MX record would point at the antispam server, which would then process and forward the mail on. (I'm assuming that the mailserver at example.org would be firewalled such that it would only accept SMTP connections from the anti-spam host). The only challenges I see would be: The last one is the killer point which makes me wonder if I'm wasting my time on the general case; I don't believe I could persuade people to pay for such a service (on the grounds that I wouldn't!) and if ever a mail were dropped I'd be the first person who would be blamed. And probably rightly so. The simple solution would be to always accept mail - but just tag it. Then you still have the same issue, but you have the excuse that "I still delivered your mail; just tagged wrongly". The downside of that is that the recipient still has to filter the mail; and still eats the bandwidth cost. The main gain is the lack of spam-processing CPU that is eaten locally. Anti-spam, and to a lesser extent anti-virus, topics are very interesting to me, and I'd love to hear any thoughts - or even what you use for yourself. Right now I'm 50/50 on setting up my main mailserver as the proxy for a few domains I have to manage (family, friends) to see how it works, but I'm not quite convinced yet. (Single point of failure == bad. Though centralised configuration == good.)

Junichi Uekawa: Added content:encoded to my RSS feed.

Added content:encoded to my RSS feed. I've received a request to show links to my RSS feed. Apparently, RSS is no longer what it originally was. People expect full font specifications, images, and links to be functional. I've added encoded content as a CDATA. It should hopefully work.

Daniel Burrows: Seattle LUG meeting

The Seattle Linux user's group has been defunct for the last two years or so, but an effort is underway to renergize it. This Saturday, the group will be meeting for the first time in years. The meeting will take place at the North Seattle Community College beginning at high noon -- check the official Web page for more details. TBH, the presentations don't look that interesting to me, but it's always fascinating to meet people who actually use Linux...

Yes, I'll be there, but I'm not giving any of the presentations, so please don't let that keep you away. ;-)

Romain Francoise: Random fact of the day

Over the last five months I have orphaned or given away a total of 12 packages. It feels good.

Chris Lamb: Strawman

We have a somewhat esoteric heating arrangement at my parent’s house. We burn bales of bean straw inside a large combustion chamber (similar to these) which is located in an out-house to the main building. A number of water-filled pipes run through the chamber which is then pumped around the house. Environmentally, it’s really good. Most of the straw would have been burnt anyway (the rest cut into the soil) and the combustion is fan-assisted to minimise incomplete combustion. Very little ash is produced from burning such a bale. Anyway, the delivery and storage of approximately 700 straw bales has become a yearly tradition in our house. As a guide, the trailer in the picture below is holding 160. It’s pretty tough going: even individually these things weigh a considerable amount, and they require removing from the trailer and then stacking in a 3 metre pile inside another shed! You quickly adopt the rules of moving a bale as little as possible vertically (carry them on your back if you’re young enough!), and never, ever, moving a bale twice. There’s also a large amount of dust, and a geek’s delicate palms quickly tire of the string holding the bales together. Anyway, this happened today on a couple of hours notice. The other two males in the house decided to be elsewhere *cough*, leaving it up to me and my poor mum. If anyone was expecting email/code/chat/info today.. sorry.

Patrick Winnertz: Back from Austria

Hey, I'm back from Austria today. We had there 5 very nice days in the mountains (should be 8, but cause of some troubles we cancel our trip after the fifth day. But until this we saw very much and took very many nice pictures. For all who wants to see a bit of our trip through the " tztaler Alpen", here are the pictures. :)

Miriam Ruiz: Finally Gnash 0.8.1

The 4th and hopefully last alpha version (I expect the next one to be a beta) of Gnash, the GNU’s free Flash player has been released yesterday. There are many important changes, but the most relevant thing you’ll notice is that it’s by far more stable than the previous one. Gnash supports right now the majority of Flash opcodes up to SWF version 7, and a wide sampling of ActionScript 2 classes for SWF version 8.5. The program is still under heavy development and Flash version 9 and ActionScript 3 support are also being worked on. Debian SID has right now one of the latest release candidates for this version, and 0.8.1 will probably be in the repositories soon. As it is expected that in one or two versions it will be able to select between the different possible backends, we’ve decided to have just one package with pre-selected options in the repositories. AGG is probably the most conservative version that will work for everyone, and even though OpenGL might be better for certain graphic cards, we’ve decided to play safe. In any case, I’ve also made some unofficial packages for those who want to try different configurations of Gnash, like, as I said, using an OpenGL backend.

Michael Janssen: In my own head consume, I sit down in my room

Lately I have been tasked with a lot of writing to do. I'm writing a chapter for a book on the field that my research is in, which is a good thing for me to get done, but I started it quite late. I had to finish a 9,000-12,000 word chapter in 2 weeks. Here's how I set it up:
  1. For the first week, write 2,000 words each day.
  2. For the second week, edit the words already written.
The first half of the schedule was easier than I thought it would be. In general, writing in my field doesn't usually happen that fast, but the subject is something I'm pretty versed in, so it was not too hard to get 2,000 words out. I had a clear defined goal for each day that once I met, I could feel okay about not working on the project for the rest of the day. I also only had to write 6 days, and I was able to take the seventh day off. Both of these combined made it a lot easier to not feel guilty about being behind. Editing is a bit more abstract and ongoing than the writing part, so it's hard to tell how well it's really going. There are some easy parts like fixing grammar and proofreading to make sure you don't repeat yourself, but there are also a good portion of hard parts as well, like which sections to cut a bunch of words in, and which word choice should be made in a particular spot. I'm at the point where some things NEED to be cut because the document is too long, so I have to make some hard choices. I also met with my advisor last week and we discussed my progress toward finishing my Ph. D. I had been thinking about this problem for a while now and was glad that it was also on his mind as well. We agreed that I would set the goal for having my orals done by the end of this year (christmas). I am thinking I will use a similar tactic to the chapter that I am writing, but on a much slower schedule, so next week I will start writing 500 words a day, and do that for a couple months. This will leave me with 30,000 words that I will then edit down by quite a bit, reducing it by almost half. Hopefully this will make the process easier as it has for the chapter. If writing my thesis proposal works well this way, I hope I can use a chunk of it for the final thesis, which I want to finish one year after my orals, putting me on track for graduating at the end of 2009. I'm looking forward to that.

John Goerzen: Technology

Two days ago, I was out by the road digging a hole for our mailbox.

Along comes a guy on a tractor. The tractor was built in maybe the 1960s. It had no cab, and was loud, as tractors are. Attached to the back was a mower. It had long since lost any part of paint that was on it, and appeared to be made of rust.

The farmer driving this tractor was wearing a bluetooth earpiece for his cellphone.

(I don't think there would be any way to use a phone while driving that tractor due to the noise, but hey.)

Now, the rest of the story...

This being rural Kansas, the farmer saw me and stopped to chat, turning off the tractor first, of course. He introduced himself as "that crazy guy from south of town", and of course had a pretty good idea of who I was. After all, he's lived around here for decades and knew my grandpa.

I told him why I was digging the hole for the mailbox. There's going to be a second house down our mile, so now the post office will actually deliver to a mailbox at our driveway, rather than one almost a mile away. I thought he looked confused, so I pointed down the road and said that's our mailbox on the corner.

"Oh, I know. I probably shouldn't say this, but I knew when you moved in because I checked your mailbox one day and it didn't have 40-year-old ads piling up anymore."

We chatted a few more minutes, about the neighbor's goats, how annoying it is that he can't get DSL, why he wishes he could still use DOS instead of Windows. Then he went off towards home.

He had stopped his tractor in the middle of the road. But it wasn't a problem. Nobody drove by that whole time anyway.

Russell Coker: Identifying the Distribution of a Linux System

I just needed to test something so I mounted the filesystem of one of my Xen domains in the Dom0 and chroot’d into it (I didn’t need the overhead of running a DomU for a quick test). Then strangely I found that my chroot environment had no apt-get and no dpkg installed. After a small amount of thought I realised that I had accidentally mounted the filesystem for a Fedora image instead of a Debian image. It seems to me that it might be a good idea for distributions to have shell scripts replacing the package tools for other distributions. For example dpkg on a Fedora box could be a shell script that runs echo “This system is running Fedora, you want to use rpm instead of dpkg”. Such a command would have saved me a couple of minutes of thinking. This may sound trivial, but if you consider the number of people who make such mistakes (and the even larger number of people who don’t realise that there is even more than one package tool in existence) then wasting a few K of disk space on every system to help them seems like a good idea. The minimum size of new hard drives that you can purchase seems to be 36G nowadays. So it’s not as if this would really cost anything. Please leave comments to tell me if I’m being sensible or silly. If the idea is regarded as good I’ll start filing bug reports.

Joachim Breitner: Haskell Syntax Gem

Often when creating text from a program, you encounter this situation: You have a value, e.g. first_name, that might be empty (depending on your programming language, this means undefined, NILL, None, nil or Nothing) or contain a string. In the latter case, you want to surround it by some markup, in the former you want to do nothing. Here is how I d code that in Template::Toolkit:
<table>
[% IF second_name %] <tr><th>Second name</th><td><b>[% second_name %] </b></td></tr> [% END %]
[% IF first_name %] <tr><th>First name</th><td>[% first_name %]</td></tr> [% END %]
</table>
And here in python:
output = "<table>"
if second_name:
output += "<tr><th>Second name</th><td><b>%s</b></td></tr>" % second_name
if first_name:
output += "<tr><th>First name</th><td>%s</td></tr>" % first_name
output += "</table>"
I really don t like entering each variable name twice, when I basically want to do one thing with it.Here is how you can use Haskell s flexible syntax to help you out. First we define a unconditional insert here operator ++!++ and then a conditional one, named ++?++:
(++!++) :: String -> String -> String -> String
pre ++!++ post = \ins -> pre ++ ins ++ post
-- Or more haskell-style:
-- pre ++!++ post = (pre ++).(++ post)

(++?++) :: String -> String -> Maybe String -> String
pre ++?++ post = \ins -> maybe "" (pre ++!++ post) ins
-- Or more haskell-style:
-- pre ++?++ post = maybe "" (pre ++!++ post)
Note that the first line of each function, the type declaration, could be left out as Haskell can figure it out by itself. Also note that these function are not restricted to strings (as lists of characters), but can be used for any kind of list.Now I can write the code up there as:
output = "<table>" ++
         ("<tr><th>Second name</th><td><b>" ++?++ "</b></td></tr>")  second_name ++
         ("<tr><th>First name</th><td>" ++?++ "</td></tr>") first_name ++
         "</table>"
I think that s a nice display of the flexibility of Haskell s syntax, in this case, using symbols for function names and infix application.

Nacho Barrientos Arias: Example: How to statically and dynamically link your executables

People usually uses Google, among other things, to look for hints about how to do small tasks. Hopefully, you will find the hint you were looking for in somebody’s blog, because he or she had the same problem time ago and decided to talk about it. Last night, I was a bit bored and started writing a dumb set of files to introduce people how static and dynamic linking work, so trying to put my two cents and add a new hint to the wild wild web, I’m sharing it. The C source files are practically useless, therefore pay attention to the Makefile, the magic is in there. If you’re downloading it only to compile, execute and see what happens forget about it, the program is completely silly. Otherwise, probably the Makefile is buggy somewhere so bug reports are welcome. For teaching purposes, try, for example, breaking the ABI and see what happens. Google, index this post please! Update: This example does not cover autotools/libtool

Pablo S. Torralba: Shell date and time tricks

One of the things I hate the most when programming is dealing with time and date functions and all the special cases which exists. Even more, I have the feeling I'm walking a path many times walked before, so it becomes one of the most unpleasant tasks for me.

Fortunately, it's true, so many others walked before that path so here are some quick tricks for shell programming using the wonderful date UN*X program:
  1. Converting epoch:
    1. From epoch to anything else: date -d @$epoch_value +FORMAT (where FORMAT is of course as described on date(1), and '@' makes the actual undocummented trick).
    2. From anything else to epoch: date +%s
  2. Calculating times
    1. One day forward: date -d "1 day"
    2. One day backwards: date -d "1 day ago"
    3. Just imagine "1 month", "3 months ago" and the like. Not only google is so friendly with human language ;-)
  3. More format conversion: '-d' option accepts several other formats as input, even with calculations:
    1. date -d "1977-08-19 30 years", yeah! my 30th birthday was on sunday. Thanks date, and it was (as epoch): date -d "1977-08-19 30 years" +%s... 1187474400 :-D
    2. Funny ls:

      ls -l while read perms links user group size d t name
      do
      echo $perms $links $user $group $size $( date -d "$d $t 1 day" ) $name
      done
      You can, of course, change the way date is shown. That's because 'YYYY-MM-DD hh:mm' is also a valid input format for date as it is 'YYYY/MM/DD'.
So '@', '1 day' and 'date' saved me the day.

Update: This features and more are indeed described in the coreutils info manual. Thanks mp for pointing it out.

Matthew Palmer: "Printer Friendly"

Obviously some people have a much, much better printer than me, because the "Printer Friendly" link I just clicked on took me to a page with a flash ad at the top of it.

Theodore Ts'o: On the benevolent dictator model

Recently, Josh Berkus blogged about The Myth of the Benevolent Dictator. In it he complained about people who try to posit that a benevolent dictator was "an unalloyed asset" to their project, and that there were many successful and valid forms project governance other than the singleton project leader. Furthermore, he argues that the best way is to form a community, and then ends by suggesting that people who say "dictatorship good" is really saying "democracy bad", and perhaps the motives of the person using that argument should be questioned.

Given that I was one of the first people (and probably the first person) to use that phrase to describe Linus's governance model, obviously I feet the need to respond to his thoughts on the matter.

First of all, the term "benevolent dictator" comes from an old saying, "the best form of government is the benevolent dictator --- there's only one problem, finding the benevolent dictator"[1]. And in my presentations where I explained the Linux project management model, I was always careful to say that there were other models that were used by other projects, and that it was interesting to study why certain management models worked for some projects but not others.

So by definition, if a project is successful with a single project leader ultimately responsible for making decisions to settle conflicts, then that leader is a "benevolent dictator"; if they aren't successful, then that would be an example of a dictator who wasn't able to be "benevolent", eh? :-)

In all seriousness, though, I agree with Josh when he says that the key part of an open source project being successful is gathering together a healthy community. But let's unpack that a little. In order for a community to be healthy, there needs to be general consensus on the values and cultural norms for that community. So for example, in the case of Debian, which Josh holds up as a successful community, not everyone has the ability to vote; you have to pass a fairly stringent process which tests your technical skills and your willingness to subscribe to Debian's core values as embedded to the Debian Social Contract. People who do not pass the New Membership process do not have the right to vote in Debian, even if they are the most rabid, fanatical users of Debian.

This brings up a key point about governance analogies; they all don't map cleanly into the real world for two closely related and extremely important reasons: (1) No one has a fundamental human right to be a member in some OSS project, and (2) No one is forced to stay in a particular OSS project. These are really two sides of the same coin, and what it means is that, as in Debian, "democracy" does not mean that everyone is entitled to political franchise, or the right to vote, and in a project which has a "benevolent dictator", the powers of the dictator is fundamentally limited by the simple fact that if he is too unreasonable, people are always free to leave or fork the project. These differences are extremely important when trying to reason about "democracy" or "dictatorship" as being good or bad as applied to open source projects.

Democracy is rarely the best way for an open source project to make decisions. For technical issues, you want the right answer, and majority vote isn't necessarily way to resolve a technical issue. As far as policy decisions, if the decision can not be made by consensus, then some percentage of the community will be unhappy with how the decision, and that can cause a huge amount of arguments and dissension. If the community has very clearly expressed values, then the number of times where such votes need to be made will be minimal.

For example, Debian has an explicit declaration of its values and mission in its Debian Social Contract; people who don't agree to the Social Contract aren't allowed to become Debian Developers and thus are not allowed to vote. But, one of the more controversial disputes that have threatened to tear apart Debian is the question of the non-free packages, and that's fundamentally because of an ambiguity in the Social Contract. On the one hand, Debian has declared that it is fundamentally 100% about Free Software, to the extent that it has adopted Richard Stallman's rather petulant request that the Linux operating system be called GNU/Linux (which admittedly is better than Lignux.) On the other hand, the Social Contract also explicitly specifies the existent of the non-free section in the distribution. Over time, this ambiguity have been the source of a lot of highly passionate debate and controversial votes that have satisfied neither the FSF fanatics nor the more Linux-like moderate position tolerating the use of proprietary as well as open source software. I submit that if Debian had either explicitly stated an FSF-centric position, and only accepted members that supported point of view, or explicitly subscribed to a position that users should be able to use whatever software they feel meets their needs, as Ubuntu has, it would avoided many arguments that have threatened to tear apart Debian.

More recently the fact that the Social Contract has been silent about whether or not Debian Developers should be paid or purely be 100% volunteer. This was never an issue in the Linux Kernel community, but for some reason it has been a highly divisive and disruptive issue inside Debian. Democratic votes have not really resolved the conflicts, and in fact some might claim that these votes have if anything hardened various Debian Developers' positions.

Going back to Josh's final point, "Next time you hear the words 'benevolent dictator' you probably want to think about the motives of the person saying it. Because the corollary to 'dictator good' is 'democracy bad', and is that a place you really want to go?", I am quite proud to stand by my convictions that for Open Source Projects, pure democracy is a bad idea. If a projects wants to be technically successful, it needs to be a meritocracy, and chose the best technical decisions; Linus does not decide by abiding with majority vote whether or not a patch should be accepted, and that's as it should be.

Even Debian's "raw democracy" doesn't let any random luser get to vote on who should be the Debian Project Leader. Decisions need to be made by people who are competent to make a valid choice. Even in real life, one could argue that the choice made by Americans, over of which 70% believed that Saddam Hussein was "very likely" or "somewhat likely" to be personally involved with the 9/11 attacks even though there has been absolutely no evidence to support this "gut feeling", made a rather disastrous choice in voting to re-elect George Bush to the presidency. Democracy without sufficient education, literacy, and intellectual curiosity to learn about what is happening in the world can result in truly disastrous choices being made. So certainly, democracy is not a panacea. In the real world, it may be the best choice of many bad choices, given how much people have suffered under military dictatorships. However, in the Open Source world, things are different because people are always free to leave one project and affiliate with another --- not an alternative most people living in dictatorships have historically had. Given these key differences, I think it is clear that for open source projects, democracy is indeed often a bad idea, and that if you if a project has a single person with a strong technical vision and good interpersonal skills, the benevolent dictator model can indeed be a very viable and successful.

Does that mean that other forms of governance can't work? Of course not! The rotating dictatorship used by Perl[2], the core-team-with-strongarm leader used by OpenBSD, the corporate dominated scheme of MySQL, the self-selecting core team model of Samba, all are successful models. I just have to strongly disagree with Josh's claim the single strong leader approach is somehow inferior to "democracy" as if democracy was somehow a magic bullet.


[1] For am early example of this quote, nine years ago, please see this message, where I'm pretty sure I authored the colon prefixed quote, and I know I was using the term "benevolent dictator" much earlier than 1998.

[2] In the early days of Perl, it also used the benevolent dictator model. Larry Wall is a great exemplar of how someone who has a strong vision of what he wanted to accomplish, and was humble and easy to work with, both on-line and in person, can make all the difference in the world for an up-and-coming open source project.

29 August 2007

Russell Coker: The Silly BMW 745h

BMW has released a new prototype hydrogen powered car. The bmwworld.com web page about it claims the cruising range is 190 miles. Added to the 400-mile range of the normal fuel tank, the 745h can go 600 miles between fill-ups. The first issue is that 10 miles are not accounted for (maybe it finishes the 190 miles of hydrogen power at the top of a hill). But more seriously the hydrogen needed to drive for 190 miles would take as much space as petrol needed to drive for 646 miles (hydrogen needs 3.4* the volume to store an equivalent amount of energy). I wonder if that BMW has any space left in the boot/trunk? Now we have some green bloggers praising BMW. An internal combustion engine that burns hydrogen will not give no emissions other than water vapour, it will produce some nitrogen oxides. The processes to produce hydrogen for fuel all consume unreasonable amounts of energy (more than is required to charge a plug-in hybrid). BMW demonstrates their level of interest by giving the cars to some celebrities. This gets some PR but no analysis of the performance. They also introduce the prototype based on one of the most expensive models (the 745) which you almost never see on the roads. If they produced a 318 or 520 that ran on hydrogen it would demonstrate some level of interest in getting this working for the mass market. If BMW wanted to make their cars more environmentally friendly they would start by adopting some of the technology from the Prius. Rumour has it that part of Toyota’s plan to make money from Prius development is in licensing the technology that they patent. A couple of years ago I test drove a BMW 316 and a Prius. The Prius was very quiet and gave a smooth ride (you might call these luxury features), and also gave decent performance (it’s widely regarded that luxury cars should perform well - pity the BMW 316 is a slug). In Australia the concept of “badge engineering” of cars is well established. When government subsidies favoured large manufacturing runs the Ford Laser and Mazda 323 were essentially the same car. Maybe BMW could adopt this concept and sell a re-badged Prius i-tech with a few extra luxury features as a BMW 4 series (it’s a much better car than the 3 series BMW). Finally bmwworld.com has an amusing FAQ about hydrogen power, here are some of the mistakes that they make:
  1. They say “About 45 billion kilograms (50 million tons) [of hydrogen] is produced every year enough hydrogen to fuel 250 million fuel cell cars“, but only if the average fuel-cell car uses 180Kg of fuel per year. According to Wikipedia hydrogen has slightly more than 3* the energy density per mass than petrol, so 180Kg of fuel would be equivalent to 540L of petrol per year. The Australian Bureau of Statistics states that in 1996 the average annual distance travelled by car (it’s not clear whether this is per car or per person) was 14,600Km while among the countries listed the lowest was Japan with 10,130. When efficiently using hydrogen in a Prius (that is quoted as using 5.4L of petrol per 100Km) you might expect that 540/5.4*100=10,000Km could be travelled on the 180Kg of hydrogen. So the FAQ claim that 250M cars could be powered by the current hydrogen production would only apply if the cars are of Prius efficiency and driven the typical distances of Japanese drivers, or the cars were 46% more efficient than the Prius and driven in the Australian manner. Of course in the US things are even worse with 17,862Km being the average distance driven which means that their hypothetical fuel-cell car would need to be 78% more efficient than a Prius.

  2. They state that “the majority of merchant hydrogen is produced by a process called steam methane reforming“. Why not just run cars on methane then? Anything that burns can be used to fuel cars, and methane has a much higher boiling point than hydrogen so it would be easier to store and transport (see the Wikipedia page on methane).

  3. In regard to hydrogen production they say “about 95% of the total global hydrogen production is captive meaning it is used at the site where it is produced“, that is of course because it’s difficult and expensive to transport hydrogen.

  4. The final amusing fact is that it is noted that most hydrogen comes from fossil-fuels. What problem are they trying to solve here? Hydrogen isn’t going to help the environment if it comes from fossil fuels, it will be more expensive than other fuels. Apart from getting government grant money for BMW it doesn’t seem to do any good.

Gunnar Wolf: Gl cklich in sterreich!

Good comrades, great chat, greater motivation.
Some good Scotch whisky, a good friend who was lumped along with me in .br by mere chance. A very good time.
A strong whisky aftertaste and numbness in the mouth. My first couple of pages of Terry Pratchet - Thanks a bunch!
My mind wanders, I go over all the nice and dear things and people
Maybe tomorrow I should restart my reading? I know Pratchett is not supposed to make much (rational) sense, but still... Although I've enjoyed this couple of pages, I'd rather let the whisky wear out before continuing with the gollem owner's life and tribulations, with his friendly treatment for his plausible but honorable assassin...
Today I saw quantum superpositions mixed with special relativity in a small (less than 200 lines) Perl module. Positronic variables go back in time, yay! Damian Conway rules.
Time to sleep, yes, if tomorrow you want to be in time for the lightning talks. Oh, BTW: great honor, great honor: One of the lightning talkers requested /me to sit on the front row "to have a friendly face to look at". Have to comply, have to do.
But... Last reflection before going away: What a better way to describe bliss in Vienna (oder auf Deutstch, ich glaube - gl cklich in sterreich;) than to go to sleep while listening to the neighbour's fucking-loud music? Of course, his fucking-loud-music is just the-Balkan-music-you-seem-to-love, so everything's berfine!
Thanks to everybody who made this possible. Specially to the Austrian friends.

Pierre Habouzit: postfix and SRS

Peter, it's fun you ask right now, because I happen to just be writing a SRS daemon for postfix, to be used as a tcp_table(5) canonical lookup table. It's part of my soon to be pfixtools (Postfix Tools), that you can grab on my git repositories. I should package them as soon as the srs daemon is ready (and it's almost ready, it just needs the pidfile and fork-in-the-baground thingies). And as a matter of a fact, yes, if you're a forwarder you have (because of things like SPF, but not only) to use a Sender Rewriting thing, and SRS is somehow elegant in the sense that if many people use it in the forwarding chain, the sending address won't bloat. But even if nobody else uses it, then well, it works, and serves its purpose really well. As of performance: on my laptop, it's able to deal with 100k SRS rewrites in less than 0.72seconds, so it's as fast as it can be, only postfix supporting SRS natively can beat that I'd say.

Next.

Previous.