Search Results: "ag"

7 May 2009

Biella Coleman: Make our words glisten



glisten vs hardened words, originally uploaded by the biella.
Now that I am (thankfully) done teaching until September, I have time to devour two small mountains of readings that I need to finish before I return to my manuscript, which I will be working on, I hope uber-productively, all summer long. One pile of readings deals with coding, open source, and the commons, such as Scott Rosenberg s Dreaming in Code and David Bollier s Viral Spiral. Another pile of reading edges toward the theoretical side of things, having to do with craft, pleasure, and humor, since it is pleasure in its many many many guises from from the calm feeling of self-satisfaction that underlies pride in one s craft, to the more sublime feeling of ecstatic bliss that powers many creative sprints. If one entertains pleasure, one must also entertain its darker side, for all of this feel good stuff is nonetheless often springs forth from a deep sea of passionate frustration. This seems to be the driving theme of Dreaming in Code and it is also what animates Ellen Ullman s fictional account of pure frustration, The Bug. I am quite fond of native expressions of geek frustration and recently was provided with an exquisite example a rant against the Adobe PSD format. The author of Xee, A light-weight, fast and convenient image viewer for Mac OS X explained his utter contempt for the Adobe PSD in the following way:
At this point, I d like to take a moment to speak to you about the Adobe PSD format. PSD is not a good format. PSD is not even a bad format. Calling it such would be an insult to other bad formats, such as PCX or JPEG. No, PSD is an abysmal format. Having worked on this code for several weeks now, my hate for PSD has grown to a raging fire that burns with the fierce passion of a million suns. If there are two different ways of doing something, PSD will do both, in different places. It will then make up three more ways no sane human would think of, and do those too. PSD makes inconsistency an art form. Why, for instance, did it suddenly decide that *these* particular chunks should be aligned to four bytes, and that this alignement should *not* be included in the size? Other chunks in other places are either unaligned, or aligned with the alignment included in the size. Here, though, it is not included. Were it within my power, I would gather every single copy of those specs, and launch them on a spaceship directly into the sun.
Even if this account represents unadulterated irritation, he leaves us, the reader, with nothing of the irritation, only pleasure. This aftermath of frustration is delivered through the vehicle of humor, which within the hacker context, is the cultural container that best captures the spirit of hacker pleasure or so I will be arguing. Like many humorous rants from the world of hacking (and please send me any others you know of), this text dances with liveliness; it exudes its own rhythm; it glistens to use Ronald Barthes apt phrasing from his short book The Pleasure of Text, which I just finished as part of my theoretical escape into the pleasure-dome. Although there are parts of his book which are to be frank, *really* *not* *pleasurable*, partly due to obscure references to High French Theory, which elide even an academic pair of eyes, the book generally pleases. And one of the most pleasing chunks is his definition of a stereotype:
The stereotype is the word repeated without any magic, any enthusiasm, as though it were natural, as though by some miracle this recurring words were adequate on each occasion for different reasons, as though to imitate could no longer be sensed as an imitation: an unconstrained word that claims consistency and is unaware of its own insistence
In contrast to the stereotype, a string of words that enchants does so by slipping off the page to hit you squarely in the heart or the gut. Unfortunately, while academic writing steers clear of stereotypes, often trying to present the detailed singularity of a phenomena (even when conditioned by social forces), it does not exactly glisten, though there are a handful of exceptions. I think we need more texts that glisten, even if only during sections or parts of our books and articles (much like the rant helped enliven the more staid technical document). In recent years, in large part due to the influence of free software, there has been an explosion, a move toward going open access. All of this is laudable and I fully embrace it (and have gotten into some small battles over it). But without an aesthetic politics that values pleasure in reading and writing we are doomed to obscurity anyway. A move toward making our knowledge public also required a move toward thinking about the literary aesthetics of pleasure.

Pablo Lorenzzoni: Another small victory - don't relax just yet

Months (even years) of activism, over 140 thousand signatures, and finally another small victory: Brazilian Minister of Justice Mr. Tarso Genro sent a letter [pt-BR] stating that Sen. Azeredo s bill is dangerous, and that the Ministry is working in an alternative (among other things). We had already incited a public hearing that were very fruitful [pt-BR] and might have brought the Ministry to the issue. But don t relax just yet, folks! Right now, working in this alternative , are people with every kind of agenda It s safe to assume that some of them are from the same lobby that pushed Sen. Azeredo first version of the thing. So, yes, this was another victory, but nothing really changed The bill is still approved by the Senate and still has to be reviewed by the Chamber-of-Deputies, and the alternative that will be presented by the Ministry is still under construction. What we accomplished is nothing more than making the Minister aware of the issue So, keep the pressure over your representatives, send messages to the Ministry, stating how you feel about the issue! Let s show them what we want them to do After all, that s why we elected them, in the first place, isn t it? [Published also at Trezentos, in portuguese]

Jaldhar Vyas: Shaka, When the Firewall Fell

Debra and Ian at Tanagra. The Source. The Source at Yahoo. Jaldhar and the Source at Tanagra. Torvalds under two moons, his sky is grey. Git, his arms wide. Jaldhar of Tanagra, Git of Torvalds, at Lungha. Jaldhar and Git in court. The court of silence. Jaldhar, his eyes closed. #debian-devel, its arms wide, its thighs fat. Jaldhar, his eyes open! The Source in Git, its sails unfurled. Update: From Barak A. Pearlmutter who doesn't have a blog.
JOIN US, AS GNULIB HAS.
THERE IS NOTHING TO FEAR.
SUSPEND YOUR DOUBTS.
SUBMIT TO THE GIT.OR.CZ SUPERIORITY.
YOUR REPOSITORY WILL BE CONVERTED.
COMPLEXITY IS BLISS.
ALL CODE WILL BE REPLICATED.
ALL BRANCHES SERVE THE CONSENSUALITY.
YOUR INDIVIDUALITY WILL BE A
TREASURED ASSET OF THE GITHUB.

Joey Hess: passing mp3s from firefox to mpd

I have finally figured out how to make clicking on a mp3 link in firefox cause the url to be instantly passed to mpd and played. If this seems like it should be easy, think again.. Firefox makes it hard, because while it lets you configure an program to run for a mp3, if the mp3 is not streamed, it will first download the whole mp3, and then run your program, passing it the local file. That's not what we want: It's slow, and it's much easier to queue an url in mpd than a new file. The trick to making it work is an addon called MediaPlayerConnectivity. Confusingly, this addon sometimes refers to itself as "MPC" -- not to be confused with "mpc(1)". Warning: This addon is a ugly mess that wants to do a lot of other stuff than play mp3s, so make sure to disable all that. MediaPlayerConnectivity's preferences allows you to specify a command to run for mp3 files (but annoyingly, not ogg vorbis). This command will be passed the url to the mp3. So you need to write a little script that runs mpc add and starts the queued url playing. My take on that is mpqueue, which uses the mpinsert command from mpdtoys to add the url just after the currently playing song in the playlist. Then it uses mpc next to skip to it. This way, after whatever you clicked on finishes playing, mpd continues with whatever was next in your playlist, and the music never stops. BTW, since I use a mpd proxy this is all done on whatever remote mpd the proxy is currently set to use, rather than my laptop. Clicking on a link and having the sound system in the next room switch to playing it is pretty nice. :) Previously: My mpd setup

Adrian von Bidder: Why Public Health-Care is Difficult

