:Info: entry_bound.gi: 02/10/82 entry bound

     For protection purposes, control must not be passed to a gate
procedure at other than its defined entry points.  To enforce this
restriction, the first N words of a gate segment with N entry points
must be an entry point transfer vector.  To ensure that only these
entries can be used, the hardware enforced entry bound of the gate
segment must be set so that the segment can be entered only at the
first N locations.  See the hcs_$set_entry_bound entry point.


:Info: entry_point.gi: 02/10/82 entry point

     An address in an object segment referred to by a symbolic name;
e.g., that which would be produced by the PL/I or FORTRAN procedure,
subroutine, or entry statements.


:Info: entry_point_name.gi: 02/10/82 entry-point name

     The name associated with an entry point in an object segment.
The entry-point name is found by the dynamic linker.


:Info: error_codes.gi: 02/10/82 error codes

     A value returned by a subroutine indicating either the success
of or the reason for failure to accomplish the requested action.
Associated with standard system error codes are certain predefined
messages that tell what happened.


:Info: exclamation_point.gi: 02/10/82 exclamation point convention

     A name, generated from a system clock value, that is
guaranteed to be different from any other name so generated (e.g.,
!BBBnZNlqLQddRJg).  Also called a shriek name.  See the unique
command.


:Info: fault.gi: 02/10/82 fault

     A hardware signal similar to an interrupt that may cause the
signalling of a condition.


:Info: file.gi: 02/10/82 file

     A term that stands for segment and/or multisegment file.


:Info: frame.gi: 02/10/82 frame

     A pushdown list where active procedures maintain private regions
used for temporary variables and interprocedure communication.


:Info: gate.gi: 02/10/82 gate

     The only point at which a procedure in an outer ring can transfer
to a procedure in an inner ring.


:Info: hardcore.gi: 02/10/82 hardcore (hardcore supervisor)

     The set of routines that perform the supervisory functions of the
system.  The hardcore executes in ring 0.


:Info: hierarchy_backup.gi: 02/10/82 hierarchy backup

     The hierarchy backup system dumps (copies) user segments and
directories onto removable storage (magnetic tape).  The dumping
is conventionally done using the processes Backup.SysDaemon and
Dumper.SysDaemon.  The information dumped can be recovered by the
operations staff at the user's request.  See the
enter_retrieval_request command.


:Info: home_directory.gi: 03/05/82 home directory

     The home directory is the working directory of a user when he or
she first logs in to the system (also known as the initial working
directory).  Usually this directory has a pathname of the form:

	     >udd>Project_id>Person_id


                                          -----------------------------------------------------------


Historical Background

This edition of the Multics software materials and documentation is provided and donated
to Massachusetts Institute of Technology by Group BULL including BULL HN Information Systems Inc. 
as a contribution to computer science knowledge.  
This donation is made also to give evidence of the common contributions of Massachusetts Institute of Technology,
Bell Laboratories, General Electric, Honeywell Information Systems Inc., Honeywell BULL Inc., Groupe BULL
and BULL HN Information Systems Inc. to the development of this operating system. 
Multics development was initiated by Massachusetts Institute of Technology Project MAC (1963-1970),
renamed the MIT Laboratory for Computer Science and Artificial Intelligence in the mid 1970s, under the leadership
of Professor Fernando Jose Corbato. Users consider that Multics provided the best software architecture 
for managing computer hardware properly and for executing programs. Many subsequent operating systems 
incorporated Multics principles.
Multics was distributed in 1975 to 2000 by Group Bull in Europe , and in the U.S. by Bull HN Information Systems Inc., 
as successor in interest by change in name only to Honeywell Bull Inc. and Honeywell Information Systems Inc. .

                                          -----------------------------------------------------------

Permission to use, copy, modify, and distribute these programs and their documentation for any purpose and without
fee is hereby granted,provided that the below copyright notice and historical background appear in all copies
and that both the copyright notice and historical background and this permission notice appear in supporting
documentation, and that the names of MIT, HIS, BULL or BULL HN not be used in advertising or publicity pertaining
to distribution of the programs without specific prior written permission.
    Copyright 1972 by Massachusetts Institute of Technology and Honeywell Information Systems Inc.
    Copyright 2006 by BULL HN Information Systems Inc.
    Copyright 2006 by Bull SAS
    All Rights Reserved