Search Results: "ag"

18 December 2008

Tiago Bortoletto Vaz: scottish musician



Auld Reekie, something to be remembered yep, today is a nostalgic day. Posted in english

Michal Čihař: Gammu stable version 1.22.0

After two and half months of development, new Gammu stable release is out. Since last testing version there are only minor changes in vCard export, but full changelog since 1.21.0 is quite long: You can download from usual place: http://cihar.com/gammu/, Binary packages will be available soon in all usual places (Debian Unstable, OpenSuse build service, Ubuntu PPA repository).

Raphaël Hertzog: Release Lenny GR

This is the worst vote that has come up since I m part of Debian. And Manoj the secretary has refused to listen to the remarks of many developers about the misleading titles/summaries, about the unjustified 3:1 ratio, and worst of all, about the mixing of multiple questions in a single ballot. I have ranked misleading options ( Reaffirm social contract at least) lowest and below Further discussion and sorted all the other options according to my preference, and ranked some of them equally when the choices answer different questions (where I can not prioritize any preferred outcome). I m not yet sure if I put Further discussion first or not. There s some hope that the vote will be cancelled and redone with separate ballots but I ve lost trust in Manoj s abilities to do his job properly. I m sure he s convinced that he s doing the right thing but that doesn t help at all, on the contrary. It also means we probably should fix the constitution to make it crystal-clear how the secretary should decide whether 3:1 ratio is needed for a given resolution or not. Not really the kind of thing I enjoy within Debian, but that s the price to pay if we want to continue to work together. On this and much more I agree with Russ Alberry. Update: Manoj resigned as secretary. I want to thank him for having taken this hard decision. And I sincerely hope he doesn t resign from Debian completely as our strength is also in our diversity of opinions. Partagez cet article / Share This

17 December 2008

Biella Coleman: Going, going (gone) Monastic



Not Ballistic, Monastic, originally uploaded by the biella.
Have you ever gone monastic, taken a step away from the rough tumble of life to throw yourself totally and completely in one or just a few things? I have been in this state a few times before, sometimes by my own volition, other times I was forced into such state, as when I spent nearly a year homebound, sick. The last time I went monastic, I did so to finish my dissertation in 2005 and it worked rather well. In fact, I recall those few months where I barely left home (and as result my PJs) with deep fondness. I just loved the intensity and simplicity of it all, which is why I loved my other periods of self-enforced solitude/simplicity and often yearn for those moments again. The pile of writing projects I am trying to complete (or start) are mounting and honestly, I want the pile to move from a mountain to at least a hill and in order to do so, I think I will have to retreat. So tonight, I declared that upon my return from PR, I will once again go monastic but given that I have a pretty demanding full time job, I can t really go full-on monastic. I can only go semi-monastic, shirking some of my extracurricular activities and duties but I still think that I can enter into a more seclusionary (I know not really a word) mode than has been my life for the last year. I will report back in a few months with a story of success or failure about entering Monastic Mode x

Joey Hess: Dell Mini 9

Well, I got the Dell Mini 9. Tiny little toy-looking laptop. It's too soon to tell if I'll like it. Or if my goal of using this as my only laptop, and primary work machine will succeed. But what a lot of firsts and changes! My first laptop with no moving parts. Yay! My first completely silent laptop. Double yay! First laptop I've bought with linux preloaded. The default Ubuntu load was ok. It also contains my name 886 times. :-) Scarily, it also runs bits of code I wrote for base-config. Installing Debian went ok, mostly, though wireless is a bit of a pain, and I have a strange problem with something fiddling with LCD brightness periodically. Oh, and SHDC cards make it crash on boot and resume. I've set up a page with the details, including how to fix the missing punctuation keys. I've switched to using white on black for my terminals, and run them full screen rather than tiled. Cause the screen is small, and doesn't handle large black expanses as well as I've been spoiled to expect by machines that cost three times as much. I like that netbooks encourage minimalism.

