xref: /freebsd/share/man/man8/intro.8 (revision 10ff414c)
1.\" Copyright (c) 1983, 1991, 1993
2.\"	The Regents of the University of California.  All rights reserved.
3.\"
4.\" Redistribution and use in source and binary forms, with or without
5.\" modification, are permitted provided that the following conditions
6.\" are met:
7.\" 1. Redistributions of source code must retain the above copyright
8.\"    notice, this list of conditions and the following disclaimer.
9.\" 2. Redistributions in binary form must reproduce the above copyright
10.\"    notice, this list of conditions and the following disclaimer in the
11.\"    documentation and/or other materials provided with the distribution.
12.\" 3. Neither the name of the University nor the names of its contributors
13.\"    may be used to endorse or promote products derived from this software
14.\"    without specific prior written permission.
15.\"
16.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
17.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
18.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
19.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
20.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
21.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
22.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
23.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
24.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
25.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
26.\" SUCH DAMAGE.
27.\"
28.\"	@(#)intro.8	8.2 (Berkeley) 12/11/93
29.\" $FreeBSD$
30.\"
31.Dd October 22, 2006
32.Dt INTRO 8
33.Os
34.Sh NAME
35.Nm intro
36.Nd "introduction to system maintenance procedures and commands"
37.Sh DESCRIPTION
38This section contains information related to system operation
39and maintenance.
40.Pp
41It describes commands used to create new file systems
42.Pq Xr newfs 8 ,
43verify the integrity of the file systems
44.Pq Xr fsck 8 ,
45control disk usage
46.Pq Xr edquota 8 ,
47maintain system backups
48.Pq Xr dump 8 ,
49and recover files when disks die an untimely death
50.Pq Xr restore 8 .
51.\" The
52.\" .Xr format 8
53.\" manual
54.\" for the specific architecture the system is running on should be
55.\" consulted when formatting disks and tapes.
56Network related services like
57.Xr inetd 8
58and
59.Xr ftpd 8
60are also described.
61.Pp
62All commands set an exit status.
63Its value may be tested
64to see if the command completed normally.
65Unless otherwise noted (rare), the value 0 signifies successful
66completion of the command, while a value >0 indicates an error.
67Some commands attempt to describe the nature of the failure by using
68error codes defined in
69.Xr sysexits 3 ,
70or set the status to arbitrary values >0 (typically 1), but many
71such values are not described in the manual.
72.Pp
73A number of pages in this section describe general system
74management topics.
75.Pp
76For example, the
77.Xr boot 8
78manual page describes the system bootstrapping procedures,
79and the
80.Xr diskless 8
81manual page describes how to boot a system over a network.
82The
83.Xr crash 8
84manual page
85should be consulted to understand how to interpret system
86crash dumps.
87.Sh HISTORY
88The
89.Nm
90section manual page appeared in
91.Bx 4.2 .
92