A Look at the Kindle
The Kindle is underpowered, especially with larger books or when it's busy indexing or doing some other background task.
Next, the Kindle crashed a few times during my testing. Granted, I was running several apps that don't officially exist, but I don't feel I should have had to use the reset button as often as I did. Amazon still has some work to do there.
The Mobipocket format is another annoyance. It is an old binary format from the days when the Palm was known as the Pilot. It's not a very well documented format, and all of the tools for converting documents to it are proprietary and Windows-only.
The big question regarding the Kindle is whether it is actually worth $350. My thought is it is, if you read a lot.
And, I do. I carry around lots of books and printouts and miscellaneous scraps of paper—some for enjoyment and many for my job. I used to try reading things on my computer, but found my eyes quickly tired, so I switched to printing out longer articles and documentation I wanted to read. Apart from being environmentally wasteful, all that loose, printed material has to be organized or it grows into a big mess.
The Kindle has eliminated a lot of the mess. Now, when I head back to the server room, the only thing I need to carry is the Kindle—no stacks of notes and no reams of product documentation. It's all in the Kindle, along with a new novel to read while waiting for the server to finish its install. And, my desk is cleaner than any time in recent memory.
Is it worth $350? For me? Yes.
A Discussion of the .mobi File Format: www.mobileread.com/forums/showthread.php?t=16514
Hacking the Kindle, Parts 1–3: igorsk.blogspot.com/2007/12/hacking-kindle-part-1-getting-console.html, igorsk.blogspot.com/2007/12/hacking-kindle-part-2-bootloader-and.html and igorsk.blogspot.com/2007/12/hacking-kindle-part-3-root-shell-and.html
MobileRead—a Forum Devoted to eBooks: www.mobileread.com
Daniel Bartholomew lives with his wife and children in North Carolina. His normal on-line presence is at daniel-bartholomew.com, but he also can be found on Twitter as daniel_bart and on identi.ca (and Jaiku and Pownce) as bartholomew.
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!
- SUSE LLC's SUSE Manager
- My +1 Sword of Productivity
- Managing Linux Using Puppet
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Non-Linux FOSS: Caffeine!
- Doing for User Space What We Did for Kernel Space
- SuperTuxKart 0.9.2 Released
- Google's SwiftShader Released
- Parsing an RSS News Feed with a Bash Script
- SourceClear Open
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