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.
|Dynamic DNS—an Object Lesson in Problem Solving||May 21, 2013|
|Using Salt Stack and Vagrant for Drupal Development||May 20, 2013|
|Making Linux and Android Get Along (It's Not as Hard as It Sounds)||May 16, 2013|
|Drupal Is a Framework: Why Everyone Needs to Understand This||May 15, 2013|
|Home, My Backup Data Center||May 13, 2013|
|Non-Linux FOSS: Seashore||May 10, 2013|
- Dynamic DNS—an Object Lesson in Problem Solving
- Making Linux and Android Get Along (It's Not as Hard as It Sounds)
- Using Salt Stack and Vagrant for Drupal Development
- New Products
- A Topic for Discussion - Open Source Feature-Richness?
- RSS Feeds
- Drupal Is a Framework: Why Everyone Needs to Understand This
- Validate an E-Mail Address with PHP, the Right Way
- Readers' Choice Awards
- The Secret Password Is...
- All the articles you talked
2 hours 15 min ago
- All the articles you talked
2 hours 18 min ago
- All the articles you talked
2 hours 20 min ago
6 hours 44 min ago
- Keeping track of IP address
8 hours 35 min ago
- Roll your own dynamic dns
13 hours 49 min ago
- Please correct the URL for Salt Stack's web site
17 hours 48 sec ago
- Android is Linux -- why no better inter-operation
19 hours 16 min ago
- Connecting Android device to desktop Linux via USB
19 hours 44 min ago
- Find new cell phone and tablet pc
20 hours 42 min ago
Enter to Win an Adafruit Pi Cobbler Breakout Kit for Raspberry Pi
It's Raspberry Pi month at Linux Journal. Each week in May, Adafruit will be giving away a Pi-related prize to a lucky, randomly drawn LJ reader. Winners will be announced weekly.
Fill out the fields below to enter to win this week's prize-- a Pi Cobbler Breakout Kit for Raspberry Pi.
Congratulations to our winners so far:
- 5-8-13, Pi Starter Pack: Jack Davis
- 5-15-13, Pi Model B 512MB RAM: Patrick Dunn
- 5-21-13, Prototyping Pi Plate Kit: Philip Kirby
- Next winner announced on 5-27-13!
Free Webinar: Hadoop
Some of key questions to be discussed are:
- What is the “typical” Hadoop cluster and what should be installed on the different machine types?
- Why should you consider the typical workload patterns when making your hardware decisions?
- Are all microservers created equal for Hadoop deployments?
- How do I plan for expansion if I require more compute, memory, storage or networking?