A reply to Tore, who is probably partly wrong. I don't claim the U.S. system is good or bad, I don't know it. But I don't think public (which he seems to imply means free) health care is as easy as he suggests. I'm starting at his assertion that
Very few people break their legs intentionally to stay at a nice hospital. [Health care] is not a resource likely to be wasted once people are given free access to it.
The case of a broken leg is easy. What about chronic illnesses, especially those difficult to diagnose (some kinds of back pain, psychological problems, ...)? What about bored old people who spend their days talking to doctors about how bad getting older is? Easily available (cheap or free) health care has lead to hospitals being swamped with people with minor issues to the point where people with serious problems died because hospital staff didn't get to them in time. And, because the state's budget is not infinite, hospitals become badly run institutions with always-overworked staff leading to even fewer people wanting to work there etc. This has happened in the UK, for example (I think the system I have been reading about ages ago has since been replaced by a different one.) Switzerland doesn't have this problem (to this extent) because we really care about (this means, here: throw money at) our health system, but the result is that the mandatory health insurance becomes insanely expensive. There is talk about half the population needing state subsidies to pay for their health insurance within the next few years. Which, of course, will just move the cost from the whole population (via mandatory health insurance) to the whole population (via taxes) so I don't quite see the point... You'll note I don't propose solutions either. But I think it's important to acknowledge that health care is a difficult topic because, in the end, it always comes down to the question How much money should be spent on this person's illness? which is a very, very bad question. We try to sidestep it by only taking about statistics etc., but no matter how you look at it, you either do 20'000 per week medications for 80 year old patients who will die soon anyway and get a system society can't pay, or you don't and you get a system where the rich are better off than the poor. Or you delegate the decision to the doctor or the insurance or ... and try to minimize the number of people who deserve (can you see it, the hard question didn't get away!) treatment but don't get it. Update 20090508 - Response to comments I'd like to thank you for commenting. I didn't know (and sorry about that didn't care to research) that the U.S. system is even more expensive than ours, since my main message is just that health care is about hard decisions. Some people always will be left out. Elaborating a bit on the 20'000 a week medication: partly, I agree with Adrian and Tore: patent-supported monopolies on medication plays a part. Partly, because I stipulate there will always be rare illnesses where a few cases per year worldwide will have to pay for all the research and production of the medication. Of course, the cost can be distributed so that the patient (or his insurance) doesn't have to pay it, but society as a whole will still pay. So the hard question won't go away easily, now it's just become Do we fund research for this rare illness with fewer than five cases per year worldwide? Of course, now we're not speaking of people anymore, but already just of cases, and we're not cutting treatment for an actual person but we're just cutting budget on research, so it may be easier on the conscience, but it's still fundamentally the same question. Conclusion? Health-care will always be a difficult topic, and it will never be free. The cost can just be distributed in different ways.

Ian Wienand: Quickly describing hash utilisation

I think the most correct way to describe utilisation of a hash-table is using chi-squared distributions and hypothesis and degrees of freedom and a bunch of other things nobody but an actuary remembers. So I was looking for a quick method that was close-enough but didn't require digging out a statistics text-book. I'm sure I've re-invented some well-known measurement, but I'm not sure what it is. The idea is to add up the total steps required to look-up all elements in the hash-table, and compare that to the theoretical ideal of a uniformly balanced hash-table. You can then get a ratio that tells you if you're in the ball-park, or if you should try something else. A diagram should suffice. Scheme for acquiring a hash-utilisation ratio This seems to give quite useful results with a bare minimum of effort, and most importantly no tricky floating point math. For example, on the standard Unix words with a 2048 entry hash-table, the standard DJB hash came out very well (as expected)
Ideal 2408448
Actual 2473833
----
Ratio 0.973569
To contrast, a simple "add each character" type hash:
Ideal 2408448
Actual 6367489
----
Ratio 0.378241
Example code is hash-ratio.py. I expect this measurement is most useful when you have a largely static bunch of data for which you are attempting to choose an appropriate hash-function. I guess if you are really trying to hash more or less random incoming data and hence only have a random sample to work with, you can't avoid doing the "real" statistics.

Robert Collins: 7 May 2009

My desktop machine blew up, so I got a lovely fresh install of Jaunty. And, X and Gnome still disagreed by default about my actual screeen size... it was unreadably small with the default fonts. I've posted the following instructions before - these are basically unchanged except that the location of the fonts dialog has moved. Tip for folk that would like X to show fonts (i.e. the GDM log in screen) in the correct size: Teach X about the dpi setting! Step 1: run xdpyinfo and look for the dimensions: line. There will be something like this: dimensions: 1280x768 pixels (266x161 millimeters) resolution: 122x121 dots per inch Grab a ruler and measure the screen you have. If it matches the millimeters reported by X, then skip step 2. Step 2: edit /etc/X11/xorg.conf, and locate your Monitor section: Section "Monitor" Identifier "Generic Monitor" Option "DPMS" DisplaySize 265 160 EndSection Add in a DisplaySize like I have there. Now logout of your GUI and restart X - you can run /etc/init.d/ g,k dm restart from the console, or do what I do - just hit ctrl-alt-bkspace so it restarts. Your login screen should change appearance slightly - either the fonts and regions will get bigger if your dpi was set too low, or vice verca. Step 3: (For KDE users, someone please tell me what it should be, for GNOME read on)... Run xdpyinfo again and find the Resolution: line. Ignore the fact that it may not be square, grab one of the two numbers ( I suggest the higher).. Go to System, Preferences, Appearance, and the Font tab. Select 'Details'. There is a Resolution field there. Put in the single number you chose. Changes should take effect immediately. Applications I know of which benefit from having this set correctly: xpdf, gnome-* (panels are readable etc etc), firefox.

