Print this page
6198 Let's EOL cachefs
| Split |
Close |
| Expand all |
| Collapse all |
--- old/usr/src/man/man1m/Intro.1m.man.txt
+++ new/usr/src/man/man1m/Intro.1m.man.txt
1 1 INTRO(1M) Maintenance Commands INTRO(1M)
2 2
3 3
4 4
5 5 NAME
6 6 Intro, intro - introduction to maintenance commands and application
|
↓ open down ↓ |
6 lines elided |
↑ open up ↑ |
7 7 programs
8 8
9 9 DESCRIPTION
10 10 This section describes, in alphabetical order, commands that are used
11 11 chiefly for system maintenance and administration purposes.
12 12
13 13
14 14 Because of command restructuring for the Virtual File System
15 15 architecture, there are several instances of multiple manual pages that
16 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.
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.
29 28
30 29 COMMAND SYNTAX
31 30 Unless otherwise noted, commands described in this section accept
32 31 options and other arguments according to the following syntax:
33 32
34 33 name [option(s)] [cmdarg(s)]
35 34
36 35
37 36
38 37 where:
39 38
40 39 name
41 40 The name of an executable file.
42 41
43 42
44 43 option
45 44 noargletter(s) or,
46 45
47 46 argletter<>optarg
48 47
49 48 where <> is optional white space.
50 49
51 50
52 51 noargletter
53 52 A single letter representing an option without an
54 53 argument.
55 54
56 55
57 56 argletter
58 57 A single letter representing an option requiring an
59 58 argument.
60 59
61 60
62 61 optarg
63 62 Argument (character string) satisfying preceding
64 63 argletter.
65 64
66 65
67 66 cmdarg
68 67 Pathname (or other command argument) not beginning with
69 68 or, by itself indicating the standard input.
70 69
71 70
72 71 ATTRIBUTES
73 72 See attributes(5) for a discussion of the attributes listed in this
74 73 section.
75 74
76 75 ACKNOWLEDGMENTS
77 76 Sun Microsystems, Inc. gratefully acknowledges The Open Group for
78 77 permission to reproduce portions of its copyrighted documentation.
79 78 Original documentation from The Open Group can be obtained online at
80 79 http://www.opengroup.org/bookstore/.
81 80
82 81
83 82 The Institute of Electrical and Electronics Engineers and The Open
84 83 Group, have given us permission to reprint portions of their
85 84 documentation.
86 85
87 86
88 87 In the following statement, the phrase ``this text'' refers to portions
89 88 of the system documentation.
90 89
91 90
92 91 Portions of this text are reprinted and reproduced in electronic form
93 92 in the SunOS Reference Manual, from IEEE Std 1003.1, 2004 Edition,
94 93 Standard for Information Technology -- Portable Operating System
95 94 Interface (POSIX), The Open Group Base Specifications Issue 6,
96 95 Copyright (C) 2001-2004 by the Institute of Electrical and Electronics
97 96 Engineers, Inc and The Open Group. In the event of any discrepancy
98 97 between these versions and the original IEEE and The Open Group
99 98 Standard, the original IEEE and The Open Group Standard is the referee
100 99 document. The original Standard can be obtained online at
101 100 http://www.opengroup.org/unix/online.html.
102 101
103 102
104 103 This notice shall appear on any product containing this material.
105 104
106 105 SEE ALSO
107 106 getopt(1), getopt(3C), attributes(5)
108 107
109 108 DIAGNOSTICS
110 109 Upon termination, each command returns 0 for normal termination and
|
↓ open down ↓ |
72 lines elided |
↑ open up ↑ |
111 110 non-zero to indicate troubles such as erroneous parameters, bad or
112 111 inaccessible data, or other inability to cope with the task at hand. It
113 112 is called variously ``exit code,'' ``exit status,'' or ``return code,''
114 113 and is described only where special conventions are involved.
115 114
116 115 NOTES
117 116 Unfortunately, not all commands adhere to the standard syntax.
118 117
119 118
120 119
121 - November 17, 2008 INTRO(1M)
120 + September 8, 2015 INTRO(1M)
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX