Language Selection

English French German Italian Portuguese Spanish

Add-on PS3 HDD will run Linux

Filed under
Gaming

Since E3, Sony Computer Entertainment president Ken Kutaragi has been calling the PlayStation 3 an "entertainment supercomputer" rather than a gaming console. Now, he's revealed a new plan to make sure that it's acknowledged as one.

In an interview with Impress PC Watch, Kutaragi disclosed that he plans to install the Linux operating system on the PS3's hard disc drive (HDD) so it will be recognized as a computer, rather than a mere console.

But while Linux would require a hard drive to run on, Kutaragi told Impress PC Watch, "We're not going to equip [the PS3 with] a HDD by default, because no matter how much [capacity] we put in it, it won't be enough." It was unclear whether he was referring to the previously known fact that the PS3 would not have an internal hard drive or whether he was indicating that the device would not come with the external 2.5-inch detachable HDD outlined in the specs revealed at E3.

If the latter is the case, then hard drives will be optional--and will cost extra. Kutaragi seemed to confirm this when he said, "There are still some issues if the machine doesn't come with an HDD." Further comments seemed to indicate that there will be more than one model of optional add-on PS3 HDDs available at launch. "We've added a 2.5-inch HDD bay so that users can equip HDDs, such as 80GB and 120GB, even though that's still not enough [capacity]." By contrast, the Xbox 360 will ship with a 20GB hard drive, standard. No other 360 HDD models have been announced, although Microsoft officials have indicated larger-capacity models could be produced if needed.

A complete translation of Kutaragi's interview with Impress PC Watch is below:

Impress PC Watch: The PlayStation 3 has some extremely high specifications, but it doesn't come with an HDD. Why?

Ken Kutaragi: We're not going to equip [the PS3 with] an HDD by default, because no matter how much [capacity] we put in it, it won't be enough. The next step is definitely network drives. With the Cell server, they can be accessed from anywhere, via network. Whether it's your own house [or] your friend's house, you can access the [network hard drive] anywhere. That's the kind of world we're imagining. But there are still some issues if the machine doesn't come with an HDD. So this time, we've added a 2.5-inch HDD bay so that users can equip HDDs, such as 80GB and 120GB, even though that's still not enough [capacity]. Although a network drive would allow for terabytes of storage, there's still the necessity to run an operating system offline. A hard drive for running an OS will be required for [the PS3] to be recognized as a computer.

IPCW: Do you mean to say that you'll run an OS on the PS3 to use it as a computer?

