Make it happen, or bet on when it will
iTux: I envision a Linux-based iMac. Call it an iTux (too bad, the domain is already taken). Dress it up in those handsome penguin colors (or lack of them), rather than the iMac's silly “flavors”. Use nothing but end-of-life components with no fan and no floppy so it can be built dirt cheap. Boot from the CD-ROM drive. Solder everything to the boards including memory, with the possible exception of a communications slot. Now we're talking about a black & white box: simple and reliable as an old phone. Shoot for a $500+ price point, complete with all network connections, OS and software including management agents. Put the money in memory and display, which ought to be active matrix, if there's any way. Build two classes: corporate and home. Skew cute for the home version and add a slot for a Sony Playstation module. Message: for the price of a Playstation, get a computer too.
Internet Floppies, Any Size: FTP and e-mail killed the floppy. Now it is time to unburden those (social as well as technical) protocols. Let's create Internet floppies. Create easily understood ways to create, share and manage virtual Internet file servers of 10 to 100MB (or larger). This will eliminate the need for virtual private networks, e-mail attachments and complicated remote access routines. Any user should be able to sign up for one with his or her ISP, then decide who else can use it. Versions of this already exist at dedicated sites, such as NetFloppy, http://www.NetFloppy.com/. Why not at any site, any ISP, any business, using free and open software?
ISPs would get stickier sites and happier customers. Businesses would get turn-key field file-service solutions for maybe $2 per user, instead of the $50-75 it might cost from a file-service vendor. End users would get easy ways to pass files around and back up hunks of their local directories.
Alexa Internet is best known for three things:
A neat little browser accessory that reveals stats, domain ownership and other non-obvious information. Alexa gathered pages for 220 million unique URLs and found that only 6 percent of Web content has changed in the last three months.
Regularly backing up the entire contents of the Web. “Links in” are determined from their ongoing web crawls.
Selling to Amazon.com for something like $250 million.
The Alexa browser accessory does not yet work on Linux, but that didn't stop us from using it to tally up some comparative numbers for various Linux-related web sites. The results are below—we'll leave the interpretations up to you.
Notes: These numbers were collected on 5/13/99. “Links in” are from surveys of pages served across the entire Web. “Vists” are accumulated over the previous six months of activity by Alexa users, nearly all of which are on Windows clients. Some sites, such as Scripting.com and Slackware, contain high percentages of links and visits that are not Linux-related. One major site, Linux.com, went live from VA Linux Systems only in the last few days of the survey period. A follow-up survey on 6/1 showed a 24.6 percent increase in visits to that site.
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
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Managing Linux Using Puppet
- Non-Linux FOSS: Caffeine!
- SuperTuxKart 0.9.2 Released
- Doing for User Space What We Did for Kernel Space
- Parsing an RSS News Feed with a Bash Script
- Google's SwiftShader Released
- Rogue Wave Software's Zend Server
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