Search Results: "ag"

30 October 2007

Martin F. Krafft: I am thinking of installing Windows

Did that title get your attention? Thought so. Now you have to read on as I explain! I am working on my PhD thesis and despite a bunch of gimmicks in place to help me with discipline (ha!), such as a pretty sweet mail filter setup (in need of further improvement), I end up distracted too often. For me, it's not the Internet which draws my attention, it's rather just Debian. As a developer, whenever I encounter a suboptimality (there are no problems with Debian!), I end up fixing it, or at least filing a bug report. Or I'll play around with my system and tweak things. I'd even argue that I am not playing around, actually, for I am good enough staying away from geeky fiddling and rather put proper fixes and enhancements in place. But those still consume time. Thus the idea of putting a second system with Windows installed wandered through my head in search of something to connect with. Yes, Windows, for one simple reason: I hate using it. So the theory goes that with Windows, I might actually stick with working on the thesis, trying to avoid touching that disgusting system otherwise. There are at least two (obvious) reasons why this isn't going to happen, any time soon at least: first, I am sure that the devil in me would find ways to kill time, and if only by cheating to obtain access to a Real operating system. Whether this is true, only a trial would tell. The second, and more important reason is that I have an important deadline coming up and anticipating the lovely whooshing sound it'd make zooming by is not an option. To get Windows up and running, and to have it ready for service, with LaTeX and Git and all the other tools I use properly configured, I'd have to invest 2-3 days, at least. And those I cannot afford at this stage. But the thought is now in my head. I hope you haven't just lost all your respect. I may actually be kidding. NP: Red Snapper: Prince Blimey

Benjamin Mako Hill: Post Deleted

Perhaps my favorite article in Wikipedia, the List of homophonous phrases, was deleted from Wikipedia in mid-August. Those arguing for deletion claimed that it was original research and were, I suppose, correct in that designation. But that doesn't make me happy to see it go. I asked an admin to move the list into a temporary home in my userspace until I can find a better home for it. Please help me find one and I'll redirect. It's the latest in several unfortunate deletions I witnessed recently. I created a humorous "undeletionist" barnstar to give to an admin for undeleting some humorous project pages in Wikipedia (which have since been redeleted, but copied first). My barnstar was also deleted. In retaliation for this all, and in good fun, I proposed the Association of Deletionist Wikipedians for deletion. The delete tag stuck around for a week until it was deleted under suspicion that it might be a joke. True enough. On the other hand, I have similar suspicions about the subject of the article.

MJ Ray: More cut-and-paste browser fun: message-id search engine

If you use a firefox-based browser, bookmark http://mid.gmane.org/%s then right-click it in your bookmarks menu, pick Properties and enter "message-id:" in the Keywords field. Then you can paste Message-Id lines from email headers (or some debian list posts) into your browser window and it will search gmane for it. Handy. (2007-10-31: 1 comment)

Jan Wagner: Too much coffee

… it’s a old, but matchs the actual complex of some discussions in the country where I actualy live.
Terrorism

Marc 'HE' Brockschmidt: No DPL campaigning to see, please move along

Even though Adrian von Bidder suggests that I'm starting a bit early with the DPL campaigning, I thought I could add a few more thoughts to the blagosphere.

Adrian suggested to make the discussion of our of "vision of Debian" a regular event on debconf - I think it's a nice idea, but that doesn't mean we should keep silent about that topic the rest of the year. I think one of the problems we see in Debian is that we are missing an aim to strive for. We are currently just moving from release to release, while more and more developers have actually lost interest in stable releases. The impression that a common ground like Debian 4.0 is irrelevant seems to prevail, because the people most vocal in our user base usually want to see the newest and shiniest software on their desktop. We have been spending more and more effort to cater to their wishes and have ignored the fact that a majority of Debian-based installations are not run by such people, but by system administrators who do mass roll-outs and neither want nor need the newest X.org with more *bling*.

