Search Results: "ag"

6 May 2008

Matthew Garrett

One of the advantages of working in a biology lab is getting deliveries of stuff in dry ice and getting to play with the dry ice afterwards. Sadly, while dry ice is clearly very cool (a-ha ha ha ha ha (dies)) it makes a lousy way of cooling down your drinks[1]. With a latent heat of sublimation of merely 199kJ/kg, CO2 draws less energy out of the liquid than ice's latent head of melting of 334kJ/kg. That's easily dealt with by using larger blocks of dry ice, but the fundamental problem seems to be that most of the sublimed CO2 boils straight out of the glass and just gently cools the atmosphere instead. Maybe ethanol cubes are the way forward.

[1] Much like Red Stripe, it is also a lousy fabric softner.

Biella Coleman: Monsanto: Making the RIAA and Big Pharma Look Kinda Good

Surveillance, massive patent litigation, and toxic trails are just a few of the atrocities that are part and parcel of the global giant Monsanto. They do not just produce a lot of the worlds GE crops but some MAJOR FUD with real muscle as this disturbing in-depth article demonstrates . Whether it is their shadowy, relentless fight against American farmers to “protect” their patents or their fight to scare dairy farmers from labeling their milk BST free, they deploy an astonishing range of legal and extra-legal tactics to make sure they stay on top. Below is a smattering of some of their creepiest tactics, which kinda make the RIAA look angelic in comparison.
“To gather leads, the company maintains an 800 number and encourages farmers to inform on other farmers they think may be engaging in seed piracy. Once Pilot Grove had been targeted, Monsanto sent private investigators into the area. Over a period of months, Monsanto s investigators surreptitiously followed the co-op s employees and customers and videotaped them in fields and going about other activities. At least 17 such surveillance videos were made, according to court records
“Studies by health authorities consistently found elevated levels of PCBs in houses, yards, streams, fields, fish, and other wildlife and in people. In 2003, Monsanto and Solutia entered into a consent decree with the E.P.A. to clean up Anniston. Scores of houses and small businesses were to be razed, tons of contaminated soil dug up and carted off, and streambeds scooped of toxic residue. The cleanup is under way, and it will take years, but some doubt it will ever be completed the job is massive. To settle residents claims, Monsanto has also paid $550 million to 21,000 Anniston residents exposed to PCBs, but many of them continue to live with PCBs in their bodies. Once PCB is absorbed into human tissue, there it forever remains.”
The company contends that advertising by Kleinpeter and other dairies touting their no rBGH milk reflects adversely on Monsanto s product. In a letter to the Federal Trade Commission in February 2007, Monsanto said that, notwithstanding the overwhelming evidence that there is no difference in the milk from cows treated with its product, milk processors persist in claiming on their labels and in advertisements that the use of rBST is somehow harmful, either to cows or to the people who consume milk from rBST-supplemented cows. Monsanto called on the commission to investigate what it called the deceptive advertising and labeling practices of milk processors such as Kleinpeter, accusing them of misleading consumers by falsely claiming that there are health and safety risks associated with milk from rBST-supplemented cows.

Biella Coleman: Summer Reading: Dominican nerdiness

It is the end of the semester as well as the end of my first year of full time teaching. It has been quite a handful, mouthful, and especially mindful but I am happy to say that I like a lot more than I dislike it, which bodes well for the future. I would like to spend some time writing about teaching and what I enjoyed to teach (and what the students like) but for now I want to note what was my favorite book of the academic year, which unsurprisingly, was fiction (and thus nothing I taught). The book is The Brief Wondrous Life of Oscar Wao by MIT professor, Junot D az and I read it over my winter break. It is a heart breaking but deeply humorous story that I could barely put down and I can’t wait till his next novel and will gladly wait the 10 years it took him to write this one after his amazing book Drown. It is about the life, trials, and tribulations of an unlikely character, a Dominican SUPER NERD by the name of Oscar Wao who has more than a lot of trouble scoring with the ladies (a “lovesick ghetto nerd” in the words of the author. Or to put in Dominican speak, he is no “tigre”). In the process of his many failures and attempt at love and lust, you learn about the experiences of Dominican immigrants in the tri-state area, the brutal history of the Trujillo dictatorship in the Dominican Republic as well as a good dose of odd culture folklore (both geek and Dominican, if you can believe it!) and all of this is told in a style that manages to combine the rhythm and passion of a poetry slam with classic issues of tragedy common in Greek literature. It is books like these which make me a little down on purely academic ones which tend to lack the style, pizazz, rhythm, flow, narrative, and heart needed to make you fall in love with words on a page.

