1 INTRO(1M) Maintenance Commands INTRO(1M)
2
3
4
5 NAME
6 Intro, intro - introduction to maintenance commands and application
7 programs
8
9 DESCRIPTION
10 This section describes, in alphabetical order, commands that are used
11 chiefly for system maintenance and administration purposes.
12
13
14 Because of command restructuring for the Virtual File System
15 architecture, there are several instances of multiple manual pages that
16 begin with the same name. For example, the mount, pages mount(1M),
17 mount_cachefs(1M), mount_hsfs(1M), mount_nfs(1M), mount_tmpfs(1M), and
18 mount_ufs(1M). In each such case the first of the multiple pages
19 describes the syntax and options of the generic command, that is, those
20 options applicable to all FSTypes (file system types). The succeeding
21 pages describe the functionality of the FSType-specific modules of the
22 command. These pages list the command followed by an underscore ( _ )
23 and the FSType to which they pertain. Note that the administrator
24 should not attempt to call these modules directly. The generic command
25 provides a common interface to all of them. Thus the FSType-specific
26 manual pages should not be viewed as describing distinct commands, but
27 rather as detailing those aspects of a command that are specific to a
28 particular FSType.
29
30 COMMAND SYNTAX
31 Unless otherwise noted, commands described in this section accept
32 options and other arguments according to the following syntax:
33
34 name [option(s)] [cmdarg(s)]
35
36
37
38 where:
39
40 name
41 The name of an executable file.
42
43
44 option
45 noargletter(s) or,
46
47 argletter<>optarg
48
101 http://www.opengroup.org/unix/online.html.
102
103
104 This notice shall appear on any product containing this material.
105
106 SEE ALSO
107 getopt(1), getopt(3C), attributes(5)
108
109 DIAGNOSTICS
110 Upon termination, each command returns 0 for normal termination and
111 non-zero to indicate troubles such as erroneous parameters, bad or
112 inaccessible data, or other inability to cope with the task at hand. It
113 is called variously ``exit code,'' ``exit status,'' or ``return code,''
114 and is described only where special conventions are involved.
115
116 NOTES
117 Unfortunately, not all commands adhere to the standard syntax.
118
119
120
121 November 17, 2008 INTRO(1M)
|
1 INTRO(1M) Maintenance Commands INTRO(1M)
2
3
4
5 NAME
6 Intro, intro - introduction to maintenance commands and application
7 programs
8
9 DESCRIPTION
10 This section describes, in alphabetical order, commands that are used
11 chiefly for system maintenance and administration purposes.
12
13
14 Because of command restructuring for the Virtual File System
15 architecture, there are several instances of multiple manual pages that
16 begin with the same name. For example, the mount, pages mount(1M),
17 mount_hsfs(1M), mount_nfs(1M), mount_tmpfs(1M), and mount_ufs(1M). In
18 each such case the first of the multiple pages describes the syntax and
19 options of the generic command, that is, those options applicable to
20 all FSTypes (file system types). The succeeding pages describe the
21 functionality of the FSType-specific modules of the command. These
22 pages list the command followed by an underscore ( _ ) and the FSType
23 to which they pertain. Note that the administrator should not attempt
24 to call these modules directly. The generic command provides a common
25 interface to all of them. Thus the FSType-specific manual pages should
26 not be viewed as describing distinct commands, but rather as detailing
27 those aspects of a command that are specific to a particular FSType.
28
29 COMMAND SYNTAX
30 Unless otherwise noted, commands described in this section accept
31 options and other arguments according to the following syntax:
32
33 name [option(s)] [cmdarg(s)]
34
35
36
37 where:
38
39 name
40 The name of an executable file.
41
42
43 option
44 noargletter(s) or,
45
46 argletter<>optarg
47
100 http://www.opengroup.org/unix/online.html.
101
102
103 This notice shall appear on any product containing this material.
104
105 SEE ALSO
106 getopt(1), getopt(3C), attributes(5)
107
108 DIAGNOSTICS
109 Upon termination, each command returns 0 for normal termination and
110 non-zero to indicate troubles such as erroneous parameters, bad or
111 inaccessible data, or other inability to cope with the task at hand. It
112 is called variously ``exit code,'' ``exit status,'' or ``return code,''
113 and is described only where special conventions are involved.
114
115 NOTES
116 Unfortunately, not all commands adhere to the standard syntax.
117
118
119
120 September 8, 2015 INTRO(1M)
|