Ubuntu, the biggest Debian-based distribution, has found its users by packing up new software behind a nice installer, adding some branding elements and then shipping it. Stability is an issue for Ubuntu, but they don't spend as much time as we do on eliminating the last seemingly important bug in some esoteric software package before actually releasing. That observation is the ground for one of my ideas: Our current metric to determine how far testing is away from a release is counting the number of rc bugs - it doesn't matter if the rc bug is X.org crashing for all people or if it is a policy violation in a package with 12 users. Perhaps we should start thinking about a new metric, keeping in mind that for a majority of users, some bugs matter a lot and some matter not at all. With the release of etch, the number of installations of popcon has risen a lot, so for the first time, we have actual usage data that could help us with such a metric. There are a few problems with that approach, though:

I don't have more time right now, so the rest of my ideas will follow in the next few days, so stay tuned or add me to your killfile.

John Goerzen: Review: Terk TV38 Antenna

Last year, as we were planning our move, I knew we would need to buy a new TV antenna. According to AntennaWeb (a very useful site), we are in the violet (or "fat chance") zone for several TV stations. Add to that the fact that we have a tin-covered building pretty much in the direct path to several of the transmitter. Metal buildings often cause "multipathing", where a signal bounces off buildings and arrives multiple times at the antenna. This causes ghosting on analog signals and can cause problems getting a signal lock on digital ones. We also have a fairly long run from the antenna to the receiver (a MythTV box) and are wanting to receive digital signals. Not only that, but the TV transmitters are in different areas about 40 degrees apart, and most high-gain antennas are also highly directional. So it's a difficult situation.

So in our situation, an outdoor antenna is a must. At our old place, we had used the best outdoor antenna Radio Shack sold. Despite having more friendly reception conditions, it didn't work well.

After a good deal of research, I bought a Terk TV38 outdoor antenna from Amazon. It comes with:


It comes with the hardware you need to mount it in an attic or attach it to an exterior wall or chimney in most situations. However, we wanted to attach it to the roof directly, so we purchased a tripod mount from RadioShack for that purpose. I had also purchased some quad-shield RG6 coax from Cat5ECableGuy.Com.

I assembled the antenna on the ground. That took some time, but wasn't difficult. But this was in winter, a fairly wet winter, and I knew that weather wouldn't cooperate well enough for us to get the antenna up on our roof safely some Saturday for a few weeks. So I thought I'd just leave the antenna on the ground for a little while, hook it up, and see if we get anything. I put it on the ground, aimed it about in the middle of the TV transmitters, and went to set up the MythTV.

I was shocked to discover that, even with the antenna on the ground, I got a perfect digital picture on all channels but one. Once we got the antenna mounted on the roof, reception has been perfect. I've had no need for actuators (to rotate the antenna) or amplifiers. Just the antenna itself, even with the long coax run, has performed quite well.

For anyone that needs an outdoor antenna, I highly recommend the Terk TV38.

Andrew McMillan: Getting Blood from a Stone

Last week I installed Ubuntu Gutsy onto Heather's laptop. While Gutsy seems to be an easy task for most situations, installing it onto a Pentium 366 laptop with 200M of RAM and (particularly) an 800x600 screen was harder than it perhaps should have been. I'm sure that most installations these days aren't 800x600, but the graphical installer in Gutsy seems determined to make this painful. I had to move the toolbars to the sides of the screen, and then I could see the top half of the buttons on each page. It was like the page was sized for 600 vertical pixels, but the designer had forgotten about toolbars and title bars - not that I could see any screens in the process I followed that needed more than 5/6 of that screen anyway. Eventually I got it installed, and it even seemed to run OK once we booted into it. That's "OK for a 200M P366 with an 800x600 screen" though. Looking around at the price of a new laptop made putting up with that sort of performance a whole lot less palatable. The Acer Aspire 5310 (with free RAM upgrade) was $898 at Dick Smith, with a $99 cashback offer. A quick google shows that it's using the Broadcom 43xx wireless which isn't even close to being the best, but can be made to work with Linux. Everything else seemed likely to work, so we bought it. Installing Gutsy on it was nearly trivial, though I had to install bcm43xx-fwcutter on a different PC (my laptop, which is running Debian, in fact) to get the firmware for the WLAN before I could get the wireless working. I'm surprised that Broadcom still don't make that firmware publicly available somewhere, rather than forcing people to jump through the sort of hoops that would get them wanting an Intel chipset next time. Anyway, everything installed very easily, and the laptop is working quite nicely. Strangely neither sound, nor suspend to ram are working out of the box, but perhaps I'll get them going in due course. They're not so important in this case fortunately, but perhaps in due course I'll try and get them working and post some details about it. Much harder has been getting the fabled 'cashback' from Acer. I think I now know what I'm being paid $99 for. Firstly the only way to get your cashback is by registering through a webpage. Heather's first attempt to do this resulted in an error from our proxy about a malformed request, so I got called in. I tried registering using on my laptop, but couldn't even get to the cashback page. I then tried using IE6, with similar results. So perhaps it's my PC? I tried using a different PC, with the same result again! We tried ringing them up, but they were absolutely determined that (even after 20 minutes on the phone) they were not going to accept that information over the phone. So the only way to get the cashback from Acer was via their thoroughly broken website. Even their Contact Acer page is broken in firefox just showing a blank. Firefox users need not apply. Eventually, while spending some time in front of Heather's main computer (which had made it all the way through to submitting their on-line form before failing) I realised that the error she was getting was a proxy error from some in-form javascript submitting an invalid request, so I disabled the proxy, the form finally worked, and I managed to apply for the cashback. Now we just have to send the printed form in, along with some blood from our firstborn, the ashes of my grandmother, various barcodes, receipts and toenail clippings and we're sweet. They say they'll send us some money within 30 days. I think we should maybe frame it or something. I just know I'm going to feel really inclined to take advantage of cashback offers in future. In Other News: DVD Slideshow Meanwhile I've been playing with DVD Slideshow which seems to be just what my parents have been after for a while, so they don't have to keep their favourite photos on the camera to be able to show them off on someone's TV. It's great! At least it is great now after I changed all the calls to ffmpeg to add a 'k' after the bitrate parameter. But that's Open Source Software, I guess. I'll send a patch to them... :-)

