Port enterprise applications from UNIX to Linux

Port enterprise applications from UNIX to Linux-general Linux technology-Linux programming and kernel information. The following is a detailed description. At present, most enterprise-level software on UNIX is designed to meet the business needs of large companies. Therefore, it must support new technologies and adapt to the rapidly growing market trend, such as the extensive use of powerful and flexible Linux operating systems. Because most of the software is large, multi-threaded, and multi-process, porting it to Linux is a challenge. Through this article, you can obtain the list and suggestions you get when porting an enterprise-level software to Linux.
One Actual Situation of current business IT behavior is that many organizations are transferring IT to Linux because IT has the flexibility and stability as a system platform. Another reality is that it is too costly to discard existing enterprise-level software. These two situations often occur at the same time, but the key is to solve them.

Porting enterprise-level software to Linux may face many interesting challenges. Every step must be careful-from making design choices, to obtaining available build systems, to finally obtaining code for specific systems to be executed on Linux.

This article is based on my experience in running C applications in RHEL and SLES releases (running C applications on Intel and IBM eServer zSeries architectures), but it applies to other releases as well. I will discuss some plans for running your application on Linux and the technical issues to consider, including the following:

Obtain available build systems.
Determine a feasible operating environment.
Minimize the effort invested in building products on a variety of architectures (Linux needs the support of those architectures ).
Determine changes to a specific architecture, such as mutex locking ).
Use the new compiler to maintain a detailed general code base for as many architectures as possible ).
Determine the IPC Mechanism.
Select a proper thread model.
Change the installation and packaging methods according to specific Linux guidelines.
Determine the signal options.
Select a parser tool, such as lex/yacc.
Make regionalization choices.
Obtain available build systems
A product that supports multiple platforms usually requires the specific operating system of the product to be run. This general code is usually stored in the independent code components of the source directory structure.

For example, the Code planning specific to the operating system may be similar to this:

Src/operating_system_specific_code_component/aix (for AIX ).
Src/operating_system_specific_code_component/solaris (for Solaris ).
Src/operating_system_specific_code_component/UNIX (for other types of Unix ).

The operating system-specific code planning is displayed in a more graphical view.

Figure 1. Code Organization Planning



(400) {this. resized = true; this. width = 400; this. alt = 'click here to open new window';} "onmouseover =" if (this. resized) this. style. cursor = 'hand'; "onclick =" window. open ('HTTP: // www.unix-cd.com/unixcd12/eWebEditor/UploadFile/20051216101527868.gif'); ">

Obtain the Linux build system
First, you should create a directory for the code specific to Linux and place the files from a specific platform. After you introduce a new directory for Linux, the plan may look like this:

Src/operating_system_specific_code_component/linux (for Linux)

Then we will get a new code plan similar to the following.