Day: December 11, 2012

California law enforcement moves to buy drones, draws controversy

UAV set up for Wylye intersection. QinetiQ group Since Congress passed legislation in February ordering the Federal Aviation Administration to fast-track the approval of unmanned aerial vehicles—more colloquially known as drones—for use by law enforcement agencies, police and sheriff departments across the country have been scrambling to purchase the smaller, unarmed cousins of the Predator and Reaper drones which carry out daily sorties over Afghanistan, Yemen, and other theaters of operation. Alameda County in California has become one of the central battlegrounds over the introduction of drones to domestic police work. Earlier this year , Alameda County Sheriff Gregory Ahern raised the hackles of local civil libertarians (and there are quite a few of those in the county, which encompasses Berkeley and Oakland) by declaring his intention to purchase a drone to assist with “emergency response.” According to Ahern, Alameda Sheriff’s personnel first tested a UAV in fall 2011 and gave a public demonstration of the machine’s usefulness for emergency responses during the Urban Shield SWAT competition in late October. Were Alameda County to purchase a drone, it would set a precedent in California, which has long been an innovator in law enforcement tactics: from SWAT teams (pioneered in Delano and Los Angeles) to anti-gang tactics such as civil injunctions. The first documented incident of a drone being used to make an arrest in the United States occurred in North Dakota in June 2011, when local police received assistance from an unarmed Predator B drone that belonged to US Customs and Border Protection . The Federal Bureau of Investigation and Drug Enforcement Administration have also reportedly used drones for domestic investigations. Read 7 remaining paragraphs | Comments

Read this article:
California law enforcement moves to buy drones, draws controversy

Samba 4.0 Released: the First Free Software Active Directory Compatible Server

Jeremy Allison – Sam writes “We released Samba 4.0 today, containing the first compatible Free Software implementation of Microsoft’s Active Directory protocols. ‘Samba 4.0 comprises an LDAP directory server, Heimdal Kerberos authentication server, a secure Dynamic DNS server, and implementations of all necessary remote procedure calls for Active Directory. Samba 4.0 provides everything needed to serve as an Active Directory Compatible Domain Controller for all versions of Microsoft Windows clients currently supported by Microsoft, including the recently released Windows 8. The Samba 4.0 Active Directory Compatible Server provides support for features such as Group Policy, Roaming Profiles, Windows Administration tools and integrates with Microsoft Exchange and Free Software compatible services such as OpenChange.'” Full release notes are available, and you grab the files from the download page. Read more of this story at Slashdot.

See more here:
Samba 4.0 Released: the First Free Software Active Directory Compatible Server

Skeleton Muscle Bot Brings I, Robot’s Future One Step Closer

Eerily reminiscent of the design of Sonny and the other NS-5s in I, Robot , Kenshiro is the University of Tokyo’s latest attempt to create a humanoid robot that accurately mimics human movement. And the researchers there believe the best way to build an artificial human is to simply copy our anatomy, particularly our muscular and skeletal systems. More »

Visit site:
Skeleton Muscle Bot Brings I, Robot’s Future One Step Closer

Linux 3.7 Released

The wait is over; diegocg writes “Linux kernel 3.7 has been released. This release adds support for the new ARM 64-bit architecture, ARM multiplatform — the ability to boot into different ARM systems using a single kernel; support for cryptographically signed kernel modules; Btrfs support for disabling copy-on-write on a per-file basis using chattr; faster Btrfs fsync(); a new experimental ‘perf trace’ tool modeled after strace; support for the TCP Fast Open feature in the server side; experimental SMBv2 protocol support; stable NFS 4.1 and parallel NFS; a vxlan tunneling protocol that allows to transfer Layer 2 ethernet packets over UDP; and support for the Intel SMAP security feature. Many small features and new drivers and fixes are also available. Here’s the full list of changes.” Read more of this story at Slashdot.

Continued here:
Linux 3.7 Released

Why Gmail went down: Google misconfigured load balancing servers

Portions of the Internet panicked yesterday when Gmail was hit by an outage that lasted for an agonizing 18 minutes . The outage coincided with reports of Google’s Chrome browser crashing. It turns out the culprit was a faulty load balancing change that affected products including Chrome’s sync service, which allows users to sync bookmarks and other browser settings across multiple computers and mobile devices. Ultimately, it was human error. Google engineer Tim Steele explained the problem’s origins in a developer forum : Chrome Sync Server relies on a backend infrastructure component to enforce quotas on per-datatype sync traffic. That quota service experienced traffic problems today due to a faulty load balancing configuration change. That change was to a core piece of infrastructure that many services at Google depend on. This means other services may have been affected at the same time, leading to the confounding original title of this bug [which referred to Gmail]. Because of the quota service failure, Chrome Sync Servers reacted too conservatively by telling clients to throttle “all” data types, without accounting for the fact that not all client versions support all data types. The crash is due to faulty logic responsible for handling “throttled” data types on the client when the data types are unrecognized. If the Chrome sync service had gone down entirely, the Chrome browser crashes would not have occurred, it turns out. “In fact this crash would *not* happen if the sync server itself was unreachable,” Steele wrote. “It’s due to a backend service that sync servers depend on becoming overwhelmed, and sync servers responding to that by telling all clients to throttle all data types (including data types that the client may not understand yet).” Read 4 remaining paragraphs | Comments

Read More:
Why Gmail went down: Google misconfigured load balancing servers

TSMC and Global Foundries Plan Risky Process Jump As Intel Unveils 22nm SoC

MrSeb writes with news on the happenings with next generation fabrication processes. From the article: “… Intel’s 22nm SoC unveil is important for a host of reasons. As process nodes shrink and more components move on-die, the characteristics of each new node have become particularly important. 22nm isn’t a new node for Intel; it debuted the technology last year with Ivy Bridge, but SoCs are more complex than CPU designs and create their own set of challenges. Like its 22nm Ivy Bridge CPUs, the upcoming 22nm SoCs rely on Intel’s Tri-Gate implementation of FinFET technology. According to Intel engineer Mark Bohr, the 3D transistor structure is the principle reason why the company’s 22nm technology is as strong as it is. Earlier this year, we brought you news that Nvidia was deeply concerned about manufacturing economics and the relative strength of TSMC’s sub-28nm planar roadmap. Morris Chang, TSMC’s CEO, has since admitted that such concerns are valid, given that performance and power are only expected to increase by 20-25% as compared to 28nm. The challenge for both TSMC and GlobalFoundries is going to be how to match the performance of Intel’s 22nm technology with their own 28nm products. 20nm looks like it won’t be able to do so, which is why both companies are emphasizing their plans to move to 16nm/14nm ahead of schedule. There’s some variation on which node comes next; both GlobalFoundries and Intel are talking up 14nm; TSMC is implying a quick jump to 16nm. Will it work? Unknown. TSMC and GlobalFoundries both have excellent engineers, but FinFET is a difficult technology to deploy. Ramping it up more quickly than expected while simultaneously bringing up a new process may be more difficult than either company anticipates.” Read more of this story at Slashdot.

See original article:
TSMC and Global Foundries Plan Risky Process Jump As Intel Unveils 22nm SoC