Slashdot Mirror

RogueyWon writes "Eurogamer is reporting that Sony has closed its subsidiary developer Studio Liverpool. Beginning its life in 1984 under the name Psygnosis, the development house has played an important role in the history of computer and video gaming, publishing classics such as the Lemmings series. Since its acquisition by Sony in 1993, the studio has been best known for its work on the WipEout franchise, which helped to establish the PlayStation console as a successful brand. Sony's statements indicate that it will seek to find positions for staff in its other development houses, but that some redundancies will be necessary." Eurogamer posted an update, indicating that the studio was working on WipEout for the PS4.

New submitter Celarent Darii writes "Prospects for harvesting Uranium from seawater turned interesting by using shrimp shells as a sort of catalyst." Researchers at ORNL presented their findings from a test of a chitin net for harvesting Uranium at the ACS fall meeting. From the ORNL press release: "In a direct comparison to the current state-of-the-art adsorbent, HiCap provides significantly higher uranium adsorption capacity, faster uptake and higher selectivity, according to test results. Specifically, HiCap's adsorption capacity is seven times higher (146 vs. 22 grams of uranium per kilogram of adsorbent) in spiked solutions containing 6 parts per million of uranium at 20 degrees Celsius. In seawater, HiCap's adsorption capacity of 3.94 grams of uranium per kilogram of adsorbent was more than five times higher than the world's best at 0.74 grams of uranium per kilogram of adsorbent. The numbers for selectivity showed HiCap to be seven times higher."

judgecorp writes "Reports that BitCoin is to issue a credit card have turned out to be false — or at least premature. Mastercard has denied there are any such plans and given details of the procedural barriers to creating such a card."

Hugh Pickens writes "Only four stars, including Barnard's Star, are within six light-years of the Sun, and only 11 are within 10 light-years. That's why Barnard's star, popularized in Robert Forward's hard-SF novel Flight of the Dragonfly, is often short-listed as a target for humanity's first interstellar probe. Astronomers have long hoped to find a habitable planet around it, an alien Earth that might someday bear the boot prints of a future Neil Armstrong, or the tire tracks of a souped-up 25th-century Curiosity rover. But now Ross Anderson reports that a group of researchers led by UC Berkeley's Jieun Choi have delivered the fatal blow to those hopes when they revealed the results of 248 precise Doppler measurements that were designed to examine the star for wobbles indicative of planets around it. The measurements, taken over a period of 25 years, led to a depressing conclusion: 'the habitable zone around Barnard's star appears to be devoid of roughly Earth-mass planets or larger ... [p]revious claims of planets around the star by van de Kamp are strongly refuted.' NASA's Kepler space telescope, which studies a group of distant Milky Way stars, has found more than 2,000 exoplanet candidates in just the past two years, leading many to suspect that our galaxy is home to billions of planets, a sizable portion of which could be habitable. 'This non-detection of nearly Earth-mass planets around Barnard's Star is surely unfortunate, as its distance of only 1.8 parsecs would render any Earth-size planets valuable targets for imaging and spectroscopy, as well as compelling destinations for robotic probes by the end of the century.'"

Sparrowvsrevolution writes "In an update to an earlier story on Slashdot, hotel lock company Onity is now offering a hardware fix for the millions of hotel keycard locks that hacker Cody Brocious demonstrated at Black Hat were vulnerable to being opened by a sub-$50 Arduino device. Unfortunately, Onity wants the hotels who already bought the company's insecure product to pay for the fix. Onity is actually offering two different mitigations: The first is a plug that blocks the port that Brocious used to gain access to the locks' data, as well as more-obscure Torx screws to prevent intruders from opening the lock's case and removing the plug. That band-aid style fix is free. A second, more rigorous fix requires changing the locks' circuit boards manually. In that case, Onity is offering 'special pricing programs' for the new circuit boards customers need to secure their doors, and requiring them to also pay the shipping and labor costs."

tsu doh nimh writes "An examination of a control server seized in the recent takedown of the Grum spam botnet shows the crime machine was far bigger than most experts had assumed. A PHP panel used to control the botnet shows it had just shy of 200,000 systems sending spam when it was dismantled in mid-July. Researchers also found dozens of huge email lists, totaling more than 2.3 billion addresses, as well evidence it was used for phishing and malware attacks in addition to mailing pharmacy spam. Just prior to its takedown, Grum was responsible for sending about one in six spams worldwide."

An anonymous reader writes "As a follow-up to the story about Verizon being forced to allow tethering, the engineers at Connectify climbed on the roof and made a video showing an 85Mbps download rate through a combination of a tethered Verizon mobile phone and all of the available open Wi-Fi networks. It's a darn shame that they cancelled the unlimited 3G on the Kindle; tether 20 of those bad boys and you could have had a real Internet connection."

wiredmikey writes "Wireless Internet routers used in homes and offices could be knitted together to provide a communications system for emergency responders if the mobile phone network fails, German scientists reported on Monday. In many countries, routers are so commonplace that they could be used by police and fire departments if cell towers and networks are down or overwhelmed by people caught up in an emergency, they say. This rich density means that an emergency network could piggyback on nearby routers, giving first responders access to the Internet and contact with their headquarters. The researchers suggest that routers incorporate an emergency 'switch' that responders can activate to set up a backup network, thus giving them a voice and data link through the Internet. This could be done quite easily without impeding users or intruding on their privacy, the study argues. Many routers already have a 'guest' mode, meaning a supplementary channel that allows visitors to use a home's Wi-Fi." This is a cool angle on mesh networking — reminds me of the emergency response capabilities of ham radio; if it sounds intriguing, remember that even sparse networks can make use of this kind of networking with the right antennas. Related: even without touching the hardware on your router, you can do some meshing around with Byzantium.

Nerval's Lobster writes with a piece at SlashCloud that says "Amazon is expanding its reach into the low-cost, high-durability archival storage market with the newly announced Glacier. While Glacier allows companies to transfer their data-archiving duties to the cloud — a potentially money-saving boon for many a budget-squeezed organization—the service comes with some caveats. Its cost structure and slow speed of data retrieval make it best suited for data that needs to be accessed infrequently, such as years-old legal records and research data. If that sounds quite a bit like Amazon Simple Storage Service, otherwise known as Amazon S3, you'd be correct. Both Amazon S3 and Glacier have been designed to store and retrieve data from anywhere with a Web connection. However, Amazon S3 — 'designed to make Web-scale computing easier for developers,' according to the company — is meant for rapid data retrieval; contrast that with a Glacier data-retrieval request (referred to as a 'job'), where it can take between 3 and 5 hours before it's ready for downloading."

kkleiner writes with this snippet: "Just as Google's self-driving Prius goes for distance, recently passing 300,000 miles, Stanford's self-driving Audi TTS instead has the need for speed. The Audi, known as Shelley, sped around the Thunderhill Raceway track north of Sacramento topping 120 miles per hour on straightaways. The less than two and a half minutes it took to complete the 3-mile course is comparable to times achieved by professional drivers." Now if only Montana could take a cue from Nevada's rules for self-driving cars, and bring back "reasonable and prudent" speed regulation, driving out west could get a lot more exciting.

techfun89 writes with an update on OnLive shutting down. From the article: "The restructured OnLive has issued an press release and FAQ to attempt to clear up any rumors and misinformation on the companies recent changes. OnLive is emphasizing that the streaming game service will go on uninterrupted and the 'Newly formed company' will continue to use the OnLive name. The press release also outlines the Assignment for the Benefit of Creditors (ABC) process OnLive used to settle debts and that an affiliate of Lauder Partners, a technology investment firm, was the new OnLive's first investor. The firm talked about the necessity of laying off its staff, stating that 'neither OnLive, Inc. shares nor OnLive staff could transfer under this type of transaction,' and confirming that nearly half of the previous staff had been offered positions at the new company. The new firm mentions that this acquisition holds hope for the future 'of transforming the OnLive vision into reality.' This effectively means that OnLive was essentially bought out by OnLive, or rather, more specifically, one of their original investors in the company who backed the startup back in 2009."

Jon Brodkin writes "There’s a new Super Mario Bros. game out for the 3DS handheld console. It’s called New Super Mario Bros. 2 and features Mario, Princess Peach, Bowser, and the same fun gameplay you’ve come to expect from Nintendo’s most iconic game series. But this latest adventure stands out by not standing out at all." Read below for the rest of Jon's review. To be fair, no one buys a new Mario game looking for a completely new experience. Lovers of “Super Mario Bros. 3” will smile when they stumble upon a very familiar raccoon tail, for example, and use it to take flight into the blue sky of the Mushroom Kingdom. It’s grin-inducing gameplay and familiarity. But nearly every Mario game offers at least one new attribute that distinguishes it from its predecessors—that is, except for this one.

Unlike last year’s “Super Mario 3D Land,” this latest Mario is a 2D side-scroller with gameplay almost identical to the “New Super Mario Bros.” released on Nintendo DS in 2006. The game’s main course is ridiculously easy even by Mario standards, although there’s some challenge presented by the final level and a few of the extra unlockable courses.

While I enjoyed the game (which I’ll now start referring to as “NSMB2”), I couldn’t shake the feeling that I had played it before. Entire courses seemed identical to ones from the “New Super Mario Bros. Wii” game released in 2009, particularly in the lava-filled final world and a middle world filled with purple water, spiderwebs, and giant caterpillars.

Most Mario games have a few levels that are positively exhilarating. “Super Mario Galaxy” was filled with them, including an epic final battle vs. Bowser spanning three planets. “New Super Mario Bros. Wii” has what might be my all-time favorite Mario level, a secret course involving a gigantic skeletal roller-coaster that you ride and cling to until the bitter end—all while hopping and avoiding a treacherous lava pit and the enemies emerging from it. By contrast, there really wasn’t a single level in “NSMB2” that felt exciting; again, the game stands out not for what it offers but for what it doesn’t.

Like previous games in the New Super Mario Bros. series, each course has three star coins tucked away in hidden, hard-to-access areas. It’s the primary trick Nintendo uses to make these games replayable—if you don’t find all the star coins, keep going back and exploring until you do. The star coins can be used to unlock special levels and mushroom houses containing items to help Mario on his way.

Separately from the hidden star coins, there are plain-old-regular Super Mario coins everywhere throughout each level. As you clear levels and build up coins, you unlock a bonus game, “Coin Rush,” in which you replay courses in order to collect more coins. Collect a million coins and the title screen will feature a gold Mario statue. I’m up to 17,000 coins, but I’ve already accomplished my goal of unlocking and completing each level, so I won’t be going much further.

It becomes clear while playing “NSMB2” that Nintendo needs to stop making new Mario games every year. Last year there was “Super Mario 3D Land,” today there’s “New Super Mario Bros. 2,” and coming soon is “New Super Mario Bros. U.” I love Mario, but there are only so many times you can trot out the same game and call it a sequel before the well of innovative gameplay is sucked dry.

After playing through the Italian plumber’s latest, I argue that the only way to save Super Mario Bros. is to give the series a time-out. If Nintendo needs cash in 2012 and 2013, issue a remake of every 8- and 16-bit Mario game for the iPhone, iPad, and Android. Or (since Nintendo hates releasing software for hardware it didn’t build) just release them again with better graphics for the 3DS and upcoming Wii U. No one will hold it against the company.

After doing that, Nintendo should wait. While Mario development will never completely cease, it should be put on the back burner in favor of developing new intellectual property. Keep the Mario wheels moving slowly behind the scenes until you hit upon the right idea, the one that takes the series to the next level like “Super Mario World” and “Super Mario 64” did in the 1990s, or “Super Mario Galaxy” in 2007.

Nintendo can take a page from its own Legend of Zelda series, which maintains its excellence with clever dungeon and over-world design, strong storytelling, and gameplay tweaked to fit the unique strengths of both handheld and traditional consoles. Crucially, years go by between major Zelda releases—that’s how long it takes to get everything right.

I will gladly wait until 2015 for the next Mario game if it’s anywhere near as satisfying as Zelda’s “Twilight Princess” or “Skyward Sword.” Fans waited five years between Zelda releases for the Wii and were rewarded. The same could be true of Mario.

The State of Mario Today: Haven’t I Already Played This Game?

Most gamers assume that each new Mario game will just offer more of the same. But that’s not entirely true. I’ve been playing Mario my whole life, and to my mind nearly every one stands out from the rest for one reason or another.

“Super Mario Bros. 3” and “Super Mario World” built upon the classic original with more intricate level designs, power-up items, and the ride-able dinosaur, Yoshi. “Super Mario 64” brought Nintendo into the 3D age and influenced an entire generation of games. “Super Mario Galaxy” introduced gravity as both villain and friend. And last year’s “Super Mario 3D Land” condensed the best bits of side-scrolling and 3D Mario action into one rollicking, lengthy video game.

With this latest Mario, only one thing distinguishes it from previous editions: coins. Lots and lots of coins. Yes, every Mario game has coins, but this one has lots of them, and you get the aforementioned special rewards for collecting them. If you played “New Super Mario Bros.” for the Nintendo DS, just about everything in this sequel will be familiar: it’s all nearly identical, just not quite as memorable.

Nintendo has fallen behind Sony and Microsoft in courting serious gamers. The fact that its biggest hits are new versions of classic games wouldn’t be concerning if Nintendo could also produce some great new series and attract third-party developers before the latter’s newest games hit the PS3, Xbox 360, and PC (or iOS and Android).

And while Nintendo still leads the handheld gaming market, it had to drastically cut the price of the 3DS. This holiday season, Nintendo will release a home console that finally puts it on graphical parity with the half-decade-old PS3 and Xbox 360. The list of launch games for the Wii U is notable for including third-party titles that hit rival consoles a year ago, such as “Batman: Arkham City.”

The thing Nintendo is really trying to build excitement around is “Nintendo Land,” a game that will supposedly explain the appeal of the Wii U in the same way Wii Sports sold players on the motion control capabilities of the original Wii. It’s hard to see how this strategy will succeed on a massive scale. “Nintendo Land” is basically just a series of mini-games based on Nintendo’s most successful franchises, as the company desperately clings to its past to remain relevant. It’s like saying, “hey, remember when these games really mattered?”

The Future of Mario

Ultimately, “NSMB2” is an enjoyable experience that leaves me discouraged about the future of the Mario series. While the Legend of Zelda has remained fresh, Nintendo is relying on gimmicks to make each new Mario game seem slightly different than the last. But with level design virtually identical from one game to the next, releasing three Mario games in just over a year will only make matters worse.

I don’t think Mario has run its course for all time. As I mentioned before, I just think the course has been run for 2012 and probably 2013. (Instead of playing the essentially same game with a “2” or a “U” appended to the title, I may as well replay the games that made me love Mario in the first place.) That’s why, instead of releasing one new Mario game every year (or worse, several), Nintendo should dramatically slow down and focus on one or two new Marios for each console generation.

