Slashdot Mirror

In the summer of 1999, Bruce Perens became our very first interview subject, answering questions about open source licensing. Almost 14 years later, Bruce is still one of the most influential programmers and advocates in the open source community. He's graciously agreed to answer all your questions about the state of things and what's changed in those 15 years. As with previous interviews, we'll send the best questions to Mr. Perens, and post his answers in a day or two. Ask as many questions as you'd like, but please keep them to one per post.

concealment writes "In the face of the violence that frequently results from anti-religious expression, some world leaders seem to be losing their patience with free speech. After a video called 'Innocence of Muslims' appeared on YouTube and sparked violent protests in several Muslim nations last month, U.N. Secretary General Ban Ki-moon warned that 'when some people use this freedom of expression to provoke or humiliate some others' values and beliefs, then this cannot be protected.' It appears that the one thing modern society can no longer tolerate is intolerance. As Australian Prime Minister Julia Gillard put it in her recent speech before the United Nations, 'Our tolerance must never extend to tolerating religious hatred.'"

MrSeb writes "Felix Baumgartner has successfully completed his stratospheric skydive from 128,000 feet (39km), breaking a record that was set 52 years ago by Air Force Captain Joe Kittinger — that much we know. From the balloon, to the capsule, to the gear that Baumgartner wore during his 730 mph (1174 kph) free fall, the technology behind the scenes is impressive, and in some cases bleeding edge. ExtremeTech takes a deep dive into the tech that kept Baumgartner alive during the three-hour ascent and (much shorter) descent — and the tech that allowed us to watch every moment of the Red Bull Stratos mission live, as captured by no less than 15 digital cameras and numerous other scientific instruments."

First time accepted submitter madcarrots writes "The Red Bull Stratos space jump is about to take place. The balloon is filling up and launch is expected around 10 AM MDT. Check out the live feed of the inflation process... it's beautiful!" After some delays it looks like the jump is finally going to happen. UPDATE: The jump was a success. Baumgartner is on the ground and apparently fine.

An anonymous reader writes "'When all 3 legs of your 3-legged strategy fail, what do you do? You rush — run run run — to change your total strategy. But what would a madman do?' Ex-Nokia exec Tommi Ahonen's new article has a few suggestions. Is the Nokia board either asleep at the wheel, or incompetent, or in collusion with the incompetent CEO? Ahonen provides an insider's view not just of how Nokia's Windows phone strategy has failed, but how this has spread to other parts of the company's technology. He says the 'Elop Effect' has 'single-handedly destroyed [...] Europe's biggest tech giant.' He raises the question: Why is Nokia's board failing to act? We've discussed Tommi's articles before, where he was correctly predicting Windows Phone's market failure at a point where others were claiming that 'the Lumia line is, in fact, selling quite nicely.'"

Giorgio Maone writes "Ubuntu developer and fellow Mozillian Benjamin Kerensa chatted with various people about the new Amazon Product Results in the Ubuntu 12.10 Unity Dash. Among them, Richard Stallman told him that this feature is bad because: 1. 'If Canonical gets this data, it will be forced to hand it over to various governments.'; 2. Amazon is bad. Concerned people can disable remote data retrieval for any lens and scopes or, more surgically, use sudo apt-get remove unity-lens-shopping."

SpzToid writes "U.S. Secretary of Defense Leon E. Panetta has warned that the country is 'facing the possibility of a "cyber-Pearl Harbor" and [is] increasingly vulnerable to foreign computer hackers who could dismantle the nation's power grid, transportation system, financial networks and government.' Countries such as Iran, China, and Russia are claimed to be motivated to conduct such attacks (though in at least Iran's case, it could be retaliation). Perhaps this is old news around here, even though Panetta is requesting new legislation from Congress. I think the following message from Richard Bejtlich is more wise and current: 'We would be much better served if we accepted that prevention eventually fails, so we need detection, response, and containment for the incidents that will occur.' Times do changes, even in the technology sector. Currently Congress is preoccupied with the failure of U.S. security threats in Benghazi, while maybe Leon isn't getting the press his recent message deserves?"

hypnosec writes "Raynaldo Rivera has pleaded guilty at the US District Court for the Central District of California to hacking the Sony Pictures Entertainment website in May 2011. The 20-year-old in his plea agreement revealed that he joined Lulzsec in May of last year in a bid to help the hacking collective carry out cyberattacks on governments and businesses. Rivera, who surrendered to the FBI on August 28 this year, admitted that he was the one who launched an SQL injection attack against sonypictures.com that enabled him to extract confidential information from the website's database."

itwbennett writes "As Slashdot readers will recall, ICANN has been struggling to find a way to decide which applications to evaluate first. At the end of June, ICANN announced it had abandoned plans to use the Digital Archery contest. Then at the end of July, ICANN said it would process all applications simultaneously. Now there's a new plan in the works: an old-fashioned, manual raffle with tickets costing $100. There's just one catch, though: California law prohibits unlicensed lotteries."

itwbennett writes "As Slashdot readers will recall, ICANN has been struggling to find a way to decide which applications to evaluate first. At the end of June, ICANN announced it had abandoned plans to use the Digital Archery contest. Then at the end of July, ICANN said it would process all applications simultaneously. Now there's a new plan in the works: an old-fashioned, manual raffle with tickets costing $100. There's just one catch, though: California law prohibits unlicensed lotteries."

Hugh Pickens writes "The Guardian reports that members of computer hacker collective Anonymous have distanced themselves from WikiLeaks, claiming the whistleblowers' site has become too focused on the personal tribulations of its founder, Julian Assange. A statement linked from the Anonymous Twitter account, AnonymousIRC, described WikiLeaks as 'the one man Julian Assange show,' and complained that the website implemented a paywall seeking donations from users who wanted access to millions of leaked documents. 'The idea behind WikiLeaks was to provide the public with information that would otherwise be kept secret by industries and governments. Information we strongly believe the public has a right to know,' said the statement on behalf of Anonymous. The dispute could starve WikiLeaks of potentially newsworthy leaks in the future, as some of Wikileaks' recent disclosures – including the Stratfor emails – are alleged to have come from Anonymous."

Ever since news broke last year that Microsoft would require Windows 8 machines to have UEFI secure boot enabled, there were concerns that it would be used to block the installation of other operating systems, such as Linux distributions. Now, reader dgharmon sends this quote from Ars Technica about a new defense against that outcome: "The Linux Foundation has announced plans to provide a general purpose solution suitable for use by Linux and other non-Microsoft operating systems. The group has produced a minimal bootloader that won't boot any operating system directly. Instead, it will transfer control to any other bootloader — signed or unsigned — so that can boot an operating system." The announcement adds, "The pre-bootloader will employ a 'present user'; test to ensure that it cannot be used as a vector for any type of UEFI malware to target secure systems. This pre-bootloader can be used either to boot a CD/DVD installer or LiveCD distribution or even boot an installed operating system in secure mode for any distribution that chooses to use it."

concealment writes "A judge has ruled that the libraries who have provided Google with their books to scan are protected by copyright's fair use doctrine. While the decision doesn't guarantee that Google will win—that's still to be decided in a separate lawsuit—the reasoning of this week's decision bodes well for Google's case. Most of the books Google scans for its book program come from libraries. After Google scans each book, it provides a digital image and a text version of the book to the library that owns the original. The libraries then contribute the digital files to a repository called the Hathitrust Digital Library, which uses them for three purposes: preservation, a full-text search engine, and electronic access for disabled patrons who cannot read the print copies of the books."