Theodore Ts'o: Tip o the hat, wag o the finger Linux power savings for laptop users

It’s interesting to see how far, and yet how much more work we need to do on power management for Linux. I recently got a new laptop — a Lenovo Thinkpad X61s — and using the powertop tool, I was able to configure my system to the point where in what I can “airplane mail reading mode” (mailbox preloaded into memory, USB disabled, wireless and ethernet disabled, backlight down to 30% brightness, sloppily written power hogs like Firefox and Notes — every single application writer should be forced to run powertap and explain why their program feels it necessary to constantly wake up the CPU), I can get my usage down to about 9.8 watts. Using the 8 hours extended battery, that’s 8 hours of battery life, although granted doing very little. On the flip side, if I’m doing a major kernel compile, I can drive up utilization up to almost 30 watts, which means less than 3 hours of battery life. So that’s definitely the good news; Linux can sharply reduce its power consumption to the point where it is highly competitive with Windows. (And probably better than Vista, just because that OS is so heavy and bloated.) So thanks and and a tip of the hat to Intel and to Arjan van de Ven for making such a useful tool like Powertop available. So now for the bad news. Getting down to this level of power saving thriftness, where the laptop is carefully sipping only the minimal amounts of power from the battery, is definitely a work in progress. First of all, you can only get this level of power savings by unloading a specific USB driver, uhci_hcd. This will disable low speed devices (including unfortunately the fingerprint reader and the EVDO WWAN device if you were silly enough to buy one that was built into the laptop as opposed to a stand-alone card that you can swap between laptops and lend out to friends as necessary). But how many users are going to open up a terminal window, su to root and type the command “rmmod uhci_hcd”? And know how to reload the driver using “modprobe uhci_hcd” when they need to use the USB devices again? A similar problem exists for Network Manager; when the user disables the network by right-clicking on the applet, why doesn’t it automatically bring down the interface, instead of forcing the user to manually su to root and then type the command “ifconfig eth0 down; ifconfig wlan0 down”? A more serious problem is the Intel Wireless driver for the 4965. Even with the wlan0 interface configured down, and with the RF kill switch enabled, keeping the iwl4965 driver loaded will still cost you an extra full watt of power. When you’re down to 9.6 watts, that means that keeping the iwl4965 driver loaded when you don’t need it will cost you a 10% reduction in your battery life! That’s just sloppy, and hopefully it will be fixed in a future update to the iwl4965 driver, but as long as you don’t mind manually removing and reloading it, you can work around this power-saving oversight. A bigger issue, though, one for which no workaround exists, is that unlike the ipw3945 drivers, which at least had private, non-standard iwpriv commands to engage the 802.11’s power-saving features, the iwl4965 driver has neither the non-standard Intel iwpriv interfaces, nor the standard iwconfig interfaces for enabling any kind of powersaving features, including changing the transmit power of the card. So while powertop deserves plenty of kudos, iwl4965 deserves a wag of the finger from a power saving viewpoint. No doubt Intel just needs to allocate more money to its Open Source Technology Center so it get more of its crack developers to work improving Linux support for their processors and chipsets. Speaking of which, I’m still waiting for an Intel x.org 965GM driver that can support compiz/beryl and simultaneously show video clips at the same time… And being able turn off the 50 interrupts/second generated by the video card when they aren’t needed because 3-d graphics aren’t currently in use, without requiring a restart of the X server, would also be a nice touch. The bottom line is that Linux power savings and Linux support for laptops in general is much better than it was a year ago, and a lot of credit has to go to the efforts of Intel’s teams producing such good work as powertop, their wireless drivers, and their open X server drivers. We still have a lot of work left to be done, though!