Joey Hess: sha-1

So, sha-1 is looking increasingly insecure in applications where birthday attacks are possible. ("Birthday attacks" ... what a phrase ... I hope my non-technical readers stopped at "sha-1".) Two things about that:
First, I wanted to mention that I've today released jetring 0.15, which adds support for arbitrary hashes in the index file, and deprecates use of sha-1, going to sha-256 by default. There is a jetring-checksum -u utility that can be used to upgrade sha-1 hashes in existing jetring index files. If you're using jetring in an application where changesets are provided by third paries, then a birthday attack could be possible (though not easy?), and you should upgrade your index. debian-maintainer is a good example of such a jetring user.
Secondly, our beloved git uses sha-1, and this seems unlikely to change soon or without significant pain. So, what kinds of collision attacks would you need to watch out for when using git? Here is a real-world example I've been pondering. Is it accurate? Here's a different scenario.. This seems more plausible. This sort of attack is easy to accomplish with a subversion repository, and was one of the reasons I was glad to switch to git, since its checksums and signed tags seemed to prevent this kind of mischief. So, worrying, especially if your project uses such a build server. Update: Thanks to the commenters for helping me correct my example. (I hope!)

6 May 2009

Tiago Bortoletto Vaz: Homage to Augusto Boal


The 9 may, 2009 at 20:00 UTC, the Center of The Theater of the Oppressed in Rio de Janeiro will pay homage to Augusto Boal. There will be a live video and audio streaming available at: http://aovivo.pontaodaeco.org:8000/homenagemboal.ogg.m3u It s recommended using the free software VLC to watch it: http://www.videolan.org/vlc/ There will also be an IRC chat room open for everyone in FreeNode, channel #homenagemboal. Posted in english Tagged: augusto boal, theater, theater of the oppressed

David Welton: Improving github?

I've written several articles (*) lately that are, if not exactly critical of github, certainly question some of the community dynamics that have sprung up around it. I'm not the only one: http://www.cubiclemuses.com/cm/articles/2009/04/28/a-community-of-rockstars/ However, I think the Github guys have actually done really great work, and done some cool stuff. And I think - and hope - that they're here to stay, so instead of focusing on what's not quite right about it, I thought I'd toss out some ideas on how it could be fixed. Some of them may not be great, but hey, that's what you get for free - go ahead and throw out your own ideas too.
  • When you clone a project, it's techncially a "fork", but it's not necessarily a fork in the real open source sense of "ok, I think I'm better able to develop this code, so I'm going my own way", ala xemacs or x.org, or the bsd's splitting apart. It might be nice if github gave people the means to indicate what sort of fork they're creating - if it's just a place to play with and publish some code, or if they think their code should be the one others reference.
  • Perhaps it should be optional to copy the wiki and issues tabs on your new fork. If you're not really aiming to supplant the main project, do you really need those? You might need the issue tracker.
  • It might be an interesting experiment to let people vote on which one is the main project. Forkers could also indicate which one they want to keep working with as the main branch and maintainer.
  • Perhaps github could add some visual encouragement for people to send their patches on to the main branch of a given project.
Anyway, just a few ideas off the top of my head. (*)

Ingo Juergensmann: Fixing RAID Issues

Well, yesterday I wrote about a looping RAID1 rebuild:

Usually I would wait for the rebuild to be finished and asking the hosting provider to replace the second disk (sdb), but as the medium error causes just another rebuild process, this won't work for obvious reasons. So, the next plan is to fail the drive sdb and get a replacement disk then. Hopefully the first disk won't fail as well then... but well, Murphy, Backup, stuff... sigh


Speaking of Murphy... it happened, of course, as it had to happen. I failed one of the drives of one of the RAIDs, did a pvmove to move all data from one RAID1 device to another and ... then Murphy came along! The machine hang after I went to bed late in the night.