SternisheFan writes "Google Maps has been updated with what's described as the 'biggest ever" increase in Street View photography, with more than 250,000 miles of road around the world gaining street-level imagery. Street View coverage has been boosted in eleven countries, with new 'special collections' of photography, giving more insight into particular landmarks. Google has also sent its cameras inside some landmarks, so you can now step into Kronborg castle in Denmark, for instance. The search giant uses a combination of Street View photography cars, bikes, and even individually-work camera backpacks to gather its footage. Support for viewing Street View on mobile devices has been contentious in recent weeks, with Apple's decision to oust Google Maps from iOS 6 and replace it with its own Apple Maps app. Google re-added access by updating its webapp, however, and has promised a native version of Google Maps for iOS by the end of the year."

Michael Ross writes "With the advent of graphical user interfaces (GUIs) decades ago, most of the commercially-available software transitioned from command-line usage to point-and-click interfaces, with the majority of these applications completely phasing out all command-line capabilities, or never implementing them in the first place. But for programmers — most of whom are comfortable working on the command line — performing administrative actions within a GUI can become tedious and time-consuming, and there is a growing movement toward adding command-line support back to software development applications. An example of this is Drush, which is a command-line interface for the Drupal content management system. Drush, whose name is derived from "Drupal shell," was originally developed six years ago, and is seeing a resurgence within the Drupal community. However, what appears to be the primary information resource for Drush, the community documentation, currently has a status of "incomplete." Fortunately, there is now a book available that provides more extensive coverage, Drush User's Guide, authored by Requena Juan Pablo Novillo ("juampy"). The book was released by Packt Publishing on 10 April 2012, under the ISBN 978-1849517980. The publisher's page offers descriptions of the book, its table of contents, a brief author biography, the known errata, the example code used in the book, and a free sample chapter (the third one, "Customizing Drush"). This review is based upon a print copy kindly furnished by the publisher; an e-book version is also available." Read below for the rest of Michael's review. Drush User's Guide author Requena Juan Pablo Novillo pages 125 pages publisher Packt Publishing rating 8/10 reviewer Michael J. Ross ISBN 978-1849517980 summary A tutorial on Drupal's CLI. The book comprises 125 pages, mostly grouped into four chapters, which cover how to install, use, customize, and extend Drush. The preface briefly summarizes those chapters, the software needed to use Drush, the target audience of the book, the styling conventions used in the text, and various publisher information. The author states that "Apache 2.0 or higher" is required to use Drush (page 2), but the project's README.txt does not mention this, and Drupal 7 itself runs fine on Apache 1.3; so this requirement is unclear. He also states that "Drush 4 does not support Windows" (page 13); Windows users are instructed to use Drush 5. This seems questionable, since a quick test revealed that Drush 4.5 runs on a Windows XP machine. Admittedly, it always elicits a warning: "Drush 4.x has significant limitations on Windows; it is not advisable to use on that platform. Substantial progress has been made towards supporing [sic] Windows on the 5.x branch; please upgrade."

The first chapter of the Drush User's Guide naturally begins with instructions on how to install Drush on Linux, Mac, and Windows systems. The book's examples use Drush 4.5, even though 5.1 was available at the time of the book's publication, and 5.0 was available a month earlier. Version 4.5 was the last 4.x release, and was probably the latest stable release when the book was being finalized. Throughout the book, all Windows instructions are specific to Windows 7, so any XP straggler will need to modify them as needed. In the "Manual installation" section, the subheads are almost identical in font size to the higher-level subheads, forcing the reader to check the table of contents hierarchy just to see where the manual installation instructions end. But the main problem is that the reader is not given recommendations as to which optional features should or should not be chosen. For instance, if you already have PHP installed on your system, should you decline to have the Drush installer try to add the "Php [sic] Required Runtime," even though it is enabled by default?

The author then shows how to set up a Drush-specific PHP configuration file, in order to bypass potential problems, such as memory limitations in the default configuration file. In the rest of the chapter, he demonstrates how to perform Drush commands (in general), define arguments and options for those commands, create command aliases, and specify which Drupal website any Drush command is supposed to operate upon.

In the second chapter, "Executing Drush Commands," the author shows the reader how to perform a fresh installation of Drupal 7 — including creation of the database and its tables — with just two commands. He introduces the music festival website that will be used throughout the rest of the book for demonstration purposes. At this point, some readers may hit a stumbling block: The "--drupal-project-rename" option used in the text fails on Windows machines (this is a known issue). Presumably the author did not test his suggested commands in a Windows environment. The bulk of the chapter is devoted to introducing numerous Drush commands, including those used to get and set variables, install modules, administer users, back up the database, and many more.

The author notes that "Drush is highly configurable," and in the third chapter he shows the reader how to create custom commands, include their help information in the output of the command "drush help," extend existing commands, run custom PHP scripts, and define site aliases. Readers new to Drupal may find these topics fairly advanced, as they necessitate familiarity with command namespaces, as well as Drupal's hook system, callbacks, and database API. Defining remote site aliases involves SSH and public keys. However, given the flexibility and power of custom Drush functionality, it is arguably worthwhile to make the effort to learn how to do it properly. At the end of the chapter, the reader learns how to use and configure the Drush command-line interface.

The fourth and final chapter, "Extending Drush," discusses how to utilize some of the modules that are integrated with Drush — specifically, Backup and Migrate, Devel, Features, Views, and Module Builder. The chapter concludes with a section on Drush Make, which packages the module information of a Drupal website so it can be re-created using Drush easily.

As with all of the Packt Publishing titles that I have reviewed, this one has a high number of errata relative to the total page count, aside from the seven already reported online (as of this writing): "command line interface" (page 1; "command line" should be hyphenated when used as an adjective), "book title through the subject" (same page; should be "book title in the subject"), "Clear cache" (page 7; should be "Clear all caches"), "follow [the] instructions" (page 13), "close [it] and open [it] again" (page 18), "try and" (page 21; should be "try to"), "change version by something" ("by" should be "to"), "parenthesis" (page 23, twice; should be "parentheses"), "within [the] sites subdirectory" (page 25), "execute commands towards" (page 26; "towards" should be "on"), "MySql's" (page 28; should be "MySQL database's"), "provided with it" (should be "provided it with"), "that resolves" (page 29; should be "resolves"), "First, of all" (page 33), "anoying" (page 48), "Imagine, that" (page 52), "lists [the] latest messages" (page 55), and "altering existing" (page 57; should be "alter existing"). At this point, not yet halfway through the book, I stopped recording errata. The Packt Publishing copyeditors should have spotted and fixed these obvious errors.

Although the author's meaning is invariably clear enough, the writing style is awkward in many places. For instance, "replace by" (page 4) should instead be "replace with," "take the chance to review" (page 41) should be "take the opportunity to review," and "of the flow" (page 55) should be "in the flow." The term "at" is used to indicate "in" a file — e.g., "at the Drush README.txt" (page 9); the same is true for MySQL tables — e.g., "stored at the variable table" (page 30). In addition, countless passages in the text would have benefited from a comma. Conversely, there are some extraneous commas (e.g., on page 43).

Yet the main flaw of the book is the neglect for readers who are using the Windows operating system for building and administering Drupal websites. The aforesaid "--drupal-project-rename" bug likely would have been caught had the Drush pm-download command been tested on a Windows computer. Another example is on page 48, where it is assumed that the command "firefox" will work as a link to the browser's executable on the reader's computer. Also, the ".drush" folder is critical for creating site aliases and other configuration settings; but where will the Windows user find this folder? This Linux partiality could result in Windows readers encountering — and possibly being frustrated by — confusing technical problems.