John Goerzen: More Wiki Annoyances

So today, I discovered that MoinMoin has an all or nothing attachment setting: either everyone with write permission to a page can upload attachments, or uploading attachments is disabled for the entire site. No exceptions. Period. Not only that, but there is no maximum attachment size setting unless the attachment was uploaded embedded in a ZIP file. How s that for irony? Not wanting to have my railroad site turn into a file trading site, I don t really want to let everyone upload attachments. Oh, also MoinMoin doesn t maintain a history of attachments. So if somebody drives by and vandalizes an attachment, you get to . restore the original version from tape. Yay? So I decided I d look back at MediaWiki, which has better attachment controls. I still had my test installation, so I went to use it. I edited the main page. I wanted to read about the markup, so I clicked the Editing help link. Whoops, broken link. It links to Help:Editing on the local wiki. Which MediaWiki does not install for you. I asked about it on #mediawiki. The answer was: copy from mediawiki.org. OK, fine. How? Cut and paste. Yes, that s right. Every time a new version of MediaWiki comes out, you get to cut and paste dozens of pages from mediawiki.org to your wiki, or else you ll have outdated help. Yay? The MediaWiki folks on IRC seem to like it this way. Not everyone wants the same help. Fine, but provide a sane default for those that don t care. Who thought running a wiki would be so hard? Update: since yesterday, I went to moinmo.in and fixed the ThemeMarket page to reflect what versions a MoinMoin theme works with. I m happy to help out with fixing Free Software though I don t really have time to add fundamental features like working syntax help links on this particular project.

Stefano Zacchiroli: on facebook and graphology