29 October 2007

Andreas Schuldei: Random Acts of Kindness

Some time ago a friend of my sister in law contacted me and offered his services as a courier for gifts. I had told him that I knew someone in Israel and he was traveling to Sweden. So I contacted Lior with the strange proposal to give me a gift (and I promised to return the favour). A few days later I got a book about Israel from Lior, was very happy and started to ponder what kind of present could be fun and entertaining for him. I ended up going to the supermarket and bought all kinds of special swedish food (and obviously skipped some). I wrote some short notes with cooking instructions and explanations and sent the whole lot back to Israel.

I enjoyed both getting the present, reading the book and picking a present for someone I regard highly. I would like to recomment this as a fun game within Debian: If you know someone traveling abroad find out if there is a DD (or Debian contributor) around at the destination and send a present to that person. This kind of love bombing is low cost and lots of fun and creates bonds parallel to those of the Web of Trust. Try It!

Yves-Alexis Perez: Two years

Today, it's been two years I'm stuck in the NM queue. I've registered on oct 24, 2005, because Sam Hocevar told me that it could last a little, so if I was interested I should register early. I wondered for a long time if I should resign on this two years birthday, but I dropped this eventuality. I still want to be a Debian Developer, and if I resign I don't think I'll really want to still work on Xfce packages. But on the other hand I wouldn't really like to use an Xfce not packaged by me (no offense, but I guess I'd still want to hack on it) and I don't think I would be able to be on another distro. So I'm still there, sitting in NM queue, waiting for the next step. The only required step to be accepted as a Debian Developer is to have its gpg key added to the debian keyring (then an account is created on debian boxes, there's a -private subscription etc.). This is done by a team, called DAM, "Debian Accounts Managers". Because at one time they had a lot of work, they could not examine each candidate and decide if he was a potential good Debian Developer, so people imagined the NM Process: some volunteers would help them asking questions to candidates, then write a report, so DAM would only have to read it and decide if it was ok or not to create an account. I've already passed this step. I am "DAM Approved". One could imagine that, if the Debian *Accounts* Managers reviewed and approved my application, the account creation should follow. But no, the next step (according to NM pages) is "DAM creates account or rejects application". The problem here is that there is no "DAM Team", responsible for Debian accounts, but various people which are not really equivalent in this team. This is really a problem in Debian, where teams aren't really a "team". Not every team I guess, but in some cases one can trust a team to do a job. Debian is a volunteer organisation, so people think nobody can be forced to do a job if he doesn't have time to it. I'm fine with that, real life can be really time-consuming sometime. But my opinion is that teams may have to be forced to do their job. If nobody in the team has time, fine, it means somebody should join the team. But the team itself shouldn't fail, and this should be the only thing visible from outside: the "team", and the team actions. There are some proposition about this on lists at the moment, but I don't really know how it'll end. It's not easy doing social stuff, there's a lot of people involved, with many different views. But sometimes the consensus is *not* findable, and sometimes, somebody has to decide. That's why why need team leaders, and that's the project leader role. I guess people are quite opposed to have a "strong" leader in a volunteer organization, and I don't have concrete proposals but I really thing team management is not really perfect and a lot of people (users and developers) suffer from that (not only NM applicants, I mean) and from "elephants". As I said, I have no good solution, nor even concrete proposals (except "sometimes we need a leader to make decisions") but I really think there are things Debian (as a project) needs to improve.