Nonetheless, the author does a fine job of explaining how to utilize the many Drush commands presented, as well as many of their arguments and options — oftentimes pointing out differences in their usage for Drupal 6 versus Drupal 7. Any Drupal developer interested in learning how to harness the power of a command-line interface for building and administering websites, should find Drush User's Guide a worthwhile tutorial.

Michael J. Ross is a freelance web developer and writer.

You can purchase Drush User's Guide from amazon.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

Michael Ross writes "With the advent of graphical user interfaces (GUIs) decades ago, most of the commercially-available software transitioned from command-line usage to point-and-click interfaces, with the majority of these applications completely phasing out all command-line capabilities, or never implementing them in the first place. But for programmers — most of whom are comfortable working on the command line — performing administrative actions within a GUI can become tedious and time-consuming, and there is a growing movement toward adding command-line support back to software development applications. An example of this is Drush, which is a command-line interface for the Drupal content management system. Drush, whose name is derived from "Drupal shell," was originally developed six years ago, and is seeing a resurgence within the Drupal community. However, what appears to be the primary information resource for Drush, the community documentation, currently has a status of "incomplete." Fortunately, there is now a book available that provides more extensive coverage, Drush User's Guide, authored by Requena Juan Pablo Novillo ("juampy"). The book was released by Packt Publishing on 10 April 2012, under the ISBN 978-1849517980. The publisher's page offers descriptions of the book, its table of contents, a brief author biography, the known errata, the example code used in the book, and a free sample chapter (the third one, "Customizing Drush"). This review is based upon a print copy kindly furnished by the publisher; an e-book version is also available." Read below for the rest of Michael's review. Drush User's Guide author Requena Juan Pablo Novillo pages 125 pages publisher Packt Publishing rating 8/10 reviewer Michael J. Ross ISBN 978-1849517980 summary A tutorial on Drupal's CLI. The book comprises 125 pages, mostly grouped into four chapters, which cover how to install, use, customize, and extend Drush. The preface briefly summarizes those chapters, the software needed to use Drush, the target audience of the book, the styling conventions used in the text, and various publisher information. The author states that "Apache 2.0 or higher" is required to use Drush (page 2), but the project's README.txt does not mention this, and Drupal 7 itself runs fine on Apache 1.3; so this requirement is unclear. He also states that "Drush 4 does not support Windows" (page 13); Windows users are instructed to use Drush 5. This seems questionable, since a quick test revealed that Drush 4.5 runs on a Windows XP machine. Admittedly, it always elicits a warning: "Drush 4.x has significant limitations on Windows; it is not advisable to use on that platform. Substantial progress has been made towards supporing [sic] Windows on the 5.x branch; please upgrade."

The first chapter of the Drush User's Guide naturally begins with instructions on how to install Drush on Linux, Mac, and Windows systems. The book's examples use Drush 4.5, even though 5.1 was available at the time of the book's publication, and 5.0 was available a month earlier. Version 4.5 was the last 4.x release, and was probably the latest stable release when the book was being finalized. Throughout the book, all Windows instructions are specific to Windows 7, so any XP straggler will need to modify them as needed. In the "Manual installation" section, the subheads are almost identical in font size to the higher-level subheads, forcing the reader to check the table of contents hierarchy just to see where the manual installation instructions end. But the main problem is that the reader is not given recommendations as to which optional features should or should not be chosen. For instance, if you already have PHP installed on your system, should you decline to have the Drush installer try to add the "Php [sic] Required Runtime," even though it is enabled by default?

The author then shows how to set up a Drush-specific PHP configuration file, in order to bypass potential problems, such as memory limitations in the default configuration file. In the rest of the chapter, he demonstrates how to perform Drush commands (in general), define arguments and options for those commands, create command aliases, and specify which Drupal website any Drush command is supposed to operate upon.

In the second chapter, "Executing Drush Commands," the author shows the reader how to perform a fresh installation of Drupal 7 — including creation of the database and its tables — with just two commands. He introduces the music festival website that will be used throughout the rest of the book for demonstration purposes. At this point, some readers may hit a stumbling block: The "--drupal-project-rename" option used in the text fails on Windows machines (this is a known issue). Presumably the author did not test his suggested commands in a Windows environment. The bulk of the chapter is devoted to introducing numerous Drush commands, including those used to get and set variables, install modules, administer users, back up the database, and many more.

The author notes that "Drush is highly configurable," and in the third chapter he shows the reader how to create custom commands, include their help information in the output of the command "drush help," extend existing commands, run custom PHP scripts, and define site aliases. Readers new to Drupal may find these topics fairly advanced, as they necessitate familiarity with command namespaces, as well as Drupal's hook system, callbacks, and database API. Defining remote site aliases involves SSH and public keys. However, given the flexibility and power of custom Drush functionality, it is arguably worthwhile to make the effort to learn how to do it properly. At the end of the chapter, the reader learns how to use and configure the Drush command-line interface.

The fourth and final chapter, "Extending Drush," discusses how to utilize some of the modules that are integrated with Drush — specifically, Backup and Migrate, Devel, Features, Views, and Module Builder. The chapter concludes with a section on Drush Make, which packages the module information of a Drupal website so it can be re-created using Drush easily.

As with all of the Packt Publishing titles that I have reviewed, this one has a high number of errata relative to the total page count, aside from the seven already reported online (as of this writing): "command line interface" (page 1; "command line" should be hyphenated when used as an adjective), "book title through the subject" (same page; should be "book title in the subject"), "Clear cache" (page 7; should be "Clear all caches"), "follow [the] instructions" (page 13), "close [it] and open [it] again" (page 18), "try and" (page 21; should be "try to"), "change version by something" ("by" should be "to"), "parenthesis" (page 23, twice; should be "parentheses"), "within [the] sites subdirectory" (page 25), "execute commands towards" (page 26; "towards" should be "on"), "MySql's" (page 28; should be "MySQL database's"), "provided with it" (should be "provided it with"), "that resolves" (page 29; should be "resolves"), "First, of all" (page 33), "anoying" (page 48), "Imagine, that" (page 52), "lists [the] latest messages" (page 55), and "altering existing" (page 57; should be "alter existing"). At this point, not yet halfway through the book, I stopped recording errata. The Packt Publishing copyeditors should have spotted and fixed these obvious errors.

Although the author's meaning is invariably clear enough, the writing style is awkward in many places. For instance, "replace by" (page 4) should instead be "replace with," "take the chance to review" (page 41) should be "take the opportunity to review," and "of the flow" (page 55) should be "in the flow." The term "at" is used to indicate "in" a file — e.g., "at the Drush README.txt" (page 9); the same is true for MySQL tables — e.g., "stored at the variable table" (page 30). In addition, countless passages in the text would have benefited from a comma. Conversely, there are some extraneous commas (e.g., on page 43).

Yet the main flaw of the book is the neglect for readers who are using the Windows operating system for building and administering Drupal websites. The aforesaid "--drupal-project-rename" bug likely would have been caught had the Drush pm-download command been tested on a Windows computer. Another example is on page 48, where it is assumed that the command "firefox" will work as a link to the browser's executable on the reader's computer. Also, the ".drush" folder is critical for creating site aliases and other configuration settings; but where will the Windows user find this folder? This Linux partiality could result in Windows readers encountering — and possibly being frustrated by — confusing technical problems.