KK: I believe its wrong that, while we've been calling PlayStations "computers," Nintendo, which is in our same business, keeps telling the world their consoles are "toys." So even though we're making something that has the capability to be recognized as a supercomputer and requires paperwork when exporting or importing, the government sees it as a "toy." The PlayStation 2 has something as great as the Emotion Engine, and it can even run Linux, but it's still considered a gaming machine. I thought that the situation would become better since Microsoft appeared [in the gaming industry] from the IT field. But they won't say it either, since they want to protect their business. They see problems if the Xbox could run Windows, so they keep calling the Xbox a "game machine." It is really a pain in the neck. This time, we're positioning the PS3 as a "supercomputer." But people won't recognize it as a computer unless we call it a computer, so we're going to run an OS on it. In fact, the Cell can run multiple OSes. In order to run the OSes, we need an HDD. So in order to declare that the PS3 is a computer, I think we'll have [the PS3's HDD] preinstalled with Linux as a bonus.

IPCW: So Linux can be run on the Cell?

KK: Linux is legacy, but it will be a start. In the case of the Cell, operation systems are applications. The kernel will be running on the Cell, and multiple OSes will be running on top of that as applications. Of course, the PS3 can run Linux. If Linux can run, so can Lindows. Other PC Operating Systems can run too, such as Windows and Tiger (Max OS X 10.4), if the publishers want [them] to do so. Maybe a new OS might come out.

IPCW: Does that mean that we can expect applications that take advantage of the Cell, aside from games?

KK: As an example, HD video-editing software is basically the same as the nonlinear editing system used in broadcasting stations. What we're trying to do on the PS3 is that level of software. Nonlinear editing systems are incredible, but if it was done on the Cell, it would be even more incredible... The difference will be obvious. I think other PC applications, like photo-retouching software, will also be able to be done on the PS3. The user interface will also get interesting. In the case of the PC, users will have to wait for years between XP's UI to Longhorn's. But the PS3's UI will evolve much faster. For example, if we had an interface where we could control applications using gestures and words using the EyeToy, it would be like Minority Report. Of course, that kind of an evolution will also reflect on games. This will be the first form that [the Cell] will be spread. It can connect a keyboard, and it has all the necessary interfaces. It can run media, and it can run on a network. It's got such an all-around purpose, and it's open. It will become completely open if we equip it with Linux, and programmers will be able to do anything with it. It's the same thing with the graphics, since it's got the shaders.

GameSpot.

More in Tux Machines

Security Leftovers

  • Stop using SHA1 encryption: It’s now completely unsafe, Google proves
    Security researchers have achieved the first real-world collision attack against the SHA-1 hash function, producing two different PDF files with the same SHA-1 signature. This shows that the algorithm's use for security-sensitive functions should be discontinued as soon as possible. SHA-1 (Secure Hash Algorithm 1) dates back to 1995 and has been known to be vulnerable to theoretical attacks since 2005. The U.S. National Institute of Standards and Technology has banned the use of SHA-1 by U.S. federal agencies since 2010, and digital certificate authorities have not been allowed to issue SHA-1-signed certificates since Jan. 1, 2016, although some exemptions have been made. However, despite these efforts to phase out the use of SHA-1 in some areas, the algorithm is still fairly widely used to validate credit card transactions, electronic documents, email PGP/GPG signatures, open-source software repositories, backups and software updates.
  • on pgp
    First and foremost I have to pay respect to PGP, it was an important weapon in the first cryptowar. It has helped many whistleblowers and dissidents. It is software with quite interesting history, if all the cryptograms could tell... PGP is also deeply misunderstood, it is a highly successful political tool. It was essential in getting crypto out to the people. In my view PGP is not dead, it's just old and misunderstood and needs to be retired in honor. However the world has changed from the internet happy times of the '90s, from a passive adversary to many active ones - with cheap commercially available malware as turn-key-solutions, intrusive apps, malware, NSLs, gag orders, etc.
  • Cloudflare’s Cloudbleed is the worst privacy leak in recent Internet history
    Cloudflare revealed today that, for months, all of its protected websites were potentially leaking private information across the Internet. Specifically, Cloudflare’s reverse proxies were dumping uninitialized memory; that is to say, bleeding private data. The issue, termed Cloudbleed by some (but not its discoverer Tavis Ormandy of Google Project Zero), is the greatest privacy leak of 2017 and the year has just started. For months, since 2016-09-22 by their own admission, CloudFlare has been leaking private information through Cloudbleed. Basically, random data from random sites (again, it’s worth mentioning that every site that used CloudFlare in the last half year should be considered to having fallen victim to this) would be randomly distributed across the open Internet, and then indefinitely cached along the way.
  • Serious Cloudflare bug exposed a potpourri of secret customer data
    Cloudflare, a service that helps optimize the security and performance of more than 5.5 million websites, warned customers today that a recently fixed software bug exposed a range of sensitive information that could have included passwords and cookies and tokens used to authenticate users. A combination of factors made the bug particularly severe. First, the leakage may have been active since September 22, nearly five months before it was discovered, although the greatest period of impact was from February 13 and February 18. Second, some of the highly sensitive data that was leaked was cached by Google and other search engines. The result was that for the entire time the bug was active, hackers had the ability to access the data in real-time by making Web requests to affected websites and to access some of the leaked data later by crafting queries on search engines. "The bug was serious because the leaked memory could contain private information and because it had been cached by search engines," Cloudflare CTO John Graham-Cumming wrote in a blog post published Thursday. "We are disclosing this problem now as we are satisfied that search engine caches have now been cleared of sensitive information. We have also not discovered any evidence of malicious exploits of the bug or other reports of its existence."

Security Leftovers

  • Change all the passwords (again)
    Looks like it is time to change all the passwords again. There’s a tiny little flaw in a CDN used … everywhere, it seems.
  • Today's leading causes of DDoS attacks [Ed: The so-called 'Internet of things' (crappy devices with identical passwords) is a mess; programmers to blame, not Linux]
    Of the most recent mega 100Gbps attacks in the last quarter, most of them were directly attributed to the Mirai botnet. The Mirai botnet works by exploiting the weak security on many Internet of Things (IoT) devices. The program finds its victims by constantly scanning the internet for IoT devices, which use factory default or hard-coded usernames and passwords.
  • How to Set Up An SSL Certificate on Your Website [via "Steps To Secure Your Website With An SSL Certificate"]
  • SHA-1 is dead, long live SHA-1!
    Unless you’ve been living under a rock, you heard that some researchers managed to create a SHA-1 collision. The short story as to why this matters is the whole purpose of a hashing algorithm is to make it impossible to generate collisions on purpose. Unfortunately though impossible things are usually also impossible so in reality we just make sure it’s really really hard to generate a collision. Thanks to Moore’s Law, hard things don’t stay hard forever. This is why MD5 had to go live on a farm out in the country, and we’re not allowed to see it anymore … because it’s having too much fun. SHA-1 will get to join it soon.
  • SHA1 collision via ASCII art
    Happy SHA1 collision day everybody! If you extract the differences between the good.pdf and bad.pdf attached to the paper, you'll find it all comes down to a small ~128 byte chunk of random-looking binary data that varies between the files.
  • PayThink Knowledge is power in fighting new Android attack bot
    Android users and apps have become a major part of payments and financial services, carrying an increased risk for web crime. It is estimated that there are 107.7 million Android Smartphone users in the U.S. who have downloaded more than 65 million apps from the Google App Store, and each one of them represents a smorgasbord of opportunity for hackers to steal user credentials and other information.
  • Red Hat: 'use after free' vulnerability found in Linux kernel's DCCP protocol IPV6 implementation
    Red Hat Product Security has published details of an "important" security vulnerability in the Linux kernel. The IPv6 implementation of the DCCP protocol means that it is possible for a local, unprivileged user to alter kernel memory and escalate their privileges. Known as the "use-after-free" flaw, CVE-2017-6074 affects a number of Red Hat products including Red Hat Enterprise Linux 6, Red Hat Enterprise Linux 7 and Red Hat Openshift Online v2. Mitigating factors include the requirement for a potential attacker to have access to a local account on a machine, and for IPV6 to be enabled, but it is still something that will be of concern to Linux users. Describing the vulnerability, Red Hat says: "This flaw allows an attacker with an account on the local system to potentially elevate privileges. This class of flaw is commonly referred to as UAF (Use After Free.) Flaws of this nature are generally exploited by exercising a code path that accesses memory via a pointer that no longer references an in use allocation due to an earlier free() operation. In this specific issue, the flaw exists in the DCCP networking code and can be reached by a malicious actor with sufficient access to initiate a DCCP network connection on any local interface. Successful exploitation may result in crashing of the host kernel, potential execution of code in the context of the host kernel or other escalation of privilege by modifying kernel memory structures."

Android Leftovers

today's howtos