today: illegal graphology ; tomorrow: illegal facebook query Join two dots and obtain a line. The first dot. A few days ago, on the blog of an italian journalist I've found a reference to an old article about facebook originally from the guardian (even equipped with an italian translation, just in case ...). The article is quite long, but I found it a worthy read. (Well, at least it is one assuming you can skip over the initial rhetoric about "social networking = autistic geeks". Similar arguments were as annoying as untrue already 10 years ago about the Internet, and even more so 20 years ago about role playing games.) In the article you can find interesting facts about who are the creators of facebook and even more interesting ones about who has been more than happy to finance it more recently. All is topped with a fun re-reading of facebook's "privacy policy". The second dot. This late afternoon, speaking with Ralf in the lab, I got introduced to the practice of some companies to ask for an hand-written curriculum vitae as a regular practice to be considered as a candidate. Why so? Well, because they can then ask a graphologist to draw a psychological profile and take a more "informed decision" about whether to hire you or not (assuming you believe in graphology, of course). Sure, it's illegal. But still it seems to be common practice in Japan and a not yet completely vanished practice in specific employment fields in France. The line. Guess what? Tomorrow it will become easier (and already is for all the places where the facebook penetration is sky-rocketing): instead of paying a graphologist for a (possibly inaccurate) profile, you can just pay the faceboook guys to get a record of a lot of your private life wanderings, pictures, past relationships, ... Sure, it will be illegal. But still ..., and it will be way more efficient! I'm every passing day more and more proud of having closed my facebook account more than 1 year ago (and trust me: closing a facebook account ain't easy).
Now, anyone of you can drop by on my homepage, spot a shiny linkedin logo, and call me a cheap talker. I'd concur that in a sense every social networking has bad privacy implications, but that's trivial, we all know that. Still, I think linkedin is somehow better. Why? Because it is specifically geared toward professional information. While giving information to them, I'm usually thinking about my professional "figure" and I've high barriers that are likely to inhibit me to leak personal information, or at least make me think about that. On the contrary, with facebook you have low barriers and you are encouraged to provide personal information, and that's exactly the point of the facebook owners. (And here I'm even assuming you do have some barriers while providing information to facebook, which I'm convinced is not the case for most of its users.) I see a parallel with the early days of blogs, where the euphoria of blogging made a lot of people mistaking their public blog with their personal diary; stuff which will strike back. While experienced bloggers develop defenses against the initial foolish attitude, people do not develop similar defenses on facebook, because that defenses will defeat the purpose of the network.

Petr Rockai: farewell, adept

I am quite sad to announce that I am discontinuing Adept development for good. Since Kubuntu will be changing its default manager to KPackageKit (I wish everyone involved good luck), I have no further motivation to work on Adept at all. I have mostly done the 3.0 overhaul since Jonathan Riddell is my friend, and I like to make my friends happy. However, since this is no longer a factor, and my time is likely better invested elsewhere, I am giving up altogether. Of course, if anyone steps up for maintainership, I will happily delegate Adept to them. It is in a relatively good shape these days, I hope. I will keep the source (darcs) repositories around as long as reasonably possible. If you are interested in taking over, even despite the Adept userbase declining sharply in near future, please drop me a mail. With Adept goes also libept, a more general-purpose library for working with APT. I will be around when people need me to fix it, but won t add anything on my own. I am not even sure what is Enrico s status on libept, but probably just consider libept as good as orphaned, too. On a more personal note, this closes a long (very long) chapter in my free software life. I d like to thank everyone involved with it, there have been many of you. Moreover, this apparently cuts the few remaining ties I had to KDE development community I will miss you. well, maybe one of those days UPDATE: No, this does not mean I am no longer friends with Jonathan. I don t know why, but already two people managed to read it that way. To put it in hopefully less ambiguous words: The fact that Jonathan is my friend is no longer a factor just because he does not need Adept anymore. Hope that helps.

Gunnar Wolf: 5 million breakfasts a day?

Our municipal (Coyoac n, Mexico City) government announces 5,147,000 breakfasts are served daily in the Coyoac n public schools.
Sounds great, doesn't it?
...Until you remember Coyoac n has only 628,000 inhabitants. I'd venture to say, 100,000 children in public schools can be a decent figure. So... Is the government forcing each child to eat 51 breakfasts a day?
Truth to be said: A week after the advertisement appeared, it was replaced by other, more believable figures: Over 5 million school uniforms given to the students for free. And now it mentions Distrito Federal, which contains Coyoac n - The total DF population is around 9 million people (from the ~25 million that live in the metropolitan area), say 3-4 million kids in school age, lets assume 2.5 million of them go to public schools. Two uniforms per kid. Sounds possible.

Romain Beauxis: When Rambo meets the Teletubbies..

Some recent discussions made me remember about this very nice trailer... The interesting moment is at 01:45...

Les Inconnus - J sus 2 le retour
envoy par kikkako

Tollef Fog Heen: varnishlog's poor man's filtering language

Currently, varnishlog does not support very advanced filtering. If you run it with -o, you can also do a regular expression match on tag While in Brazil, I needed something a bit more expressive. I needed something that would tell me if I had vcl_recv call pass and the URL ended in .jpg.
varnishlog -o -c   perl -ne 'BEGIN   $/ = "";  print if
(/RxURL.*jpg$/m and /VCL_call.*recv pass/);'
fixed this for me.

Russ Allbery: Asking the wrong question

I'm posting way too much to debian-vote right now, which I realize and which I'm going to try to cut back on. (I at least did start the lintian.d.o upgrade process today, so I got non-discussion Debian work done.) The reason why I keep reacting, though, is that I'm finding it frustrating that people seem to be asking the wrong question for resolving the firmware freeness argument. We currently have a strong disagreement over what the implications of the Debian Social Contract and DFSG should be for our release process. Some Debian Developers believe that releasing lenny as-is requires a special exception to the Social Contract. Some Debian Developers believe that releasing lenny as-is is consistent with the Social Contract. We've tried and failed to achieve consensus. That's the first point of my frustration: some people don't seem willing to accept that this has happened. They are apparently having a hard time understanding how anyone couldn't agree with them, and are therefore repeatedly reopening the discussion on which we don't have consensus. Once it's clear that consensus doesn't exist, this is very counter-productive. The discussion is futile, which frustrates people, and then in that frustration they become increasingly angry and harsh. Once consensus fails, all interesting decision-making processes start. A decision-making process basically reduces to "who decides?". When you have a dispute and consensus is not possible, some body has to make a decision. If people believe in the decision-making process, they can then support, or at least live with, the decision because they respect the process, even if they disagree with that particular outcome. The most important output of a decision-making process is closure: you stop debating and move on. If that doesn't happen, the decision-making process has failed, even if it makes a decision. Why does this all matter and why am I going on at such length about it? It's simply this, which I think is so important I'll highlight it:
Even people who strongly disagree on some issues can work together cordially and well in the same project provided that they can agree on a decision-making process in those areas where they disagree.
Agreeing on how decisions are made in Debian is important because that's how we continue to work together when we disagree (and we will disagree). If we can agree on how disputes are resolved, we can all respect and honor the outcome even if it isn't what we would have wanted, and then move forward. If we don't agree on how disputes are resolved, we'll keep re-arguing them rather than accepting the outcome. The discussions will get more heated, more people will get upset, and more people will not have fun working on Debian. What I've been trying to analyze on debian-vote is the "who decides" part of this question. We have a decision-making process outlined in the Debian constitution for non-technical decisions (of which this is one). That process is somewhat scattered through the document, but bringing it together in one place, it seems to go like this:
  1. Developers are empowered to make decisions about their own work. That means that, according to the constitution, the primary people who get to decide how the SC and DFSG should apply are every Debian Developer in the tasks on which they're working.
  2. The project leader can define an area of ongoing responsibility and delegate to a developer or a group of developers responsibility for making decisions in that area. There are two relevant delegations here. The ftp team has the delegated authority to determine what packages may enter Debian given, among other things, licensing and DFSG issues. The release team has the delegated authority to decide what goes into the next stable release and when that release happens. (Let's put aside quibbles over whether or not that authority was formally delegated; I think that we can all agree in practice that it's close enough.) The ftp team has accepted the relevant firmware packages into Debian main and hence have made a decision in their area of responsibility. The release team, through the lenny-ignore tag, has decided that the relevant packages can be part of the next release. Those are delegate decisions that have already been made, and neither of those teams seem to want to change their mind.
  3. The final decision-making body in this case, therefore, is the developers at large, who can override any delegate decision via a GR. That's what Robert Millan proposed, although he doesn't seem to have realized he was doing that, and it's not marked as such on the ballot.
Now that this has happened, we all vote whether or not to override the delegate decision. The only option on the ballot that does so, by my reading, is the first one, so if the first option does not win the GR, the delegate decision is not overridden and both the ftp-master and release team decisions stand. This is why Further Discussion means we continue the release as previously planned. We have a decision-making process, which has been followed, and the current decision is to release including those packages. In order to change that decision, it has to be overridden. A result of Further Discussion on a GR means that GR does nothing, and hence the decision stands. The second point of frustration is the decision that option four on the ballot (delegate to the release team the power to make decisions about how DFSG issues affect what is included in the release) needs a 3:1 majority. They have already been delegated the authority to do that as part of their delegated authority to manage the release. The effect of option four on the project is therefore identical to Further Discussion; the only difference is whether we make a positive statement or fail to make a negative statement. It makes no sense to treat it as supersession of a foundation document when it just supports the existing decision-making process in the constitution. A third point of frustration is the apparent feeling that foundation documents like the DFSG are outside of the normal decision-making process described in the constitution. I can find no evidence of this in the constitution, but more fundamentally, the people arguing this are not stating what decision-making process they believe does apply other than "my view of the DFSG is obviously the only reasonable one and hence you should follow it." This reduces to a plea for consensus, which we've already established that we don't have, and hence, as mentioned above, is horribly unproductive to keep raising. There will never be a policy document that is so clear that everyone will agree on its implications in every situation. I find it much more useful to analyze governance processes by looking at who decides disputes rather than looking at position statements. The decision-making process is what will determine the outcome of all the really interesting cases.

16 December 2008

Biella Coleman: If Programming Languages Were Religions and What is Up with Ruby on Rails?

I am sure this is making the rounds but this seems like an appropriate place for this list: If Programming Languages Were Religions. My favorite description:
Lisp would be Zen Buddhism - There is no syntax, there is no centralization of dogma, there are no deities to worship. The entire universe is there at your reach - if only you are enlightened enough to grasp it. Some say that it s not a language at all; others say that it s the only language that makes sense.
Speaking of computer languages and projects and religious holy wars, in the last few weeks I have been totally intrigued by the culture being built by the Ruby on Rails guys. As a researcher of Free and Open Source Software, I, like others, actually tend to see the similarities more than the difference between these two poles (in part because I focus on practice, not on the purist ideologies or two ideologues, you know who I am taking about) but it seems to me -and I could be wrong here but I suspect I am not -that Ruby on Rails is producing a unique Open Source culture, one that really diverges from some of the core principles of Free Software, much more so than other Open Source projects like Apache. The rail guys as I have heard, are Open Source evangelists of a certain stripe, who are quite cultish (you know, it is weird if you don t use github, a Mac, TextMate). What do you think of Ruby on Rails? Are the attacks fair? Are they a bunch of douchebags, as this (very incisive) post argues? Is it where Open Source meets and marries, for better or for worse, the Web 2.0 craze? If I could clone me, this is definitely one line of research, I would love to dive into right now but since I can t, your opinions would be greatly appreciated.

John Goerzen: Wiki Software

I used to run a website for traveling by rail in the United States. I let it falter, and eventually took it down. But I still have the domain, and am working to bring it back as a wiki. The first step in that process was selecting which wiki software to use. I have a few requirements for the site: I m frustrated that there is no wiki out there that does all of these. There are quite a few that do all but one, but which one they omit varies. My two finalists were MoinMoin and MediaWiki. MoinMoin MoinMoin will let you easily define arbitrary categories (by creating a wiki page following a certain name). The search screen automatically presents checkboxes for restricting searches to a particular category. Some reviews have complained about its anti-spam features, but they are all talking about older versions and they seem to have done some work on this lately. MoinMoin has tons of features and is easy to set up and maintain. But here s where it falls down: themes. Over at moinmo.in, there is a theme market for themes. Only most of the themes there haven t been compatible with the current MoinMoin release since about 2005. Most of the rest have one download, then a long discussion page full of mixed bug reports, diffs, and non-diff edit this to make it work comments. Most of these don t state what version of the theme they apply to. Most themes won t work with current browsers and Moin releases without them. UGH. After discussing on #moin, I ll probably go in there and at least organize the ThemeMarket page by release. MediaWiki Then there s MediaWiki. It s got a lot of features, and a lot of complexity. It has no current WYSIWYG feature, though apparently there is work on one. MediaWiki has an amazing category system. It can generate sorted lists of pages in a category, supports subcategories, etc. Surprisingly, though, you can t search in just one category. (Though it might be possible indirectly via some syntax; not sure.) Searching in MediaWiki overall is less capable that in MoinMoin. MediaWiki does offer namespaces, and namespaces are the sole way of searching just one part of a site. They re used well over at, say, uesp.net. But namespaces are heavy-handed. You have to edit config files to define them, and they bring with them other associated namespaces for discussion and whatnot. It s not as easy as creating a category in MoinMoin, and might not scale well to lots of future categories. MediaWiki does appear to have good spam prevention, and support recaptcha. Conclusions I eventually selected MoinMoin and have set up most of my content in it. But now that I am to the point of selecting themes, I m having some second thoughts. I also looked at DokuWiki. Its design makes me nervous. The user list is stored in a single file. You can t search by category. You can search by namespace, but there aren t checkboxes for it in the search screen; you have to know the syntax. WYSIWYG is a plugin. Categories are a plugin. So too many plugins to maintain, and no real features above MoinMoin.

Joerg Jaspert: dinstall runtime

I just added a script from Thomas Viehmann to our dak repository to create a few graphic files out of our dinstall cronjob. We now have (click the graph for the full size version) These images are now updated at the end of each dinstall run, showing the last 20 runs. Now, if you are an R expert and want to make the graphs look nicer, we always love to get patches. Our git repository is at https://ftp-master.debian.org/git/dak.git/ and you want to look into tools/logs.py,pretty much at the end of the file. (If you dislike git, a copy of the file is available here, and our data input file is also available. You just need to modify the header of the script, changing the path entries and can start playing. :) Yes, at the time of writing this post the two first entries look a little odd. Thats known. Ignore. Thanks.

Pablo Lorenzzoni: Lenny in the Asus EEE PC 901 - day 1

Following my previous post, today I began to turn my brand new Asus EEE PC 901 into a Debian Machine. At first I wanted to do all in one day, but since work is taking too much out of me (and everything seems to take more time than expected), I ll have to split this in different days So, first things first. I read Debian Wiki on the issue and began by doing the most important: backing it up. So I got a daily netinst iso, put it on a USB Pendrive and followed the tip on backup over the network using netcat. Easy and effective, and took only 8 minutes on the 901 (I think the 35 minutes described on the wiki were for models with slower NICs). From there, I had to decide which version of the installer I d use. I chose Standard, since I want an encrypted disk on my EEE. So I run the installer and, on the partition manager, I deleted /dev/sda1 (where Xandros was installed), turning it into a 300 MB /dev/sda5 (to use as /boot) and a 3 GB /dev/sda6 building a Logical Volume over an LVM Volume Group with it and /dev/sdb1 (where the user directory was), and enciphering it. This took a long time, since, I believe, random data were being written to the device to increase crypto strength. I left /dev/sda 2,3,4 as they were, since they can belong to the Asus EEE Recovering System (and they don t take too much space :-) ) Now base system is installed, and wired network works like a charm Next steps will have to wait until tomorrow.