Nonetheless, the author does a fine job of explaining how to utilize the many Drush commands presented, as well as many of their arguments and options — oftentimes pointing out differences in their usage for Drupal 6 versus Drupal 7. Any Drupal developer interested in learning how to harness the power of a command-line interface for building and administering websites, should find Drush User's Guide a worthwhile tutorial.

Michael J. Ross is a freelance web developer and writer.

You can purchase Drush User's Guide from amazon.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

concealment writes "Dotcom confirmed to the Associated Press in a telephone interview that he has completed 90% the work on "new Mega" and "Megabox", a music site that he announced in June. Megabox will allow users to download music for free in exchange for accepting some advertisements, and 90% of the revenue will go to the artists."

Monday you had a chance to ask Linus Torvalds any question you wanted. We sent him a dozen of the highest rated and below you'll see what he has to say about computers, programming, books, and copyrights. He also talks about what he would have done differently with Linux if he had to do it all over again. Hint: it rhymes with nothing. The Absolute Death of Software Copyright?
by eldavojohn

Recently you spoke out about software patents and the patent process. But I was interested in what you said about how "nasty" copyright issues could get. You use SCO as the obvious nightmare case but what about violations against open source licenses like the GPLv3? Would you care if someone forked the Linux kernel and made major modifications to it and started selling it without releasing the code to the customers? What does your ideal situation look like for open source and commercial closed source? Would you just copy the Finnish model and aren't you afraid American experts are just as daft as American juries?

Linus: So I like copyrights, and even on patents I'm not necessarily in the "Patents are completely evil" camp. When I rant about patents or copyrights, I rant against the *excesses* and the bad policies, not about them existing in the first place.

The patent problems people on slashdot are probably familiar with: the system is pretty much geared towards people abusing it, with absolutely ridiculous patents being admitted, and it hindering invention rather than helping it. The failures are many, and I don't know how to fix it, but much stricter limits on what can be patented are clearly needed.

People were apparently surprised by me saying that copyrights had problems too. I don't understand why people were that surprised, but I understand even *less* why people then thought that "copyrights have problems" would imply "copyright protection should be abolished". The second doesn't follow at all.

Quite frankly, there are a lot of f*cking morons on the internet.

Anyway, the problems with copyright come from absurdly long protection periods, and some overly crazy enforcement. And don't get me wrong: I don't actually think that these problems show up all that much in the software industry. The case of SCO was not, I think, so much a failure of copyright law itself: sure, it was annoying, but at the same time it was really more about a psychopathic company with a failed business that tried to game the system. Tried, and lost. And yes, that fiasco took much too long, and was much too expensive, and should have been shut down immediately, but that whole "using the law for harassment" in the US is a separate issue independent of the copyright issues.

No, when I stated that copyright protection is too strong, I was talking about things like "life of author+70 years" and the corporate 95-year version. That's *ridiculous*. Couple that with the difficulty of judging fair use etc, and it really hinders things like archival of material, making of documentaries, yadda yadda...

So I personally think that IP protection isn't evil in itself - but that it turns evil when it is taken too far. And both patent protection and copyright protection has been taken much much too far.

Scale the term limits back to fifteen years or so, and copyrights would be much better.



When I'm designing a processor for Linux.
by Art Popp (29075)

I spend some time designing things in Verilog and trying to read other people's source code at opencores.org, and I recall you did some work at Transmeta. For some time I've had a list of instructions that could be added to processors that would be drastically speed up common functions, and SSE 4.2 includes some of my favorites, the dqword string comparison instructions. So...What are your ideas for instructions that you've always thought should be handled by the processor, but never seen implemented?

Linus: I actually am not a huge fan of shiny new features. In processor design - as in so much of technology - what matters more is interoperability and compatibility. I realize that this makes people sad, because people are always chasing that cool new feature, but hey, in the end, technology is about doing useful things. And building and extending on top of existing knowledge and infrastructure is how 99% of all improvement gets done.

The occasional big shift and really new thing might get all the attention, but it seldom really is what matters. I like to quote Thomas Edison: "Genius is 1% inspiration, 99% perspiration". And that very much covers CPU architecture too: the inspiration is simply not as important as executing well. Sure, you need some inspiration, but you really don't need all that *much* of it.

So in CPU design, what should really be looked at is how well the CPU is able to do what we expect. The instruction set is important - but it is important mainly as a "I can run the same instructions the previous CPU did, so I can run all your programs without you having to do any extra work" issue - not as a "what new cool feature would you want in an instruction set".

To a CPU architect, I'd tell them to do the best they damn well can in the memory subsystem, for example. Regardless of instruction set, you'll want a great memory subsystem end-to-end. And I don't just mean good caches, but good *everything*. It's a hell of a lot of detail (perspiration), and I guarantee you that it will take a large team of people many generations to do really well on it. There is no simple silver bullet with a cool new instruction that will solve it for you.

And don't get me wrong - it's not *all* about the memory subsystem. It's about all the other details too.

Now, when it comes to actual instructions, I do tend to think that the world has shifted away from RISC. I'm a big believer in being good at running existing binaries across many different micro-architectures - the whole "compatibility" thing. And as a result, I think fragile architectures that depend on static instruction scheduling or run in-order are simply insane. If your CPU requires instruction scheduling for one particular set of instruction latencies or decoder limitations, your CPU is bad. I detested Itanium, for this reason - exposing the microarchitecture in the instruction set is just insane.

No, I want out-of-order and "high-level" instructions that actually work across different implementations of the same ISA, and across different classes of hardware (iow, span the whole "low-power embedded" to "high-end server" CPU range). So for example, I think having a "memcpy" or "memset" instruction is a great idea, if it allows you to have something that works optimally for different memory subsystems and microarchitectures.

As an example of what *not* to do, is to expose direct cacheline access with some idiotic "DCBZ" instruction that clears them - because that will then make the software have to care about the size of the cacheline etc. Same goes for things like "nontemporal accesses" that bypass the L1 cache - how do you know when to use those in software when different CPU's have different cache subsystems? Software just shouldn't care. Software wants to clear memory, not aligned cachelines, and software does *not* want to have to worry about how to do that most efficiently on some particular new machine with a particular cache size and memory subsystem.



What would you have done differently?
by Rob Kaper

It's been over twenty years since the inception of Linux. With 20/20 hindsight, what you have done differently if you had had today's knowledge and experience back in the early days?

Linus: I get asked this quite often, and I really don't see how I could possibly have done anything better. And I'm not claiming some kind of great forethought - it's just that with 20:20 hindsight, I really did choose the right big things. I still love the GPLv2, and absolutely think that making Linux open source was the greatest thing ever.

Have I made mistakes? Sure. But on the whole, I think Linux has done incredibly well, and I've made the right decisions around it (and the big things have *occasionally* been about technical issues, but more often about non-technical things like "Don't work for a commercial Linux company even if it seems like such a natural thing to do - keep working in a neutral place so that people can continue to work with me")



Monolithic vs. Micro-kernel architecture
by NoNeeeed

Has there ever been a time in the development of the Linux Kernel where you've wished you'd gone the Hurd-style micro-kernel route espoused by the like of Tannenbaum, or do you feel that from an architectural standpoint Linux has benefited from having a monolithic design?

Linux has been massively more successful than Hurd, but I wonder how much of that is down to intrinsic technical superiority of its approach, and how much to the lack of a central driving force supported by a community of committed developers? It always seemed like the Hurd model should have allowed more people to be involved, but that has never seemed to be the case.

