1 :Info: entry_bound.gi: 02/10/82 entry bound
 2 
 3      For protection purposes, control must not be passed to a gate
 4 procedure at other than its defined entry points.  To enforce this
 5 restriction, the first N words of a gate segment with N entry points
 6 must be an entry point transfer vector.  To ensure that only these
 7 entries can be used, the hardware enforced entry bound of the gate
 8 segment must be set so that the segment can be entered only at the
 9 first N locations.  See the hcs_$set_entry_bound entry point.
10 
11 
12 :Info: entry_point.gi: 02/10/82 entry point
13 
14      An address in an object segment referred to by a symbolic name;
15 e.g., that which would be produced by the PL/I or FORTRAN procedure,
16 subroutine, or entry statements.
17 
18 
19 :Info: entry_point_name.gi: 02/10/82 entry-point name
20 
21      The name associated with an entry point in an object segment.
22 The entry-point name is found by the dynamic linker.
23 
24 
25 :Info: error_codes.gi: 02/10/82 error codes
26 
27      A value returned by a subroutine indicating either the success
28 of or the reason for failure to accomplish the requested action.
29 Associated with standard system error codes are certain predefined
30 messages that tell what happened.
31 
32 
33 :Info: exclamation_point.gi: 02/10/82 exclamation point convention
34 
35      A name, generated from a system clock value, that is
36 guaranteed to be different from any other name so generated (e.g.,
37 !BBBnZNlqLQddRJg).  Also called a shriek name.  See the unique
38 command.
39 
40 
41 :Info: fault.gi: 02/10/82 fault
42 
43      A hardware signal similar to an interrupt that may cause the
44 signalling of a condition.
45 
46 
47 :Info: file.gi: 02/10/82 file
48 
49      A term that stands for segment and/or multisegment file.
50 
51 
52 :Info: frame.gi: 02/10/82 frame
53 
54      A pushdown list where active procedures maintain private regions
55 used for temporary variables and interprocedure communication.
56 
57 
58 :Info: gate.gi: 02/10/82 gate
59 
60      The only point at which a procedure in an outer ring can transfer
61 to a procedure in an inner ring.
62 
63 
64 :Info: hardcore.gi: 02/10/82 hardcore (hardcore supervisor)
65 
66      The set of routines that perform the supervisory functions of the
67 system.  The hardcore executes in ring 0.
68 
69 
70 :Info: hierarchy_backup.gi: 02/10/82 hierarchy backup
71 
72      The hierarchy backup system dumps (copies) user segments and
73 directories onto removable storage (magnetic tape).  The dumping
74 is conventionally done using the processes Backup.SysDaemon and
75 Dumper.SysDaemon.  The information dumped can be recovered by the
76 operations staff at the user's request.  See the
77 enter_retrieval_request command.
78 
79 
80 :Info: home_directory.gi: 03/05/82 home directory
81 
82      The home directory is the working directory of a user when he or
83 she first logs in to the system (also known as the initial working
84 directory).  Usually this directory has a pathname of the form:
85 
86                >udd>Project_id>Person_id