Marc 'HE' Brockschmidt: Perl5.10 transition

We are currently having the fun of a perl update in unstable - most packages have been rebuilt and work just fine, now cleaning up the mess starts. Please don't expect perl to enter lenny in the next few days. Also, hold back on the uploads of perl packages or SONAME bumps, thanks. For the moment, I'm keeping my todo list in my hint file. If you would like to help out, just pick one of the bugs listed there and do the work, thanks :)

Steve Kemp: Only after disaster can we be resurrected

I leave my main desktop logged in for months a time; as demonstrated by my previous bug with the keyboard transition for xorg. The screen is setup to lock after 5 minutes of idle, so there's no real security issue, and it is extremely convenient. Every few weeks though my desktop gets into a funny state where no new windows may be opened.. Existing applications continue running without any problems, but no new windows/shells/whatever may be opened. Tonight it happened again. And the lightbulb went on in my head: My flat uses CFEngine to manage itself. (Two physical servers here, with 5-10 Xen guests, and a number of remote servers.) One of the things that CFengine is configued to do is to tidy directories of files which are older than 30 days. Including /tmp. So that explains that. Every month the magic cookie in $TMP would be nuked, and X would disallow new connections. I guess the next time this happens I should look at using Xauth to fix the issue, but generally I just logout, make coffee, smoke a cigarette, and login again. In conclusion: I'm a stupid-head. ObQuote: Fight Club

Julian Andres Klode: News on debimg


Well, you may have noticed that debimg 0.1 is still not released. But a lot of work happened over the weekend in my local branch. First of all, debimg’s set support is almost finished. I uploaded a tarball containing the differences between the official lenny weekly build from yesterday and a build created today by debimg, using the tasks of debian-cd 3.0.4 (after manual conversion to a format supported by debimg). Look at http://jak-linux.org/cdimage/tests/ for the tarball. Secondly, the dependency resolver has been rewritten. It’s a bit slower now (0.72 seconds for main), but creates much better results. Resolving the dependencies of all packages in Debian Lenny i386 in alphabetical order, debimg 0.0.X resolved 206 dependencies differently than apt. Now, these have been decreased to 15 dependencies, whereas 13 dependencies are false-positive (some packages were not installed because they were already installed). This means that only two ones were different, in this caseachims-guestbook and chdrv, which both depend on virtual-only packages (achims-guestbook: apache httpd, chdrv: console-utilities). The third big change is the addition of the hooks module. This module allows you to hook in custom functions, which have access to the Configuration object (ConfigObj) and the MediaSet. There are currently three types of hooks: pre_hooks (run before fetching packages, adding files to the disk), mid_hooks (run after the packages have been fetched) and post_hooks (run after the image has been built). Hooks can be added based on project and architecture, using a simple syntax which support shell patterns. (It’s ‘project/arch’). The hooks module uses python decorators to register functions. debimg 0.2 will switch to hooks for internal functions, too, like bootloaders and other stuff. The code has not been merged into the master branch, but I will hopefully be able to merge it tomorrow. The release of debimg 0.1 is now planned for this weekend.

Martin F. Krafft: How launchpad got it wrong