Linus: I think microkernels are stupid. They push the problem space into *communication*, which is actually a much bigger and fundamental problem than the small problem they are purporting to fix. They also lead to horrible extra complexity as you then have to fight the microkernel model, and make up new ways to avoid the extra communication latencies etc. Hurd is a great example of this kind of suckiness, where people made up whole new memory mapping models just because the normal "just make a quick system call within the same context" model had been broken by the microkernel model.

Btw, it's not just microkernels. Any time you have "one overriding idea", and push your idea as a superior ideology, you're going to be wrong. Microkernels had one such ideology, there have been others. It's all BS. The fact is, reality is complicated, and not amenable to the "one large idea" model of problem solving. The only way that problems get solved in real life is with a lot of hard work on getting the details right. Not by some over-arching ideology that somehow magically makes things work.



Avoiding the Unix Wars
by dkleinsc

Why do you think Linux has been able to (mostly) avoid the fragmentation that plagued the competing Unixes of the 1980's? What would you say helps keep Linux a unified project rather than more forked system like BSD?

Linus: So I'm a huge believer in the GPLv2, and I really do believe the license matters. And what - to me - is important for an open-source license is not whether you can fork (which the BSD's allow), but whether the license encourages merging things back.

And btw, before people go all "license flamewar" on me, I would like to really emphasize the "to me" part. Licensing is a personal choice, and there is no "wrong" choice. For projects *I* care about, and that I started and can make the licensing decision for, I think the GPLv2 is the right thing to do for various reasons. But that does *not* mean that if somebody else makes another choice for his or her code, that wouldn't be the right choice for *that* person.

For example, I'd use a BSD-like license for code that I simply didn't care about, and wanted to just "push out there in case somebody else wants to use it". And I don't think proprietary licenses are evil either. It's all fine, it's up to the original author to decide what direction you want to do in.

Anyway, to just get back to the question - I really do think that encouraging merging is the most important part for a license for me. And having a license like the GPLv2 that basically *requires* everybody to have the right to merge back useful code is a great thing, and avoids the worry of forking.

And I do want to say that it's not that forking is bad. Forking is absolutely *required*, because easy forking is how development gets done. In fact, one of the design principles behind git was to make forking easy, and not have any technical barrier (like a "more central repository") that held back forking. Forking is important, and forking needs to happen any time there is a developer who thinks that they can do a better job in some area. Go wild, fork the project, and prove your point. Show everybody that you can make improvements.

But forking becomes a problem if there is no good way to merge things back. And in Linux, it's not been just about the license.Sure, the license means that legally we can always merge back the forks if they prove to be good forks. But we have also had a culture of encouraging forking and making forking be something that isn't acrimonious. Basically *all* the Linux distributions have had their own "forks" of the kernel, and it's not been seen as something bad, it's been seen as something natural and *good*. Which means that now the fork is all amicable and friendly, and there are not only no legal issues with merging it back into mainline, but there are also generally no big personality clashes or bad feelings about it either.

So it's not that Linux doesn't fork, it's that we've tried to make forks small and painless, and tried to be good about merging things back. Sure, there are disagreements, but they get resolved. Look at the Android work, for example: yeah, it wasn't all happy people and no problems, and it took a while, but most of it got merged back, and without excessively bad feelings, I think.



GIT
by vlm

If you had to do GIT over again, what, if anything, would you change?VERY closely related question, do you like the git-flow project and would you think about pulling that into mainline or not?

Linus: So there's been a few small details that I think we could have done better, but on the whole I'm *very* happy with git. I think the core design is very solid, and we have almost zero redundant information, and the core model is really built around a few solid concepts that make a lot of sense. Git is very unix-like in that it has a few basic design things ("everything is an object" with a few basic relationships between the different objects in the git database) and then a lot of utility is built up around that whole thing.

So I'm very proud of git. I think I did a great design, and then others (and Junio Hamano in particular) have taken that great design and really run with it. Sure, it wasn't all that pleasant to use for outsiders early on, and it can still be very strange if you come from some traditional SCM, but it really has made my life *so* much better, and I really think it got the fundamentals right, in ways that SCM's that came before did not.

As to git-flow, I want to really re-iterate how great Junio Hamano has been as a git maintainer, and I haven't had to worry about git development for the last five years or so. Junio has been an exemplary maintainer, and shown great taste. And because I don't need to, I haven't even followed some of the projects around git, like git-flow. It's not what I need for *my* git workflow, but if it helps people maintain a good topic-branch model with git, then all the more power to them. And whether it should go into mainline git or not, I won't even comment on, because I absolutely trust that Junio will make the right decision.



Storage advancements in the kernel?
by ScuttleMonkey

Now that Ceph is gathering momentum since having been included in the mainline kernel, what other storage (or low level) advancements do you see on the horizon? (full disclosure: I work for Inktank now, the consulting/services company that employs most of the core Ceph engineers)

Linus: I'm not actually all that much of a storage guy, and while I'm the top-level kernel maintainer, this is likely a question that would be better asked of a number of other people.

The one (personal) thing storage-related that I'd like to re-iterate is that I think that rotating storage is going the way of the dodo (or the tape). "How do I hate thee, let me count the ways". The latencies of rotational storage are horrendous, and I personally refuse to use a machine that has those nasty platters of spinning rust in them.

Sure, maybe those rotating platters are ok in some NAS box that you keep your big media files on (or in that cloud storage cluster you use, and where the network latencies make the disk latencies be secondary), but in an actual computer? Ugh. "Get thee behind me, Satan".

That didn't answer the question you really asked, but I really don't tend to get all that excited about storage in general.



favorite hack
by vlm

I asked a bunch of hard architecture questions, now for a softball Q. Your favorite hack WRT kernel internals and kernel programming in general. drivers, innards, I don't care which. The kind of thing where you took a look at the code and go 'holy cow that's cool' or whatever. You define favorite, hack, and kernel. Just wanting to kick back and hear a story about cool code.

Linus: Hmm. You do realize that I don't get all that close to the code any more? I spend my time not coding, but reading emails, and merging stuff others wrote. And when I *do* get involved with the code, it's not because it's "cool", it's because it broke, and you'll find me cursing the people who wrote it, and questioning their parentage and that of their pets.

So I very seldom get involved in the really cool code any more, I'm afraid. I end up being involved in the "Holy sh*t, how did we ever merge that cr*p" code. Perhaps not as much as Greg (who has to deal with the staging tree), but then Greg is "special".

That said, we do have lots of pretty cool code in the kernel. I'm particularly proud of our filename lookup cache, but hey, I'm biased. That code is *not* for the weak of heart, though, because the whole lockless lookup (with fallbacks to more traditional locked code) is hairy and subtle, and mortals are not supposed to really look at it. It's been tweaked to some pretty extreme degrees, because it ends up being involved any time you look up a filename. I still remember how happy I was to merge the new lockless RCU filename lookup code last year.

At the opposite end of the spectrum, I actually wish more people understood the really core low-level kind of coding. Not big, complex stuff like the lockless name lookup, but simply good use of pointers-to-pointers etc. For example, I've seen too many people who delete a singly-linked list entry by keeping track of the "prev" entry, and then to delete the entry, doing something like

if (prev)
prev->next = entry->next;
else
list_head = entry->next;

and whenever I see code like that, I just go "This person doesn't understand pointers". And it's sadly quite common.

People who understand pointers just use a "pointer to the entry pointer", and initialize that with the address of the list_head. And then as they traverse the list, they can remove the entry without using any conditionals, by just doing a "*pp = entry->next".

