Search Results: "ag"

26 January 2009

Y Giridhar Appaji Nag: Wagah-Attari and Hussainiwala

Pakistan flag and Emblem of India Fellow countrymen, happy Republic day to you all.

Any trip to Punjab is incomplete without atleast one visit to the daily tamasha at the Wagah-Attari border. This is probably one of the few places on earth where you would see the Pakistan flag right next to the Emblem of India.

I arrived at the place a couple of hours before the vening flag down ceremony but was too late to be able to get a comfortable seat in the crowd of a few thousands; the place was already packed. Luckily, a BSF ranger (who incidentally was not allowing the crowds in any more) looked at my tripod and camera, thought I was a journalist and led me to the VIP section which is as close to the gates as one can get.

For a very long time preceding the ceremony, there is nationalist music blaring on the tannoys, crowds screaming in unison: LA ilAha ill-Allah on the Pakistani side and vandE mAtaram, bhArat mAtA ki jai on the Indian side. On either side of the border gates, kids run up and down the road with their respective national flags while young men climb onto the top-most walls and wave flags high in the air. One gentleman was commenting that while women on 'our' side are allowed to dance and sit anywhere, 'they' don't allow that, "see how the men and the women there are grouped separately".

Thousands of spectators Waving the Pakistan flag Waving the Indian flag Women dancing

The half hour of the retreat ceremony is full of action with the Indian BSF rangers in their red turbans and khakhis, and the Pakistani rangers in black salwaar-kameez marching heavily down the road, glaring into each others eyes, competing on who can kick higher into the air and possibly also on who has the best kept moustache. The rangers on either side of the gates know that they are entertaining their home crowd and spare no effort to do their best.

Indian BSF rangers marching Indian BSF rangers at-ease
Indian ranger marching towards the gate Indian BSF ranger Indian BSF ranger
Border gate, Pakistan crowd and rangers India and Pakistan flags Crowds going back home

The retreat ceremony is so popular that it is difficult to allow in all the people that come in to watch. So a clone of the ceremony has been setup at the Hussainiwala border. However, Hussainiwala is popular not because of the flag retreat, much less because the 1971 war memorial still has a lot of marks of artillery firing, but because of Bhagat Singh's memorial. The memorial moves one to tears.

Hussainiwala: Sukhdev, Bhagat Singh and Raj Guru Hussainiwala bridge: Sympathetically detonated in the 1971 war

Few more pictures from the Hussainiwala memorials:

Hussainiwala: Sukhdev, Bhagat Singh and Raj Guru Hussainiwala: Bhagat Singh memorial Hussainiwala bridge piers and war memorial Artillery fire on Hussainiwala bridge piers Artillery fire on Hussainiwala bridge piers

Matthew Garrett: Nnngh.

Intel have a magic communciation channel between the system firmware and the graphics hardware. It's based on a region of shared memory and judicious use of interrupts, and it's documented here.

Nvidia have a magic communication channel between the system firmware and the graphcis hardware. It's based on WMI and bonghits, and it's not documented.

Why, yes, I have spent half the day trying to work out how the NVIF method works.

Daniel Burrows: A map of the apt and dpkg state files

Continuing my recent interest in making diagrams of things, this weekend's project was a visual representation of what the global state files of apt and dpkg are, what's stored in them, and how they're manipulated. As before, this includes only the core part of the system (ok, I squeezed aptitude in there too), for the simple reason that I'm not smart enough to include more stuff in the diagram without making it utterly illegible. As it is, it's already pushing the boundaries of how much you can fit on a single page of paper: diagram of apt files This image is also available in svg and pdf formats. Be warned, though, that the SVG might display oddly in anything but Inkscape, and the PDF only displays correctly in Acrobat Reader. If you want to print off a copy without wasting toner, if you don't have a program capable of printing the above, or if gradients offend you, you can also download a simpler version of the diagram: simpler diagram of apt files Also available as an svg file or a pdf file. Unlike the last diagram I produced, this one was made in Inkscape. It took pretty much the whole weekend, most of which time I spent learning features of Inkscape that I didn't end up using. Oh well. I've come to the conclusion that Inkscape is an amazing graphics program and an utterly terrible diagram editor. Although to be fair, it seems to be one of the best, if not the best, diagram editors in Debian; also, if you slog through it and you have more graphical talent than me, the diagrams will look very good. [EDIT]: fixed an oversight in the first version of the diagram (apt-get also writes the extended_states file).

Andrew Pollock: [life] Too much deja vu