Nerval's Lobster writes "Dr. Armando Angulo was indicted in 2007 on charges of illegally selling prescription drugs. He fled the country in 2004, with the Drug Enforcement Administration (DEA) and U.S. Marshals Service eventually finding him in Panama. As the case developed (and Panama resisted calls to extradite Angulo back to the United States), the DEA apparently amassed so much electronic data that maintaining it is now a hardship; consequently, the government wants to drop the whole case. 'These materials include two terabytes of electronic data (which consume approximately 5 percent of DEA's world-wide electronic storage capacity),' Stephanie M. Rose, the U.S. attorney for northern Iowa, wrote in the government's July motion to dismiss the indictment. 'Continued storage of these materials is difficult and expensive.' In addition, information associated with the case had managed to fill 'several hundred boxes' of paper documents, along with dozens of computers and servers. As pointed out by Ars Technica, if two terabytes of data storage represents 5 percent of the DEA's global capacity, then the agency has only 40 terabytes worth of storage overall. That seems quite small for a law enforcement agency tasked with coordinating and pursuing any number of drug investigations at any given time."

This past week, SCO filed for Chapter 7 bankruptcy, which finally begins the end of a long saga that started over nine years ago. While their anti-IBM litigation has risen from the grave and still shambles onward, the company itself is nearly put to rest after nine years of choosing the wrong legal battle to get into. Even if it may be too early to dance on SCO's grave, join me as I look back over the long and bumpy road to nowhere of The SCO Group.

The Beginning, or, We Sure Do Miss Ransom Love Around Here

Back in January of 2003, SCO announced that Unix SYSV code had been misappropriated into Linux. They didn't say much more than this, saying that they would only reveal the code in question to the court, and that it was a secret. Given the nature of Linux, this set off the BS-meters of nearly anyone with a clue, including the Linux kernel developers, not the least of which being Linus himself. In March of that year, SCO announced that they owned the copyrights to Unix, and that they were suing IBM for a billion dollars, for leaking SCO trade secrets into Linux. When people who had a clue thought about the case for more than a few minutes, they remembered back to the USL v. BSDi case that had been settled a decade prior, and figured SCO was full of it. Unfortunately, instead of SCO's announcement being taken as the ramblings of a crazy CEO desperate to increase the value of his flagging company, it went ahead. The worst part, is that at least for the short term, it worked. SCO's stock price shot from under $2/share to over $20/share in six months.

Around this time, a new champion would arise. A new website, Groklaw, run by paralegal Pamela Jones began blogging daily coverage of SCO v. IBM. While Groklaw was originally intended as a way for PJ to practice blogging, it soon grew into the front lines of the PR war against SCO, a war which they were losing badly.

This is where the case should have been thrown out, and everyone gone out for beers and had a good laugh, but that didn't happen. However, a new challenger would appear. In August of 2003, Red Hat sued SCO to try and put an end to this mess. While this was a valiant effort on Red Hat's part, ultimately a judge would stay the case pending the outcome of SCO v. IBM. Those hard-earned beers would have to wait.

At this point, SCO's claims were sounding dubious at best, so they showed off two samples of alleged copied code at a reseller show later that month. However, the code in question was shown to be part of BSD, and previously released under the BSD license. In spite of this, SCO decided that to save face, they should waste everyone's time with continuing their warpath of litigation.

SCO v. Everyone

Since the suit against IBM was going so well, The SCO Group came up with the brilliant strategy of "sue all the things!" and proceeded to do just that. In lieu of having their own product that people actually liked and used, they figured they could just sue their way to profitability.

One of SCO's key claims was that they owned the copyrights to Unix, due to some purchases they'd made from Novell. Novell, however, didn't take this sitting down and respectfully disagreed. For butting in on SCO's new business model, Novell was served with a lawsuit in January of 2004. 2004 was the year that SCO decided to sue everyone they looked at. AutoZone, who had recently switched from using SCO OpenServer to Linux, got sued for doing so. DaimlerChrysler was just walking down the opposite side of the street and accidentally made eye contact with SCO, and they got sued as well.

While also suing everyone in sight, SCO also announced that they would not sue their own customers, so for the price of a SCO license, a company could exclude themselves from possible litigation. A few companies actually bought into the madness, but for the most part, the world collectively rolled its eyes at SCO, meaning that SCO would have to soldier on with their lawsuit-based business strategy, or face the wrath of their shareholders.

Novell Jams SCO's Gears

A few years went past while the SCO v. IBM case was still in the discovery phase, with SCO not wanting to reveal the code they were suing over, without seeing sources from IBM first, and IBM not wanting to give SCO any source without first being told what code was in question. This provided time for the Novell case to advance, albeit also slowly. By 2007, Novell was awarded several summary judgements, and several of SCO's claims were denied. By 2008, Novell had been awarded over $3 million as a result of the case. Just under half of that amount would be appealed by SCO, and temporarily reversed for a couple of more years. The main outcome here, however, was that Novell was ruled as the owner of the Unix copyrights.

The SCO legal juggernaut, however, would not, nay, could not be stopped. Despite not owning the Unix copyrights they contended they were the owners of "control rights" to derivatives of SYSV, and for the period during the appeals to SCO v. Novell, they were still able to claim potential ownership of the Unix copyrights in court as well. When they finally lost the appeals, they were forced to fall back to their claims of control rights, which is where they still stand today.

Being faced with having to pay out to Novell, SCO finally received its first nail in its coffin. Following the Novell ruling, SCO filed for Chapter 11 bankruptcy, and SCO v. IBM was stayed until SCO could emerge from Chapter 11 and continue the case. Shortly thereafter, SCO's stock price fell to under $0.50/share and they were de-listed from NASDAQ.

The End of SCO, but not of SCO v. IBM

So that's where we are today. Once the Chapter 7 filing is finalized by a judge, SCO will cease to be as a corporate entity, however they are proposing that SCO v. IBM be allowed to continue, not for sheer entertainment value, but rather so that they don't risk the wrath of their shareholders.

Nine years on, it's difficult to say who the real winners are. It's definitely not The SCO Group themselves, since they've gone under. It's also probably not SCO's lawyers, since their chances for being paid are greatly diminished since SCO's short-lived high times in 2003. IBM stands poised to win the case should it go forward, however their legal expenditures at this point are so large they could only be fielded by the likes of IBM. Novell, despite having already won, may not ever get paid all that it's owed. Linux users will most likely eventually emerge as not having to pay SCO a dime, which while is nice to have reaffirmed, is where they were back in 2003 to begin with. Another side effect of the courts rulings, was the reaffirmation of USL v. BSDi, which means that FreeBSD users are definitely safe from licensing fees and litigation.

While I've given an overview of the SCO-Linux litigations here, I've surely missed many of the bumps in the road. I only briefly touched on the PR war SCO fought against Groklaw, and many of the other insanities brought on by this case. With SCO v. IBM still possibly lunging ahead in a stupor, it may be too early to finally enjoy those aforementioned hard-earned beers, but it's still safe to chill them with the ice off SCO's corpse.

This past week, SCO filed for Chapter 7 bankruptcy, which finally begins the end of a long saga that started over nine years ago. While their anti-IBM litigation has risen from the grave and still shambles onward, the company itself is nearly put to rest after nine years of choosing the wrong legal battle to get into. Even if it may be too early to dance on SCO's grave, join me as I look back over the long and bumpy road to nowhere of The SCO Group.

The Beginning, or, We Sure Do Miss Ransom Love Around Here

Back in January of 2003, SCO announced that Unix SYSV code had been misappropriated into Linux. They didn't say much more than this, saying that they would only reveal the code in question to the court, and that it was a secret. Given the nature of Linux, this set off the BS-meters of nearly anyone with a clue, including the Linux kernel developers, not the least of which being Linus himself. In March of that year, SCO announced that they owned the copyrights to Unix, and that they were suing IBM for a billion dollars, for leaking SCO trade secrets into Linux. When people who had a clue thought about the case for more than a few minutes, they remembered back to the USL v. BSDi case that had been settled a decade prior, and figured SCO was full of it. Unfortunately, instead of SCO's announcement being taken as the ramblings of a crazy CEO desperate to increase the value of his flagging company, it went ahead. The worst part, is that at least for the short term, it worked. SCO's stock price shot from under $2/share to over $20/share in six months.

Around this time, a new champion would arise. A new website, Groklaw, run by paralegal Pamela Jones began blogging daily coverage of SCO v. IBM. While Groklaw was originally intended as a way for PJ to practice blogging, it soon grew into the front lines of the PR war against SCO, a war which they were losing badly.

This is where the case should have been thrown out, and everyone gone out for beers and had a good laugh, but that didn't happen. However, a new challenger would appear. In August of 2003, Red Hat sued SCO to try and put an end to this mess. While this was a valiant effort on Red Hat's part, ultimately a judge would stay the case pending the outcome of SCO v. IBM. Those hard-earned beers would have to wait.

At this point, SCO's claims were sounding dubious at best, so they showed off two samples of alleged copied code at a reseller show later that month. However, the code in question was shown to be part of BSD, and previously released under the BSD license. In spite of this, SCO decided that to save face, they should waste everyone's time with continuing their warpath of litigation.

SCO v. Everyone

Since the suit against IBM was going so well, The SCO Group came up with the brilliant strategy of "sue all the things!" and proceeded to do just that. In lieu of having their own product that people actually liked and used, they figured they could just sue their way to profitability.

One of SCO's key claims was that they owned the copyrights to Unix, due to some purchases they'd made from Novell. Novell, however, didn't take this sitting down and respectfully disagreed. For butting in on SCO's new business model, Novell was served with a lawsuit in January of 2004. 2004 was the year that SCO decided to sue everyone they looked at. AutoZone, who had recently switched from using SCO OpenServer to Linux, got sued for doing so. DaimlerChrysler was just walking down the opposite side of the street and accidentally made eye contact with SCO, and they got sued as well.

While also suing everyone in sight, SCO also announced that they would not sue their own customers, so for the price of a SCO license, a company could exclude themselves from possible litigation. A few companies actually bought into the madness, but for the most part, the world collectively rolled its eyes at SCO, meaning that SCO would have to soldier on with their lawsuit-based business strategy, or face the wrath of their shareholders.

Novell Jams SCO's Gears

A few years went past while the SCO v. IBM case was still in the discovery phase, with SCO not wanting to reveal the code they were suing over, without seeing sources from IBM first, and IBM not wanting to give SCO any source without first being told what code was in question. This provided time for the Novell case to advance, albeit also slowly. By 2007, Novell was awarded several summary judgements, and several of SCO's claims were denied. By 2008, Novell had been awarded over $3 million as a result of the case. Just under half of that amount would be appealed by SCO, and temporarily reversed for a couple of more years. The main outcome here, however, was that Novell was ruled as the owner of the Unix copyrights.

The SCO legal juggernaut, however, would not, nay, could not be stopped. Despite not owning the Unix copyrights they contended they were the owners of "control rights" to derivatives of SYSV, and for the period during the appeals to SCO v. Novell, they were still able to claim potential ownership of the Unix copyrights in court as well. When they finally lost the appeals, they were forced to fall back to their claims of control rights, which is where they still stand today.

Being faced with having to pay out to Novell, SCO finally received its first nail in its coffin. Following the Novell ruling, SCO filed for Chapter 11 bankruptcy, and SCO v. IBM was stayed until SCO could emerge from Chapter 11 and continue the case. Shortly thereafter, SCO's stock price fell to under $0.50/share and they were de-listed from NASDAQ.

The End of SCO, but not of SCO v. IBM

So that's where we are today. Once the Chapter 7 filing is finalized by a judge, SCO will cease to be as a corporate entity, however they are proposing that SCO v. IBM be allowed to continue, not for sheer entertainment value, but rather so that they don't risk the wrath of their shareholders.

Nine years on, it's difficult to say who the real winners are. It's definitely not The SCO Group themselves, since they've gone under. It's also probably not SCO's lawyers, since their chances for being paid are greatly diminished since SCO's short-lived high times in 2003. IBM stands poised to win the case should it go forward, however their legal expenditures at this point are so large they could only be fielded by the likes of IBM. Novell, despite having already won, may not ever get paid all that it's owed. Linux users will most likely eventually emerge as not having to pay SCO a dime, which while is nice to have reaffirmed, is where they were back in 2003 to begin with. Another side effect of the courts rulings, was the reaffirmation of USL v. BSDi, which means that FreeBSD users are definitely safe from licensing fees and litigation.

While I've given an overview of the SCO-Linux litigations here, I've surely missed many of the bumps in the road. I only briefly touched on the PR war SCO fought against Groklaw, and many of the other insanities brought on by this case. With SCO v. IBM still possibly lunging ahead in a stupor, it may be too early to finally enjoy those aforementioned hard-earned beers, but it's still safe to chill them with the ice off SCO's corpse.

This past week, SCO filed for Chapter 7 bankruptcy, which finally begins the end of a long saga that started over nine years ago. While their anti-IBM litigation has risen from the grave and still shambles onward, the company itself is nearly put to rest after nine years of choosing the wrong legal battle to get into. Even if it may be too early to dance on SCO's grave, join me as I look back over the long and bumpy road to nowhere of The SCO Group.

The Beginning, or, We Sure Do Miss Ransom Love Around Here

Back in January of 2003, SCO announced that Unix SYSV code had been misappropriated into Linux. They didn't say much more than this, saying that they would only reveal the code in question to the court, and that it was a secret. Given the nature of Linux, this set off the BS-meters of nearly anyone with a clue, including the Linux kernel developers, not the least of which being Linus himself. In March of that year, SCO announced that they owned the copyrights to Unix, and that they were suing IBM for a billion dollars, for leaking SCO trade secrets into Linux. When people who had a clue thought about the case for more than a few minutes, they remembered back to the USL v. BSDi case that had been settled a decade prior, and figured SCO was full of it. Unfortunately, instead of SCO's announcement being taken as the ramblings of a crazy CEO desperate to increase the value of his flagging company, it went ahead. The worst part, is that at least for the short term, it worked. SCO's stock price shot from under $2/share to over $20/share in six months.

Around this time, a new champion would arise. A new website, Groklaw, run by paralegal Pamela Jones began blogging daily coverage of SCO v. IBM. While Groklaw was originally intended as a way for PJ to practice blogging, it soon grew into the front lines of the PR war against SCO, a war which they were losing badly.

This is where the case should have been thrown out, and everyone gone out for beers and had a good laugh, but that didn't happen. However, a new challenger would appear. In August of 2003, Red Hat sued SCO to try and put an end to this mess. While this was a valiant effort on Red Hat's part, ultimately a judge would stay the case pending the outcome of SCO v. IBM. Those hard-earned beers would have to wait.

At this point, SCO's claims were sounding dubious at best, so they showed off two samples of alleged copied code at a reseller show later that month. However, the code in question was shown to be part of BSD, and previously released under the BSD license. In spite of this, SCO decided that to save face, they should waste everyone's time with continuing their warpath of litigation.

SCO v. Everyone

Since the suit against IBM was going so well, The SCO Group came up with the brilliant strategy of "sue all the things!" and proceeded to do just that. In lieu of having their own product that people actually liked and used, they figured they could just sue their way to profitability.

One of SCO's key claims was that they owned the copyrights to Unix, due to some purchases they'd made from Novell. Novell, however, didn't take this sitting down and respectfully disagreed. For butting in on SCO's new business model, Novell was served with a lawsuit in January of 2004. 2004 was the year that SCO decided to sue everyone they looked at. AutoZone, who had recently switched from using SCO OpenServer to Linux, got sued for doing so. DaimlerChrysler was just walking down the opposite side of the street and accidentally made eye contact with SCO, and they got sued as well.

While also suing everyone in sight, SCO also announced that they would not sue their own customers, so for the price of a SCO license, a company could exclude themselves from possible litigation. A few companies actually bought into the madness, but for the most part, the world collectively rolled its eyes at SCO, meaning that SCO would have to soldier on with their lawsuit-based business strategy, or face the wrath of their shareholders.

Novell Jams SCO's Gears

A few years went past while the SCO v. IBM case was still in the discovery phase, with SCO not wanting to reveal the code they were suing over, without seeing sources from IBM first, and IBM not wanting to give SCO any source without first being told what code was in question. This provided time for the Novell case to advance, albeit also slowly. By 2007, Novell was awarded several summary judgements, and several of SCO's claims were denied. By 2008, Novell had been awarded over $3 million as a result of the case. Just under half of that amount would be appealed by SCO, and temporarily reversed for a couple of more years. The main outcome here, however, was that Novell was ruled as the owner of the Unix copyrights.

The SCO legal juggernaut, however, would not, nay, could not be stopped. Despite not owning the Unix copyrights they contended they were the owners of "control rights" to derivatives of SYSV, and for the period during the appeals to SCO v. Novell, they were still able to claim potential ownership of the Unix copyrights in court as well. When they finally lost the appeals, they were forced to fall back to their claims of control rights, which is where they still stand today.

Being faced with having to pay out to Novell, SCO finally received its first nail in its coffin. Following the Novell ruling, SCO filed for Chapter 11 bankruptcy, and SCO v. IBM was stayed until SCO could emerge from Chapter 11 and continue the case. Shortly thereafter, SCO's stock price fell to under $0.50/share and they were de-listed from NASDAQ.

The End of SCO, but not of SCO v. IBM

So that's where we are today. Once the Chapter 7 filing is finalized by a judge, SCO will cease to be as a corporate entity, however they are proposing that SCO v. IBM be allowed to continue, not for sheer entertainment value, but rather so that they don't risk the wrath of their shareholders.

Nine years on, it's difficult to say who the real winners are. It's definitely not The SCO Group themselves, since they've gone under. It's also probably not SCO's lawyers, since their chances for being paid are greatly diminished since SCO's short-lived high times in 2003. IBM stands poised to win the case should it go forward, however their legal expenditures at this point are so large they could only be fielded by the likes of IBM. Novell, despite having already won, may not ever get paid all that it's owed. Linux users will most likely eventually emerge as not having to pay SCO a dime, which while is nice to have reaffirmed, is where they were back in 2003 to begin with. Another side effect of the courts rulings, was the reaffirmation of USL v. BSDi, which means that FreeBSD users are definitely safe from licensing fees and litigation.

While I've given an overview of the SCO-Linux litigations here, I've surely missed many of the bumps in the road. I only briefly touched on the PR war SCO fought against Groklaw, and many of the other insanities brought on by this case. With SCO v. IBM still possibly lunging ahead in a stupor, it may be too early to finally enjoy those aforementioned hard-earned beers, but it's still safe to chill them with the ice off SCO's corpse.

This past week, SCO filed for Chapter 7 bankruptcy, which finally begins the end of a long saga that started over nine years ago. While their anti-IBM litigation has risen from the grave and still shambles onward, the company itself is nearly put to rest after nine years of choosing the wrong legal battle to get into. Even if it may be too early to dance on SCO's grave, join me as I look back over the long and bumpy road to nowhere of The SCO Group.

The Beginning, or, We Sure Do Miss Ransom Love Around Here

Back in January of 2003, SCO announced that Unix SYSV code had been misappropriated into Linux. They didn't say much more than this, saying that they would only reveal the code in question to the court, and that it was a secret. Given the nature of Linux, this set off the BS-meters of nearly anyone with a clue, including the Linux kernel developers, not the least of which being Linus himself. In March of that year, SCO announced that they owned the copyrights to Unix, and that they were suing IBM for a billion dollars, for leaking SCO trade secrets into Linux. When people who had a clue thought about the case for more than a few minutes, they remembered back to the USL v. BSDi case that had been settled a decade prior, and figured SCO was full of it. Unfortunately, instead of SCO's announcement being taken as the ramblings of a crazy CEO desperate to increase the value of his flagging company, it went ahead. The worst part, is that at least for the short term, it worked. SCO's stock price shot from under $2/share to over $20/share in six months.

Around this time, a new champion would arise. A new website, Groklaw, run by paralegal Pamela Jones began blogging daily coverage of SCO v. IBM. While Groklaw was originally intended as a way for PJ to practice blogging, it soon grew into the front lines of the PR war against SCO, a war which they were losing badly.

This is where the case should have been thrown out, and everyone gone out for beers and had a good laugh, but that didn't happen. However, a new challenger would appear. In August of 2003, Red Hat sued SCO to try and put an end to this mess. While this was a valiant effort on Red Hat's part, ultimately a judge would stay the case pending the outcome of SCO v. IBM. Those hard-earned beers would have to wait.

At this point, SCO's claims were sounding dubious at best, so they showed off two samples of alleged copied code at a reseller show later that month. However, the code in question was shown to be part of BSD, and previously released under the BSD license. In spite of this, SCO decided that to save face, they should waste everyone's time with continuing their warpath of litigation.

SCO v. Everyone

Since the suit against IBM was going so well, The SCO Group came up with the brilliant strategy of "sue all the things!" and proceeded to do just that. In lieu of having their own product that people actually liked and used, they figured they could just sue their way to profitability.

One of SCO's key claims was that they owned the copyrights to Unix, due to some purchases they'd made from Novell. Novell, however, didn't take this sitting down and respectfully disagreed. For butting in on SCO's new business model, Novell was served with a lawsuit in January of 2004. 2004 was the year that SCO decided to sue everyone they looked at. AutoZone, who had recently switched from using SCO OpenServer to Linux, got sued for doing so. DaimlerChrysler was just walking down the opposite side of the street and accidentally made eye contact with SCO, and they got sued as well.

While also suing everyone in sight, SCO also announced that they would not sue their own customers, so for the price of a SCO license, a company could exclude themselves from possible litigation. A few companies actually bought into the madness, but for the most part, the world collectively rolled its eyes at SCO, meaning that SCO would have to soldier on with their lawsuit-based business strategy, or face the wrath of their shareholders.

Novell Jams SCO's Gears

A few years went past while the SCO v. IBM case was still in the discovery phase, with SCO not wanting to reveal the code they were suing over, without seeing sources from IBM first, and IBM not wanting to give SCO any source without first being told what code was in question. This provided time for the Novell case to advance, albeit also slowly. By 2007, Novell was awarded several summary judgements, and several of SCO's claims were denied. By 2008, Novell had been awarded over $3 million as a result of the case. Just under half of that amount would be appealed by SCO, and temporarily reversed for a couple of more years. The main outcome here, however, was that Novell was ruled as the owner of the Unix copyrights.

The SCO legal juggernaut, however, would not, nay, could not be stopped. Despite not owning the Unix copyrights they contended they were the owners of "control rights" to derivatives of SYSV, and for the period during the appeals to SCO v. Novell, they were still able to claim potential ownership of the Unix copyrights in court as well. When they finally lost the appeals, they were forced to fall back to their claims of control rights, which is where they still stand today.

Being faced with having to pay out to Novell, SCO finally received its first nail in its coffin. Following the Novell ruling, SCO filed for Chapter 11 bankruptcy, and SCO v. IBM was stayed until SCO could emerge from Chapter 11 and continue the case. Shortly thereafter, SCO's stock price fell to under $0.50/share and they were de-listed from NASDAQ.

The End of SCO, but not of SCO v. IBM

So that's where we are today. Once the Chapter 7 filing is finalized by a judge, SCO will cease to be as a corporate entity, however they are proposing that SCO v. IBM be allowed to continue, not for sheer entertainment value, but rather so that they don't risk the wrath of their shareholders.

Nine years on, it's difficult to say who the real winners are. It's definitely not The SCO Group themselves, since they've gone under. It's also probably not SCO's lawyers, since their chances for being paid are greatly diminished since SCO's short-lived high times in 2003. IBM stands poised to win the case should it go forward, however their legal expenditures at this point are so large they could only be fielded by the likes of IBM. Novell, despite having already won, may not ever get paid all that it's owed. Linux users will most likely eventually emerge as not having to pay SCO a dime, which while is nice to have reaffirmed, is where they were back in 2003 to begin with. Another side effect of the courts rulings, was the reaffirmation of USL v. BSDi, which means that FreeBSD users are definitely safe from licensing fees and litigation.

While I've given an overview of the SCO-Linux litigations here, I've surely missed many of the bumps in the road. I only briefly touched on the PR war SCO fought against Groklaw, and many of the other insanities brought on by this case. With SCO v. IBM still possibly lunging ahead in a stupor, it may be too early to finally enjoy those aforementioned hard-earned beers, but it's still safe to chill them with the ice off SCO's corpse.

This past week, SCO filed for Chapter 7 bankruptcy, which finally begins the end of a long saga that started over nine years ago. While their anti-IBM litigation has risen from the grave and still shambles onward, the company itself is nearly put to rest after nine years of choosing the wrong legal battle to get into. Even if it may be too early to dance on SCO's grave, join me as I look back over the long and bumpy road to nowhere of The SCO Group.

The Beginning, or, We Sure Do Miss Ransom Love Around Here

Back in January of 2003, SCO announced that Unix SYSV code had been misappropriated into Linux. They didn't say much more than this, saying that they would only reveal the code in question to the court, and that it was a secret. Given the nature of Linux, this set off the BS-meters of nearly anyone with a clue, including the Linux kernel developers, not the least of which being Linus himself. In March of that year, SCO announced that they owned the copyrights to Unix, and that they were suing IBM for a billion dollars, for leaking SCO trade secrets into Linux. When people who had a clue thought about the case for more than a few minutes, they remembered back to the USL v. BSDi case that had been settled a decade prior, and figured SCO was full of it. Unfortunately, instead of SCO's announcement being taken as the ramblings of a crazy CEO desperate to increase the value of his flagging company, it went ahead. The worst part, is that at least for the short term, it worked. SCO's stock price shot from under $2/share to over $20/share in six months.

Around this time, a new champion would arise. A new website, Groklaw, run by paralegal Pamela Jones began blogging daily coverage of SCO v. IBM. While Groklaw was originally intended as a way for PJ to practice blogging, it soon grew into the front lines of the PR war against SCO, a war which they were losing badly.

This is where the case should have been thrown out, and everyone gone out for beers and had a good laugh, but that didn't happen. However, a new challenger would appear. In August of 2003, Red Hat sued SCO to try and put an end to this mess. While this was a valiant effort on Red Hat's part, ultimately a judge would stay the case pending the outcome of SCO v. IBM. Those hard-earned beers would have to wait.

At this point, SCO's claims were sounding dubious at best, so they showed off two samples of alleged copied code at a reseller show later that month. However, the code in question was shown to be part of BSD, and previously released under the BSD license. In spite of this, SCO decided that to save face, they should waste everyone's time with continuing their warpath of litigation.

SCO v. Everyone

Since the suit against IBM was going so well, The SCO Group came up with the brilliant strategy of "sue all the things!" and proceeded to do just that. In lieu of having their own product that people actually liked and used, they figured they could just sue their way to profitability.

One of SCO's key claims was that they owned the copyrights to Unix, due to some purchases they'd made from Novell. Novell, however, didn't take this sitting down and respectfully disagreed. For butting in on SCO's new business model, Novell was served with a lawsuit in January of 2004. 2004 was the year that SCO decided to sue everyone they looked at. AutoZone, who had recently switched from using SCO OpenServer to Linux, got sued for doing so. DaimlerChrysler was just walking down the opposite side of the street and accidentally made eye contact with SCO, and they got sued as well.

While also suing everyone in sight, SCO also announced that they would not sue their own customers, so for the price of a SCO license, a company could exclude themselves from possible litigation. A few companies actually bought into the madness, but for the most part, the world collectively rolled its eyes at SCO, meaning that SCO would have to soldier on with their lawsuit-based business strategy, or face the wrath of their shareholders.

Novell Jams SCO's Gears

A few years went past while the SCO v. IBM case was still in the discovery phase, with SCO not wanting to reveal the code they were suing over, without seeing sources from IBM first, and IBM not wanting to give SCO any source without first being told what code was in question. This provided time for the Novell case to advance, albeit also slowly. By 2007, Novell was awarded several summary judgements, and several of SCO's claims were denied. By 2008, Novell had been awarded over $3 million as a result of the case. Just under half of that amount would be appealed by SCO, and temporarily reversed for a couple of more years. The main outcome here, however, was that Novell was ruled as the owner of the Unix copyrights.

The SCO legal juggernaut, however, would not, nay, could not be stopped. Despite not owning the Unix copyrights they contended they were the owners of "control rights" to derivatives of SYSV, and for the period during the appeals to SCO v. Novell, they were still able to claim potential ownership of the Unix copyrights in court as well. When they finally lost the appeals, they were forced to fall back to their claims of control rights, which is where they still stand today.

Being faced with having to pay out to Novell, SCO finally received its first nail in its coffin. Following the Novell ruling, SCO filed for Chapter 11 bankruptcy, and SCO v. IBM was stayed until SCO could emerge from Chapter 11 and continue the case. Shortly thereafter, SCO's stock price fell to under $0.50/share and they were de-listed from NASDAQ.

The End of SCO, but not of SCO v. IBM

So that's where we are today. Once the Chapter 7 filing is finalized by a judge, SCO will cease to be as a corporate entity, however they are proposing that SCO v. IBM be allowed to continue, not for sheer entertainment value, but rather so that they don't risk the wrath of their shareholders.

Nine years on, it's difficult to say who the real winners are. It's definitely not The SCO Group themselves, since they've gone under. It's also probably not SCO's lawyers, since their chances for being paid are greatly diminished since SCO's short-lived high times in 2003. IBM stands poised to win the case should it go forward, however their legal expenditures at this point are so large they could only be fielded by the likes of IBM. Novell, despite having already won, may not ever get paid all that it's owed. Linux users will most likely eventually emerge as not having to pay SCO a dime, which while is nice to have reaffirmed, is where they were back in 2003 to begin with. Another side effect of the courts rulings, was the reaffirmation of USL v. BSDi, which means that FreeBSD users are definitely safe from licensing fees and litigation.

While I've given an overview of the SCO-Linux litigations here, I've surely missed many of the bumps in the road. I only briefly touched on the PR war SCO fought against Groklaw, and many of the other insanities brought on by this case. With SCO v. IBM still possibly lunging ahead in a stupor, it may be too early to finally enjoy those aforementioned hard-earned beers, but it's still safe to chill them with the ice off SCO's corpse.

This past week, SCO filed for Chapter 7 bankruptcy, which finally begins the end of a long saga that started over nine years ago. While their anti-IBM litigation has risen from the grave and still shambles onward, the company itself is nearly put to rest after nine years of choosing the wrong legal battle to get into. Even if it may be too early to dance on SCO's grave, join me as I look back over the long and bumpy road to nowhere of The SCO Group.

The Beginning, or, We Sure Do Miss Ransom Love Around Here

Back in January of 2003, SCO announced that Unix SYSV code had been misappropriated into Linux. They didn't say much more than this, saying that they would only reveal the code in question to the court, and that it was a secret. Given the nature of Linux, this set off the BS-meters of nearly anyone with a clue, including the Linux kernel developers, not the least of which being Linus himself. In March of that year, SCO announced that they owned the copyrights to Unix, and that they were suing IBM for a billion dollars, for leaking SCO trade secrets into Linux. When people who had a clue thought about the case for more than a few minutes, they remembered back to the USL v. BSDi case that had been settled a decade prior, and figured SCO was full of it. Unfortunately, instead of SCO's announcement being taken as the ramblings of a crazy CEO desperate to increase the value of his flagging company, it went ahead. The worst part, is that at least for the short term, it worked. SCO's stock price shot from under $2/share to over $20/share in six months.

Around this time, a new champion would arise. A new website, Groklaw, run by paralegal Pamela Jones began blogging daily coverage of SCO v. IBM. While Groklaw was originally intended as a way for PJ to practice blogging, it soon grew into the front lines of the PR war against SCO, a war which they were losing badly.

This is where the case should have been thrown out, and everyone gone out for beers and had a good laugh, but that didn't happen. However, a new challenger would appear. In August of 2003, Red Hat sued SCO to try and put an end to this mess. While this was a valiant effort on Red Hat's part, ultimately a judge would stay the case pending the outcome of SCO v. IBM. Those hard-earned beers would have to wait.

At this point, SCO's claims were sounding dubious at best, so they showed off two samples of alleged copied code at a reseller show later that month. However, the code in question was shown to be part of BSD, and previously released under the BSD license. In spite of this, SCO decided that to save face, they should waste everyone's time with continuing their warpath of litigation.

SCO v. Everyone

Since the suit against IBM was going so well, The SCO Group came up with the brilliant strategy of "sue all the things!" and proceeded to do just that. In lieu of having their own product that people actually liked and used, they figured they could just sue their way to profitability.

One of SCO's key claims was that they owned the copyrights to Unix, due to some purchases they'd made from Novell. Novell, however, didn't take this sitting down and respectfully disagreed. For butting in on SCO's new business model, Novell was served with a lawsuit in January of 2004. 2004 was the year that SCO decided to sue everyone they looked at. AutoZone, who had recently switched from using SCO OpenServer to Linux, got sued for doing so. DaimlerChrysler was just walking down the opposite side of the street and accidentally made eye contact with SCO, and they got sued as well.

While also suing everyone in sight, SCO also announced that they would not sue their own customers, so for the price of a SCO license, a company could exclude themselves from possible litigation. A few companies actually bought into the madness, but for the most part, the world collectively rolled its eyes at SCO, meaning that SCO would have to soldier on with their lawsuit-based business strategy, or face the wrath of their shareholders.

Novell Jams SCO's Gears

A few years went past while the SCO v. IBM case was still in the discovery phase, with SCO not wanting to reveal the code they were suing over, without seeing sources from IBM first, and IBM not wanting to give SCO any source without first being told what code was in question. This provided time for the Novell case to advance, albeit also slowly. By 2007, Novell was awarded several summary judgements, and several of SCO's claims were denied. By 2008, Novell had been awarded over $3 million as a result of the case. Just under half of that amount would be appealed by SCO, and temporarily reversed for a couple of more years. The main outcome here, however, was that Novell was ruled as the owner of the Unix copyrights.

The SCO legal juggernaut, however, would not, nay, could not be stopped. Despite not owning the Unix copyrights they contended they were the owners of "control rights" to derivatives of SYSV, and for the period during the appeals to SCO v. Novell, they were still able to claim potential ownership of the Unix copyrights in court as well. When they finally lost the appeals, they were forced to fall back to their claims of control rights, which is where they still stand today.

Being faced with having to pay out to Novell, SCO finally received its first nail in its coffin. Following the Novell ruling, SCO filed for Chapter 11 bankruptcy, and SCO v. IBM was stayed until SCO could emerge from Chapter 11 and continue the case. Shortly thereafter, SCO's stock price fell to under $0.50/share and they were de-listed from NASDAQ.

The End of SCO, but not of SCO v. IBM

So that's where we are today. Once the Chapter 7 filing is finalized by a judge, SCO will cease to be as a corporate entity, however they are proposing that SCO v. IBM be allowed to continue, not for sheer entertainment value, but rather so that they don't risk the wrath of their shareholders.

Nine years on, it's difficult to say who the real winners are. It's definitely not The SCO Group themselves, since they've gone under. It's also probably not SCO's lawyers, since their chances for being paid are greatly diminished since SCO's short-lived high times in 2003. IBM stands poised to win the case should it go forward, however their legal expenditures at this point are so large they could only be fielded by the likes of IBM. Novell, despite having already won, may not ever get paid all that it's owed. Linux users will most likely eventually emerge as not having to pay SCO a dime, which while is nice to have reaffirmed, is where they were back in 2003 to begin with. Another side effect of the courts rulings, was the reaffirmation of USL v. BSDi, which means that FreeBSD users are definitely safe from licensing fees and litigation.

While I've given an overview of the SCO-Linux litigations here, I've surely missed many of the bumps in the road. I only briefly touched on the PR war SCO fought against Groklaw, and many of the other insanities brought on by this case. With SCO v. IBM still possibly lunging ahead in a stupor, it may be too early to finally enjoy those aforementioned hard-earned beers, but it's still safe to chill them with the ice off SCO's corpse.

This past week, SCO filed for Chapter 7 bankruptcy, which finally begins the end of a long saga that started over nine years ago. While their anti-IBM litigation has risen from the grave and still shambles onward, the company itself is nearly put to rest after nine years of choosing the wrong legal battle to get into. Even if it may be too early to dance on SCO's grave, join me as I look back over the long and bumpy road to nowhere of The SCO Group.

The Beginning, or, We Sure Do Miss Ransom Love Around Here

Back in January of 2003, SCO announced that Unix SYSV code had been misappropriated into Linux. They didn't say much more than this, saying that they would only reveal the code in question to the court, and that it was a secret. Given the nature of Linux, this set off the BS-meters of nearly anyone with a clue, including the Linux kernel developers, not the least of which being Linus himself. In March of that year, SCO announced that they owned the copyrights to Unix, and that they were suing IBM for a billion dollars, for leaking SCO trade secrets into Linux. When people who had a clue thought about the case for more than a few minutes, they remembered back to the USL v. BSDi case that had been settled a decade prior, and figured SCO was full of it. Unfortunately, instead of SCO's announcement being taken as the ramblings of a crazy CEO desperate to increase the value of his flagging company, it went ahead. The worst part, is that at least for the short term, it worked. SCO's stock price shot from under $2/share to over $20/share in six months.

Around this time, a new champion would arise. A new website, Groklaw, run by paralegal Pamela Jones began blogging daily coverage of SCO v. IBM. While Groklaw was originally intended as a way for PJ to practice blogging, it soon grew into the front lines of the PR war against SCO, a war which they were losing badly.

This is where the case should have been thrown out, and everyone gone out for beers and had a good laugh, but that didn't happen. However, a new challenger would appear. In August of 2003, Red Hat sued SCO to try and put an end to this mess. While this was a valiant effort on Red Hat's part, ultimately a judge would stay the case pending the outcome of SCO v. IBM. Those hard-earned beers would have to wait.

At this point, SCO's claims were sounding dubious at best, so they showed off two samples of alleged copied code at a reseller show later that month. However, the code in question was shown to be part of BSD, and previously released under the BSD license. In spite of this, SCO decided that to save face, they should waste everyone's time with continuing their warpath of litigation.

SCO v. Everyone

Since the suit against IBM was going so well, The SCO Group came up with the brilliant strategy of "sue all the things!" and proceeded to do just that. In lieu of having their own product that people actually liked and used, they figured they could just sue their way to profitability.

One of SCO's key claims was that they owned the copyrights to Unix, due to some purchases they'd made from Novell. Novell, however, didn't take this sitting down and respectfully disagreed. For butting in on SCO's new business model, Novell was served with a lawsuit in January of 2004. 2004 was the year that SCO decided to sue everyone they looked at. AutoZone, who had recently switched from using SCO OpenServer to Linux, got sued for doing so. DaimlerChrysler was just walking down the opposite side of the street and accidentally made eye contact with SCO, and they got sued as well.

While also suing everyone in sight, SCO also announced that they would not sue their own customers, so for the price of a SCO license, a company could exclude themselves from possible litigation. A few companies actually bought into the madness, but for the most part, the world collectively rolled its eyes at SCO, meaning that SCO would have to soldier on with their lawsuit-based business strategy, or face the wrath of their shareholders.

Novell Jams SCO's Gears

A few years went past while the SCO v. IBM case was still in the discovery phase, with SCO not wanting to reveal the code they were suing over, without seeing sources from IBM first, and IBM not wanting to give SCO any source without first being told what code was in question. This provided time for the Novell case to advance, albeit also slowly. By 2007, Novell was awarded several summary judgements, and several of SCO's claims were denied. By 2008, Novell had been awarded over $3 million as a result of the case. Just under half of that amount would be appealed by SCO, and temporarily reversed for a couple of more years. The main outcome here, however, was that Novell was ruled as the owner of the Unix copyrights.

The SCO legal juggernaut, however, would not, nay, could not be stopped. Despite not owning the Unix copyrights they contended they were the owners of "control rights" to derivatives of SYSV, and for the period during the appeals to SCO v. Novell, they were still able to claim potential ownership of the Unix copyrights in court as well. When they finally lost the appeals, they were forced to fall back to their claims of control rights, which is where they still stand today.

Being faced with having to pay out to Novell, SCO finally received its first nail in its coffin. Following the Novell ruling, SCO filed for Chapter 11 bankruptcy, and SCO v. IBM was stayed until SCO could emerge from Chapter 11 and continue the case. Shortly thereafter, SCO's stock price fell to under $0.50/share and they were de-listed from NASDAQ.

The End of SCO, but not of SCO v. IBM

So that's where we are today. Once the Chapter 7 filing is finalized by a judge, SCO will cease to be as a corporate entity, however they are proposing that SCO v. IBM be allowed to continue, not for sheer entertainment value, but rather so that they don't risk the wrath of their shareholders.

Nine years on, it's difficult to say who the real winners are. It's definitely not The SCO Group themselves, since they've gone under. It's also probably not SCO's lawyers, since their chances for being paid are greatly diminished since SCO's short-lived high times in 2003. IBM stands poised to win the case should it go forward, however their legal expenditures at this point are so large they could only be fielded by the likes of IBM. Novell, despite having already won, may not ever get paid all that it's owed. Linux users will most likely eventually emerge as not having to pay SCO a dime, which while is nice to have reaffirmed, is where they were back in 2003 to begin with. Another side effect of the courts rulings, was the reaffirmation of USL v. BSDi, which means that FreeBSD users are definitely safe from licensing fees and litigation.

While I've given an overview of the SCO-Linux litigations here, I've surely missed many of the bumps in the road. I only briefly touched on the PR war SCO fought against Groklaw, and many of the other insanities brought on by this case. With SCO v. IBM still possibly lunging ahead in a stupor, it may be too early to finally enjoy those aforementioned hard-earned beers, but it's still safe to chill them with the ice off SCO's corpse.

This past week, SCO filed for Chapter 7 bankruptcy, which finally begins the end of a long saga that started over nine years ago. While their anti-IBM litigation has risen from the grave and still shambles onward, the company itself is nearly put to rest after nine years of choosing the wrong legal battle to get into. Even if it may be too early to dance on SCO's grave, join me as I look back over the long and bumpy road to nowhere of The SCO Group.

The Beginning, or, We Sure Do Miss Ransom Love Around Here

Back in January of 2003, SCO announced that Unix SYSV code had been misappropriated into Linux. They didn't say much more than this, saying that they would only reveal the code in question to the court, and that it was a secret. Given the nature of Linux, this set off the BS-meters of nearly anyone with a clue, including the Linux kernel developers, not the least of which being Linus himself. In March of that year, SCO announced that they owned the copyrights to Unix, and that they were suing IBM for a billion dollars, for leaking SCO trade secrets into Linux. When people who had a clue thought about the case for more than a few minutes, they remembered back to the USL v. BSDi case that had been settled a decade prior, and figured SCO was full of it. Unfortunately, instead of SCO's announcement being taken as the ramblings of a crazy CEO desperate to increase the value of his flagging company, it went ahead. The worst part, is that at least for the short term, it worked. SCO's stock price shot from under $2/share to over $20/share in six months.

Around this time, a new champion would arise. A new website, Groklaw, run by paralegal Pamela Jones began blogging daily coverage of SCO v. IBM. While Groklaw was originally intended as a way for PJ to practice blogging, it soon grew into the front lines of the PR war against SCO, a war which they were losing badly.

This is where the case should have been thrown out, and everyone gone out for beers and had a good laugh, but that didn't happen. However, a new challenger would appear. In August of 2003, Red Hat sued SCO to try and put an end to this mess. While this was a valiant effort on Red Hat's part, ultimately a judge would stay the case pending the outcome of SCO v. IBM. Those hard-earned beers would have to wait.

At this point, SCO's claims were sounding dubious at best, so they showed off two samples of alleged copied code at a reseller show later that month. However, the code in question was shown to be part of BSD, and previously released under the BSD license. In spite of this, SCO decided that to save face, they should waste everyone's time with continuing their warpath of litigation.

SCO v. Everyone

Since the suit against IBM was going so well, The SCO Group came up with the brilliant strategy of "sue all the things!" and proceeded to do just that. In lieu of having their own product that people actually liked and used, they figured they could just sue their way to profitability.

One of SCO's key claims was that they owned the copyrights to Unix, due to some purchases they'd made from Novell. Novell, however, didn't take this sitting down and respectfully disagreed. For butting in on SCO's new business model, Novell was served with a lawsuit in January of 2004. 2004 was the year that SCO decided to sue everyone they looked at. AutoZone, who had recently switched from using SCO OpenServer to Linux, got sued for doing so. DaimlerChrysler was just walking down the opposite side of the street and accidentally made eye contact with SCO, and they got sued as well.

While also suing everyone in sight, SCO also announced that they would not sue their own customers, so for the price of a SCO license, a company could exclude themselves from possible litigation. A few companies actually bought into the madness, but for the most part, the world collectively rolled its eyes at SCO, meaning that SCO would have to soldier on with their lawsuit-based business strategy, or face the wrath of their shareholders.

Novell Jams SCO's Gears

A few years went past while the SCO v. IBM case was still in the discovery phase, with SCO not wanting to reveal the code they were suing over, without seeing sources from IBM first, and IBM not wanting to give SCO any source without first being told what code was in question. This provided time for the Novell case to advance, albeit also slowly. By 2007, Novell was awarded several summary judgements, and several of SCO's claims were denied. By 2008, Novell had been awarded over $3 million as a result of the case. Just under half of that amount would be appealed by SCO, and temporarily reversed for a couple of more years. The main outcome here, however, was that Novell was ruled as the owner of the Unix copyrights.

The SCO legal juggernaut, however, would not, nay, could not be stopped. Despite not owning the Unix copyrights they contended they were the owners of "control rights" to derivatives of SYSV, and for the period during the appeals to SCO v. Novell, they were still able to claim potential ownership of the Unix copyrights in court as well. When they finally lost the appeals, they were forced to fall back to their claims of control rights, which is where they still stand today.

Being faced with having to pay out to Novell, SCO finally received its first nail in its coffin. Following the Novell ruling, SCO filed for Chapter 11 bankruptcy, and SCO v. IBM was stayed until SCO could emerge from Chapter 11 and continue the case. Shortly thereafter, SCO's stock price fell to under $0.50/share and they were de-listed from NASDAQ.

The End of SCO, but not of SCO v. IBM

So that's where we are today. Once the Chapter 7 filing is finalized by a judge, SCO will cease to be as a corporate entity, however they are proposing that SCO v. IBM be allowed to continue, not for sheer entertainment value, but rather so that they don't risk the wrath of their shareholders.

Nine years on, it's difficult to say who the real winners are. It's definitely not The SCO Group themselves, since they've gone under. It's also probably not SCO's lawyers, since their chances for being paid are greatly diminished since SCO's short-lived high times in 2003. IBM stands poised to win the case should it go forward, however their legal expenditures at this point are so large they could only be fielded by the likes of IBM. Novell, despite having already won, may not ever get paid all that it's owed. Linux users will most likely eventually emerge as not having to pay SCO a dime, which while is nice to have reaffirmed, is where they were back in 2003 to begin with. Another side effect of the courts rulings, was the reaffirmation of USL v. BSDi, which means that FreeBSD users are definitely safe from licensing fees and litigation.

While I've given an overview of the SCO-Linux litigations here, I've surely missed many of the bumps in the road. I only briefly touched on the PR war SCO fought against Groklaw, and many of the other insanities brought on by this case. With SCO v. IBM still possibly lunging ahead in a stupor, it may be too early to finally enjoy those aforementioned hard-earned beers, but it's still safe to chill them with the ice off SCO's corpse.

This past week, SCO filed for Chapter 7 bankruptcy, which finally begins the end of a long saga that started over nine years ago. While their anti-IBM litigation has risen from the grave and still shambles onward, the company itself is nearly put to rest after nine years of choosing the wrong legal battle to get into. Even if it may be too early to dance on SCO's grave, join me as I look back over the long and bumpy road to nowhere of The SCO Group.

The Beginning, or, We Sure Do Miss Ransom Love Around Here

Back in January of 2003, SCO announced that Unix SYSV code had been misappropriated into Linux. They didn't say much more than this, saying that they would only reveal the code in question to the court, and that it was a secret. Given the nature of Linux, this set off the BS-meters of nearly anyone with a clue, including the Linux kernel developers, not the least of which being Linus himself. In March of that year, SCO announced that they owned the copyrights to Unix, and that they were suing IBM for a billion dollars, for leaking SCO trade secrets into Linux. When people who had a clue thought about the case for more than a few minutes, they remembered back to the USL v. BSDi case that had been settled a decade prior, and figured SCO was full of it. Unfortunately, instead of SCO's announcement being taken as the ramblings of a crazy CEO desperate to increase the value of his flagging company, it went ahead. The worst part, is that at least for the short term, it worked. SCO's stock price shot from under $2/share to over $20/share in six months.

Around this time, a new champion would arise. A new website, Groklaw, run by paralegal Pamela Jones began blogging daily coverage of SCO v. IBM. While Groklaw was originally intended as a way for PJ to practice blogging, it soon grew into the front lines of the PR war against SCO, a war which they were losing badly.

This is where the case should have been thrown out, and everyone gone out for beers and had a good laugh, but that didn't happen. However, a new challenger would appear. In August of 2003, Red Hat sued SCO to try and put an end to this mess. While this was a valiant effort on Red Hat's part, ultimately a judge would stay the case pending the outcome of SCO v. IBM. Those hard-earned beers would have to wait.

At this point, SCO's claims were sounding dubious at best, so they showed off two samples of alleged copied code at a reseller show later that month. However, the code in question was shown to be part of BSD, and previously released under the BSD license. In spite of this, SCO decided that to save face, they should waste everyone's time with continuing their warpath of litigation.

SCO v. Everyone

Since the suit against IBM was going so well, The SCO Group came up with the brilliant strategy of "sue all the things!" and proceeded to do just that. In lieu of having their own product that people actually liked and used, they figured they could just sue their way to profitability.

One of SCO's key claims was that they owned the copyrights to Unix, due to some purchases they'd made from Novell. Novell, however, didn't take this sitting down and respectfully disagreed. For butting in on SCO's new business model, Novell was served with a lawsuit in January of 2004. 2004 was the year that SCO decided to sue everyone they looked at. AutoZone, who had recently switched from using SCO OpenServer to Linux, got sued for doing so. DaimlerChrysler was just walking down the opposite side of the street and accidentally made eye contact with SCO, and they got sued as well.

While also suing everyone in sight, SCO also announced that they would not sue their own customers, so for the price of a SCO license, a company could exclude themselves from possible litigation. A few companies actually bought into the madness, but for the most part, the world collectively rolled its eyes at SCO, meaning that SCO would have to soldier on with their lawsuit-based business strategy, or face the wrath of their shareholders.

Novell Jams SCO's Gears

A few years went past while the SCO v. IBM case was still in the discovery phase, with SCO not wanting to reveal the code they were suing over, without seeing sources from IBM first, and IBM not wanting to give SCO any source without first being told what code was in question. This provided time for the Novell case to advance, albeit also slowly. By 2007, Novell was awarded several summary judgements, and several of SCO's claims were denied. By 2008, Novell had been awarded over $3 million as a result of the case. Just under half of that amount would be appealed by SCO, and temporarily reversed for a couple of more years. The main outcome here, however, was that Novell was ruled as the owner of the Unix copyrights.

The SCO legal juggernaut, however, would not, nay, could not be stopped. Despite not owning the Unix copyrights they contended they were the owners of "control rights" to derivatives of SYSV, and for the period during the appeals to SCO v. Novell, they were still able to claim potential ownership of the Unix copyrights in court as well. When they finally lost the appeals, they were forced to fall back to their claims of control rights, which is where they still stand today.

Being faced with having to pay out to Novell, SCO finally received its first nail in its coffin. Following the Novell ruling, SCO filed for Chapter 11 bankruptcy, and SCO v. IBM was stayed until SCO could emerge from Chapter 11 and continue the case. Shortly thereafter, SCO's stock price fell to under $0.50/share and they were de-listed from NASDAQ.

The End of SCO, but not of SCO v. IBM

So that's where we are today. Once the Chapter 7 filing is finalized by a judge, SCO will cease to be as a corporate entity, however they are proposing that SCO v. IBM be allowed to continue, not for sheer entertainment value, but rather so that they don't risk the wrath of their shareholders.

Nine years on, it's difficult to say who the real winners are. It's definitely not The SCO Group themselves, since they've gone under. It's also probably not SCO's lawyers, since their chances for being paid are greatly diminished since SCO's short-lived high times in 2003. IBM stands poised to win the case should it go forward, however their legal expenditures at this point are so large they could only be fielded by the likes of IBM. Novell, despite having already won, may not ever get paid all that it's owed. Linux users will most likely eventually emerge as not having to pay SCO a dime, which while is nice to have reaffirmed, is where they were back in 2003 to begin with. Another side effect of the courts rulings, was the reaffirmation of USL v. BSDi, which means that FreeBSD users are definitely safe from licensing fees and litigation.

While I've given an overview of the SCO-Linux litigations here, I've surely missed many of the bumps in the road. I only briefly touched on the PR war SCO fought against Groklaw, and many of the other insanities brought on by this case. With SCO v. IBM still possibly lunging ahead in a stupor, it may be too early to finally enjoy those aforementioned hard-earned beers, but it's still safe to chill them with the ice off SCO's corpse.

An anonymous reader writes "Microsoft founder Bill Gates has pledged to develop with Korea a revolutionary nuclear reactor that will leave far less radioactive waste than existing ones. Gates invested US$35 million in a nuclear-power venture company TerraPower in 2010. TerraPower is led by John Gilleland. It was formed from an effort initiated in 2007 by Nathan Myhrvold's company, Intellectual Ventures. The company includes expert staff and individual consultants who have worked for some of the most prestigious nuclear laboratories and engineering companies in the world." You may remember that Gates worked with China to build a reactor late last year.

Croakyvoice writes "Nintendo has today released the 3DS XL in the U.S. The console comes with features such as screens which are 90% bigger in size than the original 3DS, a much needed improvement in battery life and also the 3D effect on the console has noticeably improved. The 3DS XL is Nintendo's attempt at even moreso dominating the handheld console market over the PSVita, but also bringing back the gamers lost to the likes of Android and iOS devices. The other major 3DS news of the day is the release of New Super Mario Bros 2, a continuation of the DS game released in 2006. In Japan the game has sold over 800,000 copies since game launch and Nintendo will be hopeful to replicate that success in the U.S."

Croakyvoice writes "Nintendo has today released the 3DS XL in the U.S. The console comes with features such as screens which are 90% bigger in size than the original 3DS, a much needed improvement in battery life and also the 3D effect on the console has noticeably improved. The 3DS XL is Nintendo's attempt at even moreso dominating the handheld console market over the PSVita, but also bringing back the gamers lost to the likes of Android and iOS devices. The other major 3DS news of the day is the release of New Super Mario Bros 2, a continuation of the DS game released in 2006. In Japan the game has sold over 800,000 copies since game launch and Nintendo will be hopeful to replicate that success in the U.S."

hypnosec writes "Demonoid domain names that were put up for sale last week have been de-listed by Sedo because of 'legal issues'. Trouble for Demonoid started sometime during the last week of July when it was rendered inaccessible following DDoS attacks after which it started serving malware laden ads. About four days after these reports, Ukrainian authorities got the best of Demonoid and closed down the site entirely by raiding the hosting service provider of the site. Sedo has said that no third-party or law enforcement agency has ordered the de-listing of the domain names."

hypnosec writes "Demonoid domain names that were put up for sale last week have been de-listed by Sedo because of 'legal issues'. Trouble for Demonoid started sometime during the last week of July when it was rendered inaccessible following DDoS attacks after which it started serving malware laden ads. About four days after these reports, Ukrainian authorities got the best of Demonoid and closed down the site entirely by raiding the hosting service provider of the site. Sedo has said that no third-party or law enforcement agency has ordered the de-listing of the domain names."

hypnosec writes "Demonoid domain names that were put up for sale last week have been de-listed by Sedo because of 'legal issues'. Trouble for Demonoid started sometime during the last week of July when it was rendered inaccessible following DDoS attacks after which it started serving malware laden ads. About four days after these reports, Ukrainian authorities got the best of Demonoid and closed down the site entirely by raiding the hosting service provider of the site. Sedo has said that no third-party or law enforcement agency has ordered the de-listing of the domain names."

MojoKid writes "The venerable Lenovo ThinkPad, with its little red TrackPoint nub, has gone the way of the Ultrabook. If there's one small dig ThinkPads have taken with regularity over the years, it's that though there's a ton of quality and substance built into these machines, style was not a hallmark of the brand. The all new ThinkPad X1 Carbon could very well change the utilitarian stereotype of Lenovo's business-backed line-up, however. As the name suggests, the ThinkPad X1 Carbon is built from carbon fiber material throughout its chassis and internal rollcage. Its 14-inch display drives a native resolution of 1600x900, and its keyboard, arguably one of the nicest features of the ThinkPad line, is backlit and even more refined with contoured key caps. Battery life hits a max of about six hours on a full charge, and the machine weighs in at 3lbs and .31-inches at it thinnest dimension."

If you're sick of the term "cloud" to refer to pretty much anything on "the internet" and consider that phrase a symptom of useless MBA, PHB, PowerPoint talking points oozing where they don't belong, sorry — you'll probably have to endure it for a while yet. Nerval's Lobster writes that Gartner's 2012 Hype Cycle of Emerging Technologies says that "Cloud computing" (along with a few other terms, such as "Near Field Communication" and "media tablets") is not just alive but growing. "Gartner uses the report to monitor the rise, maturity and decline of certain terms and concepts, the better for corporate strategists and planners to predict how things will trend over the next few months or years. As part of the report, Gartner's analysts have built a Hype Cycle which positions technologies on a graph tracing their rise, overexposure, inevitable fall, and eventual rehabilitation as quiet, productive, well-integrated, thoroughly un-buzz-worthy technologies. Right now, Gartner views hybrid cloud computing, Big Data, crowdsourcing, and the 'Internet of Things' as on the rise, while private cloud computing, social analytics and the Bring Your Own Device (BYOD) phenomenon are coasting at the Peak of Inflated Expectations."

itwbennett writes "Earlier this month, the judge in the Oracle v. Google trial ordered the companies to disclose the names of bloggers and reporters who had taken payments from them. Not surprisingly, both companies have denied making direct payments to writers (with the exception of Florian Mueller of FOSSPatents, whose relationship to Oracle was disclosed in April). But Oracle has tattled on Google regarding some indirect connections. In particular, Oracle called out Ed Black for an article he wrote about the case for Forbes. And Jonathan Band, co-author of the book, 'Interfaces on Trial 2.0,' which Google cited in its April 3, 2012 copyright brief." Groklaw has an in-depth look at the filings. Oracle's fingerpointing is based in part on this BBC article and this piece at The Recorder, both of which they entered into evidence. Google's filing (PDF) affirmed that they have not paid media for articles or done any quid pro quo in exchange for coverage. However, they acknowledged that many people receive money from Google through other means (the company's philanthropy, ad business, etc.), and asked the judge if he wanted further details about those instances.

Microsoft has rolled out many new products and many revisions of old products over the past couple of decades. The releases haven't always gone well, as in the case of Windows Vista, but Redmond has managed to ride out the rough patches. However, Windows 8 is an even more dramatic revamp of one of Microsoft's top products than Vista was. At the same time, they're piling their tablet hopes onto Windows 8 as well. Does this make it Microsoft's riskiest bet ever? "Thus the problem facing Microsoft: How to convince Windows users to rush out and buy an upgrade of a perfectly good (and relatively new, at least by Windows standards) operating system? Compounding the issue is the new Windows 8 design, with a Start screen that discards the traditional desktop interface in favor of a bunch of colorful tiles linked to applications. That revamp is supposed to make Windows 8 more touch-screen friendly, and thus optimized for tablet use; but it could turn off consumers who don’t like change, not to mention businesses that shudder at the idea of retraining their workers in new ways of doing things. ... if Surface and the other Windows 8 tablets fail to make an impact on the market, then Microsoft will have lost a major chance at seizing the new paradigm, which is centered on mobility and the cloud. Meanwhile, that same paradigm shift is drifting the center of peoples’ computing lives from desktops and laptops to smartphones and tablets—which puts Windows’ traditional center of strength at long-term risk.

bbianca127 writes "Kentucky mandated that schools include tests that are based on national standards, and contracted test maker ACT to handle them. Legislators were then shocked that evolution was so prominently featured, even though evolution is well-supported and a central tenet of modern biology. One KY Senator said he wanted creationism taught alongside evolution, even though the Supreme Court has ruled that teaching creationism in science classes is a violation of the establishment clause. Representative Ben Wade stated that evolution is just a theory, and that Darwin made it all up. Legislators want ACT to make a Kentucky-specific ACT test, though the test makers say that would be prohibitively expensive. This is just the latest in a round of states' fight against evolution — Louisiana and Tennessee have recently passed laws directed against teaching evolution."

bbianca127 writes "Kentucky mandated that schools include tests that are based on national standards, and contracted test maker ACT to handle them. Legislators were then shocked that evolution was so prominently featured, even though evolution is well-supported and a central tenet of modern biology. One KY Senator said he wanted creationism taught alongside evolution, even though the Supreme Court has ruled that teaching creationism in science classes is a violation of the establishment clause. Representative Ben Wade stated that evolution is just a theory, and that Darwin made it all up. Legislators want ACT to make a Kentucky-specific ACT test, though the test makers say that would be prohibitively expensive. This is just the latest in a round of states' fight against evolution — Louisiana and Tennessee have recently passed laws directed against teaching evolution."

yourlord writes "Just under two years ago Musopen launched a Kickstarter campaign covered here on Slashdot. Today that project is complete with the release of a large amount of classical recordings into the public domain. This brings an extensive collection of high quality classical music into the public domain. The project music is hosted on the Musopen site, and on archive.org."

ananyo writes "Gene patents have been upheld in a landmark case over two genes associated with hereditary forms of breast and ovarian cancer. The lawsuit against Myriad Genetics, a diagnostic company based in Salt Lake City, Utah, that holds patents on the genes BRCA1 and BRCA2, has bounced from court to court since 2010. In a 2-1 decision today, a federal appeals court reaffirmed their latest decision that genes represent patent-eligible matter. As noted before on Slashdot, the case will have major implications for cancer researchers, patients and drug makers."

ananyo writes "Gene patents have been upheld in a landmark case over two genes associated with hereditary forms of breast and ovarian cancer. The lawsuit against Myriad Genetics, a diagnostic company based in Salt Lake City, Utah, that holds patents on the genes BRCA1 and BRCA2, has bounced from court to court since 2010. In a 2-1 decision today, a federal appeals court reaffirmed their latest decision that genes represent patent-eligible matter. As noted before on Slashdot, the case will have major implications for cancer researchers, patients and drug makers."

hypnosec writes "BitTorrent has backtracked on their stance that uTorrent ads cannot be 'turned off,' following a user revolt. They announced that users can opt-out of sponsored torrents if they don't wish to see them. Last weekend BitTorrent announced it would make uTorrent ad-enabled and that it would have a 'sponsored torrents' feature which couldn't be disabled. As one would have imagined, this didn't go over well with many users, and they let out their anger on the uTorrent forums. 'You seriously think that uTorrent is going to survive now? The Admin/Devs are seriously deluded. Pure greed has turned your once loved app into a bloated and buggy cash cow,' said one user."

wiredmikey writes "Saudi Aramco, Saudi Arabia's national oil company and the largest oil company in the world, confirmed that is has been hit by a cyber attack that resulted in malware infecting user workstations and forcing IT to kill the company's connection to the outside world. '..An official at Saudi Aramco confirmed that the company has isolated all its electronic systems from outside access as an early precautionary measure that was taken following a sudden disruption that affected some of the sectors of its electronic network,' the company wrote in a statement. This incident follows an attack on systems at the National Iranian Oil Company back in April, when a virus was detected inside the control systems of Kharg Island oil terminal, which also resulted in the company taking its systems offline. In response to continued cyber attacks against its networks and facilities, Iran earlier this month said it plans to move key ministries and state bodies off the public Internet to protect them from such attacks."

Nerval's Lobster writes "Tech writer and programmer Jeff Cogswell does a head-to-head comparison of Microsoft Azure and Amazon Web Services from a pure programming perspective, examining the respective sides' vendor lock-in and vendor-specific APIs (among other issues). 'If you're not using any vendor-specific APIs, then it's safe to say the experience you get on either Amazon or Microsoft will be roughly the same,' he writes. 'But that means you're also not developing an app that necessarily takes advantage of all possible cloud capabilities—not just add-ons, but scalability. Your app might need to expand and grow as your user base grows.' He suggests it's ultimately a tie between the two companies. 'From a strict programming perspective, both companies have their own RESTful API, and their own libraries for using the API.'" The problem with both of these services, though, that RMS could have told you about: "The moment you start using either, you're locked in for the most part."

Several readers have submitted news that as expected, Ecuador is formally accepting Julian Assange's request for political asylum. paulmac84 writes "The Guardian are live blogging the Ecuadorian Foreign Minister's announcement that Ecuador is to grant asylum to Julian Assange. In the announcement Minister Patino said, 'We can state that there is a risk that he will be persecuted politically... We trust the UK will offer the necessary guarantees so that both governments can act adequately and properly respect international rights and the right of asylum. We also trust the excellent relationship the two countries have will continue.' The Guardian also carries a translated copy of the letter the UK sent to Ecuador regarding the threat to 'storm' the Ecuadorian embassy." Also at Reuters.

hypnosec writes "Anonymous has claimed a new attack on Sony's PlayStation Network, and this time around it seems they have information from nearly 10 million user accounts. As a proof of the hack they dumped more than 3000 credentials online in the form of a pastebin post. The notorious hacktivist group is claiming that the entire set of hacked credentials contains over 10 million PSN accounts and that the file is of around 50GB." Update: 08/16 13:12 GMT by S : Sony has denied this claim.

An anonymous reader writes "The Royal Canadian mint has been pursuing the creation of mintchip, a digital currency for Canada, through a publicly held app contest. App development and consideration is now complete, and the public can now vote on which phone or desktop digital payment apps should be endorsed and publicized by the mint. There has been multiple arguments that the mintchip could easily have the same security, privacy, and traceability concerns as current digital payment, rather than actually introducing the benefits of cash."

jrepin writes "Awareness has been spreading among individuals, businesses and other organizations that DRM is a completely unnecessary restriction of freedom, and it drives people away. As that awareness spreads, going 'DRM-Free' becomes more and more valuable for patrons. To really build upon that image and to provide a resource for people to learn about why being DRM-Free matters, a logo was created for suppliers to proudly advertise that their files all come unencumbered by restrictive technologies. Some among early adopters are O'Reilly Media, ClearBits, Momentum Books, and ccMixter."

paulmac84 writes "According to the BBC, the UK have issued a threat to storm the Ecuadorian Embassy to arrest Julian Assange. Under the terms of the Diplomatic and Consular Premises Act 1987 the UK has the right to revoke the diplomatic immunity of any embassy on UK soil. Ecuador are due to announce their decision on Assange's asylum request on Thursday morning."

Windows 8 is drawing near, and with it comes tighter integration with Microsoft's cloud storage service SkyDrive. Because of its increased visibility, Microsoft is revamping SkyDrive to a more modern design, and is updating the SkyDrive apps for desktop PCs and Android devices. "SkyDrive’s revamped home page embraces the same tile-based design aesthetic as Microsoft’s other new and upcoming products, including Windows 8 and Windows Phone 8. Microsoft previously referred to that aesthetic as 'Metro,' but plans on giving it a new name at an unannounced future point. ... SkyDrive users can flick for a more detailed view of files, including dates modified, sharing status, and size. In terms of features, there’s the ability to search within SkyDrive for pretty much any term, including content within Word and other Office documents. Microsoft has also shifted common commands (creating and sharing folders, for example) to the toolbar that runs along the top of the SkyDrive interface.

Windows 8 is drawing near, and with it comes tighter integration with Microsoft's cloud storage service SkyDrive. Because of its increased visibility, Microsoft is revamping SkyDrive to a more modern design, and is updating the SkyDrive apps for desktop PCs and Android devices. "SkyDrive’s revamped home page embraces the same tile-based design aesthetic as Microsoft’s other new and upcoming products, including Windows 8 and Windows Phone 8. Microsoft previously referred to that aesthetic as 'Metro,' but plans on giving it a new name at an unannounced future point. ... SkyDrive users can flick for a more detailed view of files, including dates modified, sharing status, and size. In terms of features, there’s the ability to search within SkyDrive for pretty much any term, including content within Word and other Office documents. Microsoft has also shifted common commands (creating and sharing folders, for example) to the toolbar that runs along the top of the SkyDrive interface.

jfruh writes "Did you know that Craigslist founder Craig Newmark has a loyalty points account with the Starwood hotel chain? Did you know that both Tim Cook and Steve Ballmer have Dropbox accounts? All this information — and much more — can be found out because so many prominent executives use their corporate email address for their account logins, and most sites make it possible to see if an email address is associated with an account even if you don't have the account password. Just knowing that such an account exists can lead to technical and social engineering attempts to crack it, as happened in the case of Wired's Mat Honan."

According to a post on the GNU Compiler Collection list, GCC is now built as a C++ program by default. This is the fruition of much effort, and the goal now is to clean up the GCC internals that are reportedly pretty type-unsafe by rewriting them using C++ classes and templates.

jrepin writes "The Calligra team is proud and pleased to announce version 2.5 of Calligra, the KDE's office and creativity suite. Words, the word processor, has among other things improved support for editing of tables, tight run-around of text around images, manipulation of table borders, and dragging of text. Sheets, the spreadsheet application has a new stand-alone docker for the cell editor and a new cell tool window with cell formatting controls. Stage, the presentation program, has a number of usability improvements. Flow, the diagram application, has support for new stencils in odf custom shapes. Kexi, the database application, now offers a full screen mode. Krita, the painting application, has a new compositions docker, useful in movie storyboard generation. At the same time as the desktop version, the community also releases a QML based version for tablets and smartphone: Calligra Active." If there's one application here I'd like to see on a (pen) tablet, it's braindump.