Martin Zobel-Helas: It feels so good to know

…that good friends of mine, who are a couple for several years, are now engaged.

Lior Kaplan: Debian Installer Hebrew translation reached 100% for levels 1-4

Today I noticed that the d-i translation to Hebrew reached 100% at levels 1-4 on the SVN. This is the first time it happens for levels 3-4 since I started the translation back at 2004. Although the Hebrew translation started as a personal project, in the last 9 months I got help from several people: Amit Dovev, Baruch Even, Katriel Traum and Meital Bourvine. With this joint effort, level 1 was reviewed for typos and levels 2-3 were completed. Thanks you all. As level 5 contains too much technical (error) messages, I decided not to invest time with its translation. So from now on it’s mainly keeping the status quo of translation rate for Hebrew… When Christian suggested to translate d-i to Hebrew:
> Lior Kaplan
> Israel Ahem, by the way….Hebrew installation is missing…:-)
I didn’t imagine reaching this point, as the translation started without any bidi (BiDirectional) support for d-i. Only after Debconf4 I could actually read my translations in d-i’s nightly builds:
We can also mention that hard work was made on BiDirectional languages support, mostly by Steve Langasek, which was jailed by myself for some nights in the “d-i hack lab”… :-).
Working on the translation later triggered more contribution for Debian, which later made me start the NM process. So please “blame” Christian for me becoming a DD (:

Piotr Roszatycki: New YADA released.

I made a new release of YADA, the packaging helper different than others. New version of YADA supports Homepage field in debian/control file which appeared in dpkg last time. Wow. The YADA supported Home-Page field many years ago. YADA is very different that other Debian packaging helpers. Most important is that no Makefile have to be edited at all. This is the strongest and the weakest point of the YADA. People loves it or hate it. Some people even have a vendetta against YADA. Other people find the tool is very simple. Well, I think the YADA is some kind of prosthesis for native Debian packaging system, but even this prototype is much better than any Makefile-based aids just because I don't need to edit any Makefile. YADA had a black PR and much of bad FUD. There was opinion that it violates Debian policy, it is problematic for NMUs and security updates and maintaining of Debian patches is very difficult. This tool is very powerful and has some pitfalls but it doesn't mean it is evil by design. I really don't know how to make i.e. the iceape-l10n package without using YADA and its macro engine. It have to be more complicated and with much redundancy for metainformations. I think I could switch from YADA to another packaging tool, but please... Just create it! :)

Miriam Ruiz: Journalists avoiding writing about Free Software?

Some people around Free Software tend to be too enthusiastic and very critical, both with themselves and with other people. Whenever Linux or Free Software appear in the media, people who wrote the articles are severely and merciless attacked, and the criticism is not always constructive. It might be hard to properly talk about these topics in a non-technical magazine or newspaper targeted towards the mainstream population, not only because they have to explain it in an understandable way for non-initiated people, but also because they’re usually very limited in space. Thus, many times the articles are inaccurate or incomplete, not always being a journalist’s fault, but also of the conditions in which the article has to be published, as well as the time they have to develop it. Someone, a journalist, told me this last weekend that she tries to avoid writing stuff about Linux herself due to the harsh attacks she’s subjected to from the Linux and Free Software activists as soon as she publishes anything on that topic. I kind of understand that. It might be the same than when you write a program and release it as Free Software, and then some people get too demanding and aggressive towards you for not having done a perfect program and submitting to their wishes, instead of thinking about the effort invested in what is done. I seriously think that we might be losing a lot of power and strength if we attack so much the media that support us than they fear us enough to avoid these topics. We’re on the same team, and it wouldn’t be so bad to be a little understanding and supporting of them, and rely on constructive and friendly criticism instead of treating them as if they were the enemy. They also have feelings, you know.

David Moreno Garza: Saturday

Last Saturday, we attended a party at stew and rcox’ place in Brooklyn. Biella, Micah, Clint and a bunch of other people were also there. It was very nice and we had a lot of fun. I had the chance to tell Clint that some of his blog postings really intrigue me; I now feel relieved. Besides, I’ve learned that boxing against Micah on the Wii is so tiring that even days after, my arms and back still hurt :-( We left at around 1:45 am.
On our way back to Harlem, we stopped to have some tacos at El dolo on the 8th Ave and the 14th St, as Kevin suggested me before; for our surprise, they were amazing and have been so far, the best Mexican food we’ve had in NYC :-) So, after getting off on the 145th station and walked nine blocks, we arrived to our warm place at 4:30 am.

Russell Coker: New SE Linux Play Machine Online

After over a year I have finally got a SE Linux Play Machine online again. The details for logging in are at this link [1]. I’ve created T-shirt and mug designs with the login details too, they are on cafepress.com LINK [2]. For fun wear such a shirt to a conference (or even when shopping at your local electronics store. ;)

Stefano Zacchiroli: vcs browse is a typo

"Vcs-Browse" is a typo ("Vcs-Browser" is correct) Romain, "Vcs-Browse" is a typo (having "Vcs-Browser" as its correct version), at least according to the documentation I wrote a long time ago (unfortunately not yet integrated in the devref ...). So dpkg is right in supporting "Vcs-Browser" and the 52 packages you've found need to be fixed. Being a maintainer of one such packages (I don't know if I actually am), I wouldn't mind a mass-bug filing (priority wishlist of course) about that.