So there's lots of pride in doing the small details right. It may not be big and important code, but I do like seeing code where people really thought about the details, and clearly also were thinking about the compiler being able to generate efficient code (rather than hoping that the compiler is so smart that it can make efficient code *despite* the state of the original source code).



Books, Books, Books
by eldavojohn

As a software developer, I have a coveted collection of books. A few of said tomes -- both fiction and non -- have fundamentally altered the course of my life. Assuming yours aren't just man pages and .txt files, what are they?

Linus: I read a fair amount, but I have to admit that for me reading tends to be about escapism, and books to me are mostly forgettable. I can't really think of a single case of a book that struck me as life-changing, the way some people apparently find some book that really changed the way they think.

That said, I'll point to a couple of books I really enjoyed. On the non-fiction side, Richard Dawkin's "The Selfish Gene" was one book that I think is pretty influential. On the fiction side, as a teenager I enjoyed Heinlein's "Stranger in a strange land" a lot, and I have to admit to "Lord of the Rings" having been pretty important to me - but for a slightly odd reason, not as a huge Tolkien fan. For me, it was one of the first "real" books I read in English, and I started with a dictionary by my side, and ended it reading without needing one.

These days, I still read crap. I like my Kindle, and often read the self-published stuff for 99c. There are some real stinkers in there, but there's been a lot of "that was certainly worth the 99c" stuff too. I've also enjoyed just re-reading some of the classics I grew up with - I just re-read both the Count of Monte Cristo and the Three Musketeers, for example.



How do you deal with burn-out?
by kallisti5

You must of been burned out on Linux kernel development multiple-times over by now... how do you deal with it?

Linus: Oh, I really enjoy what I do. And I actually enjoy arguing too, and while I may swear a lot and appear like a grumpy angry old man at times, I am also pretty good at just letting things go. So I can be very passionate about some things, but at the same time I don't tend to really hold on to some particular issue for too long, and I think that helps avoid burn-out.

Obsessing about things is important, and things really do matter, but if you can't let go of them, you'll end up crazy.

So to me, some of the occasional flame-wars are really just invigorating. And the technology and the use cases end up changing enough that things never get *boring*, so I actually have not been close to burning out very often.

The one really painful time was some time during the middle of the 2.4.x series (about ten years ago), before I got to hand it over to stable maintenance, and we really had a lot of problems going on. You can google for "Linus doesn't scale" and various other threads about the problems we had back then, and it really was pretty painful. The kernel was growing and I wasn't keeping up, and BitKeeper and some fairly painful process changes really ended up helping a lot.



Describe your computer
by twistedcubic

Can you describe in detail your home and work computers, including processor, motherboard, and graphics card? And also say something about their compatibility with Linux?