The next morning greeted me with a instant messenger notice from my coworker that the disks stopped working and he rebooted the machine. From the rescue system one could see SMART errors on both disks, so replacing one disk and then the other wouldn't have worked. Sadly the hosting provider requested 69.- for a temporary third disks. So we went right away with backupping the data from the still working RAID and LVM, then requested the replacement disks and restored the machine from scratch.

Now the machine is back and working normally again. pheeew

Tore S. Bekkedal: Why public health care is a no-brainer to me

I m a social democrat/democratic socialist, and I m baffled by the health care system in the United States. I thought I d jot down/brain dump my main arguments for public health care: Everyone needs health care, but nobody seeks it out
Health care is a necessity in unpleasant circumstances. When you break your leg, you need health care. Very few people break their legs intentionally to stay at a nice hospital. Therefore, it is not a resource likely to be wasted once people are given free access to it. Given that everyone needs it when they need it and don t when they don t, paying it via the state budget is unlikely to cause waste.
Hospitals become badly run when run for profit
I think the point of motivation from the objective self-interest is overstated and harmfully over-emphasized, but the point bears making. For-profit hospitals are run for profit. Fancy that. A for-profit institution has an interest in your using their services as much as possible, at the expense of who-ever is paying the bill, be it your health insurance, or your fifth mortgage. A public institution wants to get you out of the system as soon as possible - by curing you. So the self-interest of the patient aligns much better with a public hospital. Although a certain measure of inefficiency is added when run by a governmental organization, I believe the inefficiency induced by the hospital s profit motive is probably much greater, perhaps more so in countries without a corporate culture in the government that seems to accept ineptitude. Close enough for government work is *not* a phrase used in Norway - for a reason. (Nevertheless, it bears mentioning that the most efficently-run hospital in the United States is the government-run Veteran s Aid.)
Denying health care to people who need it is not nice
The justification that a system has to be that way for the greater good is dangerous and bad and wrong. People needing health care should have it under all circumstances, and I consider it a matter of elementary respect for the dignity of human life that health care should be a right of citizenship. What kind of society measures the worth of a human being by the size of their wallet?
Healthy people are more productive
If you re the bean-counter sort, this point may appeal to you. I don t think it very relevant, but it seems quite plausible. The societal cost of people calling in sick is probably greater than any potential cost in efficiency from nationalization.
One point specific to the US: The current implementation in the US is, AFAICT, deeply flawed and needs Change (WCBI) anyway.
The US health care system is insanely flawed. It needs to change anyway - why not do so with a bang rather than a whimper. I think that the Democratic resurgency has given the party a mandate for quite a lot of bang. When a president wins on a single word, change , then go change things.
Got any more points? Disagree? I d love a conversation in the comments.

Gunnar Wolf: I D.F.

I   D.F.
...Just going out of almost two weeks of reclusion due to the porcine^W human^W atypical^W new-and-yet-unnamed AH1N1 influenza. The streets are still mostly deserted, but at least we are allowed back into our workplaces.

MJ Ray: Koha IRC General Meeting

There will be a general meeting on the #koha IRC channel on Wednesday, 6 May 2009 at 19:00 UTC with a nominal finish time of 21:00. To convert to your timezone, try date -d @1241636400 (thanks to SPI (Joerg?) for that idea). The meeting will include Koha 3.2/tip status and timeline, Koha 3.0.x status, Koha bugs database, KohaCon 2009 report. The full agenda is on the wiki. Connection details are shown on the wiki front page but are basically irc://irc.katipo.co.nz:6667/#koha Hope to see you there, or a summary should be linked from the comments here later.

Wouter Verhelst: 0x1f

Yes, exactly a year from now, I'l again be able to say I'm 20 years old. 0x20, that is.

Jan Hauke Rahm: irssi rulez

It s done all messages are now running through my fancy IRC client named irssi. What messages you ask? Well, there is all IRC traffic obviously, then all jabber contacts, and all ICQ/AIM contacts and woohoo thanks to twirssi I now even have my identi.ca (or Twitter if you re brave enough) feeds in an irssi window (from which I can also update my identi.ca stuff, of course). Isn t that great?

Daniel Kahn Gillmor: HOWTO prep for migration off of SHA-1 in OpenPGP