Seriously, every time Sarah has surgery, it all goes pear shaped. The bottom (last time it was towards the top) of Sarah's incision from her recent wire removal surgery was looking a bit red, swollen and hard on Friday, so she went in to the clinic at got them to take a look at it. They decided that a knot in the sutures was trying to work its way out, and causing inflammation or something, so just like last time, they decided to reopen the incision a bit. They did that, and cut the knot out, and rather than packing with gauze, they just taped the small opening closed with some steristrips and covered it with gauze and sent her on her way. Somewhat fortunately (for me) Sarah went into the clinic during the day while I was at work, so I missed participating in the fun and games. They didn't use any local anaesthetic, but Sarah said it didn't hurt too much. That night, though, she was in a reasonable amount of pain, again, similar to last time, except it was a band across her upper abdomen, below her breasts, instead of chest pain. Mindful of the staph infection disaster from last time, we trotted off to the ER on Saturday afternoon, hoping to nip this in the bud. They did some blood work, which came back clear, and gave her some IV pain medication, which didn't seem to do much, and were generally scratching their heads as to the cause of the pain. Fortunately, one of the surgeons involved with Sarah's wire removal from 2.5 weeks previously happened to be on call, so he got called in. He had a bit of a poke around the opening with a long cotton bud, and declared that it was possibly infected, because there was a bit of cloudy fluid discharged when he poked it in. Oh, and the cotton bud disappeared a good centimetre or more under the skin further up the incision, which indicated an abscess was forming. So, for the second time, I got to watch my wife being cut open with a scalpel. I think the local anaesthetic injections were the most painful part for her. He opened the incision up a bit further, and packed it with some Betadine-soaked gauze, and we got sent home with the same instructions as last time this happened: I had to repack the wound with saline-soaked gauze two to three times a day and let it heal from the bottom up. She was also prescribed some antibiotics. She's got about a 2cm incision just below her breasts. It looks a lot deeper than the hole from last year's incision. So we got home about 6pm last night, and went to bed around 11pm. Sarah lasted a couple of hours before she woke up in even more pain than before. She called up the hospital and had the same surgeon paged, and he advised her to come in to the ER again. So at I think about 2am, we headed back. They took some more blood, did a CT scan, which came back clear, and decided to admit her. They're giving her IV antibiotics and pain medication. Initially she didn't want to have any more IV pain medication because it didn't seem to be working, and it tends to make her nauseous. She wasn't keen on dealing with throwing up with the amount of pain she was having. It hurt to move as it was. With a mixture of IV anti-nausea drugs and the IV pain medication, the pain has finally come under control though. She did have one bought of vomiting this evening, which didn't seem to cause her too much discomfort, and she's getting in and out of bed more comfortably. They're going to keep her in overnight. She has a post-operative followup tomorrow in the clinic, so I expect they'll keep her in the hospital until at least then, depending on how things go. Her cardiologist, intimately familiar with last year's debacle, dropped in this afternoon. He's wondering, given how this has happened twice now, if Sarah has some sort of allergy to the type of absorbable suture they've used. Apparently there are different types of sutures, so if she ever has any other surgery, we'll have to get them to try a different type It'll be interesting to see how she goes tonight, as the pain seems to get worse overnight. She hasn't had any IV pain medication since about 1pm, and she wanted to see how she goes without it, because if she gets discharged tomorrow, she'll have to rely on oral stuff anyway. I think it definitely gets harder for her to manage her pain when the pain is causing her to lose sleep. She can only deal with having a couple of night's worth of bad sleep before it all gets too much. So I'm really hoping she gets a good night's sleep tonight. Not that hospitals are renowned for that...

John Goerzen: How The Wind Got Us A New Camera

A little while back, Terah was leaving the house one morning. On that particular morning, we had an unusually intense even for Kansas wind. It caught the storm door and whipped it around with such force that it bent the metal arm that goes into the pneumatic plunger, and even bent the bracket that the arm connects to. It was not possible to un-bend either of them with household tools, even with dad s help. So I went to the hardware store and picked up a replacement. But I had been putting off actually replacing it because, well, the door almost closed automatically and there were more important things to get to. Until yesterday. I got out the tools and went to work. Jacob was around and took an interest in the activity. I was stretched out on the floor on my stomach working with the drill to try to get out some extremely tight screws without stripping them. And Jacob, at one point, got down on the floor on his stomach right beside me, and proudly announced I (am) like dad! Terah was working on something nearby, and noticed this, and went for the camera. Unfortunately, I had left its CF card in my digital audio recorder. She found the other card, and was hurrying to put it in so she could get the cute picture. Even more unfortunately, she inserted it sideways. CF slots have 50 tiny pins in the space of 1.7 inches. The slots normally force the card to align properly, but not when the card is put in sideways. It slid back and bent a pin back. The slot is thus unusable. I was going in to town anyway to pick up my bike from the bike shop, so I stopped at Moler s Camera on the way. This is my favorite camera shop it s the sort of place where you take a seat at the counter while they help you. I showed the sales guy the camera and he knew off the top of his head that the cost to fix it is $206. Which is pretty much in line with reports on the Internet. The old camera is a Canon Digital Rebel XTi (EOS 400D). It s over 2 years old, so out of warranty, but I wasn t planning to upgrade soon. On the other hand, the camera shop estimated that they could buy the XTi from me for about $150 to $200, considering its condition, and a new XSi (EOS 450D) is $570 at B&H. So about $200 to fix the old one, or about $400 cost to us to get a new one and the next model up, which uses SD instead CF, and thus will never have a bent pin again. With that kind of cost, we decided to spring for the XSi. Plus, it would take about a month to get the repair on the XTi. So there you have it. The wind can be expensive and cause camera upgrades.

