Search Results: "ag"

28 August 2007

Wouter Verhelst: New hackergochi with Gimp 2.4

As you may have noticed, I've got a new hackergochi. This has two reasons:
  1. I noticed that since a couple of weeks there's a new Gimp in the archive (a release candidate of Gimp 2.4), and I just had to check it out,
  2. The picture of me wearing the cooking costume thing was just way too funny to ignore.
Previously, selecting a head from a picture with a very busy background was almost impossible to do. In my case I had a single-color blue background, but I've helped some people do theirs, and in one extreme case I we had to zoom in to the max and manually follow the lines separating the head from the background. This took a very, very long time -- like a day or so. Gimp 2.4 comes with a selection tool called the "Scissors Select tool" that seems made for creating hackergochis: you click on some line that appears on your picture, and a dot appears. You click on a second point along the same line—a line which may be straight, or which may be curved, or which may be zigzagging—and the tool just follows it. In this particular case, the background was a very busy cabinet. And yet selecting my head against that background was done in less than a minute. Way cool.

27 August 2007

Adam Rosi-Kessel: Terrorist Hashing?

The Hash House Harriers is “an international group of social, non-competitive running and drinking clubs.” I participated many years ago in college (e.g.), although the Princeton Group is probably more tame than most. Via Bruce Schneier, this crazy new items:
Two people who sprinkled flour in a parking lot to mark a trail for their offbeat running club inadvertently caused a bioterrorism scare and now face a felony charge.
Although I don’t hash anymore, I frequently see the characteristic flour marks while jogging in the woods. I can’t see how the perpetrators here could possibly meet the mens rea requirement for a felony bioterrorism charge.

Russell Coker: Hydrogen Powered Cars Will Never Work

One of the most important issues for a commodity fuel for vehicles is that it be convenient and safe to transport. For quite a while LP Gas has been available as a cheaper car fuel. Even with increasing petrol prices it’s acceptance is well below 100% due to extra expense in storing the fuel (high pressure and more insulation are required), the more expensive technology in the engine to heat the fuel before injecting it into the engine, and the extreme difficulty in creating something as convenient as a Jerry Can for transporting LPG. LPG is mostly comprised of Propane and Butane. Propane has the lower boiling point of -42.09C. Hydrogen however has a boiling point of -252.87C and therefore is much more difficult to store and transport. The next problem with hydrogen as a fuel is that it has a very low density. The energy density per volume of liquid hydrogen is 10.1MJ/L while the energy density of petrol/gasoline is 34.6MJ/L. Not only is liquid hydrogen difficult to transport but the vessels you transport it in need to be 3.4 times the size! Having a 3.4x larger fuel tank in a car may not be a huge obstacle, but then there is the issue of trucks used to transport it to fuel stations which are already at maximum size so the truck fleet will need to be 3.4x larger with more people driving them etc. Once these problems are solved there are a variety of safety issues. Hydrogen burns with an almost invisible flame, sustains a fire when at a concentration of between 4% and 75% of the air and ignites at a low temperature. For an explosion you need a concentration of between 18.3% and 59%. I won’t risk promoting foolish behaviour by describing details, but when younger I have performed experiments with ethanol and witnessed experiments with petrol that demonstrate that they are both far less dangerous. Page 22 of this document by the US Bureau of Transportation and Statistics gives more information about the fire risks posed by hydrogen fuel. Page 35 of the same document describes fuel cells as being 45% efficient and an internal combustion engine for methane gas as being 30% efficient thus giving overall efficiencies of 33% and 29.5% respectively. Of course using an Atkinson Cycle engine will give a significant efficiency benefit over an Otto Cycle engine and outweigh this. Also it should be noted that fuel cells tend to require expensive materials such as Platinum in their manufacture. Hydrogen is promoted by clean-coal advocates (not that any form of coal power is clean) and the nuclear industry (electrolysis is one way of using a huge amount of electricity). But there are many better options for powering cars that are available right now at minimal cost, these include bio-Diesel, ethanol, and plug-in hybrid or electric vehicles.

Dave Noble: Random #qc meetup in Utrecht!

A couple random fans of the Questionable Content webcomic decided to meet today in Utrecht! The late August weather was fantastic; and it was an amusing way to kill a day.
#qclings
In other news, I am addicted to Boards of Canada again.

