Search Results: "ana"

15 March 2006

MJ Ray: FDL: What, no explanation?

So, the position statement claims FDL-without-unmodifiables works can go into main. Sadly, the approved text says nothing about the anti-DRM or the source code problems. As I posted: "It just pulls a conclusion out of the project's backside without rationale. This leaves a huge gaping hole in the understanding of the FDL. Dumb." Others are trying to retcon past analyses to try to make the FDL PS make sense. I'd prefer to leave the ambiguity because that's what the project voted for, but the question is: can anyone explain how the no-security and format restrictions (like section 2 "technical measures" and section 3 "include a machine-readable Transparent copy along with each Opaque copy, or [a URL valid for a year]") follow the guidelines and are practically possible with the current archive? [debian-legal subthread on DRM]

Clint Adams: Finally I can purge the horseshit that is eyeD3

ZOMG 0.1.6 will now prefer Mutagen to eyeD3 if it is installed.

14 March 2006

David Pashley: Notice Periods in UK

<p><a href="http://xana.scru.org/bamamba/employmentlawrumors.html">Clint</a>, I don't know about Belgium, but in the UK, the norm is a month for most people and 3 months for senior members of staff. Of course, you may or may not be given work to do during that period. Usually your employers will want you to document and help hand over to a new person. However if you have a bad relationship with your employers, they may put you on <a href="http://www.michaelpage.co.uk/controller?event=VIEW_SUBSECTION&amp;sectionname=right_employee&amp;sectionid=3&amp;subsectionid=11014">garden leave</a> where you arent in the office, but are being paid. Presumably this is to stop you stealing their data or doing some other malicious act. All this stuff is normally written into your employment contract. Without one it is possible to leave your employer <a href="http://www.davidpashley.com/cgi/pyblosxom.cgi/life/new-job.html">within a week.</a></p>

Clint Adams: Everything should be learned from hearsay

Wouter, I don't know what's not ideal about this. I was led to believe that one was required to give 2-3 months notice in either direction, regardless of cause. Here, actually serving one's two weeks is considered slightly beyond responsible and polite. What are the standards in Belgium?

Jeff Bailey: Step class en Fran ais and Soya Nova tofu.

Went to a step class at the new gym last night. As usual, I was the only boy in the class. The teacher refered to me as "young man" a couple times, since it was the easiest way to do so. =) I enjoy taking step classes and am surprised to not find other guys in there. It seems to me that if the women I see at the gym manage to look really good and have decent strength and endurance by doing hour-long cardio and pilates/yoga classes, that they are probably better to follow than the weight room full of generally out of shape guys who look like they're risking a hernia when they exercise.<br /><br />The interesting part was that the class was in French. While my French is quite good, it seems that my parsing is a bit slower than the teacher's ability to hand it out. It took me several times hearing pas de base , before I realised the teacher wasn't telling me *not* to do something, but was in fact asking us to do the basic step. Other things which I understood quickly enough simply made no sense like carr e .<br /><br />Afterwards I came home and had a snack of some Soya Nova Westcoast Smoked Tofu. It tastes quite good, and I've had several people who still eat cheese tell me that it tastes much like Gouda. When I was in Vancouver recently, I picked up several blocks of it. I phoned them today and spoke to the owner. It seems that the Metro stores here might carry it. If not, they're expecting them to in several months as part of a deal with Sunrise Tofu.<br /><br />I remember when we first moved to Toronto, that few of the stores carried the vegan treats that <span class='ljuser' style='white-space: nowrap;'><a href='http://auzure-skies.livejournal.com/profile'><img src='http://stat.livejournal.com/img/userinfo.gif' alt='[info]' width='17' height='17' style='vertical-align: bottom; border: 0;' /></a><a href='http://auzure-skies.livejournal.com/'><b>auzure_skies</b></a></span> and I are used to eating. Places slowly acquired them until there was a whole range of products that we were eating in Toronto that we hadn't seen when we were living in Vancouver. Despite the fact that there's a few large chains of health food stores here, we're still having trouble finding a number of them. Some companies like Toffuti Canada refuse to return phone calls. Many others, like Tofurki, don't get information on which chains carry their products, or beleive that their products are being sold in stores like Provigo even though they're not.<br /><br />Perhaps one of these days I'll have spare hours in the day to contribute to the Association V g tarien de Montr al / Montreal Vegetarian Assocation.

