are mostly closed source and so open source developers have to sometimes 

reverse engineer the device interfaces to achieve some level of functionality for 

native Linux device drivers.

Developments like this have even lead to ideas like the ndiswrapper project, 

which enables the loading of Windows ndis drivers in order to run network cards 

under Linux. Ndis is the Windows network driver API, and ndiswrapper allows 

use of this API as kernel modules in Linux. The URL of this project is:

http://ndiswrapper.sourceforge.net

Further great efforts in recent time were made in the kernel development by 

giving full support for all kinds of usb devices, Firewire and Bluetooth.

In conclusion of these facts, it is very important that the hardware types are 

determined during the planning stage of a client migration. Existing hardware 

that could need more effort to get it running than the current worth might have to 

be replaced with new pieces which are known to be compatible under Linux.

This rule applies especially for the selection of PC models. Almost every big PC 

vendor provides a model type that is suitable for Linux. IBM provides a Web site 

with information about supported models, which can be found on the following 

URL:

http://www.ibm.com/pc/support/site.wss/MIGR 48NT8D.html

Regarding desktop computers, it is quite easy to determine if Linux will run 

without problems; all the components, such as the graphics card, are known and 

can be checked for Linux support. Especially inboard components need special 

consideration because they likely cause problems; but even if this happens, it is 

possible to solve this by inserting a separate AGP card with a supported graphics 

chipset.

When considering notebook computers, such an exchange cannot be made, as 

the components cannot be removed from the mainboard. Thus it is necessary to 

check Linux support for Notebook models, and their features, before purchasing 

them.

Of special concern for mobile Linux based computers is support for power 

management functions. The support of the standards APM and ACPI in Linux is 

still not the answer to all questions. Since ACPI is supported since Kernel 2.6, 

many functions can be used; but as the implementation in the hardware 

components is varying, not all problems are solved. For using standby in a stable 

way, for example, APM can still be the better choice for notebooks.

In conclusion of these considerations, it becomes clear that you have to pay 

special attention to the hardware that will be in use after the migration. Especially 

 Chapter 4. Technical planning 

77