Riku Voipio: re: how many bugs have you fixed today?

Sorry Bastian, but that marthyrdon thing doesn't work. Debian has no shortage of talkers, GR-proposers, etc. We have shortage of people of actually doing stuff. Therefor it's only fair that people not bothering fixing bugs get criticized too. And not to mention that there is enough RC bugs open that you could *easily* fix one of them before making another blog post.

This post has been brought to you by fixing #508781 and #496104. (Can I has a meme plz?)

ps, that said, pretending reaching 0 RC bugs means we have a perfect release is delusional. Bugs are found at constant rate. If we fixed bugs faster and reached 0 RC bugs a month a go, the released lenny would now have all the RC bugs found during this month. Therefor it would make much more sense to align the release schedule based on something else, such as d-i schedule and fix any RC bugs left at that point with stable release updates. update: As noted by Dato, the release update essentially says the same.

David Welton: Tcl -= Ousterhout

It's not really "news" that Dr. John Ousterhout is no longer the Tcl leader, that happened years ago, but it's finally been formalized: http://groups.google.com/group/comp.lang.tcl/browse_thread/thread/99e2693293b3c945/f4932ae01d74f8e1#f4932ae01d74f8e1 And people at large have taken notice, something that doesn't happen with Tcl very often. What I think is actually interesting about it is to consider the governance models for various programming languages. It seems that Tcl is something of an exception to the "benevolent dictator" model prevalent in the world of scripting languages. Python still uses this, with Guido van Rossum being the "BDFL", or Benevolent Dictator For Life). Perl used to, with Larry Wall, although I'm not up to date on what they do now. Ruby has Yukihiro "Matz" Matsumoto. The really big, established, popular languages like C, C++ and Java have committees that run them, although even there, the original development was often by small teams or individuals. What about other languages, like Lua, Erlang, Scala, Clojure, Haskell, OCaml, and so on and so forth? Which governance model is in use? How does it help or hinder the language's growth and adoption?

