head	1.1;
access;
symbols;
locks; strict;
comment	@# @;


1.1
date	2003.03.02.06.58.33;	author jmallett;	state Exp;
branches;
next	;


desc
@@


1.1
log
@Preliminary helpfile split, a lot of information is obsolete or incorrect
or really just needs updated for the 90s.  Also add a "help stuck" designed
to get bug reports to me, and get Greg Lehey hounded.
@
text
@* $FreeBSD$
-1
error 1 "Not owner and not super-user":
Typically this error indicates
an attempt to modify a file in some way forbidden
except to its owner.
It is also returned for attempts
by ordinary users to do things
allowed only to the super-user.
-2
error 2 "No such file or directory":
This error occurs when a file name is specified
and the file should exist but doesn't, or when one
of the directories in a path name does not exist.
-3
error 3 "No such process":
The process whose number was given to
signal does not exist, or is already dead.
-4
error 4 "Interrupted system call":
An asynchronous signal (such as interrupt or quit),
which the user has elected to catch,
occurred during a system call.
If execution is resumed
after processing the signal,
it will appear as if the interrupted system call
returned this error condition.
-5
error 5 "I/O error":
Some physical I/O error occurred during a
read or write.
This error may in some cases occur
on a call following the one to which it actually applies.
-6
error 6 "No such device or address":
I/O on a special file refers to a subdevice which does not
exist,
or beyond the limits of the device.
It may also occur when, for example, a tape drive
is not dialled in or no disk pack is loaded on a drive.
-7
error 7 "Arg list too long":
An argument list longer than 512 bytes
(counting the null at the end of each argument)
is presented to exec.
-8
error 8 "Exec format error":
A request is made to execute a file
which, although it has the appropriate permissions,
does not start with one of the magic numbers
407 or 410.
@