25 January 2009

Ana Beatriz Guerrero Lopez: End of backports and about KDE in Lenny

About a week ago I updated the KDE 4.1 backports for Lenny with the fourth and last revision of KDE 4.1.
As previously announced, this will be the last update available at http://kde4.debian.net What is next? The repository will continue there, so Lenny users can choose between KDE 3.5.9+ and KDE 4.1.4. But since 4.1.4 packages are not official, they do not have support: no bugs in the BTS or security updates.
If you are using Debian Lenny for stability and security purposes, you should use KDE 3.5. Testing users (future squeeze, current Lenny) can continue using them until KDE 4.2 reaches testing. Again, remember, no bugs in the BTS or security updates, but they will get a clean upgrade to KDE 4.2 in the near future. Unstable users. I have found that there are people using unstable with the backports, when they should be using experimental KDE 4.1. If this is your case, you can stick with 4.1.4 until KDE 4.2 reaches unstable or switch to experimental in a few days and get KDE 4.2 (no yet! it needs to be released first :) ). Last, but not less important, thanks to all the people helping with the backports: MoDaX for helping as backup and the rest of the Qt/KDE team who worked in the experimental packages. HE, zobel and aba for his sysadmin tasks. apol for allowing me torture his PowerPC machine. All those who translated the instructions into their languages and
helped to others users in mailing lists and forums. A quick note about KDE 3.5 to be released in Lenny As most of you have realized, the packages of KDE 3.5 in Lenny and unstable are a mixture of KDE 3.5.9 and 3.5.10. Given that KDE 3.5.10 was released after Lenny was frozen, we could not push this new version into Lenny, however the KDE 3.5 packages were patched about June last year with the latest changes in KDE 3.5 from the KDE subversion. This means some of the modules with the version 3.5.9 are exactly the same that is shipped as 3.5.10.
The only big stuff missing are the kicker improvements shipped in kdebase and some bug fixes in kdepim. But in global, it is closer to KDE 3.5.10 that to KDE 3.5.9. If you want to see what changes are you missing, check the KDE 3.5.10 changelog.

Roland Mas: GForge is now FusionForge

