Red Hat Summit: Overview and Reflections
The keynote talks were all good, but the breakout sessions were much better. Most of them were practical talks on how to get more out Linux and related software. For instance, one session by Bret McMillan focused on how to use Red Hat Network (RHN) to keep servers up-to-date. There was another session on tracking server performance with RHN, given by Nick Hansen. One can use RHN to monitor system usage and to improve server performance, including not only hardware and network related services but also application performance--Apache, MySQL and so on. RHN also includes an interface for setting up regular expressions for log file monitoring. RHN either provides status information in a Web interface or sends an e-mail to the systems administrator for services that exceed certain levels set by the sysadmin. A session on the various features of the FireFox Web browser was given by Chris Aillon of Mozilla. This included not only giving us some tips on its use but also a discussion of the implementation of CSS3 Selectors; the latest version supports 85% of them. Another session was conducted by Dan Williams on getting cool stuff from OpenOffice.org and how to integrate it with other applications. For instance, with the beta 2.0 version of OpenOffice.org a document can interface with a MySQL database.
The sessions mentioned above were only a few from the Desktop track and the Application Development track. Five other tracks were on the schedule for the Summit: OS Technologies, Clustering & Virtualization, Systems Management, Business and Security & Identity Management. The OS Technologies sessions, such as the one given by Larry Woodman and Douglas Shakshober on "System Performance Tuning", along with some of the Security track sessions were packed and quite informative.
While attending Red Hat Summit as well as LinuxWorld Expo in Boston a few months ago and a couple of other open-source conferences this year, I couldn't help but notice how the face of Linux is changing. When I started with Linux over eight years ago, talks about Linux were given by guys who looked geeky, nerdy or whatever label you want to put on them. It seems that Linux has grown to become the concern of big corporations, and the keynote speakers aren't guys in need of a haircut and some time in the sun. Instead, the keynote speakers are top executives wearing expensive suits or business casual clothing, all speaking in a very professional manner. I don't know if this change is good or bad, but I'm wondering if Linux belongs to us any more.
It's wonderful that Linux is well received and has been growing in success. However, I'm see huge companies, such as IBM, Hewlett-Packard, Novell and others, trying to take control of Linux and open-source software for their benefit. Of course, whether that's actually possible if debatable. The community created Linux out of simple ideas and intellectual passion. The big software companies tried to ignore it for years until it could no longer be ignored. Now, they're trying to direct it. For instance, frustrated with the haphazard progress of the various GUI desktops, Red Hat scooped up some of the volunteer developers of the GNOME desktop and gave them full-time jobs developing GNOME based on the needs of Red Hat's target markets and on its schedule. Admittedly, this has produced some great results. However, one has to wonder how much the herding and corralling of open-source developers helps and hurts the future of open source. Red Hat seems to be second-guessing themselves on this strategy by setting up Fedora in the hopes that the enthusiasm from the community from years past will take hold again--to their benefit, of course.
When I sit through the keynote speeches at these conferences, it amazes me how these top executives can come up with the most bizarre looking graphs and charts to explain the open-source development trend thus far, thereby attempting to predict accurately where it's heading. These executives seem to be trying to take data they've accumulated on the open-source industry and squeeze it into traditional business models so they can explain it in ways they as business managers can understand. From that, they hope to be able to control or at least to predict future trends. Of course, they're forgetting that the trend didn't occur as the result of careful corporate planning. Instead, it happened over usenets and e-mails and from computer hackers diligently working each night after midnight, obsessed with squashing bugs or adding new features based on their perception of what's cool, not what's profitable.
Linux purists have long been aware of this developing pattern. They regularly guffaw at Red Hat, GNOME and other such commercializations of Linux and GNU software. They stick with Slackware for their Linux distribution, Enlightenment for window management and Emacs for text editing and even word processing. Maybe I'm a little slow, but I'm starting to see their point of view and the validity of it. If the big software companies are to take over the revolution--as implied in Szulik's keynote comments--what will be the results? Will they be what Linus Torvalds set out to achieve 14 years ago? We seem to be long past that point. More importantly, will the many thousands of volunteers that donated their time over the last decade or so have done so in the end to make big corporations richer? Also, if we concede to the overpowering marketing strategies and business savvy of the technology giants, what will become of us? Are we simply to become their employees? Are our opinions in the future to be written on cards to be dropped in company suggestion boxes and thereby ignored? Or, maybe we will merely grumble for a few decades until another Linus Torvalds comes forward and starts a new revolution? I don't know what the answers are, and I don't really know what should or can be done--or if anything needs to be done. I do think, however, that we need to pay attention to what's happening to our revolution, and these are the kinds of questions that should be discussed at a "summit" on Linux--and the answers shouldn't be told to us by corporate executives.
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