Linus: My home computer isn't actually all that interesting: I don't need all that much CPU power any more, and for the last several years, my primary requirement (since CPU's are fast enough) has been that the system be really really quiet, and that it has a good SSD in it. If our cat deigns to jump into my lap while I'm working, the loudest noise in the room should be the purring of the cat, not the computer.

So my main desktop is actually a 4-core Westmere machine, not really anything special. The most unusual part of the machine is probably just the fact that it has a good case (I forget the exact case name now) which avoids rattling etc. And one of the bigger Intel SSD's. I think I'll be upgrading some time this fall, but I will have had that machine for two years now, I think.

My laptop (that I'm writing this with, since I'm traveling in Japan and Korea right now) is an 11" Apple Macbook Air from last year (but running Linux, of course - no OS X anywhere), because I really hate big laptops. I can't understand people who lug around 15" (or 17"!) monsters. The right weight for a laptop is 1kg, no more.



Re:The End
by Narnie

Speaking of ends, one day you'll pass on your duties. How do you envision the kernel and the Linux ecosystem after passing your reigns?

Linus: Oh, the kernel really has a very solid development community, I wouldn't worry about it. We've got several "top lieutenants" that could take over, and I'd worry much more about many other open-source projects that don't have nearly the same kind of big development community that the kernel does.

That said, I've been doing this for over twenty years now, and I don't really see myself stopping. I still do like what I'm doing, and I'd just be bored out of my gourd without the kernel to hack on.

jdavidb writes "46 years ago, occupying an abandoned WWII platform off the coast of Britain, Paddy Roy Bates declared independence, naming himself Prince of the Principality of Sealand. Today, Bates has passed away at 91. Long time Slashdot readers will remember Sealand as the site of HavenCo, an unsuccessful data warehousing company that tried to operate from Sealand outside the reach of larger nations' legal structures. They may also remember plans that the Pirate Bay had at one time to buy Sealand. Bates had moved to a care home a few years ago, naming his son Michael Regent of Sealand."

WikiLeaks has for years relied on donated time and money to publish the scoops that it has; now, concealment writes "As of Wednesday night, the secret-spilling site now shows a 'paywall' to any visitor who clicks on one of its leaked documents, including the 13,374 emails from the private intelligence firm Stratfor that it published earlier in the day along with the teaser that the messages regarded presidential candidate Mitt Romney. The pop-up message that blocks access to the site's content shows a video parodying Barack Obama's stump speeches and asking visitors to instead 'vote for WikiLeaks' by making a donation to the site or buying its promotional gear like tote bags and hoodies."

An anonymous reader writes with this bit from geek.com: "One of the big complaints surrounding the Nexus 7 launch was the lack of customer support when dealing with the device. Google was not initially prepared to handle the volume of users that required support, which led to an increase in wait time for callers who needed solutions. However, we've recently received word from a source that now Google is using a third party company to staff a call center for the release of the next Nexus devices." Maybe Google needs to out itself as a "devices and services company," too.

Shortly after the release of the newest major version of Firefox, an anonymous reader writes with word that "Mozilla has removed Firefox 16 from its installer page due to security vulnerabilities that, if exploited, could allow 'a malicious site to potentially determine which websites users have visited' ... one temporary work-around, until a fix is released, is to downgrade to 15.0.1"

An anonymous reader writes "Germany's minister for science and education, who is currently under investigation by her alma mater for plagiarizing parts of her Ph.D thesis, is facing new accusations: a total of 92 alleged incidents of plagiarism (German) have been documented by a blogger, who calls 'this number of violations inexcusable.'"

Nerval's Lobster writes "Futurist and author Ray Kurzweil predicts the cloud will eventually do more than store our emails or feed us streaming movies on demand: it's going to help expand our brain capacity beyond its current limits. In a question-and-answer session following a speech to the DEMO technology conference in Santa Clara, California last week, Kurzweil described the human brain as impressive but limited in its capacity to hold information. 'By the time we're even 20, we've filled it up,' he said, adding that the only way to add information after that point is to 'repurpose our neocortex to learn something new.' (Computerworld has posted up the full video of the talk.) The solution to overcoming the brain's limitations, he added, involves 'basically expanding our brains into the cloud.'"

An anonymous reader writes "Last night, Google held its Pwnium 2 competition at Hack in the Box 2012, offering up a total of $2 million for security holes found in Chrome. Only one was discovered; a young hacker who goes by the alias 'Pinkie Pie' netted the highest reward level: a $60,000 cash prize and a free Chromebook (the second time he pulled it off). Google today patched the flaw and announced a new version of Chrome for Windows, Mac, and Linux."

concealment sends this quote from an article at CNN: "Moderating a discussion on the future of broadband, Mashable editor-in-chief Lance Ulanoff tossed a provocative question to the audience: 'By quick show of hands, how many out there think that broadband is a luxury?' Next question: 'How many out there think it is a human right?' That option easily carried the audience vote. Broadband access is too important to society to be relegated to a small, privileged portion of the world population, Hans Vestberg, president and CEO of Ericsson, said during the discussion. Dr. Hamadoun Touré, secretary-general of the International Telecommunication Union, echoed Vestberg's remarks. 'We need to make sure all the world's inhabitants are connected to the goodies of the online world, which means better health care, better education, more sustainable economic and social development,' Touré said."

gabebear writes with details of what happened to OnLive back in August: "In a firesale, OnLive, which was once valued at $1.8bn, was sold for practically nothing. Workers are mostly losing their jobs and stock options and investors are having to write off their investment." More details.

Nerval's Lobster writes "According to Microsoft CEO Steve Ballmer's latest shareholder letter (not exactly a gripping read), Microsoft sees itself as a 'devices and services company.' The subsequent 1,200-odd words hammer that point, mentioning software such as Office and Windows 8 largely in the context of tablets and other hardware — and while Ballmer acknowledges the 'vast ecosystem of partners' building a 'broad spectrum of Windows PCs, tablets and phones,' he leaves the door wide open to Microsoft building its own toys in-house. If one takes Ballmer's words at face value, it seems that Surface, the tablet Microsoft's building in-house and promoting as a 'flagship' Windows 8 device, isn't so much a lark but the harbinger of the company's future direction. Whether Microsoft's decision to build its own devices affects its long-term relationship with Dell, Hewlett-Packard and other manufacturing titans remains to be seen. Perhaps Ballmer can take some comfort from Apple, which profited enormously by pursuing the 'we build everything in-house' route. But it's indisputable that a devices-centric approach is new ground for Microsoft."

jjp9999 writes "The Epoch Times reports that on Monday, the same day the Intelligence Committee released its report cautioning against Chinese telecom companies Huawei and ZTE, the U.S. said it will reject major changes to telecom at the World Administrative Telegraph and Telephone Conference in Dubai this December. The UN conference will be the first of its kind since 1988, and its members are pressing the U.S. to hand control of governing the Internet over to the International Telecommunication Union (ITU). Huawei and ZTE are both members of the ITU. Terry Kramer, the U.S. special envoy to the conference, said the US opposes proposals from some of the 'nondemocratic nations' that include tracking and monitoring content and user information, which 'makes it very easy for nations to monitor traffic.'"

concealment sends this excerpt from CNBC: "A single mysterious computer program that placed orders — and then subsequently canceled them — made up 4 percent of all quote traffic in the U.S. stock market last week, according to the top tracker of high-frequency trading activity. The motive of the algorithm is still unclear. The program placed orders in 25-millisecond bursts involving about 500 stocks, according to Nanex, a market data firm. The algorithm never executed a single trade, and it abruptly ended at about 10:30 a.m. ET Friday."

Nerval's Lobster writes "VMware has updated its cloud-management portfolio to support alternative tools, including Amazon's platform. That's a big step for the company, which for some time seemed to shy away from the idea of backing heterogeneous cloud environments. VMware's vFabric Application Director 5.0 is designed to, in the company's words, 'provision applications on any cloud.' That includes Amazon's EC2. The platform includes pre-approved operating system and middleware components for modeling and deploying those aforementioned applications, with the ability to use the platform's blueprints for deploying applications across 'multiple virtual and hybrid cloud infrastructures.' The other platform, vCloud Automation Center 5.1, enables 'policy-based provisioning across VMware-based private and public clouds, physical infrastructure, multiple hypervisors and Amazon Web Services.'" It's quite possible that this move is in response to Microsoft building similar functionality into Hyper-V 2012.

concealment points out a rebuttal from PCWorld of the increasingly common claims that we live in a post-PC world. "It's an intriguing proposition, but don't count on mobile devices killing off your desktop PC any time soon. While mobile gear is certainly convenient when you're trying to conduct business on the go, it's nowhere near as convenient as a desktop when you're trying to complete serious work in an office environment. Sure, your phone, tablet or even laptop might conveniently fit in your pocket or backpack, but all these devices are fraught with compromises, whether it's computing power, screen size, or, well, a really expensive price tag."

concealment points out a rebuttal from PCWorld of the increasingly common claims that we live in a post-PC world. "It's an intriguing proposition, but don't count on mobile devices killing off your desktop PC any time soon. While mobile gear is certainly convenient when you're trying to conduct business on the go, it's nowhere near as convenient as a desktop when you're trying to complete serious work in an office environment. Sure, your phone, tablet or even laptop might conveniently fit in your pocket or backpack, but all these devices are fraught with compromises, whether it's computing power, screen size, or, well, a really expensive price tag."

concealment points out a rebuttal from PCWorld of the increasingly common claims that we live in a post-PC world. "It's an intriguing proposition, but don't count on mobile devices killing off your desktop PC any time soon. While mobile gear is certainly convenient when you're trying to conduct business on the go, it's nowhere near as convenient as a desktop when you're trying to complete serious work in an office environment. Sure, your phone, tablet or even laptop might conveniently fit in your pocket or backpack, but all these devices are fraught with compromises, whether it's computing power, screen size, or, well, a really expensive price tag."

tsu doh nimh writes "Brian Krebs follows up on a recent Slashdot discussion about a cybercrime gang that is recruiting botmasters to help with concerted heists against U.S. financial institutions. The story looks at the underground's skeptical response to this campaign, which is being led by a criminal hacker named vorVzakone ('thief in law'), who has released a series of videos about himself. vorVzakone also is offering a service called 'insurance from criminal prosecution,' in which miscreants can purchase protection from goons who specialize in bribing or intimidating Russian/Eastern European police into scuttling cybercrime investigations. For $100,000, the service also claims to have people willing to go to jail in place of the insured. Many in the criminal underground view the entire scheme as an elaborate police sting operation."

concealment writes with this extract from GigaOm: "'We buy lots and lots of hard drives . . . . [They] are the single biggest cost in the entire company.' Those are the words of Backblaze Founder and CEO Gleb Budman, whose company offers unlimited cloud backup for just $5 a month, and fills 50TB worth of new storage a day in its custom-built, open source pod architecture. So one might imagine the cloud storage startup was pretty upset when flooding in Thailand caused a global shortage on internal hard drives last year. Backblaze details much the process in a Tuesday-morning blog post, including the hijinks that followed as the company got creative trying to figure out ways around the new hard drive limits. Maps were drawn, employees were cut off from purchasing hard drives at Costco — both in-person throughout Silicon Valley and online (despite some great efforts to avoid detection, such as paying for hard drives online using gift cards) — and friends and family across the country were conscripted into a hard-drive-buying army."

concealment writes "A new lawsuit targets Google for reading e-mails to target ads, according to TechCrunch. But the issue isn't that Google is reading e-mails from registered users; rather, the company is using e-mails sent from other services to Google users to target ads as well. Google has gotten the side-eye a few times in the past for using e-mail content to serve context-based ads to its Gmail users. And for those Gmail users, Google's hide is covered: the terms of service explicitly state that users' e-mail content determines what ads they see."

First time accepted submitter Tator Tot writes "A small radioactive cylinder that went missing from a Halliburton Co. truck last month was found on a Texas road late Thursday, the company said, ending a weeks-long hunt that involved local, state and federal authorities."

Hugh Pickens writes "Nokia has seen better days. The Finnish phone maker continues to struggle to gain traction in a marketplace dominated by Apple and Android, and its new flagship device, the Windows-powered Lumia 920, failed to impress investors when it was announced last month, subsequently causing the company's stock to dive. Now Tristan Louis argues that there are four good reasons Apple should dig into its deep pockets and buy Nokia. First Nokia has really powerful mapping technology. Apple Maps isn't very good, and Apple has been feeling the heat from a critical tech press but Nokia has been doing maps 'for a long time now, and they a have access to even more data than Google.' Next, Nokia has a treasure chest of patents and as Apple's recent smackdown of Samsung proves, the future of the mobile space 'will be dictated by the availability and ownership of patents.' Nokia's exhaustive portfolio of patents might be worth as much as $6 billion to $10 billion, a drop in the bucket from Apple's $100 billion war chest. Nokia could also help with TV. If Apple truly wants to dominate the TV arena, it'll have to beam shows and movies to iPhones or iPads in real time, and that's a field Nokia has some expertise in. Finally Microsoft has a lot riding on the release of Windows Phone 8, and Nokia is its primary launch partner. Buying Nokia would 'knock Microsoft on its heels,' says Forbes' Upbin."

Hugh Pickens writes "Nokia has seen better days. The Finnish phone maker continues to struggle to gain traction in a marketplace dominated by Apple and Android, and its new flagship device, the Windows-powered Lumia 920, failed to impress investors when it was announced last month, subsequently causing the company's stock to dive. Now Tristan Louis argues that there are four good reasons Apple should dig into its deep pockets and buy Nokia. First Nokia has really powerful mapping technology. Apple Maps isn't very good, and Apple has been feeling the heat from a critical tech press but Nokia has been doing maps 'for a long time now, and they a have access to even more data than Google.' Next, Nokia has a treasure chest of patents and as Apple's recent smackdown of Samsung proves, the future of the mobile space 'will be dictated by the availability and ownership of patents.' Nokia's exhaustive portfolio of patents might be worth as much as $6 billion to $10 billion, a drop in the bucket from Apple's $100 billion war chest. Nokia could also help with TV. If Apple truly wants to dominate the TV arena, it'll have to beam shows and movies to iPhones or iPads in real time, and that's a field Nokia has some expertise in. Finally Microsoft has a lot riding on the release of Windows Phone 8, and Nokia is its primary launch partner. Buying Nokia would 'knock Microsoft on its heels,' says Forbes' Upbin."

Jafafa Hots writes "The Supreme Court is set to decide, in the case of Kirtsaeng v. John Wiley & Sons, whether or not First Sale Doctrine applies to products made with parts sourced from outside the United States. If the Supreme Court upholds an appellate ruling, it would mean that the IP holders of anything you own that has been made in China, Japan or Europe, for example, would have to give you permission to sell it. Your old used CDs, cell phone, books, or that Ford truck with foreign parts? It may not be yours to sell unless you get explicit permission and presumably pay royalties. 'It would be absurd to say anything manufactured abroad can't be bought or sold here,' said Marvin Ammori, a First Amendment lawyer and Schwartz Fellow at the New American Foundation who specializes in technology issues."

New submitter Jalfro writes "Following premature rumors of its demise, the Diaspora core team announce the release of 0.0.1.0. 'It's been a couple of exciting months for us as we've shifted over to a model of community governance. After switching over to SemVer for our versioning system, and plugging away at fixing code through our new unstable branch, we're excited to make our first release beyond the Alpha/Beta labels.'"

concealment writes "Luckily, the Fire's low price and popularity relative to other Android tablets has made it a common target for Android's bustling open-source community, which has automated most of the sometimes-messy process of rooting and flashing your tablet. The Kindle Fire Utility boils the whole rooting process down to a couple of steps, and from there it's pretty easy to find pretty-stable Jelly Bean ROMs. A CyanogenMod-based version is actively maintained, but I prefer the older Hashcode ROM, which is very similar to the interface on the Nexus 7."

First time accepted submitter drichan writes "Those of us who watched the live feed of last night's Falcon 9 launch could be forgiven for assuming that everything went according to plan. All the reports that came through over the audio were heavy on the word "nominal," and the craft successfully entered an orbit that has it on schedule to dock with the International Space Station on Wednesday. But over night, SpaceX released a slow-motion video of what they're calling an 'anomaly.'"

First time accepted submitter poofmeisterp writes "Felix Baumgarner's planned record jump from 120,000 feet has been delayed due to 'bad wind.' Humor aside, it's good that careful thought is going into this potentially record-setting public act. From the article: 'The Austrian - who described himself as "like a tiger in a cage waiting to get out" - was due to leap from his Red Bull Stratos space capsule today at a planned altitude of 36,576m (120,000ft) over the New Mexico desert. However, the weather has forced a 24-hour launch delay. In July, Baumgartner jumped from an altitude of 29,455m (96,640ft), hitting 586.92km/h (364.69mph) during the free fall part of his drop.'"

Nerval's Lobster writes "Poor sales have driven Motorola Mobility to whack the Webtop, its attempt to make Android into an all-in-one operating system for both smartphones and traditional PCs. Motorola confirmed the death to CNET before issuing a widely circulated statement. Webtop allowed users to plug their Motorola device into a special laptop dock, which could then display Web pages and files on a full screen. Supported devices included the Motorola Atrix 2, which launched with Android 2.3 ('Gingerbread') and a dual-core 1GHz processor. For those few who bought a Webtop and now need something to do with it, Liliputing posted an article earlier this year about using the device to transform Raspberry Pi into a laptop (with the aid of some key accessories). Raspberry Pi's homebrew computer features a 700MHz processor capable of overclocking to 1GHz and 256MB of RAM, as well as an SD card for longer storage—specs that lag those of the latest smartphones, but Raspberry Pi has the virtue of being quite a bit cheaper at $35."

Linus Torvalds was (and still is) the primary force behind the development of the Linux kernel, and since you are reading Slashdot, you already knew that. Mr. Torvalds has agreed to answer any questions you may have about the direction of software, his thoughts on politics, winning the Millenial Technology Prize, or anything else. Ask as many questions as you'd like, but please keep them to one per post. We'll send the best to Linus, and post his answers when we get them back. Remember to keep an eye out for the rest of our upcoming special interviews this month.

Linus Torvalds was (and still is) the primary force behind the development of the Linux kernel, and since you are reading Slashdot, you already knew that. Mr. Torvalds has agreed to answer any questions you may have about the direction of software, his thoughts on politics, winning the Millenial Technology Prize, or anything else. Ask as many questions as you'd like, but please keep them to one per post. We'll send the best to Linus, and post his answers when we get them back. Remember to keep an eye out for the rest of our upcoming special interviews this month.

Linus Torvalds was (and still is) the primary force behind the development of the Linux kernel, and since you are reading Slashdot, you already knew that. Mr. Torvalds has agreed to answer any questions you may have about the direction of software, his thoughts on politics, winning the Millenial Technology Prize, or anything else. Ask as many questions as you'd like, but please keep them to one per post. We'll send the best to Linus, and post his answers when we get them back. Remember to keep an eye out for the rest of our upcoming special interviews this month.

concealment writes "At the end of August this year, the US Department of Transport's National Highway Traffic Safety Administration (NHTSA) and the US Environmental Protection Agency (EPA) announced new standards to significantly improve the fuel economy of cars and light trucks by 2025. Last week, we took a look at a range of recent engine technologies that car companies have been deploying in aid of better fuel efficiency today. But what about the cars of tomorrow, or next week? What do Detroit, or Stuttgart, or Tokyo have waiting in the wings that will get to the Obama administration's target of 54.5 miles per gallon (mpg) by 2025?"