07-03-2002
They arent compiled and interpreted the same way.
Also, NT based OSes (NT, 2000, XP) have some UNIX compatability/POSIX compliant guts in them, but are mostly based off of old VMS code that MS licenced from DEC. Thats where the stability and good handling of virtual memory comes from.
Didn't they get DOS from another DEC OS too? Hmmmm......
Side note, ever heard of Xenix? MS was in the UNIX OS game a long, long time ago, contrary to popular belief. I think IBM eventually snatched up Xenix from them though.
9 More Discussions You Might Find Interesting
1. Programming
I have a trouble: i cannot install and use freeBSD for some reasons(have no computer now, and comps on my work are Windowsed), but I need to compile some UNIX sources for freeBSD(this one: http://ppcpp.sf.net/). What can I do? Are there a compilers, that can run in Windows, but can compile binaries... (3 Replies)
Discussion started by: szzz
3 Replies
2. Solaris
Dear
I want to know how i can compare between two binaries by using check sum command. (2 Replies)
Discussion started by: abu_hassan
2 Replies
3. Solaris
I have the same two source files. They MUST be compiled with -g debugger option. The binaries are different. But in fact the binaries work the same. How to compare them to know the are compiled using the same source code. In Linux it is enough to: strip --strip-all <file> and diff shows no... (2 Replies)
Discussion started by: mblank
2 Replies
4. UNIX for Dummies Questions & Answers
Hello, I am the CEO of Grand Tech Corporation. We are launching Linux NT and forgive me, but I do not know how to strip binaries down in Mandriva Linux. Can someone tell me a way to?:b: (2 Replies)
Discussion started by: Linux NT
2 Replies
5. Linux
Hi ,
I am exploring the nmap utility for Linux.
I know that, nmap binaries are specific to the platforms e.g. nmap binaries will be diferent for Windows , AIX , Solaris and Linux platforms.
Can anyone tell me , will the nmap binaries be different for different flavours of Linux such as... (1 Reply)
Discussion started by: jatin56
1 Replies
6. UNIX for Dummies Questions & Answers
Why do shell builtins like echo and pwd have binaries in /bin? When I do which pwd, I get the one in /bin. that means that I am not using the builtin version? What determines which one gets used? Is the which command a definitive way to determine what is being run when I enter pwd? (16 Replies)
Discussion started by: glev2005
16 Replies
7. Red Hat
Is it possible to run binaries compiled for Intel platforms running on linux on a PPC system running on linux? I have a POWER4 IBM system and like to use it as a linux box with all desktop apps on it. (8 Replies)
Discussion started by: rein
8 Replies
8. Shell Programming and Scripting
Hi All,
I am very new to scripting and wanted to write a script for comparison of folder including binary files like ear's and jars. Following is the job for which I need it:
1. Compare two folders recursively
2. Compare the binaries like ear's but exclude files like MANIFEST files
3.... (1 Reply)
Discussion started by: maverick.topgun
1 Replies
9. Emergency UNIX and Linux Support
Hello All,
i have two 16 bit binaries that in two different variables, i want to perform a bitwise AND between the two and store the result in a different variable.
can anyone throw some light on doing this in a bourne shell...
eg var1= 1110101010101011
... (8 Replies)
Discussion started by: venu
8 Replies
LEARN ABOUT OSF1
mkmanifest
mkmanifest(1) General Commands Manual mkmanifest(1)
NAME
mkmanifest - mtools utility to create a shell script to restore UNIX file names from DOS
SYNOPSIS
mkmanifest [files]
OPTIONS
None
OPERANDS
A list of UNIX file names to be converted to DOS name format.
DESCRIPTION
The mkmanifest command creates a shell script that aids in the restore of UNIX file names that were overwritten by DOS file name restric-
tions. DOS file names are uppercase only, cannot exceed 8 character names, 3 character extensions and do not support device names or non-
alphanumeric characters.
Not all UNIX file names are supported in the DOS world. The mtools commands may have to change UNIX names to fit the DOS file name conven-
tions. Most commands provide the verbose option (-v), that displays new file names if they have been changed. The following table shows
some examples of file name conversions:
-----------------------------------------------
UNIX name DOS name Reason for the change
-----------------------------------------------
thisisatest THISISAT file name too long
file.stuff FILE.STU extension too long
prn.txt XRN.TXT PRN is a device name
.abc X.ABC null file name
hot+cold HOTXCOLD illegal character
-----------------------------------------------
EXIT STATUS
The following exit values are returned: Success. Failure.
EXAMPLES
Assume you have the following UNIX files that you want to copy to a DOS diskette using the mcopy command.
very_long_name 2.many.dots illegal: good.c prn.dev Capital
The mcopy command converts these file names to the following:
very_lon 2xmany.dot illegalx good.c xprn.dev capital
To restore the previous file names, use the mkmanifest command as follows: mkmanifest very_long_name 2.many.dots illegal:
good.c prn.dev Capital > manifest
The previous mkmanifest command line produces the following: mv very_lon very_long_name mv 2xmany.dot 2.many.dots mv illegalx illegal: mv
xprn.dev prn.dev mv capital Capital
The good.c file name did not require conversion, hence it was not included in the output.
If these files were copied from diskette to another UNIX system, and you wanted to restore the original names, retain a copy of the mani-
fest file (captured output) so that it can be used to convert the file names again.
FILES
Executable file
SEE ALSO
Commands: mcopy(1), mtools(1)
mkmanifest(1)