Apple-2gs-SW/gno
1
0
Fork 0
mirror of https://github.com/GnoConsortium/gno.git synced 2025-01-21 12:29:42 +00:00
Code Issues Projects Releases Wiki Activity

- changed all occurances of "Orca" to "ORCA", as is the correct name

Browse Source
This commit is contained in:
gdr-ftp 1998-01-25 18:03:45 +00:00
parent 8ac226b323
commit 2159dfd5c6
6 changed files with 18 additions and 18 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
usr.man/man2/chmod.2
View File

@ -119,7 +119,7 @@ by protecting set-user-id (set-group-id) files
from remaining set-user-id (set-group-id) if they are modified,
at the expense of a degree of compatibility.
.SH COMPATIBILITY
The Orca/C implementation of
The ORCA/C implementation of
.BR chmod
interprets
.IR mode

8
usr.man/man2/execve.2
View File

@ -2,7 +2,7 @@
.\" release for Gno v2.0.3 by Devin Reade. As of GNO v2.0.6 it is now
.\" part of libc.
.\"
.\" $Id: execve.2,v 1.1 1997/02/27 07:32:12 gdr Exp $
.\" $Id: execve.2,v 1.2 1998/01/25 18:03:27 gdr-ftp Exp $
.\"
.TH EXECVE 2 "19 January 1997" GNO "System Calls"
.SH NAME
@ -170,16 +170,16 @@ in the parent after child has had a chance to
however this is normally a race condition and the result is therefore
indeterminant.
.LP
Programs compiled with Orca/C v1.3 (and earlier) ignore any stack space
Programs compiled with ORCA/C v1.3 (and earlier) ignore any stack space
allocated by the GS/OS Loader (which
.BR _execve
calls. Stack space in Orca/C programs is determined by code in the
calls. Stack space in ORCA/C programs is determined by code in the
.BR "*.root"
object file, and can be set with the
.BR "#pragma stacksize"
directive. Read the chapter on GNO Compliance in the
.I "GNO Kernel Reference Manual"
for more information on this topic. Orca/C v2.0 and later versions use
for more information on this topic. ORCA/C v2.0 and later versions use
the system-provided stack space.
.SH SEE ALSO
.BR exit (2),

10
usr.man/man2/fork.2
View File

@ -1,7 +1,7 @@
.\"
.\" Devin Reade, 1997
.\"
.\" $Id: fork.2,v 1.1 1997/02/27 07:32:12 gdr Exp $
.\" $Id: fork.2,v 1.2 1998/01/25 18:03:31 gdr-ftp Exp $
.\"
.\" .TH FORK2 2 GNO "System Calls" "16 December 1996"
.TH FORK 2 GNO "16 January 1997" "System Calls"
@ -136,10 +136,10 @@ the child process does not or cannot
it should call
.BR _exit (3).
.LP
Orca/C's stack checking and stack repair code should be turned off
ORCA/C's stack checking and stack repair code should be turned off
when compiling routines containing these functions. See
.BR occ (1)
or the Orca/C Reference Manual for details.
or the ORCA/C Reference Manual for details.
.LP
Because the
.BR fork
@ -149,7 +149,7 @@ tool set), the child function
must restore the data bank register if it is going to access global
variables. See the description of the
.BR databank
pragma in the Orca/C Reference Manual for details.
pragma in the ORCA/C Reference Manual for details.
.LP
While
.BR Splat!
@ -212,4 +212,4 @@ first appeared in 3.0BSD.
the
.IR "GNO Kernel Reference Manual" ,
and the
.IR "Orca/C Reference Manual" .
.IR "ORCA/C Reference Manual" .

2
usr.man/man2/intro.2
View File

@ -133,7 +133,7 @@ will obtain the current limit.
An attempt was made to access a file in a way forbidden
by its file access permissions.
.sp 1
The default Orca/C header files use
The default ORCA/C header files use
.BR EACCESS
(with two
.BR S \'s)

10
usr.man/man2/open.2
View File

@ -101,7 +101,7 @@ a symbolic link,
will fail even if the symbolic
link points to a non-existent name.
.IP \fBO_BINARY\fR
Files opened with the Orca/Shell
Files opened with the ORCA/Shell
.BR open
call by default do newline translation unless the
.BR O_BINARY
@ -131,7 +131,7 @@ a CR (carridge return). During
calls, the opposite translation occurs.
This is similar to, but opposite of, the
.BR O_BINARY
flag interpretation under the Orca/Shell.
flag interpretation under the ORCA/Shell.
.sp 1
The
.BR O_TRANS
@ -195,7 +195,7 @@ open simultaneously by one process.
.BR getdtablesize (2)
returns the current system limit.
.SH COMPATIBILITY
Unlike the GNO implementation, the Orca/C
Unlike the GNO implementation, the ORCA/C
.BR open
call takes no optional third parameter.
.LP
@ -215,7 +215,7 @@ calls. Consequently, the umask is not used in
.BR open (2),
either.
.LP
Due to the way the stack is maintained under Orca/C, it is an error to
Due to the way the stack is maintained under ORCA/C, it is an error to
provide the
.IR mode
parameter if the
@ -225,7 +225,7 @@ flag is not set. Similarily, it is an error to omit
if
.BR O_CREATE
is set. Depending on how the calling routine was compiled, this error
will either manifest itself as a failed Orca/C runtime stack check, or
will either manifest itself as a failed ORCA/C runtime stack check, or
as a crash of the machine.
.LP
The flags

4
usr.man/man2/signal.2
View File

@ -194,10 +194,10 @@ is not in the same bank as the C global data segment
.RI ( func
is called with the data bank equal to the program bank).
.LP
Orca/C already provides a
ORCA/C already provides a
.BR signal
function, but it doesn't do very much. GNO's <signal.h> file replaces
the one that comes with Orca/C.
the one that comes with ORCA/C.
.SH RETURN VALUES
The previous action is returned on a successful call.
Otherwise, \-1 is returned and the global variable