Tips for Testing the 2.5 Kernel
Okay, now that you actually have been convinced to try the 2.5 Linux kernel (see previous article), how can you test this kernel out. And, what should you do if you have any problems?
First off, before you configure the 2.5 kernel--say, while you are downloading it--go read Dave Jones's excellent "What to Expect from 2.5" document. In that document, pay specific attention to the sections covering the Input Layer, the Framebuffer layer and module information. These sections of the kernel configuration process are the most confusing for newcomers to the 2.5 series. If you don't pay attention, it is very easy to end up with a kernel that either displays nothing on the screen or doesn't accept any input from the keyboard.
After configuring the kernel with the specific hardware you have on your system, build the kernel, install it and reboot. Don't select all the drivers, here; a number of them do not compile because no one seems to have hardware for them anymore. If you've never done this build and install process before, I suggest you read the Linux Kernel HOWTO, which details all of the necessary steps involved. I also do not recommend that 2.5 be the first kernel you ever build on your own. Try the 2.4 kernel first to rule out any operator errors you might come across.
If you do have hardware for a driver that does not build, please report this. Most kernel developers do not have access to a wide range of hardware, so they are apprehensive about fixing drivers they cannot test. If you post your building problem to the linux-kernel or kernel-janitor's mailing list, and if you have the hardware for the driver and are willing to test patches, you should be able to find a willing developer to provide you with updated code.
Now that your 2.5 kernel is up and running, what should you do to test it? It's simple; do the normal tasks you always do on your 2.4 or 2.2 kernels: run X, browse the Web, read e-mail, play games, write documentation, write code and so forth. Every user stresses the operating system in different ways; therefore, there is no one, correct way to test.
If you think you've found a problem, first off, search the past week or so of the linux-kernel mailing list to see if others have had the same problem; a fix already may have been posted. If you do not see anything relevant, try searching the 2.5 kernel bug database for your specific issue. If you still cannot find anything relevant, please create a new bug in the database so the kernel developers can realize there is a problem. From there, the bug will be assigned to someone to look at, and more importantly, it can be found by others having the same problem in the future.
I hope this short mini-article helps people start testing out the 2.5 kernel. Without users testing, there is no way that the kernel can become stable enough for everyone to use in the future.
Greg Kroah-Hartman is currently the Linux USB and PCI Hot Plug kernel maintainer. He works for IBM, doing various Linux kernel-related things.
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)
- Non-Linux FOSS: Caffeine!
- Managing Linux Using Puppet
- Doing for User Space What We Did for Kernel Space
- SuperTuxKart 0.9.2 Released
- Parsing an RSS News Feed with a Bash Script
- Tech Tip: Really Simple HTTP Server with Python
- 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