Executive summary To avoid confusion with the proprietary versions of GForge (known as GForge Advanced Server, GForge Express Edition and GForge Community Edition), the free/libre/opensource codebase will from now on be separately maintained under the name FusionForge by the main developers of the free GForge 4.x codebase. Since this is mostly a renaming, the migration path for existing users will be smooth. Longer version, with details After the initial forking from the Sourceforge codebase, the development of GForge has long been hosted, and many enhancements directly developed, by the GForge Group (GForge, LLC), with regular contributions from outsiders. The results of these evolutions were public and free, subject to the GNU GPL. In parallel, the GForge Group wrote a proprietary re-implementation of GForge, which it sold under the name "GForge Advanced Server", or "GForge AS" for short. This re-implementation added some features for "the enterprise", but was not contributed wholesale to the GForge codebase under a free license. Although some of the features were contributed to the public, the GForge Group concentrated its efforts on its (proprietary software) business model, with more versions appearing, such as "GForge Express Edition" and more recently "GForge Community Edition". As a result, it became increasingly harder for the public to know which version was which without doing extensive research (indeed, some users mistakenly installed one version instead of the other). A consequence was that the free software codebase suffered from a loss in visibility, which lowered its momentum to the point that there haven't been any moderately important releases since the (currently stable) 4.5.x series was announced in late 2005. So, in order to clarify things, avoid further confusion, and regain some of the lost momentum, it was decided by a group of leading contributors that the free software version of the GForge codebase would from now on be developed under the FusionForge name, and its development would be hosted on FusionForge.org. So is this a fork? Well, we don't know yet. It could arguably be called one, since we're taking the code and running away with it under a new name. However, we believe it's not a fork unless both roads continue their own way (more of a oddly-shaped bend). What happens to the GForge codebase developed by the GForge Group at gforge.org remains to be seen, although for the sake of our users we will backport security fixes to the gforge.org Subversion repository (at least for the 4.5.x series and the unreleased 4.6 and 4.7 pre-series) for some time. The bulk of the development will move on to FusionForge and the repositories at FusionForge.org, though, and users are encouraged to migrate at their own pace. Since we're basically continuing the evolution rather than starting from scratch, the migration path should be rather smooth. So why the FusionForge name? Because there were actually lots of locally-patched versions of GForge (and Sourceforge), and we felt it was a waste of resources that should be fixed. It seems many people and organisations took these codebases at some point in time and evolved them for their own needs. Sadly, many of the changes were not contributed back or even published, so lots of efforts were duplicated. Fortunately, many of the people managing these locally-patched forges are now realising that "out-of-tree" patches and features require quite some manpower to maintain. Some formal inter-project discussion is already taking place, and we hope to achieve actual merging of most of the interesting features that have been developed here and there into a common base that can be reused locally with minimal changes. We'd like to "un-fork" as much as possible. We also expect that, by using standard components and tools, we'll facilitate the work of potential contributors, thereby reducing the risk of a new era of fragmentation. And who are we anyway? We're Christian Bayle, Roland Mas and Alain Peyrat, long-time contributors to GForge and responsible for over 95% of the commits over the past two years, as well as a few relative newcomers. Christian and Roland have been maintaining the Debian packaging since the "Debian-SF" era, and Alain has been focusing on code quality. The three of us have, for various reasons, a vested interest in maintaining a lively codebase in a healthy ecosystem. What are our plans? Our short-term goals, as currently planned, include: Longer term goals are less well defined, but we're thinking about the following: Some of these items should be facilitated by our switch to a distributed version control system and a new coordinated workflow. Also, the Debian i18n team has been kind enough to offer to host our translation effort on their Pootle server, which means translators will have a much easier time doing their job. We hope to hear from users and contributors alike in the near future. For more information, we can be reached via our fusionforge-general mailing-list (see our lists), which is also suitable for general discussions. We can also be found on IRC (#fusionforge on the Freenode network).

Ben Armstrong: Involve kids in free software development through play

Giving up on a position within a free software project when you know you re no longer managing to do an effective job is a wonderfully liberating experience. Now that I have started to talk with Miriam Ruiz about handing over the Debian Jr. project, I can stop worrying about the leadership task and just have fun with it. I can always count on Miriam for recommendations for games in Debian my kids may enjoy, as she has a passion for finding good games to package for Debian, and in particular, games for children. Over the past few weeks we ve had some fun with her picks. At the same time, I always have Debian Jr. in mind. How can we ensure kids can have the most fun with this? How do we equip their guides to help them? What we ve done with each new piece of software is to find a quiet time when one or more of the children can start playing with it on their own while we watch, offering such guidance as they need, but for the most part just letting them loose with it. Each wrinkle of the brow, each impetuous thump of the mouse, every illuminated grin and exclamation of delight is noted. We try to see what frustrates or pleases our kids and discuss it both with them and the Debian maintainers and upstream developers. This is an excercise we ve managed to pull off without being overly intrusive and the results have been well worth the effort. Using a few of Miriam s picks we tried this week, we were able to draw their play into the free software development process. Here s a brief summary of those sessions: Platinum Arts Sandbox puts into children s hands the ability to role play in a 3D world and edit that world using simplified controls. The expressions on the faces of our kids as they played were priceless: both the ups and the downs. I wanted to capture this on video and share it. After having established a rapport with upstream, we took a 20 minute clip of one of our play sessions and gave a copy to them to use to help further their work. Here is the edited result. They were very pleased to have that kind of feedback and found the video valuable for determining where the software still needed improvement and to notice which aspects particularly pleased the children. I happen to know that Hex-a-hop is one of Miriam s personal favourites. We have a household full of puzzle-lovers so this puzzle game was an instant hit. While on irc on #debian-jr with Miriam we relayed in real-time some of the reactions as they played this and a handful of her other picks. This gave her some confirmation of areas she knew needed work as well as inspiration for upcoming releases of these packages. During this play session, which also included StegaVorto, kartofel, Anagramarama, Funny Boat and Vodovod, my youngest girl, age 7, plunked down on the couch next to me as her 10-year-old sister played. Then she started to notice I was typing what people in the livingroom were saying and doing on irc. She took a mild affront to me copying her own words and actions, so I decided it would be better to let her participate so she would feel included. At this point, I started playing secretary for her, typing what she dictated to me while she read the responses from the display. Later, I just handed her the keyboard so she could type and read the responses on her own. She was still at it long past bedtime and it was with some reluctance that she finally gave up the keyboard. We all had a lot of fun and look forward to doing this again. We are particularly careful with privacy, taking care to share pictures, videos, and other personal details only so far as we believe it does not put our children at risk. Also, we need to ensure we observe in a way that is welcome and doesn t interfere with their enjoyment. But with a little bit of prudence and a practiced eye and ear for what increases or diminishes enjoyment of the software, we can involve our children directly in the free software development process. I commend to anyone who has the privilege to share free software with children to use this method to communicate with maintainers and developers, increasing your own enjoyment of the software in the process and that of children and their guides everywhere.

