Porting Enterprise Apps from UNIX to Linux
By Martyn Honeyford2005-04-17
There's a Port in Every Storm
|
|
In this article I have touched upon various stages of porting, including design choices for various OS-specific areas, creating a suitable directory structure, creating a build system, making the code changes, and testing. I've highlighted those areas where effort needs to be concentrated, areas such as signaling, shared memory, mutexes and condition variables, threading, and architecture-specific changes. This article is based on real experience gained while porting a large multi-threaded application onto a Linux 2.6-based system, so I hope this checklist can be helpful in saving you time and effort.
The details will change with each port, but the principles I've outlined (combined with the material in the referenced below) will allow you to go through the process more easily.
Tutorial Pages:
» A Practical Checklist, Tips, and Insight Drawn from Experience
» Get the Build System Working
» Decide on a Viable Operating Environment
» Architecture-Specific Changes
» Choose an IPC Mechanism
» Select the Threading Model
» File System, Usage Parameters, Stacks
» Memory Maps and Using Shared Memory Segments
» Signaling
» Configure Kernel Karameters
» Parser Tools like lex/yacc
» Globalization Issues
» Security Concerns
» Locating Installed Packages and Variable Data
» Testing
» There's a Port in Every Storm
» Resources
First published by IBM DeveloperWorks
|
| Related Tutorials: » How to Install PHP 5 on Linux » How to Install Apache 2 on Linux » How to Install MySQL 5.0 on Linux » SMB Caching » Mound --Bind » Tar Wild Card Interpretation |