On Net Neutrality
On Tuesday in Washington, DC, the U.S. Court of Appeals for the District of Columbia ruled that the FCC lacks authority to require broadband providers to give equal treatment to all Internet traffic flowing over their networks.
This begs two questions. First, if not the FCC, then who has that authority? The second, bigger question is what does this do for the issue of Net Neutrality in the United States?
The decision was a victory for cable provider Comcast who has been accused of traffic shaping on its network. Comcast argues, perhaps correctly, that since they built the network and since they manage the network, they are in the right when it comes to what traffic can and cannot cross their network.
On the other side are users and companies, like Google, that feel that the pipes, regardless of who owns them, should be open and available to whomever wants to use them.
And therein is the rub. Third party providers of services such as VoIP have long complained that Comcast has been throttling their packets, resulting in a lower quality of service, while Comcast gave a higher QoS its own packets. This is all well and good if you are trying to keep a competing product out (or so the mantra of capitalism would go) but it causes issues when you are communicating between systems, or, as Google has argued in the past, when the route from Point A to Point E goes across the network of Point C.
Once upon a time, the communications (read telephone) network in the United States was a utility monopoly, privately run by Ma Bell (AT&T). Many of the initial phone line connections were installed on the back of a tax paid for by those who already had phone lines installed (and that tax is still collected). In the late 1970s, the late Judge Greene oversaw the cases that lead to declaring AT&T an illegal monopoly and lead us down the rabbit hole to where we are now, thirty years later.
Today, the ISPs, primarily Verizon, AT&T, Comcast, Time-Warner Cable and a few others, own the pipes that are the US Internet, over which both domestic and international traffic travels at light speeds. These pipes are interconnected, interwoven and intermeshed in such a way that it is almost impossible to tell whose network traffic is passing over, through and around at any given point in time (as anyone who has tried to resolve a routing issue at that level can tell you). So the argument that it’s my network at that level is hard to swallow, at least intellectually.
This issue will of course be going to the Supreme Court. The Federal Government cannot let this go. Despite the ruling of the Appeals court, the FCC is responsible for a wide variety of communication issues, and many believe that the FCC does have the authority to regulate traffic on the Internet (at least domestically).
A bigger question though is this. What if the Supreme Court says that the FCC does not have this authority? What happens then? Will it come down to who can buy the largest number of votes on Capitol Hill? And what does that bode for the future of the Internet, and the services many of us have come to rely on?
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
- SuperTuxKart 0.9.2 Released
- Google's SwiftShader Released
- Parsing an RSS News Feed with a Bash Script
- 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