A common rant against Launchpad is that it s closed: the code is proprietary, and Canonical doesn t give raw access to the data they collect via the interface. Anyway, other people have taken up this issue, and it s not the point of this post to do so. I ve heard two argument why Launchpad is closed: first, it s a test bed for a product, which Canonical hopes to market to commercial entities to manage their own release cycles. And second: it s purposely cross-project and tries to integrate and link between them. Thus, lots of instances of Launchpad would defeat the point. I ll address these points in turn, starting from the back: While I won t deny a pre-trend towards (back to) mainframe-like computing, with Google, Amazon, and others providing rent-a-computer-cycle services. In addition, environmental concerns cast clouds over the 400W heating appliance under your desk, which happens to run your word processor and browser when it doesn t lose track of its countless spare cycles. Yet, I maintain that centralised services, such as Launchpad are a thing of the past. If you ask me, Launchpad got it wrong, even though it s light years further than its predecessors. It features pleasant graphics and obviously has had lots of smart thinking and experience shoved into it, but it s still centralised. It might be a business case, but it s not what the world needs. We ve seen massive growth of decentralised approaches to classic services, from file sharing to version control, from number crunching to simple web browsing, and yet, there s Launchpad, single point of entry (and failure) to the world of data surrounding Free software (at least if you follow their vision). What we need is something as slick as Launchpad, and thousands of instances thereof, which all peer with each other, automatically. The information would automatically be mirrored wherever it s referenced, so the entire cloud would be highly-available and failure-proof. Obviously, this wouldn t render itself well to the (traditional) software business model Canonical seems to strive for, so they re unlikely to go down this route. But we could. It would be a non-competitor. Update: thanks for the copious feedback I ve received. Among them was a comment by [Elliot Murphy]](http://launchpad.net/~statik), who speaks of us and thus leads me to believe that he s part of the Launchpad team:
We re definitely listening, and we still have lots more improvements we want to make. Our goal is collaboration, not centralization: thats why we build bazaar, are working busily on doing two-way integration with other bug tracker systems, and are building the best API we can. Our goal in the team is to make it trivially easy for you to get all the data that you put into launchpad back out through the API, data portability is very important. There is no big evil business model, but it would be socially irresponsible if we did not work toward making launchpad self-sustaining. It has been a long road, but the launchpad team is steadily working toward a distributed model, one step at a time.
While it s definitely nice to hear that data portability is a concern to them, I don t see Debian using Launchpad without the ability to run it on our own servers. I m definitely curious to hear more about the distributed model the team is pursuing. I certainly don t have a problem with self-sustainability, but in the Free software world, I do wonder what that is supposed to achieve. Release early, release often, anyone? Update: Philip Newborough took up the issue and has received a number of noteworthy replies. It made me very happy that he sees my post as a rant about Launchpad which is not lambasting Canonical for their proprietary Launchpad software; I wasn t aiming for any lambasting. NP: Nine Inch Nails: Further Down the Spiral

Aigars Mahinovs: Ubuntu removing XML from Python?

From http://159.18.52.69/raw/983493 Error:
Traceback (most recent call last):
  File "test.py", line 12, in module
    from xml.dom.ext.reader import HtmlLib
ImportError: No module named ext.reader
Fix/workaround:
+        sys.path.append('/usr/lib/python%s/site-packages/oldxml' % sys.version[:3])
        from xml.dom.ext.reader import HtmlLib
I had an old Python script doing some XML work and after upgrade to Ubuntu 8.04 I started getting the above error message and had to use the above fix because the Ubuntu packages of python-xml moved the xml.dom.ext.* to /usr/lib/python2.5/site-packages/oldxml for some reason. Have not looked at the latest Debian packages. Does anyone know why such back-compatibility breaking change was introduced? All I find on Google are the people getting bitten by this bug and no reasoning or even discussion behind the change.

Gunnar Wolf: Ruby has a distribution problem

I usually don't like me too comments... But this is something that really disappoints me of my otherwise-favorite development framework. I must echo Matt Palmer's comment on Luke Kanies' entry:
Ruby. Has. A. Distribution. Problem.
Nice, good read. Sadly, many Rails pushers see distributability as something very minor, something that should not worry Rails developers right now, as there is too much other serious work to be done - Better UTF8, a clearer language, better performance... And besides, any programmer can live well with gems. (yes, that's all taken from a rant I had with a very convinced person)
My gripe is that... Rails is no longer a small, fringe project. Rails is an enterprise-grade development framework, with thousands of deployed production systems. And if they don't start to act responsably, if the Rails developers keep pushing said problems as low-priority, the Rails developers' (that is, their users) culture will become rigid - and will constitute a serious harm to Rails' future.
Distributability and packageability is not only for OS distributors. Not only we Debian zealots care about software being easily packageable. By using Ruby Gems, you dramatically increase entropy and harm your systems' security.
Read Luke's text for more details. It is quite worth the time.

Alastair McKinstry: IPv6 would save 300 Megawatts ?

An interesting discussion appeared over on the NANOG mailing list, based on the article, Up to 300 Megawatt Worth of Keepalive Messages to be Saved by IPv6? This points to an original study by Haverinin, Siren and Eronen at Nokia that shows how much energy is used via "keepalive" messages sent in VoIP, Instant Messaging and other systems, in order to satisfy NAT. In order to maintain connectivity through a NAT router these systems need to keep sending messages to stop the NAT router closing the connections. With IPv6 this would no longer be necessary. It turns out the power requirements are quite significant. There is good work happening elsewhere in Linux and elsewhere in IT, to minimise the amount of energy wasted, such as the Less Watts project. But perhaps its worth doing an audit of the protocols we use, to see what energy savings we can use? Tags , , ,

Kartik Mistry: Todays fortune


* From world’s favorite time pass, Orkut: You have a strong desire for a home and your family comes first. * On Debian front since Sunday, I updated chmlib (Thanks meebey for reporting and pabs for quick upload) fixing horrible bug due to my overlook in debian/copyright (#479649) and uploaded new release of libyahoo2 0.7.6 to mentors. * And yes, I am bit sick from last 2/3 days. Stomach is bad :(

Tore S. Bekkedal: Depressing.

Those of you who know me might be aware that I have a fondness for cool and neato hardware which is possibly a tiny bit above that of the average geek. I have more nodes on my ThinNet than on my TP network, for example. Back in February, I had the random idea to call SGI Norway and ask them if they had anything they were about to throw out. I knew that they were working hard on moving from MIPS to Itanium, so perhaps some hardware was disappearing along the way. Oslo didn’t have anything, but when I called Bergen I found out that they were about to throw out a large amount of hardware, including some really nice boxes like an Onyx2 deskside workstation, and some Origin systems. For those of you who aren’t into SGI machines, I can sum it up by saying that these are really cool computers: Big, noisy as hell, heavy, and in terms of performance, nearly on par with a normal desktop nowadays. In short, fantastic educational toys. So, this was in February, and we were making arrangements for transport to Oslo, until one day I stopped receiving mail. I didn’t think much of it; email is asynchronous, and I figured he was busy doing something else. I was certainly very eager to get at the machines, but didn’t feel like nagging at him either. Finally, recently I sent him a polite reminder, and I get the rather rude response: Diagnostic code: smtp;550 cuda_nsu 5.7.1 <****@sgi.com>: Recipient address rejected: THIS USER IS NO LONGER WITH SGI. CONTACT help@sgi.com IF YOU NEED INFO. I tried calling the Bergen office, but the number was out of service. So I call the Oslo office - and I am told the Bergen office has been shut down, and all the equipment has been thrown out. This is the bummer of the century, for two main reasons:
  1. I’m not getting cool hardware that I was totally looking forward to getting,
  2. Great hardware has now been ground up for use in car tires.
For some odd reason, the second reason is infinitely more grating than the first. I feel like a museum curator being forced to watch someone feed a Picasso painting to a paper shredder. This really, really screwed up my day. :(

Wouter Verhelst: Pathetic

When you're 5, you're living with your parents. If not, you're probably in an orphanage, waiting for adoptive parents. When you're 10, you're living with your parents. If you're not, something is very wrong. When you're 15, you're living with your parents—although you'd probably rather live elsewhere. When you're 20, you're most likely still living with your parents; but if you don't, that's nothing to be ashamed of. When you're 25, you've either moved out, are doing so, or are thinking about it. When you're 30 and you still live with your parents, you're pathetic. At least that's the way I look at it. As of today, I'm officially pathetic. Won't be for long, though—it's just taking slightly longer than initially expected to make the appartment habitable. Stuff left to do: Except for the "connect electricity" bit and the final step, that should all be doable in about a day, if I hurry. It's about time.

Julien Blache: Etch 1/2 considered harmful for kittens

Trying to upgrade a craptastic server that’s proving problematic under 2.6.18 to the Etch 1/2 kernel, not only is the machine extremely sloooooow to boot, but it turns out that it’s partly due to bnx2 now requesting a firmware file, whereas the firmware is built-in in the 2.6.18 Etch kernel. Of course, the machine has no working network access due to this, and, to make things even worse, the firmware file is nowhere to be found. No firmware-nonfree in etch-proposed-updates and it’s not in the firmware-nonfree package in unstable. You’d better hide your kittens, for Etch 1/2 makes me want to kill a large number of kittens.

Russ Allbery: Debian status

Tonight, I converted the XML-Security-C package from Stanford's internal Subversion repository to Git and packaged 1.4.0, but unfortunately I can't upload yet because Xalan needs to be updated to build against the latest Xerces-C. (I'd NMU, but I should not be taking on more things right now.) This is the first of the three current Shibboleth packages, and I hope to tackle OpenSAML and Shibboleth SP tomorrow or Wednesday. An Alioth project for Shibboleth packaging now exists and the pkg-shibboleth-devel mailing list is being created. I've requested Git space on git.debian.org, and as soon as that's set up, I'll push the three existing repositories. Shibboleth 2.0 packaging will add at least three more packages (OpenSAML 2.0, Shibboleth SP 2.0, and another XML support library), possibly four if we have to package log4shib, but I still hope to use the standard log4cpp. And then there will be another couple of packages once the group packages the Shibboleth IdP and WAYF, which I hope someone with more Java experience can tackle. One of the main goals for getting this set up is so that people other than me can do more of the work so that I can work on other things. Like, for example, krb5 packaging. Bastian Blank started using the Kerberos server packages and posted a whole flurry of bugs, a couple of which are (somewhat arguably) RC, and I'm trying to absorb that and fix the ones I can ASAP. OpenLDAP is in desperate need of attention, but I don't feel as much responsibility for that. I said going in that I'd only have time to work on it in fits and starts, and just because no one else has any time to work on it either doesn't change that. However, I do need to find time to post an RFH, since it really needs an active maintainer, and I'll at least find time to upload the upcoming 2.4.9 release before lenny freezes more, since the current version has a ton of bugs. Frank Lichtenheld has been doing a lot of the work on Lintian lately, which is wonderful, but I still have at least 10 bugs and patches that I want to deal with as soon as possible for it and get another upload out. We're well over my magic threshold of 100 bugs, and a lot of the stuff that's in the BTS just needs to be reviewed and committed. And then there's Policy, which is just about ready for an upload, and where I owe several responses on bugs and discussion threads. It's in the best shape right now of the stuff on my hot list, but there really should be a new upload in May, and preferrably in the first half. The current goal is to get the two other RC bugs against the Shibboleth packages dealt with in the next couple of days, then do a krb5 upload before the end of the week, and then Policy and Lintian are back at the top of the list, insofar as work lets me concentrate on anything else. BTW, I have to say, the more I use Git, the more I'm becoming a convert. I still think I'd rather use quilt if I have complex merges. Ironic, given that that's supposed to be Git's strength, but I have fifteen years of experience merging patches and I really understand how quilt works. That may mean I'll change my mind when I become even more familiar with Git. But for the typical package with a small number of divergences from upstream, I'm getting the hang of managing those on branches and I think I like it. I've yet to see a good reason to use rebase instead of merge, though, at least as part of a Debian packaging workflow. So either I'm still not getting something, or many of the people using Git are way more obsessive than I am about their branch merge graphs (which is weird, because I tend to be remarkably obsessive about things like that). I suppose if I ever get to using git bisect, that may change my mind.

5 May 2008

Junichi Uekawa: Going to be married.

Going to be married. I am currently lagging behind in e-mails by approximately by a month. If you need my attention, shout.

Christian Perrier: What to do if catched by the "l10n NMU" patrol ?

It might happen that you (I mean you, gentle reader of this blog) being a Debian developer or maintainer, just receive one of my numerous "Intent to NMU to fix pending l10n bugs" or "Announce of the upcoming NMU of ". The first gives you 10 days to react....then I send the latter which opens an 8 days translation update round. In such case, as the carefully written template for these (pretty long) mails says, please DON'T immediately upload. Speak to /me instead so that we coordinate the translation update round. That will also allow me to send you possible QA enhancements I found in your packaging while trying to build your package *and* translators to send more material. Some (rare) maintainers just uploaded immediately after getting these mails and they're now getting what could be expected: they're receiving new translations...and are then likely to be catched pretty soon by the patrol, again..:-). The "intent to NMU" mails are sent to the i18n mailing list and some translators find this to be a good opportunity to send translations in their language (that's why Finnish, Galician are for instance climbing up pretty quickly in statistics). The main intent of these NMUs is to get updates done, not doing NMUs so, of course, I will welcome uploads...it is however more efficient to coordinate them.

William Pitcock: Some musing on XMMS + Audacious + lulz

Recently, we’ve been getting a lot of the following on our IRC channel: <intangir> well xmms could do it
<intangir> and now xmms is no longer being updated
<intangir> its just been taking out of new debian and ubuntu repos ;(
<intangir> so audacious is the only thing that is close
<intangir> it must fill the void! This is incorrect for a number of reasons, I am sorry if your distribution or the internet has made you believe that we are some magical successor to XMMS. This is not the case. Furthermore, calling us a “disgrace to open source” because we have no interest in being like XMMS (even the winamp2 skins are due to be leaving at some point), does not make us want to help you. Now, why do people think Audacious is not acceptable replacement to XMMS? Well, not all people do, it’s more of the 5% of people who have specific use cases not covered in Audacious. Clearly if Audacious was not suitable, a lot of people would be blogging about it. Instead, we only see a few people blogging about it. However, that said, I think Audacious’s focus is probably not the right focus for an “XMMS replacement” solution, and I have a plan for that (although once I finish writing it, someone else will likely be maintaining it, as I don’t really care enough). More on that later.

Joey Hess: the internet empowerment spectrum

When I look at how people are using the net, I see a spectrum... At the low end, there are users who browse, and maybe post stuff to sites like flickr or youtube or wikipedia. When I hang out with these people, I'm struck by them being often quite smart, savvy, capable (and young), and wasting a lot of their time and inginuity fitting what they want to do into these narrow and (mostly) corporate-controlled and censored channels. And being limited by it in ways that they're not fully aware of. If you're in this group, please, please consider finding a way up the spectrum. At the high end are tecchies like me, we have at least one and often multiple servers, sometimes even in different countries/continents. We can write and run our own software with full control. This excellent advogato article calls it the "sovereign" level. We're not exactly kings when you look at who controls things from DNS to the internet backbone, but we're as close as it's practical to be without running your own wires. And we're statistically vanishingly few these days. So the middle is more and more interesting. For one thing, being king is expensive. So some of us move down a level, to virtual servers with xen or the like. Maybe we can't build our own kernel on our server anymore, but we don't have to worry about maintaining spinning disks and fans. And some people move up to this level too. One path is learning about running linux on a personal machine and then using an easy and cheap provider like slicehost. But still, users at this level are rare. The other interesting level (and the one I've not explored much myself) is a step up from the low end, where you have some form of inexpensive shared hosting, but can at least run your own code. This level seems quite a mess, there is no standardisation, everything has to be set up by hand, unless you use prepackaged control panel type things that probably take away most of the empowerment available at this level. A lot of people reach this level, but it's still fractions of a percent. So there seems quite a hump up from the lowest end of the empowerment spectrum to using shared hosting. How to encourage people over that hump is an interesting problem.
I've been playing with using some power tools from the top, sovereign level down in these murky shared hosting depths. Decided to see what kind of stuff I could accomplish for $5. Although it ended up costing only 2 cents for hosting so far. Amazon and google's hosting servives look interesting, but need things to be designed explcitly for them. And those companies are too big already. NearlyFreeSpeech.net is more flexible, funky, and has a cheap pay-as-you-go pricing that's ideal for little things that will only use a few dollars of bandwidth. So, I got ikiwiki working there (and documented how), along with a git backend, so my wiki's sources can be cloned to elsewhere for backups and development. Some things I hope to do later include:

Michal &#268;iha&#345;: Gammu test version 1.19.91

Next testing version of Gammu was just born. It brings only small amount of fixes, but most users of recent Nokia phones will be pleased that long outstanding bug with SMS decoding has been fixed. Full list of changes: You can download from usual place: http://cihar.com/gammu/, Debian users can get packages from experimental.

Next.

Previous.