Ian Wienand: Non-thread safe C

Recently it has come up on the LKML and other blogs about how C is not thread safe. The nice piece of example code given is
int trylock()
 
    int res;
    res = pthread_mutex_trylock(&mutex);
    if (res == 0)
            ++acquires_count;
    return res;
 
At first glance it seems OK, and I wasn't exactly sure what the problem was until I pulled it apart. GCC is well within its rights to produce the following code (annotated for clarity).
push   %ebp                     ; setting up stack frame
mov    %esp,%ebp                ; save esp to ebp
sub    $0x8,%esp                ; make some room on stack
movl   <mutex>,(%esp)           ; copy mutex to stack
call   <pthread_mutex_trylock>  ; call pthread_mutex_trylock
mov    <acquires_count>,%edx    ; copy acquires_count to %edx
cmp    $0x1,%eax                ; set carry flag if result == 0
adc    $0x0,%edx                ; add with carry
mov    %edx,<acquires_count>    ; write back acquires_count
leave                           ; release stack frame
ret                             ; done!
This code uses a bit of a trick to avoid a branch around code. It uses the carry flag, which is simple enough to understand when adding. Consider if you are adding 0001 + 1111 you end up with 11111, where the top bit is the carry bit. You can then feed this carry bit into another part of the addition operation if you were, say, using two 32 bit numbers to represent a 64 bit number on a 32 bit system. The trick uses the dual nature of the carry flag as a "borrow" bit; if a < b when a - b then the bit is set. Consider the simplest case of 0 - 1 -- the carry bit is set to indicate to the next operation that a bit needs to be borrowed. Imagine for a moment we have a four bit machine and want to do the 8-bit unsigned operation
1111 0000 -   (240) -
0000 0001     (  1)
==== ====
First we do 0000 - 0001 which leaves us 1111 with the borrow bit set. Then we do 1111 - 0000 but take note that the borrow bit is set, so get rid of the borrowed bit, leaving us 1110. Putting the two together gives us 1110 1111 or 239. Therefore the cmp $0x1, instruction (which is really just result - 1 with no output but setting flags) can only set the carry flag (i.e. borrow a bit) if the value is 0; any other value in result means there will be no need to borrow and the carry flag is not set. Consequently the add with carry (adc) will add one to the result only if the carry bit was set. A neat trick which avoids a jump, but not so much thread safe: if you are interrupted after the cmp but before the mov store you can write back the wrong value. Most people (including me till 5 minutes ago) looking at the code would assume that it was safe on the theory that acquires_count is not touched if you don't have the lock because it is inside the if statement. Interestingly, the Intel compiler does the simpler jump method
push   <mutex>                     ; push argument
call   <pthread_mutex_trylock>
pop    %ecx                        ; get return addr on top
test   %eax,%eax                   ; AND %eax,%eax
jne    <trylock+0x16>  --------+   ; if that wasn't 0, jump out
addl   $0x1,<acquires_count>    
ret                    <-------+   ; done!
Frankly I have no idea which one is faster/better (I would guess the second one because you don't always dirty a cache line, but you'd have to measure that against the cost of the branch) but obviously GCC thinks one thing and Intel thinks another and I bet if you put them in a room together you would end up with 3 opinions! I think the major point is that once upon a time it was mostly people writing kernels doing things like accessing I/O ports or other memory mapped areas that needed to be very careful the compiler didn't optimise out (or in) something incorrectly. With multi-threaded C code that problem moves up to the application developer too. A different instruction set can help here. The Itanium version is possibly less prone to this sort of thing because predication makes it faster to implement conditional branches -- any instruction with a predicate that is not set is skipped. The load and add is safe because it will only be done with the lock held. However, if anyone is wondering why Itanium come with such big caches, the difference between the 6 line version and the Itanium version below should answer that.
 [MII]       alloc r32=ar.pfs,4,3,0               ; alloc stack frame
             mov r33=b0                           ; return pointer
             mov r34=r1
 [MMI]       addl r14=72,r1;;                     ; r11 = &mutex from GOT
             ld8 r11=[r14]                        ;
             nop.i 0x0;;
 [MIB]       mov r35=r11                          ; put into argument 1
             nop.i 0x0
             br.call.sptk.few b0=<pthread_mutex_trylock>
 [MII]       cmp4.eq.unc p0,p6=r8,r0              ; if result !0, set predicate p6
             mov.i ar.pfs=r32
             mov r1=r34;;                         ; load acquires_count from GOT
 [MIB]       addl r10=144,r1                      ;
             nop.i 0x0
       (p06) br.cond.dptk.few <trylock+0x80>;;    ; jump to [1] if p6 set
 [MII]       ld4 r9=[r10]
             mov b0=r33
             addl r3=144,r1;;
 [MMI]       adds r2=1,r9;;                       ; acquires_count++
             st4 [r3]=r2                          ; save updated value
             nop.i 0x0
 [MIB]       nop.m 0x0                            ; [1]
             nop.i 0x0
             br.few <trylock+0x90>;;              ; jump to [2]
 [MII]       nop.m 0x0
             mov b0=r33
             nop.i 0x0;;
 [MIB]       nop.m 0x0                            ; [2]
             nop.i 0x0
             br.ret.sptk.many b0;;
