The Wonderful World of Linux 2.2
Perhaps the most surprising and cutting-edge addition to the Linux kernel for inclusion in version 2.2 is what is called the “frame-buffer console” driver (or fbcon, for short).
Previously, the Linux kernel (for Intel-based machines) understood and manipulated the video devices only in text mode. Graphical support was to be provided by two other systems: svgalib for console-based graphics and a specialized X server for window-based graphics. This kludgey system often required configuration information to be repeated, and each system supported only a limited slice of the myriad of video devices in common use.
Since this addition is rather new, it remains to be seen whether it will truly replace the previous long-standing duality. Unfortunately, it will be nearly a year after Linux 2.2 ships before this new system is robust enough to support the cards and technologies we already take for granted as working. My personal opinion is that this is the right idea, but I will hold judgment until I see exactly how far Linus and the developers decide to take this feature.
It is also possible to remove support for “virtual” terminals as provided by the kernel. This allows very memory-conscious people to save just a tad more.
Although unimaginable to the desktop user, Linux can now work even better on systems that do not actually include any sort of video device. In addition to being able to log in over serial or networked lines, as Linux 2.0 and previous Linux versions allowed, it is now possible to redirect all the kernel messages (usually sent to the console directly before any hardware was initialized) to a serial device.
Linux 2.2 supports a large array of solutions for amateur radio operators, including a large number of enhancements from Linux 2.0. Unfortunately, this is not my forte—I've never even seen a Linux-based amateur radio station.
I don't have much experience here; I've been using the same network cards in all my machines for several years. However, it is not hard to see that the number of Ethernet and ISDN devices supported in Linux 2.2 has risen sharply. I have been told that newer solutions such as cable modems are also supported.
On the low end, not much has changed. PPP, SLIP, CSLIP and PLIP are all still available for use. I guess some things don't need much improvement. Each of those drivers has been updated in one way or another.
My only gripe in this regard is the continued non-support of so-called Winmodems. Not that I blame Linux for their absence (making modems that are 80% software is a dumb idea anyway), but the idealist in me hopes that one day these pesky devils will be supported like their more usable cousins.
On the protocol front, a lot has happened that I simply don't understand completely. The next-generation Internet protocol, IPv6, has made an appearance. SPX, an alternate version of IPX, is new as well. DDP, the protocol of choice for AppleTalk networking has also been added. Just as you would come to expect by now, the existing protocols have been improved. I only wish I had the need to use some of this stuff.
The list keeps going, however. Linux 2.2 will have an excellent new networking core, new tunneling code, a new firewalling and routing system called “ipchains”, support for limiting bandwidth consumption and a ton more.
File- and printer-sharing protocols have also been markedly improved and enhanced. SMB, the protocol for accessing MS Windows-based shared file systems, has been improved with bug fixes and the like. If you are a fan of NetWare, you'll be happy to know that Linux 2.2 supports a large number of improvements in this area, including access to two different kinds of NCP long file names. Trusty NFS has also been improved, both at the server level and the client level. Finally, those guys over at Carnegie Mellon University have been hard at work developing the new distributed network file system, Coda. This file system supports a large number of highly requested features, including disconnected operations for laptops, an advanced cache system and security improvements.
There's quite a lot that honestly doesn't fit into any of the categories above.
For one, the old system of loading “in and out” drivers (called modules) has been replaced with a system that doesn't require a separate daemon and allows for a smaller memory footprint. This is the kmod system which replaces the kerneld system. I have to say I think this is a good thing.
Also, the old method of access to file systems has been replaced by the “dcache” system, which may be the fastest virtual file system for any OS currently on the market. It makes you proud to support Linux.
Joseph Pranevich can be reached via e-mail at knight@baltimore.wwaves.com.
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Sponsored by AMD
Built-in forensics, incident response, and security with Red Hat Enterprise Linux 6
Every security policy provides guidance and requirements for ensuring adequate protection of information and data, as well as high-level technical and administrative security requirements for a system in a given environment. Traditionally, providing security for a system focuses on the confidentiality of the information on it. However, protecting the data integrity and system and data availability is just as important. For example, when processing United States intelligence information, there are three attributes that require protection: confidentiality, integrity, and availability.
Learn more about catching the bad guy in this free white paper.
Sponsored by DLT Solutions
| Designing Electronics with Linux | May 22, 2013 |
| 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 |
- Designing Electronics with Linux
- Making Linux and Android Get Along (It's Not as Hard as It Sounds)
- Dynamic DNS—an Object Lesson in Problem Solving
- Using Salt Stack and Vagrant for Drupal Development
- New Products
- Validate an E-Mail Address with PHP, the Right Way
- Build a Skype Server for Your Home Phone System
- Why Python?
- A Topic for Discussion - Open Source Feature-Richness?
- Tech Tip: Really Simple HTTP Server with Python
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
How to Build an Optimal Hadoop Cluster to Store and Maintain Unlimited Amounts of Data Using Microservers
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
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?




3 hours 11 min ago
3 hours 19 min ago
5 hours 34 min ago
8 hours 4 min ago
18 hours 6 min ago
22 hours 33 min ago
1 day 2 hours ago
1 day 2 hours ago
1 day 5 hours ago
1 day 5 hours ago