Edd Dumbill: New XTech web site, and why we don't sell presentation space

My too-long absence from writing much here can be ascribed to two, differently pleasant, activities. First, a fantastic vacation in Cuba, and second, the redesign and launch of the XTech web site. Of the first, come to my place for dinner and I'll bore you at length about how amazing it was. Of the second, I'd like to bore you right now! Thanks to Ruby on Rails and a few late nights, the XTech site now has these new features: A few more details on the Ajax Developers' Day. As I mentioned before, when putting together the schedule we felt there was a lot of excellent content still missed out (I'm still feeling guilty at having rejected proposals from many good friends and excellent speakers). So, we put together an extra day at the beginning of the conference where we could go further into detail on Ajax technologies. This day, featuring speakers such as Simon Willison from Yahoo!, XML expert Kurt Cagle and OpenLaszlo's Max Carlson, will allow those working on Ajax projects--either deployment or toolkits--to meet, discuss best practice and move forward on new ideas. Although it's a day-long event, we didn't want to make the price tag as high as a full-day tutorial, so you can register for the cost of a half-day tutorial. A few implementation details If that all sounded a little like advertising, here are some technical details worth sharing. The site's CMS is built on Ruby on Rails. Development was done on Linux, with the help of WINE to check out the view from Internet Explorer. The newsletter is managed by the absurdly wonderful CampaignMonitor. This conference not for sale Before I went on vacation, there was some debate in various quarters about paid-for plenary and keynote slots in conferences. Though I hope it is obvious, I wanted to state where I, and thus the XTech conference, stand on this issue. It has always been my policy to maintain a strict separation between the commercial and editorial aspects of XTech. Although each year there's always a company who thinks they can buy a speaking slot, I never let this happen. The content of the conference is formed by editorial selection by the programme committee, who take the scores from the peer review panel as their primary guide. Aside from what I hope shows in the excellent quality of the talks and generally interesting keynotes (yes, we get it wrong occasionally!), there are two effects on the conference. I hope this explains a little of my position. As a stance, it often creates more issues for me than it solves, but I believe it preserves XTech's reputation as a conference where you can hear some of the best no-fluff presentations on web technology.

Matt Brown: SSC - Open Source Legal Guidelines

The State Services Commission (SSC) (the NZ government body that oversees NZ government departments) released a guide to legal issues in using Open Source Software recently. The publication of this guide has caused a certain amount of consternation in the open source community and even manged to make it to Slashdot and Groklaw as well as spawning a fairly active thread on the NZ Open Source Society’s openchat mailing list. Through all of this I’ve found myself very much on the opposite side of opinion to most other people commenting on it. My initial thoughts on the document are quite nicely summarised by the Groklaw comment that Stuart points out. While the document uses some unfortunate language, there is nothing in it that is actually untrue. In fact my initial feelings towards the document (without having read it thoroughly) were that it was good to see the SSC taking enough notice of open source to feel the need to advise departments on the particular issues that it can bring up. Particularly dissapointing to me are the conspiracy theories that have been flying around. Groklaw surmises that the paper is a Microsoft hatchet job simply because it was authored by Chapman Tripp (a large NZ law firm) who happen to also represent Microsoft NZ on a range of intellectual property issues. I’ve yet to hear a single shred of evidence to back up this assertion and I find it quite ridiculous. Large firms working in a small market such as NZ will often run into conflict of interest issues and have well established procedures for dealing with them. Without seeing evidence to the contrary I cannot accept that a reputable firm like Chapman Tripp would risk their reputation by trying to intentionally mislead the goverment in a report like this. A far more like scenario, to my mind, is simply that the author(s) of the report are not very familiar with open source issues and didn’t do quite as much research as they should have to bring themselves up to speed with the unique IP features of open source licenses. Having read the document more thoroughly now, I can agree that it is far from perfect. I think the single most glaring problem is that it focusses only on open source software and doesn’t mention that many of the risks also exist when using proprietary software. This could leave an uneducated reader completely scared off open source due to a mistaken belief that it is far too risky. On the other hand we shouldn’t completely dismiss the document either as it does raise a number of clear risks that a department will face in adding open source software to their IT environment. We’re not going to do ourselves any favours by pretending that open source is a panacea to all the worlds software ills and can just be dropped in to any IT environment to make things better! It’s worth pointing out at this point that previous evidence from the SSC indicates that they are open source friendly. They have a very clear policy stating that Departments are encouraged to consider open source software alongside proprietary software and use it in cases where it wins on the basis of cost, functionality, interoperability, and security. Given this history, I am alarmed at the hostile reactions many participants on the NZOSS open-chat mailing list had to the document. Quite frankly I think some people are responding far too emotively to the language in the document (which is problematic - but not that bad) and missing the chance to evaluate the rest of it in an objective manner. We have a SSC that has indicated a friendliness towards open source in the past, and I don’t think that they would turn around and reverse their position in this manner. This report is intended to support their overall policy after all. Rather than jumping down their throats and shouting about how poor the document is we need to engage in a civil dialog, point out the issues with the document and offer constructive suggestions for how the document can be improved. To that end, Peter Harrisson has started some pages on the NZOSS wiki where we are going to co-ordinate our impressions and responses to the document so we can present a consistent NZOSS position to the SSC in response. I’d encourage everyone with an interest in the document to read and contribute to those pages. As for exactly what I form our response should take and what it should consist of? I’ll follow up with another post on that later in the weekend when I’ve had a bit more time to reflect.
What I do know (if you haven’t guessed already) is that I think we should be very careful not to respond in a hostile and emotive manner that will result in our relationship with the SSC becoming worse. That means we should take time to consider the document objectively, evaluate its propositions and provide a well researched and substantiated list of suggested improvements to the SSC.

