Removed a couple of "not yet updated" disclaimers.
New entry: "info error "dir: No such file or directory""
This commit is contained in:
parent
20fe2a85bc
commit
a15ada7034
@ -341,9 +341,6 @@ code for beta 16.
|
|||||||
|
|
||||||
@subsection What about DOS special filenames?
|
@subsection What about DOS special filenames?
|
||||||
|
|
||||||
@strong{(Please note: This section has not yet been updated for the latest
|
|
||||||
net release.)}
|
|
||||||
|
|
||||||
Files cannot be named com1, lpt1, or aux (to name a few); either as
|
Files cannot be named com1, lpt1, or aux (to name a few); either as
|
||||||
the root filename or as the extension part. If you do, you'll have
|
the root filename or as the extension part. If you do, you'll have
|
||||||
trouble. Unix programs don't avoid these names which can make things
|
trouble. Unix programs don't avoid these names which can make things
|
||||||
@ -354,9 +351,6 @@ letters 'aux' in it will hang.
|
|||||||
|
|
||||||
@subsection When it hangs, how do I get it back?
|
@subsection When it hangs, how do I get it back?
|
||||||
|
|
||||||
@strong{(Please note: This section has not yet been updated for the latest
|
|
||||||
net release.)}
|
|
||||||
|
|
||||||
If something goes wrong and the tools hang on you for some reason (easy
|
If something goes wrong and the tools hang on you for some reason (easy
|
||||||
to do if you try and read a file called aux.sh), first try hitting ^C to
|
to do if you try and read a file called aux.sh), first try hitting ^C to
|
||||||
return to bash or the cmd prompt.
|
return to bash or the cmd prompt.
|
||||||
@ -437,16 +431,24 @@ Place the following code in your startup file and try again:
|
|||||||
(original-comint-exec-1 name buffer command switches)))
|
(original-comint-exec-1 name buffer command switches)))
|
||||||
@end smallexample
|
@end smallexample
|
||||||
|
|
||||||
@subsection Where did the man/info pages go?
|
@subsection info error "dir: No such file or directory"
|
||||||
|
|
||||||
@strong{(Please note: This section has not yet been updated for the latest
|
Cygwin packages install their info documentation in the /usr/info
|
||||||
net release.)}
|
directory. But you need to create a @code{dir} file there before the
|
||||||
|
standalone info program (probably @code{/usr/bin/info}) can be used to
|
||||||
|
read those info files. This is how you do it:
|
||||||
|
@example
|
||||||
|
bash$ cd /usr/info
|
||||||
|
bash$ for f in *.info ; do install-info $f dir ; done
|
||||||
|
@end example
|
||||||
|
|
||||||
In order to save space and download times, we have stopped providing
|
This may generate warnings:
|
||||||
the man/info files for the tools with the binary install since we are
|
@example
|
||||||
not yet providing a man page or info reader. Both types of
|
install-info: warning: no info dir entry in `gzip.info'
|
||||||
documentation are available in a tar file available from the project ftp
|
install-info: warning: no info dir entry in `time.info'
|
||||||
site. Or consult the online documentation over the WWW.
|
@end example
|
||||||
|
The @code{install-info} command cannot parse these files, so you will
|
||||||
|
have to add their entries to @code{/usr/info/dir} by hand.
|
||||||
|
|
||||||
@subsection Why do I get a message saying Out of Queue slots?
|
@subsection Why do I get a message saying Out of Queue slots?
|
||||||
|
|
||||||
@ -500,9 +502,6 @@ them have been implemented in Cygwin yet.
|
|||||||
|
|
||||||
@subsection How does everything work?
|
@subsection How does everything work?
|
||||||
|
|
||||||
@strong{(Please note: This section has not yet been updated for the latest
|
|
||||||
net release.)}
|
|
||||||
|
|
||||||
There's a C library which provides a Unix-style API. The
|
There's a C library which provides a Unix-style API. The
|
||||||
applications are linked with it and voila - they run on Windows.
|
applications are linked with it and voila - they run on Windows.
|
||||||
|
|
||||||
@ -521,9 +520,6 @@ WWW site.
|
|||||||
|
|
||||||
@subsection Are development snapshots for the Cygwin library available?
|
@subsection Are development snapshots for the Cygwin library available?
|
||||||
|
|
||||||
@strong{(Please note: This section has not yet been updated for the latest
|
|
||||||
net release.)}
|
|
||||||
|
|
||||||
Yes. They're made whenever anything interesting happens inside the
|
Yes. They're made whenever anything interesting happens inside the
|
||||||
Cygwin library (usually roughly on a nightly basis, depending on how much
|
Cygwin library (usually roughly on a nightly basis, depending on how much
|
||||||
is going on). They are only intended for those people who wish to
|
is going on). They are only intended for those people who wish to
|
||||||
@ -623,9 +619,6 @@ should be fine.
|
|||||||
|
|
||||||
@subsection Why is some functionality only supported in Windows NT?
|
@subsection Why is some functionality only supported in Windows NT?
|
||||||
|
|
||||||
@strong{(Please note: This section has not yet been updated for the latest
|
|
||||||
net release.)}
|
|
||||||
|
|
||||||
Windows 9x: n.
|
Windows 9x: n.
|
||||||
32 bit extensions and a graphical shell for a 16 bit patch to an
|
32 bit extensions and a graphical shell for a 16 bit patch to an
|
||||||
8 bit operating system originally coded for a 4 bit microprocessor,
|
8 bit operating system originally coded for a 4 bit microprocessor,
|
||||||
@ -701,9 +694,6 @@ attribute.
|
|||||||
|
|
||||||
@subsection Why do some files, which are not executables have the 'x' type.
|
@subsection Why do some files, which are not executables have the 'x' type.
|
||||||
|
|
||||||
@strong{(Please note: This section has not yet been updated for the latest
|
|
||||||
net release.)}
|
|
||||||
|
|
||||||
When working out the unix-style attribute bits on a file, the library
|
When working out the unix-style attribute bits on a file, the library
|
||||||
has to fill out some information not provided by the WIN32 API.
|
has to fill out some information not provided by the WIN32 API.
|
||||||
|
|
||||||
@ -712,9 +702,6 @@ ones which have a "#!" as their first characters.
|
|||||||
|
|
||||||
@subsection How secure is Cygwin in a multi-user environment?
|
@subsection How secure is Cygwin in a multi-user environment?
|
||||||
|
|
||||||
@strong{(Please note: This section has not yet been updated for the latest
|
|
||||||
net release.)}
|
|
||||||
|
|
||||||
Cygwin is not secure in a multi-user environment. For
|
Cygwin is not secure in a multi-user environment. For
|
||||||
example if you have a long running daemon such as "inetd"
|
example if you have a long running daemon such as "inetd"
|
||||||
running as admin while ordinary users are logged in, or if
|
running as admin while ordinary users are logged in, or if
|
||||||
@ -1007,8 +994,8 @@ rewriting the runtime library in question from specs...
|
|||||||
|
|
||||||
@subsection How do I rebuild the tools on my NT box?
|
@subsection How do I rebuild the tools on my NT box?
|
||||||
|
|
||||||
@strong{(Please note: This section has not yet been updated for the latest
|
@strong{Note:} You must build in a directory @emph{outside} the source
|
||||||
net release.)}
|
tree.
|
||||||
|
|
||||||
Assuming that you have the src installed as /src, will build in
|
Assuming that you have the src installed as /src, will build in
|
||||||
the directory /obj, and want to install the tools in /install:
|
the directory /obj, and want to install the tools in /install:
|
||||||
|
Loading…
x
Reference in New Issue
Block a user