Here a very nice video tutorial about how to add AdSense to make money with your blog, and Google Analytics to get statistics from your blog. Both are free services.
AMD’s quad-core Opterons have been notably difficult to find since their introduction two months ago, and there are many reports about a chip-level problem has impacted the supply of these chips to both server OEMs and distribution channel customers.
AMD refer to chip-level problems as errata. Errata are fairly common in microprocessors, though they vary in nature and severity. This particular erratum first became widely known when AMD attributed the delay of the 2.4GHz version of its Phenom desktop processor to the problem. Not much is known about the specifics of the erratum, but it is related to the translation lookaside buffer (TLB) in the processor’s L3 cache. The erratum can cause a system hang with certain software workloads. The issue occurs very rarely, and thus was not caught by AMD’s usual qualification testing.
An industry source at a tier-two reseller told that the TLB erratum has led to a “stop ship” order on all quad core Opterons. When asked for comment, spokesman Phil Hughes said AMD is shipping quad core Opterons now, but only for “specific customer deals.” Industry sources have suggested to TR that those deals are high-volume situations involving supercomputing clusters. Such customers may run workloads less likely to be affected by any workarounds for the erratum that reduce L3 cache performance, and those customers could potentially consume hundreds of thousands of CPUs. The current availability picture would seem to confirm, that quad-core Opterons are not shipping to OEMs or the channel more generally.
Here a nice video tutorial 45 minutes long, which explain in details step by step how to blog using WordPress.
When a Security Strategy Director at Microsoft decided to compare Internet Explorer security vulnerabilities with those of Mozilla Firefox, he may have forgotten that the Head Security Strategist of Mozilla was a former MS employee. In a rebuttal of the study, which finds IE more secure than Firefox, Mozilla said that the number of vulnerabilities publicly acknowledged was just a ’small subset’ of all vulnerabilities fixed internally. The vulnerabilities found internally are fixed in service packs and major updates without public knowledge. ‘For Microsoft this makes sense because these fixes get the benefit of a full test pass which is much more robust for a service pack or major release than it is for a security update. Unfortunately for Microsoft’s users this means they have to wait sometimes a year or more to get the benefit of this work. That’s a lot of time for an attacker to identify the same issue and exploit it to hurt users.’
As part of its ongoing effort to keep a clean index Google is soliciting the help of web browsers to let them know when we find malware in the index (you can read about it in this post). Celebrated Google hacker Johnny Long thinks it’s a good idea, though he told the site Internet News that he doesn’t think it’ll stop real hackers. From the article: ‘Most in search of malware for offensive use know the good stuff — it ain’t distributed through public Web … It’s distributed through dark Web servers, peer-to-peer networks, IRC channels, torrents and the like. Google’s efforts will not affect how skilled hackers get access to malware.’
The BBC long time user of Perl in its public websites, and after the successfully deploy of Ruby on Rails for internal websites, took the decision to fused the two by creating a ‘Perl on Rails‘ that has the advantages of rapid development that Rails brings, while performing well enough to be used for the Beeb’s high-traffic public websites. This is already powering one of their websites, and is set to be used in the controversial iPlayer project as well
Firefox 2.0.0.11 has been released, the Release Notes show the only major change as a correction of a compatibility issue with some websites and extensions as discovered in Firefox 2.0.0.10
Coders working on Wine for Mac have found that the Mac loader has gained its own undocumented ability to load and understand Windows Portable Executable (PE) files. They found PE loading capabilities in Leopard that weren’t there in Tiger. Further dissection showed that Apple is masking references to *Win* and *PE* in the dll, which means it’s not an accidental inclusion. Is Apple planning native PE execution within OSX?
Subscribe to my feed