Jos Parrella: Shame, shame

I was at a client today when I remembered that David was due to arrive to Caracas circa 1430, so I called him to his brand-new-venezuelan-GSM-cellphone and I found out that he was in problems. In big, dark, awful problems. As I told in previous posts, he went to San Crist bal (near the border with Colombia) to visit his girl and know the city. He departed from Caracas in a bus on Friday night and arrived on Saturday morning. He spent the whole weekend there, and in Monday he was due to leave San Crist bal through the Mayor Buenaventura Vivas Military Airbase, in a civilian airplane. He arrived just on time for his flight, rushing to take the plane on time, and he was stopped by two so-called Inmigration Officials who demanded to see his passport. He recently got a new one from the Passport Office in Mexico City, so he had a brand new passport with the Venezuelan Entry Stamp (Mexicans don’t need a visa to enter Venezuela)
ONIDEX, the National Office for Inmigration. Praised for lots of people for fighting against Passport Corruption, kidnaps people in San Cristobal. The Officials told him that his passport was a fake, and they told him that, from this time on, he was under arrest. They made him leave the Airport quickly and took him in a civilian vehicle with no identifications. They started the trip to San Crist bal City (1 hour away from the Airport in a very scary road) and they kept telling him that his passport was fake (they claimed that the Passport didn’t have the watermarks, and stuff) Soon their position changed and a common practice in Venezuelan officials started: extorsion. They told him that there were “several ways to fix the problem”, and asked him what was in his backpack (which had a laptop, but he denied it): they were demanding money, and David wasn’t prone to do that.
National Guard. Doesn’t have a /proc/clue about anything. They drove David to the Inmigration Office in San Crist bal and told him that they “made” some tests to the passport and they determined that the passport was fake. They told David that their “Commander” told they that he should be deported into Colombia, since he was a “very important member of a Cartel that they were willing to capture”
DISIP: the Venezuelan Political Police. They were helpful in this episode, but they’re not angels. Finally, hours after that charade of Officials telling him funny laws, stupid suppositions and wanting him to give them money, they left David in the Bus Terminal in San Crist bal, where he was able to talk to Ana, from Debian Venezuela, which picked him up and went back to the Airport. The two “Officials” weren’t there anymore, and he had a last problem with the National Guard which had stupid suppositions about his trip, and stuff (this is common, but at least it’s not illegal) before he was able to get into the plane. Being in Caracas, I was really worried. Between Ana, my mother and me we were able to move several people to check David status in the Airport (my mother called four members of the Venezuelan FAA, I called the Venezuelan CIA and Ana called the Vicechancellor) and this probably saved David’s life and money, since the “Officials” might have been scared by the movement of people caring about David. He’s safe now, back in Caracas, in home. He has all his stuff and his health is OK (yet he was scared when he arrived, which I fully understand) Why am I writing this post? I’m really concerned about what happened to David, and I want to make a public statement on this. Somehow, we venezuelans got used to this kind of practices in our Country. Probably 40 years of pseudo-democracy with messy governors helped, maybe it’s a matter of education and culture. I don’t really care about this, but I do care about what they’re doing with the people in my Country. Today, President Chavez declared that a dance against corruption was going to start. I think it’s the fourth time he’s making something about corruption, and he’s failing. There’s a gang of people in San Cristobal, Mr. President, who tries to rob and scare the visitors. They should be in jail. They arrested somebody illegally. It’s forbidden in our Constitution to arrest somebody without having proofs to do it (we have one of the best Constitutions in the World, experts say, but we don’t have people who obey it). If you’re going to arrest an alien, you need to have a Public Prosecutor in place, writing down a legal document and guaranteeing the safety of the detained. This people should be in jail.
Stop Corruption! Though, as my mother later said to David, two awful Venezuelan people kidnapped David, but probably twenty Venezuelan people quickly acted to find out what was happening. We might be a Third World Country, but we use to be able to get out of our problems by our own. And, hell it’s rewarding. I want to apologize in the name of all venezuelans to David and to make a clear statement against corruption: we venezuelan won’t tolerate more corruption. We’ve grown between that, buying places in a line to get our National ID Card, paying one million bolivares to get a Passport appointment. We’re sick of this. This is not the great Venezuela we live in. Please, losers, shoot yourselves. Or eat rat poison, whichever makes less stains.