David Welton: Tcl -= Ousterhout

It's not really "news" that Dr. John Ousterhout is no longer the Tcl leader, that happened years ago, but it's finally been formalized: http://groups.google.com/group/comp.lang.tcl/browse_thread/thread/99e2693293b3c945/f4932ae01d74f8e1#f4932ae01d74f8e1 And people at large have taken notice, something that doesn't happen with Tcl very often. What I think is actually interesting about it is to consider the governance models for various programming languages. It seems that Tcl is something of an exception to the "benevolent dictator" model prevalent in the world of scripting languages. Python still uses this, with Guido van Rossum being the "BDFL", or Benevolent Dictator For Life). Perl used to, with Larry Wall, although I'm not up to date on what they do now. Ruby has Yukihiro "Matz" Matsumoto. The really big, established, popular languages like C, C++ and Java have committees that run them, although even there, the original development was often by small teams or individuals. What about other languages, like Lua, Erlang, Scala, Clojure, Haskell, OCaml, and so on and so forth? Which governance model is in use? How does it help or hinder the language's growth and adoption?

Neil Williams: Emdebian Grip - Debian, only 25% smaller

I'm pleased to make Emdebian Grip unstable available - a smaller, binary-compatible, Debian without manpages, without unwanted translation files (uses Emdebian TDebs) and without package documentation. The current packages will be migrated into Emdebian Grip testing in due course and then be released alongside Lenny.
Emdebian now has two flavours with Grip taking the intermediate position in terms of size whilst retaining full compatibility with Debian. Grip "cherry-picks" packages from Debian but retains the unchanged Debian sources - the main binary and library packages will exist but -dev, -doc and -dbg packages may well be missing, as well as some of the more unusual OR dependencies).
I've just converted my Acer Aspire1 (i386) - running XFCE - from Debian Lenny to Emdebian Grip:
607 upgraded, 1 newly installed, 2 to remove and 0 not upgraded.
Need to get 184MB of archives.
After this operation, 278MB disk space will be freed.

