“Computers are useless. They can only give you answers.”
“Kaa's Law: In any sufficiently large group of people most are idiots.”
“It doesn't matter who you are. Most of the smartest people work for somebody else.”
“Technology lies on the leading edge of life.”
“Teach a man to make fire, and he will be warm for a day. Set a man on fire, and he will be warm for the rest of his life.”
—John A. Hrastar
“Two rules to success in life: 1. Don't tell people everything you know.”
“We are perfecting markets. We are back in the bazaar.”
“Brazil is the country of the future and always will be.”
“Prediction is very hard...especially when it's about the future.”
According to the Internet Software Consortium (www.isc.org), 72.4 million domain names were taken by this past January. That was up 16.2 million over the prior six months. That comes out to about 88 thousand a day, 37 thousand an hour or a little over one every second.
And yet some domain names are still safe from adoption. We prove that every few months by offering another list of domain names that prove untakable. Last time, we suggested “coloncam”, ''celeprosy'' and “butthook”, among others, all of which are still yours for the low, low price of 70 bucks or less for two years.
If you're one of those types that like to run with the Joneses, you're probably looking for one of those “nt” names, like Scient, Lucent, Viant, Cerent and Teligent (see http://www.enormicom.com/ for the full list). But our crack research department (that sits right here in my chair) has uncovered at least ten “nt” variants that are still available. They include: Boviant, Annoyant, Terminant, Reodorant, Cementent and Inexperient. So there you go; register at will.
Now, here's this month's orphanage, filled with children that probably will remain safe from adoption. All are available in .com, .net, .org and every other form.
by Rob Flynn and Jeramey Crawford
Once upon a term'nal dreary, while I hack'ed, weak and weary,
Over many a quaint and curious volume of forgotten code--
While I nodded, nearly napping, suddenly there came a beeping,
As of someone gently feeping, feeping using damn talk mode.
"'Tis some hacker," I muttered, "beeping using damn talk mode--
Only this. I hate talk mode.
"Ah, distinctly I remember it was in the bleak semester,
And college life wrought its terror as the school year became a bore.
Eagerly I wished for privileges--higher access I sought to borrow
For my term'nal, unceasing sorrow--sorrow for a file called core--
For the rare and radiant files of .c the coders call the core--
Access Denied. Chown me more.
"Open Source," did all mutter, when, with very little flirt and flutter,
In there stepped a stately Penguin of the saintly days of yore.
Quite a bit obese was he; having eaten lots of fish had he,
But, by deign of Finnish programmer, he sat in the middle of my floor--
Looking upon my dusty term'nal in the middle of my floor--
Came, and sat, and nothing more.
Then the tubby bird beguiling my sad code into shining,
By the free and open decorum of the message that it bore,
"Though thy term'nal be dusty and slow," he said, "Linux be not craven!"
And thus I installed a new OS far from the proprietary shore--
The kernel code open but documentation lacking on this shore.
Quoth the Penguin, "pipe grep more!"
Much I marveled this rotund fowl to hear discourse so plainly,
Though its answer little meaning--little relevancy bore;
For we cannot help believing that no living human being
Ever yet was blessed with seeing bird in the middle of his floor--
Bird or beast sitting in the middle of his cluttered floor,
With such instructions as "pipe grep more."
But the Penguin, sitting lonely in that cluttered floor, spoke only
Those words, as if its soul in that instruction he did outpour.
Nothing more did he need utter; understood did I among that clutter--
Understood his command as I could scarcely do a few moments before--
I typed as furious as was willed me, understanding just a minute before.
Again the bird said "pipe grep more!"
"Amazing!" said I, "Penguin we will conquor the world if you will!
By the network that interconnects us--by that Finn we both adore--
We'll take this very world by storm!" For now grasped I what he'd meant,
The thing I do while searching /usr/doc/* for that wond'rous lore--
Those compendiums of plaintext documentation and descriptive lore.
Quoth the Penguin, "pipe grep more!"
And the Penguin, never waddling, still is sitting, still is sitting
In the middle of my room and still very cluttered floor;
And his eyes have all the seeming of the free beer I am drinking
And the term'nal-light o'er him glowing throws his shadows on the floor;
And this OS from out the shadows that is pow'ring my term'nal on the
Shall be dominating--"Pipe grep more!"
Practical Task Scheduling Deployment
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.View Now!
|The Firebird Project's Firebird Relational Database||Jul 29, 2016|
|Stunnel Security for Oracle||Jul 28, 2016|
|SUSE LLC's SUSE Manager||Jul 21, 2016|
|My +1 Sword of Productivity||Jul 20, 2016|
|Non-Linux FOSS: Caffeine!||Jul 19, 2016|
|Murat Yener and Onur Dundar's Expert Android Studio (Wrox)||Jul 18, 2016|
- The Firebird Project's Firebird Relational Database
- Stunnel Security for Oracle
- My +1 Sword of Productivity
- Non-Linux FOSS: Caffeine!
- Managing Linux Using Puppet
- SUSE LLC's SUSE Manager
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Doing for User Space What We Did for Kernel Space
- Google's SwiftShader Released
- SuperTuxKart 0.9.2 Released
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