Speed achieved by the 350-node Cplant98 cluster running Linux at Sandia National Laboratory: 125.2GFLOPS
Where 125.2GFLOPS places the Sandia system in the current TOP 500 list of supercomputers: 53
Position of microsoft.com among the top sources of visitors to the new linux.com: 1
Number of microsoft.com visitors in the first two weeks of linux.com's operation: 15,000
Total age of Phat Linux's two founders: 30
Number of Net-connected computers whose spare CPU cycles are devoted to searching for extraterrestrial intelligence by SETI: 625,253
Total CPU time of all those computers: 99,799,890 hr 45 min 38.8 sec (11,392.68 years)
Number of “results” returned by all that terrestrial intelligence: 2,258,824
Percentage of those results produced by Linux platforms: 12
Position of Linux among all platforms in results performance: 2
Professional attendees at Linux Expo Paris 99: 5000
Number of exhibitors and vendors at Linux Expo Paris 99: 87
vi rocks. It also rules. So says Vassilii's Editors Sucks-Rules-O-Meter, which mines the verbs on Altavista and pronounces vi the winner over Emacs and all the other editors as a subject of those two superlatives. As of July 3, vi had a 350/10 rules/sucks ratio. And it looks like Linus isn't the only one out there who hates Emacs—a sentiment he shared with us on a recent panel that also featured Emacs creator Richard Stallman. Emacs' rules/sucks ratio is 22/59. This meter can be found at http://www.tarunz.org/~vassilii/srom/and is updated weekly. Thanks to Vassilii Khachaturov.
Want a new domain name? Good luck. We are at the bottom of the .com barrel, and the .net and .org barrels must be getting fairly low too. While the urban legend says every word in the dictionary has been sold for .com use, “misstep” is still there. So is “dodder”. A lot of two-word combos (such as hunkerdown) are gone as well, but a few (such as stupiddog) are still there. But your chances of getting the domain you want are being reduced every second by the sharks who buy domains from Network Solutions for $70 and then sell them for far higher prices (up to millions of US$) to the unfortunates who came too late to buy direct.
Thus, your only two strategic naming choices are anonymous or strange—or both. Why not create a front company with a camouflage name like “Symnetix.com”, while your actual business will be an enterprise NT replacement service called “Bizfloss.com”? If you do that, remember who your friends are when you file for that IPO (initial public offering).
To save you a bit of work, I went through the familiar whois routine to scope out the possibilities. They are mighty slim. Let's say you are in the bug zapper business and want “bzzt.com”. Well, Allan Henning of Stockton, California has already grabbed that one. How about dropping a z? Nope; “bzt.com” belongs to Hovinga Holding in the Netherlands. How about adding a z? Wrong again; “bzzzt.com” has gone to the Mikluhomaklai Sensation Corp. in Omsk, Siberia. Okay, how about one more z? Voilà! You can have it. Now prepare to spend the rest of your business life saying, “that's bzzzzt.com with four Z's.”
Doc Searls is Senior Editor of 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!
- SUSE LLC's SUSE Manager
- My +1 Sword of Productivity
- Managing Linux Using Puppet
- Tech Tip: Really Simple HTTP Server with Python
- Non-Linux FOSS: Caffeine!
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Rogue Wave Software's Zend Server
- Doing for User Space What We Did for Kernel Space
- 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