Linux comes from the Internet and thrives on the Internet. As the desktop Linux community struggles with proprietary formats and user lock-in, you might think those of us who are just doing network services have it easy. Wrong. Three key problems face Linux as an Internet platform today: security, proprietary software and the high cost of popularity. Naturally, Linux Journal will help you attack all three.
Networks need high-quality, secure software. Open-source licenses and development models are an important step toward that, but last year Linux Journal warned the shovelware mongers, I mean Linux distributions, that their default installs were loading users up with too many potentially exploitable services and that they should start locking things down by default. But did they listen? No. Now we have the “Red Hat Ramen Worm”, and proprietary software PR people blaming Linux for one distribution's irresponsible decision. From what I see, though, it could have been any of the distributions, so if you're not Red Hat don't think I'm not talking to you too.
Mick Bauer is writing about Bastille this month, and it certainly helps, but the very existence of a security package as an add-on is profoundly backward—like taking delivery of a car with no bumpers or seatbelts and having to get a local mechanic to install them. Exploits happen, but worm epidemics wouldn't be a public embarrassment for Linux if the distributions would just make a secure posture the default.
If you must run FTP (and most systems don't need to) please, please don't run some huge, deluxe, featureful FTP dæmon written back in ancient times, when there was no secure alternative to FTP for password-protected file transfers. Use a minimal “anonymous-only” dæmon such as oftpd (page 92) and be happy.
It might be hard for some of you to imagine the prospect of not having e-mail at work—but that's where Stew Benedict found himself. It's an old story for us but an inspiring one—set up a single, inexpensive Linux box to offer e-mail to lots of users. Internet e-mail dramatically changes work environments, as lots more people get information and help from the outside. Especially in bleak, brain-stifling places it changes the way people work for the better—and Stew did it on the smallest of budgets. Read how on page 100.
No networking issue would be complete without some discussion of the question “How can I get more performance out of my web site?” Ibrahim Haddad and Makan Pourzandi find an answer from the bottom up, using the classic “load balanced cluster” approach and the free Linux Virtual Server Project software [see page 84]. That's a workable solution for your business web site today—don't let yourself get bamboozled into proprietary load balancing or clustering.
When Richard Stallman wrote “Join us now and share the software, you'll be free, hackers, you'll be free,” he forgot “sane”. License managers, incompatible binary-only kernel modules and lack of tweakability are sending more than one webmaster over the edge. So get the free stuff and have time to make the site better, don't just work around some idiot marketing person's conception of how your site should work.
The Web is great, but the tragedy of popular independent web sites is that they start to require more bandwidth and server power than their creator can afford. At that point, the webmaster either “sells out” to a business that starts carrying ads, tracking users and doing other nasty stuff, or the site dies out. Naturally, the vendors of big bandwidth and big iron love this.
Freenet to the rescue. This much-hyped system really works—Peter Todd sent us his Freenet article over Freenet. Think of it as a distributed Berkeley DB, but one where you can get your data back from any Freenet “node”, not just the one where you stored it. It's a little more complicated than that, but honestly, not much.
Freenet's decentralized architecture was originally intended to keep the Man from suppressing underground newspapers and hash brownie recipes. But more importantly, it's becoming an architecture for sustaining web-like sites and Usenet-like groups while sharing the costs of servers and bandwidth among all the readers, not just slamming the creators. Get a DSL line, join Freenet (page 96), and soon your favorite sites won't have to make the decision of whether to shut down or sell out.
The fundamental advantage of packet-switched networks is that they disproportionately reward economically efficient and moral behavior. But like the HVAC system in Brazil, networks “don't fix themselves, sir.” Put some effort into security, free software and free peer-to-peer systems, and the network will pay you back many times over.
Peace and Linux.
—Don Marti, Technical Editor
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
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Managing Linux Using Puppet
- Non-Linux FOSS: Caffeine!
- Tech Tip: Really Simple HTTP Server with Python
- Doing for User Space What We Did for Kernel Space
- Parsing an RSS News Feed with a Bash Script
- Rogue Wave Software's Zend Server
- 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