Will The G1 Continue To Get One?
One of the significant disadvantages of being an early adopter of any new technology is what comes after it, specifically, the improvements that every technology experiences over time. Such appears to be the case for those who rushed to pick up the G1 — the first Android phone on the market — as questions have begun to pop up over whether the device is in line to see its last update.
Like any device, the G1 has certain physical limitations — only so much stuff can fit in the case, and among the stuff being stuffed in is its memory. Apparently, according to one of Google's developers, not enough memory was stuffed when the stuffing was good, and now G1 owners may find themselves short on updates.
Posting via Twitter — the mass-communication tool of choice these days, it would seem — Google's Jean-Baptiste Queru announced on Friday that the G1 is running out of space. "As much as I'm hoping that it'll be possible to somehow continue updating the G1, I can't promise anything." Queru ought to know, considering that he's one of the guys working on it, and apparently the team knew going in that space would be shrinking. "We knew that internal flash space was going to be very tight on the G1 and we kept the system partition tight on purpose," he wrote later, in response to ideas from fellow Twitterites on how to proceed.
Google, for its part, apparently isn't commenting, but T-Mobile apparently was. A statement from the company reportedly proclaimed: "We plan to continue working with Google to introduce future software updates to the T-Mobile G1. Reports to the contrary are inaccurate." That raises the question — and users are most certainly already raising it — of whether the company is denying outright that a problem exists, if there is a solution in the works that nobody is willing to talk about, or if a bit of corporate doublespeak is underway. The suggestion has already been made that "future software updates" may refer to security and bugfix updates, but not feature upgrades.
Those interested in Queru's comments might wish to have a look through his Twitter stream, though his most recent tweet, as of this writing, suggests that he's said his piece. "At this point I can't comment any further on this issue, sorry."
Justin Ryan is News Editor for LinuxJournal.com.
Submit a tip: Email IRC
Justin Ryan is a Contributing Editor for Linux Journal.
Practical Task Scheduling Deployment
July 20, 2016 12:00 pm CDT
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.Register Now!
- Paranoid Penguin - Building a Secure Squid Web Proxy, Part IV
- SUSE LLC's SUSE Manager
- Google's SwiftShader Released
- Managing Linux Using Puppet
- My +1 Sword of Productivity
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Non-Linux FOSS: Caffeine!
- SourceClear Open
- SuperTuxKart 0.9.2 Released
- Parsing an RSS News Feed with a Bash Script
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide