Home ›

Google Becomes The Mobile Linux Champion

Nov 01, 2007  By Justin Ryan

With the recent announcement that Google will be entering the mobile-phone market with a Linux-based phone, speculation is beginning to surface on just what this might mean for Linux.

It takes deep pockets to break into a market like wireless phones, and a number of previous efforts haven't worked out as well as they could — look at the GreenPhone, which Trolltech recently decided to retire. However, with a deep-pocketed partner like Google, who knows where Mobile Linux could be headed.

Read more.

______________________

Justin Ryan is a Contributing Editor for Linux Journal.

Comments

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Greenphone was a success

lpotter's picture
Submitted by lpotter (not verified) on Sat, 11/03/2007 - 03:27.

Trolltech did not retire the Greenphone because it was a failure, they never intended to become a hardware company. The Greenphone never was going to be a consumer phone, but it was part of an SDK. Think of it as an inexpensive reference board. Trolltech's Greenphone initive was a success, it achieved what Trolltech set out to achieve with it - to build up a commnunity - both commercial and open source, and to get people interested in Qtopia.

Not a failure

Justin Ryan's picture
Submitted by Justin Ryan on Fri, 11/09/2007 - 00:15.

I didn't say it was a failure, I said it didn't work out as well as it could have. Hell, Linux Journal ran a cover story on hacking for the GreenPhone in last month's issue, only to have it go out of production before the next edition hit the newsstands.

I don't think it was a failure at all - quite frankly, if even one person was able to make use of it it's been pretty successful, because that's one less person locked down by the mobile giants - but it certainly could have been more successful.

Justin Ryan is a Contributing Editor for Linux Journal.

White Paper
More Resources
Fabric-Based Computing Enables Optimized Hyperscale Data Centers

Today’s modular x86 servers are compute-centric, designed as a least common denominator to support a wide range of IT workloads. Those generic, virtualized IT workloads have much different resource optimization requirements than hyperscale and cloud applications. They have resulted in a “one size fits all” enterprise IT architecture that is not optimized for a specific set of IT workloads, and especially not emerging hyperscale workloads, such as web applications, big data, and object storage. In this report, you will learn how shifting the focus from traditional compute-centric IT architectures to an innovative disaggregated fabric-based architecture can optimize and scale your data center.

Learn More

Sponsored by AMD

White Paper
More Resources
Red Hat White Paper: Using an Open Source Framework to Catch the Bad Guy

Built-in forensics, incident response, and security with Red Hat Enterprise Linux 6

Every security policy provides guidance and requirements for ensuring adequate protection of information and data, as well as high-level technical and administrative security requirements for a system in a given environment. Traditionally, providing security for a system focuses on the confidentiality of the information on it. However, protecting the data integrity and system and data availability is just as important. For example, when processing United States intelligence information, there are three attributes that require protection: confidentiality, integrity, and availability.

Learn more about catching the bad guy in this free white paper.

Learn More

Sponsored by DLT Solutions