This is the mail archive of the
cygwin@sourceware.cygnus.com
mailing list for the Cygwin project.
Re: How To find what is Implemented
- To: desh at orp dot pdc dot com
- Subject: Re: How To find what is Implemented
- From: Tage Westlund <tage dot westlund at stockholm dot mail dot telia dot com>
- Date: Fri, 10 Oct 1997 14:58:21 +0000
- CC: gnu-win32 at cygnus dot com
- Organization: G-LOGIKMETODER
- References: <199710090900.OAA29889@marina.orp.pdc.com>
- Reply-To: tage dot westlund at stockholm dot mail dot telia dot com
desh wrote:
> Is there a way or a document available to find out which all Unix > systems calls have been ported in b18. (and are working fine ).
To "desh"!
There are simple methods to find at least the majority of the binary
modules. Suppose you want to know if tar is implemented. Then
its name is tar.exe Remember also that often the original UNIX
command may have been altered (made better often). Then you
could seek for it with a "g" in front of the UNIX command name.
bash$ tar ( simply type tar and you get a few lines )
bash$ taxxx ( non existing )
BASH.EXE: tarxxx: command not found
bash$ tar --help > /some_temp_dir/temp1.txt
( you will have a rather complete list of options.
Those texts can give you a small manual )
Two directories where binary modules reside are:
.../gnuwin32/b18/H-i386-cygwin32/bin
.../gnuwin32/b18/H-i386-cygwin32/i386-cygwin32/bin
Using Win95 it is possible to search for tar.exe among all
files starting from a root, for instance C:\gnuwin\b18
Tage
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".