Last week at eurocrypt, a small group of researchers announced a fairly serious attack against the SHA-1 digest algorithm, which is used in many cryptosystems, including OpenPGP. The general consensus is that we should be moving in an orderly fashion toward the theater exits, deprecating SHA-1 where possible with an eye toward abandoning it soon (one point of reference: US gov't federal agencies have been directed to cease all reliance on SHA-1 by the end of 2010, and this directive was issued before the latest results). Since Debian relies heavily on OpenPGP and other cryptographic infrastructure, i'll be blogging about how Debian users can responsibly and carefully migrate toward better digests. This post focuses on some first steps for users of gpg, and for Debian Developers and Debian Maintainers in particular. The good news is that gpg and gpg2 both support digest algorithms from the stronger SHA-2 family: SHA512, SHA384, SHA256, and SHA224. By using these stronger digest algorithms some of your signatures may be un-readable by users of older software. However, gpg and PGP (a proprietary implementation) have both had support for at least SHA256 for well over 5 years. Debian's gnupg packages have supported the full SHA-2 family since sarge. However, most existing signatures in today's Web of Trust were made over the SHA-1 digest algorithm, which means that abandoning it immediately would cause the Web of Trust as we know it to evaporate. So we need to rely on SHA-1-based signatures until a reasonably-fleshed-out Web of Trust based on stronger digests is in place. Since we don't want to have to rely on SHA-1 for too much longer, we need to collectively start the transition now. So what can you do to help facilitate the move away from SHA-1? I'll outline three steps that current gpg users can do today, and then i'll walk through how to do each one: The first two are simple, quick, and painless actions. You'll be done with them in minutes! The third is tougher, and while you can start it today, key transitions take a little bit of time to complete. Read on for a HOWTO! This entry has been truncated read the full entry.Tags: cryptography, openpgp, security, sha1, tip

5 May 2009

Ingo Juergensmann: Non-Stop re-syncing RAID1

Ok, since a few days there is always the same going on on one of the companies (hosted) servers: the RAID1 syncs in a loop because a medium error always happen during the rebuild progress:

May 5 21:55:28 spion29 kernel: [2339524.778339] md: md2: recovery done.
May 5 21:55:28 spion29 mdadm: RebuildFinished event detected on md device /dev/md2, component device mismatches found: 512
May 5 21:55:30 spion29 kernel: [2339526.287680] RAID1 conf printout:
May 5 21:55:30 spion29 kernel: [2339526.287702] --- wd:1 rd:2
May 5 21:55:30 spion29 kernel: [2339526.287712] disk 0, wo:1, o:1, dev:sda3
May 5 21:55:30 spion29 kernel: [2339526.287721] disk 1, wo:0, o:1, dev:sdb3
May 5 21:55:30 spion29 mdadm: RebuildStarted event detected on md device /dev/md2
May 5 21:55:30 spion29 kernel: [2339526.295476] RAID1 conf printout:
May 5 21:55:30 spion29 kernel: [2339526.295487] --- wd:1 rd:2
May 5 21:55:30 spion29 kernel: [2339526.295497] disk 1, wo:0, o:1, dev:sdb3
May 5 21:55:30 spion29 kernel: [2339526.295515] RAID1 conf printout:
May 5 21:55:30 spion29 kernel: [2339526.295523] --- wd:1 rd:2
May 5 21:55:30 spion29 kernel: [2339526.295531] disk 0, wo:1, o:1, dev:sda3
May 5 21:55:30 spion29 kernel: [2339526.295541] disk 1, wo:0, o:1, dev:sdb3
May 5 21:55:30 spion29 kernel: [2339526.295589] md: recovery of RAID array md2
May 5 21:55:30 spion29 kernel: [2339526.295598] md: minimum guaranteed speed: 1000 KB/sec/disk.
May 5 21:55:30 spion29 kernel: [2339526.295608] md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for recovery.
May 5 21:55:30 spion29 kernel: [2339526.295625] md: using 128k window, over a total of 390628416 blocks.
May 5 22:11:52 spion29 kernel: [2340506.396514] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
May 5 22:11:52 spion29 kernel: [2340506.396539] ata3.00: irq_stat 0x40000001
May 5 22:11:52 spion29 kernel: [2340506.396552] ata3.00: cmd 25/00:00:a2:20:ed/00:04:0e:00:00/e0 tag 0 dma 524288 in
May 5 22:11:52 spion29 kernel: [2340506.396553] res 51/40:00:c9:21:ed/18:00:0e:00:00/e0 Emask 0x9 (media error)
May 5 22:11:52 spion29 kernel: [2340506.396601] ata3.00: status: DRDY ERR
May 5 22:11:52 spion29 kernel: [2340506.396611] ata3.00: error: UNC
May 5 22:11:54 spion29 kernel: [2340507.733453] ata3.00: configured for UDMA/133
May 5 22:11:54 spion29 kernel: [2340507.733795] ata3: EH complete
May 5 22:11:54 spion29 kernel: [2340507.844814] sd 2:0:0:0: [sdb] 1465149168 512-byte hardware sectors (750156 MB)
May 5 22:11:54 spion29 kernel: [2340507.851787] sd 2:0:0:0: [sdb] Write Protect is off
May 5 22:11:54 spion29 kernel: [2340507.851809] sd 2:0:0:0: [sdb] Mode Sense: 00 3a 00 00
May 5 22:11:54 spion29 kernel: [2340507.852536] sd 2:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA


Usually I would wait for the rebuild to be finished and asking the hosting provider to replace the second disk (sdb), but as the medium error causes just another rebuild process, this won't work for obvious reasons. So, the next plan is to fail the drive sdb and get a replacement disk then. Hopefully the first disk won't fail as well then... but well, Murphy, Backup, stuff... sigh

Jan Hauke Rahm: Avelsieve 1.9.8

Today the SquirrelMail plugin avelsieve happened to be released with version 1.9.8. Thanks and kudos to Alexandros who after so long time still was in the mood to put things together. The new features promise to be amazing: a new user interface, much code rewriting, and an entirely new SPAM handling. Unfortunately after installing it my SquirrelMail installation went badly down somehow. While everything alse is delivered properly by apache2, SquirrelMail now runs into one timeout after another. I need to figure out what s actually going on there. The error.log is quiet so far Anyways, for all you people who are looking forward to see this new fancy and shiny version in sid, I have to ask for patience. I think the package is ready but before testing no uploading! Until then you can (if you re brave) test the package by installing it from http://downloads.jhr-online.de/avelsieve_1.9.8-1_all.deb And all you others just have a look at the changelog that s probably (hopefully) hitting sid in a few days:
  * New upstream release
     + A large part of the code has been rewritten.
     + A new-style SPAM rule has been implemented.
     + A new, global Whitelist rule has been implemented, for
       the SPAM rules to take advantage of.
     + New, "Custom Sieve Code" rule has been implemented; this allows users
       to enter directly Sieve code snippets as a rule. (experimental)
     + Miscellaneous code movement and restructuring.
     + UI: The "Add New Rule" buttons are now links, and are displayed
       both at the top and at the bottom of the rule table.
     + UI: Major rework in the UI of both the Rules Table and the Add New
       Rule / Edit Rule pages.
     + UI: If a vacation rule is active, then display a notice in the
       rules table page and upon logging in to Squirrelmail, that reminds
       the user.
     + UI: Vacation options have been aligned properly; text has been
       changed accordingly.
     + Sieve: Vacation Subject is now supported.
     + New functionality: "Insert New Rule Here"
     + New functionality: "Move Rule to Position" (requires Javascript)
     + Avelsieve now highly recommends the use of javascript_libs plugin
       for some visual effects / UI improvements.
     + UI: Added new icons and used different ones, to improve usability.
       Icons are provided by Mark James' famfamfam.com.
     + UI: Added new icon "theme" based also on famfamfam.com. This theme
       is the default from now on.
     + UI: Removed unnecessary text / clutter from rules table page.
     + UI: The notify action options have been aligned in a table.
     + Added an LDAP Sieve storage backend, compatible with Sun Messaging
       Server's Sieve features.
     + The DO_Sieve_* backends should have a separate retrieve() method
       for retrieving the raw Sieve script. Currently, only the Managesieve
       backend has it.

Aurelien Jarno: Debian is switching to EGLIBC

I have just uploaded Embedded GLIBC (EGLIBC) into the archive (it is currently waiting in the NEW queue), which will soon replace the GNU C Library (GLIBC). The EGLIBC is a variant of the GLIBC which stays source and binary compatible with the original GLIBC. While primarily targeted for embedded architectures, it has some really nice points: We do not use some of these features yet, but this upload is a first step. From the user point of view, the package names are unchanged (except the source package and the binary package containing the sources) so no transition is needed.

Next.

Previous.