Is This a Conspiracy?
Is This a Conspiracy?
Yeah, I'm sick of conspiracy theories too. But, this is starting to bother me.
I live in Seattle making me a neighbor of a large software marketing company in Redmond. I do my best to ignore that company and just get my real, Linux-based work done. But sometimes I think someone "out there" is going out of its way to make my job just a little harder.
I have DSL at home. While I went with a Linux-friendly ISP (oz.net), the connectivity is supplied by Qwest, a new name for U.S. West, one of the Bell ROCs. All has been well and very reliable. I have my Linux network hooked to a Cisco 675 router (which really is just a bridge for what I am doing). The ISP was very willing to talk ifconfig, route and all that other Linux stuff when I got up and running.
The problem, or maybe non-problem, started about two years into using this setup. I received a message that I should upgrade the OS in my Cisco router to Cisco Broadband Operating System (CBOS) version 2.4.3. I was pointed to a web site.
On the web site I find three options: PC, Mac and order a CD. Well, I have a PC--lots of them--but I find that PC means something running software from that Redmond marketing company. Ok, I admit it, I wasn't surprised. So, I opted for the CD putting in the comment field that I run Linux.
A few days later the CD arrives along with a page of instructions. They contain the surprising statement "Now, to protect your modem from the effects of [the Code Red] virus, we are enclosing a CD-ROM containing Cisco's 'long-term solution' software".
Ok, what gives? My understanding is that Code Red infects systems whose names start with MS, not Cisco. I can't believe that CBOS is an MS operating system--if for no other reason that it has run for over a year without needed a reboot.
Well, on to installation. Or, on to installation instructions for a "PC" or for a MAC. Yup, only a PC running a particular OS. Fortunately, there is a tech support phone number. I call it. I get a message telling me that this number doesn't work and I need to call another one. On the second one I am offered eight choices--none of them come close to installation support for non-"PC", non-Mac systems.
At this point I have invested enough time in what appears to be an unnecessary upgrade. Then I remember that those who picked Qwest for their ISP got railroaded into becoming an MSN user complete with a change in their e-mail address. When I called that first tech support phone number did the system sense that I had a Linux box on my DSL line and divert the call? Naw, couldn't be. After all, that would start to sound like a conspiracy.
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!
- Stunnel Security for Oracle
- SourceClear Open
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- SUSE LLC's SUSE Manager
- My +1 Sword of Productivity
- Managing Linux Using Puppet
- Google's SwiftShader Released
- Non-Linux FOSS: Caffeine!
- Parsing an RSS News Feed with a Bash Script
- Doing for User Space What We Did for Kernel Space
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