Romain Francoise: Some Emacs news

This week's emacs-snapshot release (20090118-1) reached a new milestone with more than 700 downloads in just under a week. I guess this is quite an achievement considering that not everyone wants to download 25MB of Emacs packages on a weekly basis, so thanks to all my users for their continued trust and support!

Here's a quick update on the status of the Emacs 23 release: the last remaining feature on the roadmap was finally completed this week with the merge of the rmail-mbox (pmail) branch into rmail. The pretest (GNU lingo for beta ) phase could start as early as next week, which is not to say that the release itself is right around the corner since a few major tasks need to be finished first, like updating the manuals. The release could also be delayed by the proposed (and long overdue) switch from CVS to Bazaar, pushed by newly-minted Launchpad evangelist Karl Fogel.

That being said, aiming for a release in 2009 isn't entirely unrealistic, and I really can't wait to see Emacs 23 reach a wider audience. It is the culmination of many years of work in lots of areas (Unicode support, font backend, multi-tty, Cocoa, ...) and is by far the best Emacs version to date!

Clint Adams: and it also allows Keynesians to continue to delude themselves

The funniest thing I've heard about The Economist is that it is full of neo-liberal absurdity and supported criminals like Reagan and Thatcher.

Biella Coleman: Pedagogical Re-indoctrination: FLOSSIFY!