Yes, update 600 packages and have nearly 300Mb more free space - that's a 400Kb space saving per package, on average. Gaining 90Mb more free space than the total size of the download is nice too. Comparisons are after using 'sudo apt-get clean' to remove downloaded archives:
Debian Lenny:
/dev/sda1 7.1G 1.2G 5.6G 17% /
Emdebian Grip (unstable)
/dev/sda1 7.1G 919M 5.8G 14% /

I make that about 25% smaller and not all packages installed on the machine have been "gripped" - (about 100 remain, many of which I should probably remove anyway).
Method: See http://www.emdebian.org/grip/index.html.
Add the Grip source to /etc/apt/sources.list.d/
deb http://buildd.emdebian.org/grip/ unstable main
$ sudo apt-get update
$ sudo apt-get install grip-config

This is a very important stage - Emdebian Grip is still in development and with the Lenny freeze, a few wrappers and helpers are needed to allow smooth migrations between Debian and Emdebian - grip-config is Architecture:all and contains the relevant scripts. (grip-config is Priority: required so debootstrap picks it up by default - this also means that grip-config cannot be part of Debian.) grip-config also includes the same key as the emdebian-archive-keyring package used by all Emdebian repositories.
Only after grip-config is installed should you use:
$ sudo apt-get dist-upgrade
Note that this is a complete replacement, including libc6, apt, coreutils, dpkg and (on i386) the stock kernel. As such, it can take a while to complete the installation once the download is complete. (As ever, if the kernel is updated, ensure you reboot before you next suspend to disk - even the minimal "gripping" changes to the kernel package may confuse grub when deciding whether to use the suspended image.)
A few packages are currently behind Debian Sid (notably ncurses) and I'm working on the scripts to enable full update automation.
One other problem is that /usr/share/locale/locale.alias has also disappeared which compromises localisation support right now but that's fairly easy to fix. (langupdate is also missing so there is no effective localisation support right now - I need to cross-build langupdate for the grip architectures.)
Note that this test install adds the Emdebian Grip repository to the existing Debian sources and relies on the em[0-9] version suffix to implement the upgrade - packages that are behind Debian get left at the Debian versions, you can also use normal pinning.
$ apt-cache policy
Package files:
100 /var/lib/dpkg/status
release a=now
500 http://buildd.emdebian.org unstable/main Packages
release v=0.1,o=Debian,a=sid,l=EmdebianGrip,c=main
origin buildd.emdebian.org
500 http://ftp.uk.debian.org sid/main Packages
release o=Debian,a=unstable,l=Debian,c=main
origin ftp.uk.debian.org
Pinned packages:

