03-15-2005
SCO UNIX to Linux migration
hi all
i m working in a company ...and i have to migrate a C application running on SCO-UNIX to Red hat linux.
can anybody tell me what is the difference between C commands and shell scripting on SCO-UNIX and LINUX.
best regards
harsh
10 More Discussions You Might Find Interesting
1. Filesystems, Disks and Memory
I think and believe that i could start both the two OS from HardDisk until i installed Turbo Linux after the SCO unix .
If I do anything ,Ican only start Turbo,but if i run "fdisk /mbr",the SCO unix can normally start,but the Turbo Linux could not start with unless you insert the bootdisket,which... (4 Replies)
Discussion started by: sensir163
4 Replies
2. Shell Programming and Scripting
Hi,
I have 2 Files - oraboot and orabackup, which are correct Files in Tru64 Environment and I am trying to check whether the Files are running properly in my current Linux 3.0. (basically trying to migrate them from Tru64 to Linux 3.0).
The files are neither Shell nor Perl, and just have the... (1 Reply)
Discussion started by: marconi
1 Replies
3. Linux
Hi,
I have 2 Files - oraboot and orabackup, which are correct Files in Tru64 Environment and I am trying to check whether the Files are running properly in my current Linux 3.0. (basically trying to migrate them from Tru64 to Linux 3.0).
The files are neither Shell nor Perl, and just have the... (2 Replies)
Discussion started by: marconi
2 Replies
4. Shell Programming and Scripting
Hi,
I have 2 Files - oraboot and orabackup, which are correct Files in Tru64 Environment and I am trying to check whether the Files are running properly in my current Linux 3.0. (basically trying to migrate them from Tru64 to Linux 3.0).
The files are neither Shell nor Perl, and just have the... (1 Reply)
Discussion started by: marconi
1 Replies
5. SuSE
Hi
i am new to Linux, i am trying to connect SCO Unix from SUSE LINUX Workstation but i am unable to define the terminal type.
i have also downloaded terminal softwares but function keys (f1, f2....) and some other keys are displaying code instead of working the correct function.
is there... (2 Replies)
Discussion started by: aafflatoon
2 Replies
6. Red Hat
Hi,
We are going to migrate our Dataware House system from HP Tru64 UNIX to Red Hat Linux 5.
There are more than 500 shell scripts which are written in ksh.
The schedule is very tight.
So, I want to learn whether there is a tool that can help us find the incompatible shell scripts in... (2 Replies)
Discussion started by: franksubramania
2 Replies
7. Shell Programming and Scripting
We are changing our OS from HP-Unix 11 to Linux Red Hat. We have few k- shell, c - shell and sql scripts which are currently running under HP-Unix 11. Will these scripts work on LINUX as it is? or we need to do any code changes?IS there anyone who have done this kind of migration before?Thanks for... (2 Replies)
Discussion started by: Phoenix2
2 Replies
8. Shell Programming and Scripting
Hi,
Could you please let me know what kind of changes/issues commonly occurs at Scripting /command level during AIX Unix (kshell) to Linux shell script migration. (24 Replies)
Discussion started by: Raghuraman.R
24 Replies
9. Shell Programming and Scripting
We have certain number of scripts that run on AIX server using ksh.
Now that we migrate these scripts to Linux servers.
We need to know what are the changes that we have to perform in script to make it compatible to run on Linux.
Say like in our Unix -AIX "print" command worked.
But that did... (6 Replies)
Discussion started by: SIva81
6 Replies
10. Shell Programming and Scripting
I am working on UNIX AIX to Linux migration.
Does anybody know the good site for doing this?
Thanks for contribution (4 Replies)
Discussion started by: digioleg54
4 Replies
LEARN ABOUT HPUX
standards
standards(5) File Formats Manual standards(5)
NAME
standards - UNIX standards behavior on HP-UX
DESCRIPTION
HP-UX conforms to various UNIX standards. In some cases, these standards conflict. This manpage describes the methods that programmers
and users must follow to have an application conform and execute according to a particular UNIX standard.
UNIX Standard Conformant Programmer Environment
The following table lists feature test macros and environment variables that must be defined while compiling an application. Both a fea-
ture test macro and an environment variable must be defined while compiling the application so that the application conforms and executes
according to a particular UNIX standard. Otherwise, the behavior is undefined.
Standard Feature Test Macros to be Environment variable
defined during compilation to be set
UNIX 95 _XOPEN_SOURCE_EXTENDED=1 UNIX95 or
UNIX_STD=95 or
UNIX_STD=1995
UNIX 2003 _XOPEN_SOURCE=600 UNIX_STD=2003
The compiler uses the feature test macros to obtain the appropriate namespace from the header files. The compiler uses the environment
variable to link in an appropriate object file to the executable. Using the environment variable customizes libc to match UNIX standards
for various functions.
If an application has already been compiled for default HP-UX behavior or for one particular standard, and needs to change to a particular
UNIX standard behavior, recompile the application as specified in the above table.
For an HP-UX command to conform to a particular UNIX standard behavior, the application has to set the corresponding environment variable
as specified in the above table before executing that command.
UNIX Standard Conformant User Environment
To enable a particular UNIX standard conformant user environment, set the corresponding environment variable as defined in the above table.
EXAMPLES
The following examples shows an application example. To have the system be conformant to UNIX2003 behavior, set the environment variable
to and define the feature test macro before compilation.
The following example changes the command to have UNIX95 behavior by setting one of the environment variables to or to before executing
that command. There are three ways of setting the environment variable for UNIX95:
or
or
SEE ALSO
cc(1), stdsyms(5).
standards(5)