13 March 2006

Andres Salomon: Dear Cisco,

Please choke on a bucket of cocks. What the hell are you thinking, making a *managed* switch that doesn’t have console interface? Slap a buggy web interface onto a switch and stick it on the market? Fuck your entire business model. I hope you go bankrupt.

12 March 2006

Jeff Bailey: Aniversaries

<span class='ljuser' style='white-space: nowrap;'><a href='http://auzure-skies.livejournal.com/profile'><img src='http://stat.livejournal.com/img/userinfo.gif' alt='[info]' width='17' height='17' style='vertical-align: bottom; border: 0;' /></a><a href='http://auzure-skies.livejournal.com/'><b>auzure_skies</b></a></span> and I just passed our 4th year wedding aniversary. We went away and had a good time enjoying one another's company. This partly because we managed to pick a town to visit that had little else to do on a Saturday night. The main attraction in the city is a large catherdral that seems to take up most of "downtown". <div style="float: right; margin-left: 10px; margin-bottom: 10px;"> <a href="http://www.flickr.com/photos/91538913@N00/111678841/" title="Cathedral in St. Jerome"><img src="http://static.flickr.com/34/111678841_d75a5acdec_m.jpg" alt="" style="border: solid 2px #000000;" /></a> <br /> <span style="font-size: 0.9em; margin-top: 0px;"> <a href="http://www.flickr.com/photos/91538913@N00/111678841/">DSC00030</a> <br /> Originally uploaded by <a href="http://www.flickr.com/people/91538913@N00/">jbailey</a>. </span>.<br /><br /><div style="float: left; margin-left: 10px; margin-bottom: 10px;"> <a href="http://photos/jbailey/111678837/"><img src="http://static.flickr.com/35/111678837_0b3cd503b8_m.jpg"></a></div><br />Had a good time, though. It's nice to get out of the city for the weekend.<br /><br />Meh. This entry was going to be longer. Took too long to figure out how to do redeye reduction in the gimp and how to work <a href="http://www.flickr.com/">flickr</a>.</div>

Wouter Verhelst: XFree86 still amazingly active.