If you are in the NY-area and would like to help out with the project described below, they are looking for volunteers. Help FLOSSIFY the enormously popular book Digital Foundations. The event is being hosted Feb 6-8 at the lovely Eyebeam with some Free as in Beer and Grub provided! ******************************************************* FLOSSIFY 1 : Digital Foundations
For a long time educational courses have been cheap marketing
for proprietary software companies. Can a student really afford all
those expensive softwares required by the courses? No. Ever hear of a
software company kicking up a fuss because students are using
unofficial versions? Well, it does happen but not often. And why not?
Because proprietary software companies know, as the universities know,
that once the students leave their training they will be indoctrinated
with those tools and simply slipstream into being paid up proprietary
software citizens. Simply put, unlicensed software used in education is
tolerated because it is cheap marketing. This is how tools become industry standards . FLOSS Manuals is fighting this flow by converting textbooks that
use proprietary software to using free software in their examples. We call this process FLOSSify . We convert the book from
closed software to Free Libre Open Source Software (FLOSS) hence we
FLOSSify the book. Our first text book is the wonderful Digital Foundations book produced
by Michael Mandiberg and Xtine Burrough
(http://digital-foundations.net/). Its a text book designed to teach
software by teaching design. The current toolset it uses is the Adobe
Creative Suite and we will convert these examples entirely to using free
software. FLOSSIFY 1 : Digital Foundations will focus on a fun 3 day event at
Eyebeam, NYC. Anyone is welcome to attend and some food and beer will be
provided. Come and meet some of your old geek friends, make some new,
and help make a step towards unshackling education from proprietary
software. FLOSSIFY 1 : Digital Foundations
Eyebeam, New York City
Feb 6-8
starts 10ish
finishes when we are done
fast connection, a table, some chairs, and beer and food provided
contact adam@flossmanuals.net for more info venue:
http://eyebeam.org/
540 W. 21st Street, (between 10th and 11th Avenues)
New York, NY 10011
Tel. 212.937.6580 Fax: 212.937.6582

Sami Haahtinen: Purging postfix queue

Since I keep ending up in situations where I need to clean up postfix queue from mails sent by a single host and always forget the command, I'm posting it here. Maybe someone else will find it useful as well. To begin with, you need to determine the IP address of the culprit you want to eliminate. How you do this, is up to you. Grepping logs or examining the files in the queue both work. But for some reason there doesn't appear to be a good tool to get statistics on the sending IP addresses, only the origin and destination domains. Once you have determined the IP address which you want to purge, you can use the following spell. You might have to repeat the same line for active and incoming queues as well, but usually deferred is the queue I have the most mails. grep -lrE '[^0-9]10.20.30.4[^0-9]' /var/spool/postfix/deferred xargs -r -n1 basename postsuper -d - It's important that the IP address has escaped dots, because dots can account for any character. In the worst case it will end up matching a lot of wrong IP addresses. Another important bits are the '[^0-9]' groups in both ends of the pattern. Those make the IP address only match that particular IP address. Without that extra limitation 1.1.1.1 would match anything that has 1 as the last number in the first octet and 1 as the first number of the last octet. For example: 211.1.1.154 would be a valid match. The other important bit, yet oddly unknown, is the postsuper command. Postsuper modifies the queue and -d flag makes it delete files in the queue by QueueID. For some reason I keep on seeing all sorts of find -exec rm spells all over, which isn't really that nice for the daemon itself. So here it is, one more tidbit I've been meaning to write up for quite some time now. Enjoy!

Chris Lawrence: In which I admit I am a dork

Instead of doing something productive today, I spent the day in San Antonio at an OpenStreetMap mapping party. I got to meet some interesting folks and play OpenStreetMap teacher some, and it s nice to be reminded that at least one of my dopey childhood hobbies has some practical application in the real world. And of course I got to put some more miles on the new car, which was fun too. Thanks to the folks at CloudMade, and particularly their community ambassador, for putting the meeting together as well as for the swag. I can t quite figure out how they think they re going to make money off of OSM, at least until the OSM data gets in a lot better shape, but I suppose that s their problem and not mine.
By the way, for those who ve hung on until this point (or were actually looking for some useful OpenStreetMap advice), here s my GPSBabel recipe for converting NMEA track logs from my Amod AGL3080 GPS logger into GPX track logs that can be imported into OpenStreetMap: gpsbabel -t -i nmea -f infile.log -x simplify,error=0.0005k -x discard,hdop=6 -o gpx -F outfile.gpx Basically this throws out bad GPS fixes and simplifies all of the data to throw out any points that would deviate from the current straight line by less than 0.5 meters. At least with the Amod GPS unit once it s got a good fix it seems to stay pretty accurate, even with the static navigation feature off (using the SN OFF firmware), as long as you don t leave it somewhere under partial cover.

John Goerzen: Review: The Economist

A few months ago, I asked for suggestions for magazines to subscribe to. I got a lot of helpful suggestions, and subscribed to three: The New Yorker, The Atlantic, and The Economist. Today, I m reviewing the only one of the three that I m disappointed in, and it s The Economist. This comes as something of a surprise, because so many people (with the exception of Bryan O Sullivan) recommended it. Let s start with a quote from the issue that found its way to my mailbox this week:
A crowd of 2m or more is making its way to Washington, DC, to witness the inauguration of Mr Obama. Billions more will watch it on television. [link]
Every issue, I see this sort of thing all over. An estimate, or an opinion, presented as unquestioned fact, sometimes pretty clearly wrong or misleading. For weeks before Jan. 20, and even the day before, the widely-reported word from officials was that they had no idea what to expect, but if they had to guess, they d say that attendance would be between 1-2 million. In the end, the best estimates have placed attendance at 1.8 million. Would it have killed them to state that most estimates were more conservative, and to cite the source of their particular estimate? That s all I want, really, when they do things like this. I knew going into it that the magazine (to American eyes) essentially editorializes throughout, and I don t have a problem with that. But it engages in over-generalization far too often and that s just when I catch it. This was just a quick example from the first article I read in this issue; it s more blatant other places, but quite honestly I m too lazy to go look some more examples up at this hour. I do remember, though, them referring to members of Obama s cabinet as if they were certain to be, back before Obama had even announced their pick, let alone their confirmation hearings happening. One of my first issues of The Economist had a lengthy section on the global automobile market. I learned a lot about how western companies broke into markets in Asia and South America. Or at least I think I did. I don t know enough about that subject to catch them if they are over-generalizing again. The end result is that I read each issue with a mix of fascination and distrust; the topics are interesting, but I can never really tell if I m being given an accurate story. It often feels like the inside scoop, but then when I have some bit of knowledge of what the scoop is, it s often a much murkier shade of gray than The Economist s ever-confident prose lets on. Don t get me wrong; there are things about the Economist I like. But not as much as with the New Yorker or the Atlantic, so I ll let my subscription lapse after 6 months but keep reading it until then.

Russ Allbery: Lintian 2.2.0

We're still managing to keep to the weekly release cycle and put substantial changes into each version. This makes me happy. I'm hoping that we'll be able to keep slowly working the bug count down. This release merges quite a bit of work done by Raphael Geissert, most notably the addition of pedantic tags. Lintian has quite a few open bugs for checks that are useful in only some contexts or that check coding style issues that not everyone agrees with or wants to be bothered with, and we've been holding off on implementing those since I'd like to encourage everyone to enable info-level tags and I didn't want to just put them all in there. Now we have a new level, --pedantic, which includes all the picky stuff and the stuff that may be completely wrong. It's up to each maintainer whether to use --pedantic at all. The tags won't be in the default lintian.debian.org view (right now, they're not there at all). If you do use --pedantic, please don't worry too much about making your package pedantic-clean unless the tags really seem like a good idea. Also, as noted in the man page, adding overrides for pedantic tags is probably not worth the effort. You should look over the report and apply human judgement. I expect this mode to be useful for sponsors, who want to be alerted to possible issues but can decide for themselves which ones to mention. This release will also add a new page on lintian.debian.org that shows tags sorted by severity and certainty. Not only will this be useful for people looking for problems in the archive, it will also help the Lintian maintainers with updating severities and certainties. (For example, looking at the test page, I think a lot of the important tags should probably be serious instead.) I'm currently doing a full archive run from scratch with the new version to make sure that I plugged the memory leak problems that Lintian had before and to finish fixing #507849. Once that run finishes, I'll send a "bits from the Lintian maintainers" post to debian-devel-announce with information about the pedantic mode and the new tag page.

Dirk Eddelbuettel: New CRAN Task View on HPC

A while back, I suggested to Achim to add a new CRAN Task View for High Performance Computing with R. And as of a day or two ago, we now have the new CRAN Task View for High Performance Computing with R providing an overview about available packages, grouped thematically, with a focus on the various parallel computing application. I have already received a few great comments that even lead to an entire new section on applications. Keep'em coming!

24 January 2009

James Morrison: SimTower

I found a reference on the 'net about a week ago about SimTower. I remembered playing it a long time ago and thought it would be fun to try again since I hadn't beaten it. so I found my old copy and started playing. I've acheieved TOWER status in the game in 9 years.

The basic plan I used to beat the game was to build as wide as possible and to use 3 normal elevator shafts per 15 floors, 8 stairs and 2 escalators. Primarily my building was all offices. For the there are two sets of stairs going up 3 floors from each lobby. There is also an escalator going down from the lobby for each set of stairs and one more set of stairs going down a floor from the escalator. For the floors that have stairs going to them, there should be no elevator for that floor.

Now there are only 9 floors left that need elevator transportation. The best strategy I figured out for these floors was 3 elevators, each hitting 5 floors. That way each floor got one elevator shaft and a 3rd elevator shaft provided a bit of extra transport.

The 14th floor in each set is a good place to put cafes, and shops. I put a couple cafes and shops in, a security office at on one end, then put some offices in to use up some of the remaining space on the outside of the building. I left a bunch of space between the cafes and offices.

The first 15 floors are special since those floors should have 3 floors of offices, 6 floors of hotel rooms, one housekeeping station per floor, and a service elevator between the hotel floors. Then topped off with offices.

The basement floors had shops, cafes, restaurants and a cinema on floors b1 and b2. Parking was on floors b3, b4, and b5. The recycling centers were on floors b6 and b7, then the metro was on floors b8, and b9 with the metro taking up b10. I also put shops and cafes on floors b8 and b9 with the metro.

For the express elevator I tried to have on each express elevator go to the basement floors and 1 above ground floor. This way floor 15 and floor 30 has separate elevators shafts. Each elevator had as many elevator cars as it could take.

Using this strategy I used 63 above ground floors to get to 15k people and had 128 million dollars. I didn't lower the rent on any offices until I was building up to floor 100 for my cathedral, where I lowered prices on many offices between floors 45 and 60 where I did lower the price to keep tenants. I did lower the price on some hotel rooms much earlier in the game.

You can browse with my wide tower.

Kees Cook: debugging hangs in MIMEDefang

I spent a while this morning hunting down the root cause of a 100% CPU MIMEDefang process. (Turned out to be one specific email triggering one of my custom SpamAssassin rules that seems to get processed really inefficiently.) I wasn t able to find any documentation on how to debug where in MIMEDefang an email was getting stuck, and even jacking up the debugging output of my mimedefang-filter script seemed to imply it was happening late in the filtering process. After digging through mimedefang.pl, I found a status reporting subsystem and tracked it back out into configuration in /etc/default/mimedefang:
# Uncomment next line to have busy slaves send status updates to the
# multiplexor. NOTE: Consumes one extra file descriptor per slave, plus
# a bit of CPU time.
# MX_STATUS_UPDATES=yes
Turning this on, and then using md-mx-ctrl busyslaves (I command I didn t know existed until today either) I got to see exactly where it was stuck:
3 B 13380 (Running SpamAssassin j951iX1t025805)
Now I m having fun running md-mx-ctl with histo, barstatus, and load. :)

Adeodato Sim : Leonardo DiCaprio

Many things could be said about Leonardo DiCaprio. Today, he just deserves an entry in this blog for pulling out, at the age of 18, the character of Arnie Grape, the mentally challenged brother of Johnny Depp in What s Eating Gilbert Grape.

Brice Goglin: Debian/X.org notes - Howto Input-hotplug?

I have been wondering for a while how to get X.org "input-hotplug" to work, but I never actually tried before today. It is actually fairly easy, once you know what to do. Requirements First, make sure you have the evdev X driver installed (xserver-xorg-input-evdev). You might want to use X packages from experimental since things are much more recent than in Lenny or Sid these days, and upstream improved input management in the meantime. Then, if you are not running a pre-packaged kernel, check the the evdev driver is enabled and loaded in your kernel (CONFIG_INPUT_EVDEV). Telling hal what to do with input devices Now, you need to tell hal how to configure your input devices. Actually, you do not have much to do since latest xserver-xorg-input-evdev packages bring what you need. hal reads all fdi files under /usr/share/hal/fdi/policy to find out how devices should be configured. If you run lshal and look for input, you should see that the evdev is planned to drive your input devices. However, if you look at keyboard devices in lshal (look for input.keys), you will see that the US layout is used. To switch to another layout, you can add some overriding rules as a new *.fdi file in /etc/hal/fdi/policy/. For instance, to get French layout:
<?xml version="1.0" encoding="UTF-8"?>
<deviceinfo version="0.2">
  <device>
    <match key="info.capabilities" contains="input.keys">
      <-- Enforce XkbLayout=fr and XkbVariant empty -->
      <merge key="input.xkb.layout" type="string">fr</merge>
      <merge key="input.xkb.variant" type="string" />
    </match>
  </device>
</deviceinfo>
Thanks to this, you can enforce XkbLayout, XkbVariant and friends as usual in /etc/X11/xorg.conf. Don't forget to restart hal after modifying some fdi files. Then run lshal, and look for Xkb, you should find your setup there. Note that you can add some matching rules to configure some devices with different setups if needed. Just need to read the output of lshal and find something like a hardware identifier to match on. You can find some documentation about these rules by looking at the existing fdi files in /usr/share/hal/fdi/policy/20thirdparty/, and in the upstream x11-input.fdi (note that input.xkb.foo is the actual recommended syntax instead of input.x11_options.XkbFoo). Touchpads If you have a touchpad and want to use the synaptics driver, installing the xserver-xorg-input-synaptics will bring another fdi file. /usr/share/hal/fdi/policy/20thirdparty/11-x11-synaptics.fdi matches input.touchpad in the device capabilities in hal. Now the synaptics driver will be automagically loaded for your touchpad (instead of evdev for regular mice). Again, you can override this rule in /etc/hal/fdi/policy/ and you can add many configuration options for synaptics as well. See /usr/share/hal/fdi/policy/20thirdparty/11-x11-synaptics.fdi to get an example. Fortunately, you will not have to manually take care of the above /etc/hal/fdi/policy/ file for ever. The plan is to have hal look at the Debian console configuration and get at least the keyboard layout from there automatically. Telling the Xserver to talk to hal Now, you need to tell the Xserver to use what hal wants. Basically, you want to remove everything about keyboard, mouse and other input devices from your xorg.conf. Just drop all InputDevice sections and all references to them within other sections. With recent Xserver versions, options AllowEmptyInput and AutoAddDevices are enabled by default (otherwise, you might have to add them in the ServerFlags section). For more documentation, you want to read Peter Hutterer's blog, especially this post and this one. By the way, if you don't want this input-hotplug thing and you want to run a recent Xserver anyway, you should set AllowEmptyInput and AutoAddDevices to off in the ServerFlags section. Update: Fixed the way to manage fdi files, fixed the syntax of input.xkb.foo rules, added a paragraph about synaptics, and organized things in sections. Thanks to everybody's comment.
(Permanent link)

Next.

Previous.