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 48 where <> is optional white space. 49 50 51 noargletter 52 A single letter representing an option without an 53 argument. 54 55 56 argletter 57 A single letter representing an option requiring an 58 argument. 59 60 61 optarg 62 Argument (character string) satisfying preceding 63 argletter. 64 65 66 cmdarg 67 Pathname (or other command argument) not beginning with 68 or, by itself indicating the standard input. 69 70 71 ATTRIBUTES 72 See attributes(5) for a discussion of the attributes listed in this 73 section. 74 75 ACKNOWLEDGMENTS 76 Sun Microsystems, Inc. gratefully acknowledges The Open Group for 77 permission to reproduce portions of its copyrighted documentation. 78 Original documentation from The Open Group can be obtained online at 79 http://www.opengroup.org/bookstore/. 80 81 82 The Institute of Electrical and Electronics Engineers and The Open 83 Group, have given us permission to reprint portions of their 84 documentation. 85 86 87 In the following statement, the phrase ``this text'' refers to portions 88 of the system documentation. 89 90 91 Portions of this text are reprinted and reproduced in electronic form 92 in the SunOS Reference Manual, from IEEE Std 1003.1, 2004 Edition, 93 Standard for Information Technology -- Portable Operating System 94 Interface (POSIX), The Open Group Base Specifications Issue 6, 95 Copyright (C) 2001-2004 by the Institute of Electrical and Electronics 96 Engineers, Inc and The Open Group. In the event of any discrepancy 97 between these versions and the original IEEE and The Open Group 98 Standard, the original IEEE and The Open Group Standard is the referee 99 document. The original Standard can be obtained online at 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)