Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror
×
Google

Submission + - WSJ spreads FUD on open source and Google Phone (wsj.com) 2

An anonymous reader writes: Ben Worthen at the Wall Street Journal shows a laughable grasp of what "open source" means: 'Here's the first thing that will happen when a phone with Google's operating system hits the market: Information-technology departments will ban employees from connecting phones that run Google's operating system to their computers or the corporate network. The reason is that Google's operating system is open, meaning anyone can write software for it. That includes bad guys, who will doubtlessly develop viruses and other malicious code for these phones, which unsuspecting Google phones owners will download. Employees could spread the malicious code to the rest of the company when they synch their phones to their computers or use it to check email. The way to combat this is to develop anti-virus and anti-malware software for phones and to develop security procedures similar to those that have evolved for PCs over the last several years. But that's going to take time and money — neither of which the average IT department has. So until then, expect Google phones to be persona non grata at companies.'
Censorship

Submission + - TSA Filtering Public Plane Crash Documentation?

Cutriss writes: AP is reporting allegations that the US Transportation Security Administration is reportedly screening documentation concerning the crash of Comair Flight 5191 in August 2006. The agency states that it has no role in the investigation of the crash itself, but apparently is concerned about sensitive information about airport operations becoming public. The documentation review has slowed the investigation process and also delayed the pending lawsuits filed by families of the victims, and when the documentation is finally released to the court, it will be given with redactions in place. The crash was determined to be caused by a variety of human errors contributing to the pilots' use of a runway too short to support the plane's takeoff, so the involvement of the TSA has raised eyebrows amongst some.
Power

Submission + - Primary and backup power fails, websites offline.

An anonymous reader writes: The Los Angeles Times has an article describing how the power outage in San Francisco yesterday knocked several popular web sites (including craigslist and technorati) off line. These sites were hosted at 365 Main. The article points out the irony in a 365 Main press release that day announcing one customer had shut down its "redundant" data center in the Midwest and was thrilled with 365 Main after "two years of continuous uptime." 365 Main has posted a summary of the incident.
The Courts

Submission + - Revote likey because Diebold recount impossible

Aidtopia writes: A judge in Berkeley, California, has ordered a re-vote in a 2004 medical marijuana measure which had lost by fewer than 200 votes. A group supporting the measure requested a recount, which was meaningless since the Diebold electronic voting machines didn't produce physical ballots. The group petitioned for audit logs and other supporting documentation. The Registrar initially gave them the run-around, and, with a lawsuit pending, shipped the machines back to the manufacturer where 96% of the stored votes were erased. The ruling is tentative. The revote, if it happens, will be in the 2008 general election, using different electronic voting machines that produce a paper trail.
Software

Submission + - Optimum Hardware for Visual Studio Development?

blaster151 writes: "What would your "dream development machine" look like and how would you configure it for performance?

My team is working on a large software system on the Visual Studio 2005 platform (over a thousand source files). We have fairly fast machines, but they often take 15-20 seconds to do a complete rebuild and since this happens rather often I can't help but wonder how to eke out better performance. Our developers typically have VS2005 and database client tools concurrently, but we don't usually run local databases on our machines so that's less of a consideration.

I'm in a position to do some hardware recommendations and I want to understand how to prioritize the following factors:
  1. Processor (How much does a coding/build environment like VS2005 benefit from having a Core Duo processor as opposed to a traditional, higher-end CPU?)
  2. RAM (Obviously, more is good; we currently have a minimum of 1.5GB per developer)
  3. Disk (Is SCSI worth the price difference?)
  4. Laptop (Any drawbacks or considerations if we go the mobile route?)
I am also interested in configuration tips (whether it's worth having a separate internal drive for the the paging file, etc.)

So, to restate the question, what would your "dream development machine" look like and how would you configure it?"
Windows

Submission + - Stopping WGA Installation sends data to Microsoft

rev writes: "The new WGA Notification installation that can be installed using Windows Update sends data to Microsoft if the user decides to cancel the installation. A cookie is set that could be used to identify the host and information such as version of Windows and WGA as well as language of the operating system are transmitted. Part of the data is encrypted. (read more)"

Slashdot Top Deals

A morsel of genuine history is a thing so rare as to be always valuable. -- Thomas Jefferson

Working...