I guess the moral of the story is that multi-threading is hard, but we knew that anyway.

Gunnar Wolf: Sixth Ciclot n - Finally!

I just love my city.
Mexico City, chaotic, unknowable, imposible to understand, so huge, so varied, so broken, so feared, complex, unique... I think few people realize how easy it is to fall in love with this city, to drink its beauty, which leaps up always when you least expect it. Today, it was a good day for loving it. For one thing or another, I've missed the five previous ciclotones, which are held on the last Sunday of each month, 7:00 to 14:00. Today, finally, I made it.
What is it? It is a 32 Km route circling roughly around the mid-South and Center of Mexico City:

The weather is abnormally cold lately in Mexico City - We have reached temperatures around 5 Celsius in the last two weeks, which is agreeable for December/January, but certaiunly not for October. Anyway, today it was quite chilly from the early morning. I did this ciclot n on my own, as Gaby is out of town - I left home at around 11:30, and headed North towards the nearest point of the route, ~5Km north from here (Circuito Interior and Universidad). The chosen circuit is quite good and varied. And quite enjoyable, too.
And how did I fare? Well, not bad at all, I think... I did the ~37Km (32Km of the Ciclot n, plus the ~5 to get there - I came back by metro, as I was already too tired to be alert while driving in the traffic) in 2hr 13 minutes. According to my trusty Polar watch, I used 1831 Kcal (which is a bit less than what I eat per day), averaging at 138 heartbeats per minute.
Very enjoyable. This is one of the ideas that I most like that have been promoted by our local government: As Mexico City citizens, we need to claim back our streets. Also, we have to be responsible and think about different ways of moving around than by burning gasoline - Biking is fun, and it is not riskier than driving or walking. Try it!

28 October 2007

Michael Prokop: Failed to bring up mika.

No, not running out of coffee (well, maybe) - but:
# ifup wlan=mika
[…]
No DHCPOFFERS received.
No working leases in persistent database. Exiting. Failed to bring up mika.
:grin:

Next.

Previous.