Quite a while ago, the XFree86 people managed to finally piss off everyone with their license change to the XFree86 1.1 license, so that everyone upped and went back to X.org. After that, they released XFree86 4.5.0, but nobody's been looking. So, I wondered whether they'd still be active, and what would be going on. The X source is quite a lot, it'd be hard to manage that with just a couple of people. Would be interesting to see what they've been up to, I thought. So I went and had a look at their CVSweb server, to see what the recent commits were. If there were any. Well, there have been. The latest commit I saw was the one by David Dawes, all over the tree, done 11 days ago. It goes like this:
===================================================================
RCS file: /xf86/anoncvs/cvs/xc/lib/X11/ConnDis.c,v
retrieving revision 3.32
retrieving revision 3.33
diff -u -r3.32 -r3.33
--- xc/lib/X11/ConnDis.c	2004/06/24 02:21:15	3.32
+++ xc/lib/X11/ConnDis.c	2006/01/09 14:58:24	3.33
@@ -1,4 +1,3 @@
-/* $Xorg: ConnDis.c,v 1.8 2001/02/09 02:03:31 xorgcvs Exp $ */
 /*
  
 Copyright 1989, 1998  The Open Group
@@ -24,7 +23,7 @@
 in this Software without prior written authorization from The Open Group.
 
 */