I've done some testing with debootstrap and a chroot works too - it should be possible to ally these packages with the normal Debian installer because there is no point "gripping" udebs that are already v.small and the packages that actually get installed are dictated by your choice of mirror. debian-live should be gaining support for Emdebian Grip in due course.
If someone fancies trying a test installation by choosing http://buildd.emdebian.org/grip as their mirror in d-i, let me know. ;-)
(Installing Grip is likely to result in further size gains as the Grip repository data does not support Recommends, so you don't have to try and get d-i to not use recommended packages).
Emdebian Grip (unstable) is now available for 7 architectures:
i386, amd64, arm, armel, mips, mipsel and powerpc.
(amd64 is only supported for debugging purposes, most of my development machines are amd64.)
Please report any and all bugs to the buildd.emdebian.org pseudo-package in the Debian BTS.
If you want more packages added, set up a Debian machine or chroot with all the packages you need (and only the ones you need) and send the
complete output of 'dpkg --get-selections' to the debian-embedded mailing list. Alternatively, file RFP bugs against buildd.emdebian.org at wishlist severity.
To see the current list of packages, use the search support
Headline packages:
coreutils, perl, python, apt, dpkg, grip-config, XFCE, debhelper, make, devscripts, sylpheed, iceweasel, drivel, xchat-gnome, gpe-tetris,
totem-gstreamer, liferea, thunar, evince, seahorse, gthumb, libsqlite3, pilot-link, python-gnome2, lua, tcl, gcc-4.3, binutils, libmysqlclient15off.
Currently, very few -dev packages exist in Grip. I'll make the emdebian-grip package available on Grip itself in due course so that new and bespoke packages can also be "gripped".
I'm migrating the current packages to Emdebian Grip testing soon and I'll be making a release of Emdebian Grip 1.0 (based on Debian 5.0 "Lenny") as well as Emdebian Crush 1.0 (based on Debian 5.0 "Lenny"), alongside the main Lenny release.
Finally, note that Grip is binary compatible with Debian - indeed, the binaries themselves are untouched - but bugs that appear in Emdebian Grip must only be filed against the buildd.emdebian.org pseudo-package. Right now, reportbug is not part of Emdebian Grip because I need a way of telling reportbug to only use the pseudo-package.
The main usability improvements will come in the development of Emdebian 2.0 (based on Debian 6.0 "Squeeze") - please consider Emdebian 1.0 as a "developer release", think back to what things were like with Slackware 1.0 or Debian buzz, rex or bo.
P.S. there is no concept of a release-critical bug in Emdebian Grip (at least, not yet) - the 1.0 release will happen as soon as Grip testing is in sync with the released Lenny (no matter what). Please do not file any bugs against buildd.emdebian.org with higher severity than important, it will just annoy people trying to fix RC bugs in Lenny.
If you are a maintainer in Debian and you inadvertently receive a bug report listed as 'found' in a version that ends in em[0-9], please reassign to buildd.emdebian.org, at severity no higher than important. Thanks.

Next.

Previous.