Drivers, patents and other threats, yawn.
Let's see how long have I used Linux as a desktop? Hmmm. Over 10 years? That's right. And the first issue I had at that time was finding an easy way to get to my ISP. The second issue at the time was the lack of a graphical web browser. Then Netscape produced an unsupported one that worked fine.
The video card issue came up with X. I had to find older cards to work with it. I found them and that was that.
I'm attempting to remember a time when something about Linux didn't draw criticism. I'm also attempting to remember a time when Windows didn't draw criticism. What about when my Mac crashed a dozen times a day?
I also recall how Darl McBride told the world he would beat us into flat Coca Cola cans or something like that. He had me shaking in my Dockers. I didn't own any Dockers at the time.
People forget that Linux grew out of community. A bunch of young kids in college produced it over the Internet communicating on usenet. That was around 1991. In 1994, Linux had 30,000 users. Most of the developers were kids.
Who really knows how many Linux users exist on the planet? At the same time, how many Windows users exist on the planet given the piracy in more countries than one can count?
I'm willing to admit Windows owns the PC business. I also recall that Microsoft gave Novell a free ride when it came to patent infringements. Let's consider that free ride for a moment or two while I yawn.
I seem to recall something about unfair trade practices. Can a monopoly favor one organization with the same product offering over another? Hmmm, I'm not a lawyer and I don't practice law. But, as a private citizen, I can recall some interesting legal battles here and there. Something about Linspire comes to mind. And something about announcements that stop people from buying products because of threatening announcements also comes to mind.
I don't know the outcome of these so called threats.
I do know I won't lose no sleep over that, cause I gotta plan - James Blunt.
Oh, the plan? Yawn.
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
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- My +1 Sword of Productivity
- Managing Linux Using Puppet
- Non-Linux FOSS: Caffeine!
- Doing for User Space What We Did for Kernel Space
- Google's SwiftShader Released
- SuperTuxKart 0.9.2 Released
- LiveCode Ltd.'s LiveCode
- 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