-/* $XFree86: xc/lib/X11/ConnDis.c,v 3.31tsi Exp $ */
+/* $XFree86: xc/lib/X11/ConnDis.c,v 3.32 2004/06/24 02:21:15 tsi Exp $ */
 
 /* 
  * This file contains operating system dependencies.
Yes, very crucial commit. Wait, it gets better: the commit message says 'Remove most foreign cvs keywords.' "Most"? You mean you've been slaving at all those files, carefully removing the Xorg headers, and you've left some behind? Are you kidding? But I'm not being very fair to them, obviously. There've been more commits over the last year, and most of those did not relate to comments in the code. They relate to the Imakefiles. They've been doing nothing but fixing the build system. Wonderful, isn't it? Those pesky Imakefiles... So that's it? Comment changes and build fixes? Nothing else? Well, no. I'm lying. There's also been this:
 161. Implement a major #include rework throughout the tree.  Also enforce it
      for all non-external builds (i.e. in-tree & SDK)  (Marc La France).
 160. Rework the building of hw/xfree86/parser to be more in line with the
      building of other server subdirectories (such as common/)
      (Marc La France).
 159. ANSIfy /xc/lib/font/builtins/, and fix warnings, whitespace & formatting
      (Marc La France).
A major #include rework? Wonderful. Must be some great new feature, right? Almost:
@@ -62,8 +61,8 @@
 
 #include "attributes.h"
 
-#include "Xlib.h"
-#include "Xresource.h"
+#include <X11/Xlib.h>
+#include <X11/Xresource.h>
 #include "Xrm.c"
 
 static XrmDatabase CopyDb(XrmDatabase inDb);
Yes, very useful. I didn't go through the entire tree (have better things to do) but, really; if this is the average quality of the commits they've been doing, one wonders why they don't just give up. Oh well...

Wouter Verhelst: Ten ways to make a buildd admin's life miserable.

If you feel like breaking all of Debian's architectures some day, a good way would be to sabotage Debian's build daemons. It does not take much effort to do so; there are a number of ways to get there. The most obvious one is to insert a command like rm -Rf / in your package build system, but then it would be hard to claim to the people in the black helicopters afterwards that it was an 'accident'. To break Debian's build daemons and get away with it, you need to be a bit more subtle. Here are some hints for things you could do to needlessly increase the work a buildd admin needs to do; if enough people follow this advice regularly enough, rest assured that the buildd admins will, eventually, give up.
  1. Make your build loop, but still produce output all the time. Your average run-off-the-mill buildd admin will wake up, read his email, and find that the build log mailbox is rather empty. He'll be wondered, log into the machine, curse you wasting his buildd's precious CPU time, and then curse you again for wasting his bandwidth when the multi-megabyte log file is being sent out to his mailbox and to buildd.debian.org (or, as in this case, experimental.ftbfs.de).
  2. Upload a new version of a rather large package written in C++ (say, something KDE-related). Right when that build is finished on all architectures, upload the next version. Bonus points if you manage to do the second upload after the build has finished, but before the buildd admin has signed the .changes file. Extra bonus points if you manage to do all of that during a backlog.
  3. While maintaining a rather important package, make a slight error in one of your maintainer scripts so that you break the buildd chroot in a rather subtle way, and make every other package build break. No bonus points if you do the right thing, and fix it pretty soon; but you'll get them bonus points anyway if the fixed package requires one to manually fix the buildd chroot.
  4. Break your postinst script so that it does not ever exit. Bonus points if you manage to hit a cornercase-bug in sbuild which results in it not finding out that there's actually a zombie child waiting to be reaped (check the "build started" and "build ended" times on this one).
  5. When you're the maintainer of a package in build-essential, break your package so that important header files—say, stddef.h—are gone.
  6. Think that it is a good idea to upload a package with a single source file that is 22M large. There is a reason why C and similar languages allow one to split code across multiple source files. Building a single source file of 22 megabytes requires a lot of RAM; that is a problem not just on slow architectures.
  7. Upload a package that hides the compiler command line while compiling. Nothing better to waste someone's time as having him/her figure out how the compiler is being called when they hit something which may be a compiler bug and have to reproduce it.
  8. Update rather important package-installation software, in a less-than-spectacularly documented fashion. Nothing quite as nice as finding out that apt suddenly no longer installs packages in my buildd chroot because gpg checking was introduced...
  9. Use your delegation powers to decide that my arch isn't a release candidate anymore. Okay, so that was our fault. Whatever.
  10. And, last but not least:
  11. Take all of the above too seriously. No, really. It's only a joke.

Wouter Verhelst: Employment law

Clint, Please get some way to contact you up on your site. Having to reply through Planet isn't ideal. Anyway. I'm not familiar with employment law across all of Europe, but the claim that you have to employ them for a certain period after you actually fired them, or even that you can't fire someone without due process, is simply false—at least in Belgium, though I expect the same is true for most other member states of the European union. First, there's the fact that every employment contract starts off with a "test period" which can take up to six months, depending on the type of employment (it is longer for hotshot management than it is for hand labour) and the length of the contract, if appropriate. During this period, an employer can fire someone without further explanation and without any process. This is to make sure that you can get rid of people who managed to sell skills on themselves they don't end up having. Second, an employer can fire anyone right away for what is called 'urgent reasons'—things like employees stealing from the employer; basically anything that makes the employer lose trust in the employee (though this is strictly regulated, for obvious reasons). Third, if you fire someone not during their testing period and not for urgent reasons, you do not have to keep them at your place; it is legal to tell someone that as of tomorrow, they no longer have to come to work -- you just have to give them a pay check for those three months (or whatever) you would have to employ them otherwise. Finally, the thing also works in the other direction; if some important employee (say, the only guy with the root password) decides to quit, an employer can require that they stay at work for up to (IIRC) two weeks, so as to ensure continuity. But I understand you knew that part already...

11 March 2006

Clint Adams: Everyone loves Magical Trevor

All this niggling about delegations disturbs me. You would have thought that Ian Jackson would have cleared this up but he seems to have confounded the issue by paragraphs of equivocation after a firm and sensible statement. For someone used to nearly-nonexistent labor protections, the idea of not being able to fire someone without due process is one step away from a totalitarian dystopia. Americans look at European employment laws with amazement and horror. The employees might see the added job security as comforting, but the knowledge that one can quit on 5 minutes' notice is comforting as well, and it is not a freedom that most would sacrifice. Employers see the added security as a potential nicety, but also as a terrible burden. Not only do we have to keep paying them after we fire them, we have to give them places to sit! It's tantamount to Evil Communism. I'm sure you can guess what Europeans think of American labor laws. Anyway, having anyone with augmented privileges not be fireable at the drop of a hat seems like madness to me. So I'll continue to believe that we can can anyone on the org chart any time we damn well please. Any other situation would mean that they have too much power.

Andrew Pollock: [life] Syriana

Holy Blackberry product placement, Batman! Tonight Sarah and I went and saw Syriana. It was an interesting movie. It told a story, which is what I like in a movie. In fact it told four, and that was the problem. It had four plots that vaguely intertwined, each with their own sets of characters, and it became damn hard to follow who was who, and what was what. This is definitely one to watch a few more times on DVD, with the director's commentary, just to work out exactly what the heck was going on...

Clint Adams: Snakeback in Angora

Somewhere in the vast and unspoiled natural beauty that is New Jersey, right around the corner from K-Mart, lived a man named Stellan Andrews. He lived with his wife, his enormous children, and a host of psychotic delusions. Stellan had always known that he was special. From a very early age, it was clear to him that he was superior to the other children, and as he aged, he discovered that he could employ his above-average intellect and cunning to manipulate social systems to his advantage. By the time he was 18, he thought himself invincible. His ambitious and power-hungry nature was tempered by a fair amount of social ineptitude and an utter lack of empathy for anyone who was not similarly power-hungry and evil as he. This led to a perception of him as bright and eccentric at best, or more frequently as one of them there smartypants weirdos who thought that he was too good for his neighbors in the mobile home park. His friends were few and tended to be outcasts with sociopathic tendencies. These friendships were intense and codependent until abrupt ends; one person would demand too much, the other would demur, the first would stand firm and uncompromising as this would now become a significant issue about loyalty and value and importance, and after a short-lived blowup, they would never speak again. Throughout, extreme amounts of jealousy would rage in both directions, and so Stellan never had more than one friend at a time. In between friendships, though also during them, Stellan spent much of his time tinkering with technology. He dissected and rebuilt radios, televisions, computers, and anything else he could get his hands on. He played with model rockets and explosives of many types, though without fail it was his friends who were more interested in these types of activities. With them, he also played with guns, but he never had any interest in doing so on his own. After high school, Stellan enlisted in the Army, despite a fundamental distrust of government and a lack of passion for most of the various relevant interests of his now-forgotten friends: guns, history, tanks, U.S. Cavalry catalogs, and dolls that were called action figures . However, he did enjoy strategy- and war-games, which never had any relevance to his military career. The only aspect which appealed to him was the power hierarchy, and this seemed more natural to him than any other social structure he had experienced. He was stationed in Laos for a time, and that is where he met his wife. She was a Chinese rabbi, and since she spoke no English, they hit it off smashingly. With not much to go on about her personality, he romanticized her into his perfect woman, and by the time his delusions were shattered, they were raising children in New Jersey. Neither was particularly happy. She sublimated nearly all of herself into her work at the local pan-Asian synagogue, and he, now more social than he had ever been in his life, entered into a sinister and twisted game. It was called Perfidy, and there were a couple hundred participants across the entire country. These players had a few things in common: they were moderately sociopathic; they harbored great contempt and resentment for the average citizen, whom they characterized as a stupid sheep or cow; and they believed that they, as superior creatures, were entitled to control the proletariat for entertainment purposes. The game, to boil it down to some sort of boiled-down nutshell, was the structured use of random and unwitting people as pawns in a giant and complex strategy game. The players who excelled were accomplished manipulators and liars, or, as they preferred to call themselves, social engineers. They were also cold and dispassionate. Stellan lost his head. He had just been outman uvred by Jack Breig from Delaware, and he was livid. As the bile rushed into his mouth, he lost his firm grasp on strategery, and succumbed to vengeful instincts. Within days, he and Jack were getting far too personal. His rage abided when he succeeded in triggering Jack's divorce. In response, Jack proved once again that he was Stellan's better. The next day, Stellan was arrested for a crime that he did not commit. He was sentenced to eighteen months in prison. His family was not pleased. He returned home a felon. No longer able to get credit or a job, he reacted in the most natural way possible: he joined the local Plan 9 Users' Group. [To be continued...]

Uwe Hermann: Greenpeace, E-waste, Linux Ecology-HOWTO

Greenpeace has asked companies to minimize the usage of toxic substances (English article) in computers and other electronic devices at this year's Cebit. Hewlett Packard, LGE, Motorola, Nokia, Samsung, Sony and Sony Ericsson have assured Greenpeace to reduce toxic substances in their products in the nearer future. However, many other companies have ignored Greenpeace so far. For example: Acer, Apple, Dell, Fujitsu-Siemens, IBM, Lenovo, Panasonic, Siemens and Toshiba. I'm listing the names of these companies here in the hope to increase public pressure on them a bit ;-) Although I'm not a member of Greenpeace (yet?), I do support the ideas and work of Greenpeace, and especially the above E-waste article made me think. We're all using more and more computers, PDAs and other gadgets — especially the geeks among us. I think we all should (at least to a certain degree) care about how this affects the environment. I have fired up a search engine and looked for some hints about what you can do as a computer geek in order to help save the environment — guess what... there's a HOWTO for that, the Linux Ecology-HOWTO! (I'm beginning to think that there's no topic out there anymore, which hasn't been covered in a HOWTO by some Linux geek ;-) (via netzpolitik.org)

10 March 2006

Axel Beckert: Vintage Computer Festival Europe 7.0 ahead

It’s only seven weeks to the most important vintage computing event in Europe, the Vintage Computer Festival Europe (VCFe), which for the first time will be three days this year because of May the 1st being a Monday this year and an official holiday in Germany and some of the swiss cantons (at least Zürich). So the VCFe 7.0 will take place from April the 29th to May the 1st 2006 in Munich and it’s focus this year is:
Home Made Brains
Kit-Computers and Individual Designs I’m currently thinking about which old hardware I’ll present at this year’s VCFe. There are a few ideas flowing around in my head:
  • Old x86 laptops (1989-1996). This was my exhibition last year, but ayca, my i486 Toshiba laptop is broke (probably the display controller) and the “new” Compaq LTE pony hasn’t been setup yet. Nevertheless, I’ll bring my (nearly) everyday ThinkPad bijou with me since it’s now 10 years old and therefore ontopic now. Yeah!
  • The HP 9000 Apollo Series 400 I got from dwalin and dyfa, if I manage to get a NetBSD installed on that box.
  • Buying a tux case but installing some old hardware in it instead of the current FOX board. On the other hand: There should be at least a Linux running on that box.
Anyway, I’ll be there, many other Symlinker (at least dino and Venty) also will be there. And I hope to see you there, too. :-) Oh, and btw: One wish to the Debian community regarding the VCFe: Perhaps someone who’s familiar with the Debian m68k Port could give a talk about how Debian plans to save this port although the old hardware isn’t fast enough to fit the requirements for inclusion in a Debian release. This would give a really interesting talk about old and new hardware. Talks can be held at least in German or Englisch IIRC. TIA. :-) Update 16:26h: I thought of this mail by Wouter Verhelst about how modern ColdFire computers could run buildds for a hybrid m68k and ColdFire port when writing this paragraph. See also this Symlink story [German] about that topic.

Clint Adams: My friend the communist is a hypoallergenic dog

I think one of the devotee hobbyists should set up a survey to help debunk the myth of monoculture and illuminate some potentially-depressing patterns that may live in the cracks between tribalist boundaries. I suggest something like this list of hostile acts.
- - -=-=-=-=-=- Don't Delete Anything Between These Lines =-=-=-=-=-=-=-=-
deadbeef-1550-53xy-114d-490b20ec1fe3
[   ] 1: Alice makes fun of Wally for writing terribly broken patches (to his face)
[   ] 2: Wally makes fun of Alice for writing useless bug reports (behind her back)
[   ] 3: Alice sucker-punches Wally in the gut.
[   ] 4: Wally calls Alice a useless, scabies-infested neo-conservative
[   ] 5: Alice calls Wally a retarded troll version of Michael Milken
[   ] 6: Wally tells lies about Alice to everyone, pitting them against her
[   ] 7: Alice emails Wally some questions, with M-F-T and Reply-To set to Wally
[   ] 8: Wally willfully ignores all communication from Alice
[   ] 9: Further disthrustion
- - -=-=-=-=-=- Don't Delete Anything Between These Lines =-=-=-=-=-=-=-=-
One could do all kinds of fun stuff with this, adding and removing context for actions, since that type of thing matters to some people, even some of those fine people in the audience with some sort of borderline personality disorder. I might rank number 8 as most epicly-proportioned hostility and number 3 as least epicly-proportioned hostility , whereas my friend Alpesh, who claims to be a pacifist, but refuses to acknowledge that verbal abuse is violence, might do the exact opposite.

9 March 2006

Clint Adams: Kabalkroogz

J rg, your use of ASCII confuses me. Do you mean , 2 3, 2 3, or a relative pathname called 2/3 ? Unicode solves all communication problems.

Next.

Previous.