Migrating Customized Linux Installations to 2.6

An anonymous reader writes "This article provides an overview of the types of changes that you may need to make to a customized or specialized Linux installation in order to use it with the Linux 2.6 kernel, building upon the configuration file and administrative updates that were touched upon in the third article in this series. This article continues William von Hagen's popular series on using the new Linux 2.6 kernel, which places special emphasis on the primary issues in migrating existing drivers, applications, and embedded Linux deployments to a Linux distribution based on the 2.6 kernel."

Please note...

[advocate_one]

This article is aimed at embedded developers... and only briefly touches upon desktop systems.

Re:Please note...

[man1ed]

Correct, but a lot of the information is relevant to desktops as well. Probably not cross-compiling, though. ;-)

Ah, yes...

[Code Dark]

The problem with using an operating system whose kernel gets updated so very often is that to stay up-to-date you must update... sigh.

Updating

[Un0r1g1nal]

There are of course many benefits to actually updating, and unlike windows, once its updated you then dont usually need to get 6 or 7 patches to fix the subsequent release of 'fixes' that get released, until they accidentaly manage to release one that is stable enough for them to ignore the relatively small number of user complaints... But I don't want to start an anti MS thread here.

Anyway, benefits... Although it can take a little while to get used to the new kernal and to impliment the changes, and ei