Steve Kemp: I'm on another world with you

So that'll be me engaged to the most beautiful girl in the world then.(*) This explains where I've been, what I've been doing, and should suggest I'll be catching up on two-three weeks of work tomorrow.
[*] - OK you might disagree. I don't.

Joey Hess: confused by Debian vim addon policy

The new policy for vim addons on Debian is that the addons should not be enabled by default. You have to install vim-addon-manager and use vim-addons to turn them on. So while I can apt-get install insecured and the daemon will automatically be run, I can't apt-get install vim-vimoutliner and edit .otl files in outline mode by default. Seems weird or backwards, no? The vim-addons program does solve several problems, like being able to disable addons, or selectively enable addons from vim-scripts. But I've read all the docs I can find about this, and I can't find a rationalle for why the addons should be disabled by default. Seems to me that addons could simply run vim-addons from their maintainer scripts. Any reason not to?

Steve Kemp: walking on the moon

According to popcon I have just under 1000 users of xen-tools. That was quite a suprise to discover via a random google search, although I guess there have been a lot of bugs filed against the package during its lifetime. Funny how some things which start as random hacks (this was originally a quick and dirty hack for a Xen introduction article) become quite useful/popular, whereas other tools which were planned and designed go virtually unnoticed...

Romain Francoise: More fun with md5sums: collisions

During my experiments with file duplication in the Debian archive, it occurred to me that having a list of files with identical MD5 hashes was a good starting point for finding MD5 collisions in the archive. If any of those files were different but had the same hash as computed by MD5, I'd have a collision.

Unfortunately, checking if the files differ involves extracting the data tarball of each affected package and computing another hash for the files (I used SHA-1), which takes a while. 3h32m and 47GB of extracted files later, I now have the results and there is no MD5 collision in the Debian archive. The chances were slim if not null, but at least now I'm sure.

(In fact I did find one occurrence, but it turned out that the file's MD5 hash in DEBIAN/md5sums was incorrect, for some reason.)

Jeff Bailey: Fido cell phone

Hey'all! As part of moving, I need to get rid of a Fido contract that has two months left on it. Anyone looking to get a cellphone in Canada sometime soon? Taking over the contract has the advantage of giving you my $207 fido dollars which can be used towards getting a sexier cellphone than you otherwise would've gotten for the contract.

So if you're out there about to go get a cellphone anyway, drop me a line: jbailey@raspberryginger.com

Radu Spineanu: Removing old packages no longer in Debian

Don’t know is anyone is interested, I wrote a small script that detects installed packages that were removed from Debian. It does this by looking at the repositories in /var/lib/apt/lists/ and comparing them with what is installed. On my home system it found 150 packages, but the installation is just 3 years old. The script can be downloaded from: http://people.debian.org/~radu/oldpackages.py Update: The script does the same thing as aptitude’s Obsolete and Removed packages option. I updated anyway a little to ignore removed but not purged packages.

Adrian von Bidder: Minority Report

Just watched Minority Report last week. Quite good, disappointing ending. Should stop ca. 6 min earlier, when it becomes clear that precrime collapses (and after the resolution of the plot.) The tagged-on happy-end seemed artificial and implausible to me (implausible by the standard of the world of the movie, that is :-).

Russell Coker: Writing a CV for a Contract Position

There is a lot of career advice related to writing CVs in books and floating around the net. Unfortunately almost all of it is tailored to permanent positions. Some advice that I have seen includes researching the company you are applying for and emphasising your experience in related fields. This probably makes some sense if you have targetted a major company to be your employer for the rest of your life. But if you are after contract work (which incidentally tends to pay better than permanent positions) then it’s not going to work. About half the time when applying for contract work you won’t know the name of the company that is receiving your CV until after they have decided whether to grant you an interview. Contractors therefore need to write their CVs to have broad appeal (emphasising common technologies such as C programming and skills such as debugging), and to appeal to a recruiting agent. Some people recommend writing your CV in MS-Word to support agencies and potential employers who are not competent enough to open other file formats (such as PDF and HTML). I strongly disagree with this advice, most contract positions are advertised by multiple recruiting agencies and it would be best for you to be represented by the most competent agency. Therefore having an agency staffed by incompetent people not represent you because they can’t figure out how to read a HTML or PDF file is a good thing! The same applies for employers, while applying for the best paying contracts will often result in some strange and unpleasant working conditions having a manager who can’t open a PDF or HTML file is likely to result in something that is unusually bad - run away! Recruiting agents will often give specific requirements for a CV. Sometimes these requirements are a little odd (such as demanding that references to C programming be removed from a CV when applying for a Unix sys-admin job), but being merely a little odd is no reason to boycot the agency. To solve this I wrote my CV in M4 macros to generate HTML code. When I wanted to apply for a position I would just type make to compile the M4 source into five or more different CVs. Sometimes a recruiting agent would request two versions when applying for one position, it’s a strange request but when five versions were compiled in one pass it was easy to satisfy it. If I liked PDF I could have written M4 macros that generate TeX and have the make process convert TeX to PS and then PS to PDF. Unfortunately I can’t share any macros because the code was not of particularly high quality (which is a little ironic) and because it’s tightly tied in to my CV. The best piece of advice that I can give to anyone trying this is to get columns sorted out as the first issue. If you want to have some lists of programming languages, lists of OSs, and lists of hardware, etc in your CV then it usually works best to have two columns in the page. If the largest list is removed then the other lists need to be shuffled around to get the column lengths to match. Doing this in HTML required some ugly M4 macros. There probably is a better way of doing this in TeX (but I’m really not good at TeX and can’t give advice about it). James has some interesting advice about writing CVs. I think that his most useful points are:
  1. Use file names based on your name so that agents can find your CV in the directory full of CVs

  2. Include complete contact details. One thing he doesn’t mention is that you should buy a mobile phone for the purpose of getting a job even if you don’t want one for any other reason. A 5% difference in pay for a year’s work would cover the cost of many mobile phones and the difference between a good job and a bad one is likely to be more than 5%. If you are afraid of brain cancer then don’t worry, if you only spend a few minutes a month talking to recruiting agents then you are at no risk.

  3. Don’t start a sentence in the career history section with the word worked - everything in that section will be related to where you worked in the past. It seems obvious in retrospect but I realised that I have made this mistake on my CV.

Michal Čihař: Photo album generator wanted

After (again) searching for some good photo album generator, I'm more and more inclined to writing yet another tool to do this. Maybe I just want too much from this, but I haven't found solution that would fit my needs: So far I'm using a bit customised Matew which really does not fulfil everything, but at least works reasonably good (but extremely slow). However the more and more pictures are in my album, the slower this beast seems to be, so it's probably time to switch to something new. So far I haven't found anything that would actually fit, but PyAC seems to be usable as starting point for my new project for generating albums. Or is there a working solution?

Enrico Zini: pkgprune

Filtering Debian Packages file
pkgprune - Filter a Packages file
Usage: pkgprune Packages > Packages.filtered
Filters a Debian Packages file by removing either a list of packages (and
their reverse dependencies) or the packages that have given tags.
Dependencies in the filtered Packages file will still be satisfied.
Available via:
wget http://people.debian.org/~enrico/2007-08/pkgprune/pkgprune
or:
hg clone static-http://people.debian.org/~enrico/2007-08/pkgprune
The top of the script has a configuration section:
#
# Configuration
#
# Set of packages you don't want to have (the reverse dependencies will be
# removed as far as it's possible)
blacklist_pkgs = set(['gconf2'])
# List of sets of tags; the packages whose tag sets contain one of these tag
# sets will be removed
blacklist_tags = [ set(['implemented-in::php']) ]
Edit that before running the script. The idea is to be able to configure a system to run such a script after apt-get update, both to make dpkg faster on slow arches and to reduce the amount of packages displayed by an interface.

26 August 2007

Miriam Ruiz: D compiler in Debian

gdc has finally entered Debian repositories (thanks Arthur Loiret, Matthias Klose, thanks GCC folks!). It’s time to start putting the rest of Kenta Cho’s games into Debian. Two of them, A7Xpg and Gunroar, are already in the NEW queue, some others are on the way. Kenta Cho is most famous for his shmups or shoot ‘em ups, mostly featuring abstract reinterpretations of retro classics with each game having a specific unique feature and using randomly generated levels. rRootage and Noiz2sa are already in the archive, since they were coded in C++. Thanks to Javier Candeira, who introduced me to Kenta Cho’s world.

Russell Coker: Never IRC as Root

Ben Fowler blogs about the issues related to running IRC as root. Google searches for (irc client exploit) and (irc client “buffer overflow”) give a number of interesting web pages. Many of the exploits require the user to perform an action that’s slightly unusual, but why take a chance? The advice to not run as root while generally sensible (run everything with minimum privileges as much as possible) is IMHO not very useful in recent times (and probably was never very useful). Generally when a user is worried about system compromise they are not worried about attackers having direct hardware access, the ability to corrupt system files, etc. They are worried that the attacker might read their email and access other personal files. Therefore the instruction should be “don’t run IRC as root or as any account that has access to data which is important to you“. It’s not difficult to start an X-term that runs “exec su - ircuser irc” or “ssh -t ircuser@localhost irc“. Note that the -t option is required for ssh to make it allocate a pty even when receiving a command to run. Note also that in the case of su you need the exec option so that if the irc client is compromised and tries to perform a ioctl(0, TIOCSTI… based attack then it won’t succeed. In any of these methods make sure that X access is not granted. Until we get Security Enhanced X working in a viable manner any process that can display an X window on your screen can own you totally. There are of course relatively safe ways of doing X, I have previously documented how to configure the Xephyr X server (replacement for Xnest) to allow a process with a different security context to safely display a graphical window on your desktop. Generally I recommend not using a graphical X client on an untrusted network (IE anything other than an Intranet IRC server). I prefer to do my IRC in an account that’s not even on a machine that I care about and have it run screen so I can disconnect and re-connect from anywhere in the world. When I first got SE Linux in Debian to be useful (when I could boot and run all programs without problem) I logged on to some IRC channels related to Debian with the security context of root:user_r:user_t. I admit that my actions in this regard could possibly be described as trolling, but I wanted to demonstrate what SE Linux can do. Unfortunately of the many people who told me off for logging in to IRC as root, none of them wanted to hear an explanation of why user_r is safe in this regard. I expect that most of them were running their IRC client in the same Unix account that was used for their email etc (and probably most of them had GPG keys accessible from such an account). Sigh, it’s so easy to run IRC as a different user - in fact it’s probably the easiest of all network client programs to run in such a manner. There’s no reason not to.

Roland Mas: Gforge in Debian, August 2007

As I type this, debs for a current snapshot of upstream Subversion are on their way to Debian Sid. They are taken from the Subversion trunk and not from the yet-to-be-released 4.6 branch, because a few important changes have taken place on the trunk only, and the 4.6 branch is merged anyway. Hence the version number, 4.6.99+svn6078-1. These packages did spend some time in experimental, and I didn't get any bug reports, but that doesn't mean they're bug-free. Use with caution. One of the big changes is that Gforge now uses Gettext rather than its home-made internationalisation system. Which means probably fewer problems, and a more standard system allowing more people to get involved. Can you guess what I'm hinting at? Yes, it's a call for translations! Anyone interested in getting involved should bzr branch http://alioth.debian.org/~lolando/bzr/gforge/upstream-svn/trunk/, and start poking the existing *.po files (or creating new ones!). Why the private repo and not the upstream Subversion repository? Rationale follows. My job as a freelancer as well as my role as an Alioth admin involve maintaining separate branches of the Gforge code (different clients have different needs and patches). In order to facilitate patch migration, I therefore need a distributed VCS, and I've been using Bazaar for a few years, with a manual gatewaying between upstream CVS first, then Subversion, and a few private Bazaar branches. Now that Bazaar (as in Arch) is dead, I'm using Bazaar (as in Bazaar-NG, Bazaar-2, or bzr), which seems to be approaching a 1.0 release, and which provides a plugin to interoperate easily with Subversion repositories. And since the upstream Subversion repository is not accessible anonymously anyway, I decided to publish my gateway branch. I'll probably publish more branches as time passes (probably the Alioth branch, and quite possibly feature branches too). Note: if you want to share a bzr repository of a project containing PHP scripts with Apache, you may encounter a problem, because the bzr repository contains files named *.php.knit and *.php.kndx. And Apache will happily give these files to the PHP interpreter when serving them, and that's not what you want. My trick to fix that is to add a .htaccess file somewhere where the repository is stored, with the following contents:
AddHandler None .knit .kndx
This will ensure that these files will be sent straight to the HTTP client, and not through the PHP interpreter.

Sebastian Harl: FrOSCon 2007: Debian on a Lego robot

Debian on a Lego robot This little Lego robot runs (well, drives) with Debian ;-)

Christian Perrier: Back...and mail read

Less than one full day to read 8000+ mails. Not that bad. Among these were like 2000 spams that hadn't been detected by my spamassassin+CRM114 setup on my mail server, but properly identified by CRM114 on my laptop. Interesting thread in debian-devel after I reported bugs about the use of "Homepage: " in packages descriptions and Christoph Berg objected to it. Apparently, this could lead to the support of a "Homepage:" field in debian/control which is Good. New samba upstream release (3.0.25c) on its way. Steve Langasek did a release of the package while I was away, Peter Eisentraut did some bug triaging and No l K the prepared the release toay, searching for the bugs that are fixed. No real problem building the new version, except for the Python bindings which are nearly unmaintained (we are seriously considering to stop providing python-samba so please speak up *and* come helping if interested). The D-I l10n-sync script was hosed for 2 weeks because of a broken Swedish translation file (I hate poEdit for this, see #420685). I really should begin seeking for a backup for D-I l10n handling as Dennis Stampfer is now apparently completely MIA. Nothing really important apart from all this. Probably time now to begin preparing a possible trip to India for FOSS.in which I really would like to participate to, if I can find a way to fund the travel. Also time to think deeper about the proposed Extremadura i18n meeting which hasn't met a huge success, probably because we really want it to be focused on *one* goal this time (DDTP/Pootle).

Biella Coleman: The problem with presentism

A few days ago, Joe Reagle was telling me about the rise of (sometimes very arcane) policies and bureaucratic imperatives that now characterize Wikipedia. A few days later I stumbled across a few interesting posts on the topic, posts (especially Nick Carr’s) seeping with almost celebratory gloom and doom:
‘But, given human nature, is it really so “incredible” that Wikipedia has evolved as it has? Although writers like Yochai Benkler have presented Wikipedia as an example of how widescale, volunteer-based “social production” on the Internet can exist outside hierarchical management structures, the reality is very different. As Wikipedia has grown, it has developed a bureaucracy that is remarkable not only for the intricacies of its hierarchy but for the breadth and complexity of its rules. The reason Deletionism has triumphed so decisively over Inclusionism is pretty simple: It’s because Deletionism provides a path toward ever more elaborate schemes of rule-making - with no end - and that’s the path that people prefer, at least when they become members of a large group. The development of Wikipedia’s organization provides a benign case study in the political malignancy of crowds.”
It is without question that a problem has arisen in Wikipedia, a problem composed of a thick web and net of rules that can be helpful as guidelines but often are often confusing and clearly work to ensnarl new users. But can we so quickly put blame on so-called human nature? Or is it not a problem of human organization, which as the anthropological and sociological record shows, can take many forms? And is it not just that: a problem begging for a solution instead of an opportunity to declare the fundamental nature of wikipedia (and that of human nature?). Not only may history prove him wrong, other large scale collaborative projects at least prove that solutions can be found to deal with problems of growth and scale. It is as if Carr just wants to see a project like Wikipedia fail, which somehow, this morning hit a raw nerve. What I find exciting about large scale projects of (at times unwieldy) collaboration are not just the explicit outputs of the projects (an encyclopedia or operating system) but the social worlds they create. And there is no inevitable path they *must* follow. These groups have a choice to react to and respond to these sort of problems and enact solutions that will hopefully solve them and allow these projects to change. Debian, a slightly older project than Wikipedia, has gone through many growing pains and there was even a period when the the whole process of integrating new Debian developers was shut down and if my memory serves me correctly, for 2 years! At the time, it could have been possible to say: “This signals the end of Debian” but eventually a solution was found, the New Maintainer process, which while not perfect (what is?) allowed the project to grow and produce a great operating system for years to come. Debian today faces new problems and is working to find solutions. I hope that Wikipedia can and will do the same. And instead of declaring its death, why not wait and see, and offer something a little more constructive and illuminating, than destructive?

Next.

Previous.