WilliamR.SissonPart No: 802-5758-10August 1997Sun Microsystems, Inc.

2550 Garcia AvenueMountain View, CA94043-1100U.S.A.

1997Sun MicrosystemsThe Solaris(TM) 2.6 operating environment (the distributed computing solution from SunSoft(TM)) is comprised of SunOS(TM) release 5.6 with the ONC(TM), OpenWindows(TM), ToolTalk(TM), DeskSet(TM), and OPEN LOOK(TM) features as well as other utilities. This book focuses on the differences between the SunOS release 4.x and SunOS release 5.6 operating systems for people already familiar with the SunOS release 4.x operating system. This book also describes other aspects of the Solaris 2.6 operating environment that can help end users, developers, and system administrators through the transition. This product or document is protected by copyright and distributed under licenses restricting its use, copying, distribution, and decompilation. No part of this product or document may be reproduced in any form by any means without prior written authorization of Sun and its licensors, if any. Third-party software, including font technology, is copyrighted and licensed from Sun suppliers.Parts of the product may be derived from Berkeley BSD systems, licensed from the University of California. UNIX is a registered trademark in the U.S. and other countries, exclusively licensed through X/Open Company, Ltd.Sun, Sun Microsystems, the Sun logo, SunSoft, SunDocs, SunExpress, and Solaris are trademarks, registered trademarks, or service marks of Sun Microsystems, Inc. in the U.S. and other countries. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. in the U.S. and other countries. Products bearing SPARC trademarks are based upon an architecture developed by Sun Microsystems, Inc. The OPEN LOOK and Sun Graphical User Interface was developed by Sun Microsystems, Inc. for its users and licensees. Sun acknowledges the pioneering efforts of Xerox in researching and developing the concept of visual or graphical user interfaces for the computer industry. Sun holds a non-exclusive license from Xerox to the Xerox Graphical User Interface, which license also covers Sun's licensees who implement OPEN LOOK GUIs and otherwise comply with Sun's written license agreements.RESTRICTED RIGHTS: Use, duplication, or disclosure by the U.S. Government is subject to restrictions of FAR 52.227-14(g)(2)(6/87) and FAR 52.227-19(6/87), or DFAR 252.227-7015(b)(6/95) and DFAR 227.7202-3(a).DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID.Ce produit ou document est protégé par un copyright et distribué avec des licences qui en restreignent l'utilisation, la copie, la distribution, et la décompilation. Aucune partie de ce produit ou document ne peut être reproduite sous aucune forme, par quelque moyen que ce soit, sans l'autorisation préalable et écrite de Sun et de ses bailleurs de licence, s'il y en a. Le logiciel détenu par des tiers, et qui comprend la technologie relative aux polices de caractères, est protégé par un copyright et licencié par des fournisseurs de Sun.Des parties de ce produit pourront être dérivées du système Berkeley BSD licenciés par l'Université de Californie. UNIX est une marque déposée aux Etats-Unis et dans d'autres pays et licenciée exclusivement par X/Open Company, Ltd. Sun, Sun Microsystems, le logo Sun, SunSoft, SunDocs, SunExpress, et Solaris sont des marques de fabrique ou des marques déposées, ou marques de service, de Sun Microsystems, Inc. aux Etats-Unis et dans d'autres pays. Toutes les marques SPARC sont utilisées sous licence et sont des marques de fabrique ou des marques déposées de SPARC International, Inc. aux Etats-Unis et dans d'autres pays. Les produits portant les marques SPARC sont basés sur une architecture développée par Sun Microsystems, Inc.L'interface d'utilisation graphique OPEN LOOK et Sun a été développée par Sun Microsystems, Inc. pour ses utilisateurs et licenciés. Sun reconnaît les efforts de pionniers de Xerox pour la recherche et le développement du concept des interfaces d'utilisation visuelle ou graphique pour l'industrie de l'informatique. Sun détient une licence non exclusive de Xerox sur l'interface d'utilisation graphique Xerox, cette licence couvrant également les licenciés de Sun qui mettent en place l'interface d'utilisation graphique OPEN LOOK et qui en outre se conforment aux licences écrites de Sun.CETTE PUBLICATION EST FOURNIE "EN L'ETAT" ET AUCUNE GARANTIE, EXPRESSE OU IMPLICITE, N'EST ACCORDEE, Y COMPRIS DES GARANTIES CONCERNANT LA VALEUR MARCHANDE, L'APTITUDE DE LA PUBLICATION A REPONDRE A UNE UTILISATION PARTICULIERE, OU LE FAIT QU'ELLE NE SOIT PAS CONTREFAISANTE DE PRODUIT DE TIERS. CE DENI DE GARANTIE NE S'APPLIQUERAIT PAS, DANS LA MESURE OU IL SERAIT TENU JURIDIQUEMENT NUL ET NON AVENU.Desktop & Window SystemsInstallation & SetupIntroduction & OverviewProgramming & ToolsSecuritySystem AdministrationPrefacePrefaceaccounting systemuser accountsadministators,See system administrators\x0dAdministration ToolHost ManagerUser Account Manageradmintool commandbacking updd commanddump commandrestoringtar commandufsdump command/bin directory,See /usr/bin directory\x0dbooting/ccs directory,See /usr/ccs directory\x0dcheckingclientsNIS (Network Information Services), clientscommandschanges incommandsconfigurationsystem configurationconfiguration files,See /etc directory\x0dconsistency checking,See checking\x0ddataless clients,See diskless/dataless clients\x0d/default directory,See /etc/default directory\x0ddebuggersdbxtool commandadb commandkadb commandtruss commanddeleting,See removing\x0ddevice configurationdevice driversdevice configurationdevice namingspecific devices/dfs directory,See /etc/dfs directory\x0ddirectoriesdomain name system,See DNS (domain name system)\x0dDriver Kernel Interface (DKI)drivers,See device drivers\x0ddump commandufsdump commanddynamic kernele-mail,See mail\x0denvironments,See Solaris operating environmentuser environment administration/etc directory/etc/rc scriptsexecutable and linking format files,See ELF (executable and linking format) files\x0dexported file systems,See shared file systems\x0dfile system administration,See file systems\x0dfile systemsexported,See shared file systems\x0dfile systemsshared,See shared file systems\x0dfile systemstemporary,See temporary file systems\x0dfile systemsfiles/fstab system file,See /etc/fstab file\x0dgraphical user interfaces (GUIs)GUIs,See graphical user interfaces (GUIs)\x0dhalting,See shutting down\x0dinformation reportinginitialization files,See environment initialization files\x0dinitialization scripts,See scripts\x0dintegrity checking,See checking\x0d/lib directory,See /etc/lib directory/usr/ccs/lib directory/usr/lib directory/usr/share/lib directorylimits/lp directory,See /etc/lp directory/usr/lib/lp directory/var/lp directory/var/spool/lp directorymagnetic tape devices,See tape devices\x0dmail command/mail directory,See /etc/mail directory/usr/lib/mail directory/var/mail directory/var/spool/mail directorymaps (NIS+),See NIS+ (Network Information Services Plus)\x0dmaps (NIS),See NIS (Network Information Services)\x0dmaster servers,See NIS (Network Information Services), master servers\x0dmaximums,See limits\x0dmodifying,See changing\x0dmodules,See kernelSTREAMSname services,See DNS (domain name system)NIS+ (Network Information Services Plus)NIS (Network Information Services)/net directory,See /etc/net directory/usr/net/servers directoryNetwork Information Services,See NIS (Network Information Services)\x0dNetwork Information Services Plus,See NIS+ (Network Information Services Plus)\x0dOpenWindowsAdministration Tool,See Administration Tool\x0d/opt directorypath namesprintcap database,See /etc/printcap database\x0dprinterscommandsproductivity tools,See DeskSet\x0dprogramming tools,See developerstools (developer)restoringrestore commandufsrestore commandrun levels,See rc scripts\x0d/sadm directory,See /usr/sadm directory/var/sadm directory/saf directory,See /etc/saf directory/usr/lib/saf directory/var/saf directorysaving/sbin directory/sbin/rc scriptsscheduling,See Calendar Managerprocess managementsecurityserversSolaris 2.6 server/share directory,See /usr/share directory\x0dshellsC shellslices,See disk slices\x0dsoftwaresoftware clusters,See clusters\x0dSoftware Manager,See swmtool command\x0dsoftware packages,See packagessoftwareSolaris 2.4 operating environmentOpenWindowsSolaris operating environmentSolaris operating environmentspool directory,See /var/spool directory\x0dstatus checking,See checkinginformation reportingstopping system,See shutting down\x0dsystem administratorssystem file,See /etc/system file\x0dsystem initialization scripts,See rc scripts\x0dsystem run levels,See rc scripts\x0dsystem scheduling,See process management\x0dtemporary file systemstime management,See Calendar Managerprocess managementTMPFS,See /tmp file system (TMPFS)\x0dtrace command/ucb directory,See /usr/ucb directoryUFS,See Unix file systems (UFS)\x0dUnix file systems (UFS)unix kernel nameUnix System V Release 4,See SVR4\x0dUnix-to-Unix Copy (UUCP)/usr/etc directory/usr/kernel directory,See /kernel directory\x0d/uucp directory,See /etc/uucp directory/usr/lib/uucp directory/var/spool/uucp directory/var/uucp directoryvfstab file,See /etc/vfstab file\x0d/xpg2lib directory,See /usr/xpg2lib directory\x0ddump commandnew 218The Solaris(TM) 2.6 operating environment, SunSoft's(TM) distributed computing solution, comprises SunOS(TM) release 5.6 software with ONC(TM), OpenWindows(TM), ToolTalk(TM), and DeskSet(TM) utilities as well as other features. Solaris 1.x to Solaris 2.x Transition Guide focuses on the differences between the SunOS release 4.x and SunOS release 5.6 operating systems for people already familiar with the SunOS release 4.x software. This guide also handles other aspects of the Solaris 2.6 operating environment that can help you through the transition. If you are looking for more information about features now available with the Solaris 2.6 operating environment, see Solaris User's Guide.The system administration tool covered in this book, Admintool, is part of the Solaris 2.6 product and can be used only for local system administration. System administration tools used to manage a network of systems are provided with the Solstice family of products.Note - The term "x86" refers to the Intel 8086 family of microprocessor chips, including the Pentium and Pentium Pro processors and compatible microprocessor chips made by AMD and Cyrix. In this document the term "x86" refers to the overall platform architecture, whereas "Intel Platform Edition" appears in the product name.This guide can help users, system administrators, and software developers make the transition from a SunOS release 4.x computing environment to the Solaris 2.6 operating environment. The purpose of this guide is to give you an overview-level understanding of the differences between SunOS release 4.x and SunOS release 5.6 operating environments to make your transition to the Solaris 2.6 operating environment a smooth one. As a result, Solaris 1.x to Solaris 2.x Transition Guide covers a wide range of topics. Because it is not practical to list detailed procedures for tasks here, you will find references throughout this guide to publications in the Solaris 2.6 documentation set where detailed information is available.This guide is divided into 2 parts with 19 chapters and 6 appendixes as outlined here.You can use this part of the guide to help install Solaris 2.6 software, to understand changes to the local computing environment, and to understand changes to routine tasks. This part of the guide contains the following chapters:Chapter 1, Introduction, discusses the benefits of migrating to the Solaris operating environment and summarizes the main differences between SVR4 and the Solaris operating environment.Chapter 2, Overview of Major Changes, is an overview of some of the principal changes between the SunOS release 4.x and SunOS release 5.6 environments. It provides background for topics in subsequent chapters, focusing on procedures, tools, and concepts that have changed between releases.Chapter 3, Converting a SunOS 4.x System to the Solaris 2.6 Environment, suggests what to consider to facilitate a smooth transition through software installation and post-installation so that SunOS release 4.x data can most easily be restored in the Solaris 2.6 operating environment. Chapter 4, Using the Compatibility Packages, discusses the SunOS/BSD Source Compatibility Package and the Binary Compatibility Package. These packages make the transition easier by enabling you to use SunOS release 4.x commands and applications during migration to the Solaris 2.6 operating environment.Chapter 5, Security , describes the major differences between SunOS release 4.x and Solaris 2.6 security, and points out how those changes might affect system administration procedures.Chapter 6, User Environment Administration, describes differences in tasks used to set up a local user environment after installing the Solaris software. It includes discussions on setting up a default shell, customizing the user environment, the window system, and user and group administration. It also discusses changes regarding man pages.Chapter 7, Device Administration, explains SunOS release 5.6 device naming conventions and discusses changes to device-related tasks such as getting information about disks, adding devices to a system, and using volume management.Chapter 8, Startup and Shutdown, describes changes to procedures for booting and shutting down a system.Chapter 9, File System Administration, familiarizes you with changes to file-system layout and the changes to file systems, virtual file systems, directories, and files. It also describes changes to file-system administration.Chapter 10, Setting Up a Solaris 2.6 Server to Support SunOS Release 4.x Diskless/Dataless Clients, discusses setting up servers for clients. It describes three programs-discover4x, install4x, and convert4x-that work together to help prepare a Solaris 2.6 server to serve SunOS release 4.x clients. Chapter 11, Managing Printers, Terminals, and Modems, describes how to set up and administer printers after you install Solaris 2.6 software and changes to printer commands. It also describes terminal and modem management using Admintool and the Service Access Facility (SAP).Chapter 12, Network Service Administration, outlines changes to the network facilities, TCP/IP and UUCP.Chapter 13, Using Name Services, discusses NIS+ and the domain name system (DNS), and compares NIS+ to NIS and DNS.Chapter 14, Solaris Common Desktop Environment, describes the Common Desktop Environment (CDE) and how to make the transition from the OpenWindows environment to CDE.This part of the guide concentrates on the changes that most affect developers. It describes these differences, points out similarities, and explains the implications for your programming environment.This part contains the following chapters:Chapter 15, Compilers, Linkers, and Debuggers , discusses which capabilities have been added to or removed from compilers, linkers, and debuggers.Chapter 16, Tools and Resources , discusses changes to tools and resources for the development environment including changes to ioctl() requests, ptrace() request values, libraries, and the make and SCCS facilities. This chapter also describes how to determine application compatibility, how to use Solaris 2.6 packaging capabilities, and how to find SunOS release 4.x tools.Chapter 17, Networking and Internationalization, discusses Solaris 2.6 networking features as they relate to the programming environment. It also describes improved internationalization features.Chapter 18, System and Device Configuration, describes aspects of system and device configuration that have changed, including the dynamically loaded kernel and kernel layout, config and boot commands, and the /etc/system file.Chapter 19, Device Drivers and STREAMS , discusses device drivers issues such as changes to device driver interfaces, the devinfo command, porting considerations, STREAMS, and the Solaris 2.6 driver architecture.The following appendixes comprises reference tables showing SunOS 4.1 interfaces and their status in several operating systems. This information is useful to users, system administrators, and developers. The appendixes are:Appendix A, Commands Reference Table, compares SunOS release 4.x and SunOS release 5.6 commands.Appendix B, System Calls Reference Table, compares SunOS release 4.x and SunOS release 5.6 system calls.Appendix C, Library Routines Reference Table, compares SunOS release 4.x and SunOS release 5.6 library routines.Appendix D, System Files Reference Table, compares SunOS release 4.x and SunOS release 5.6 system files.Appendix E, / and /usr File Systems Changes, compares SunOS release 4.x and SunOS release 5.6 system files.Appendix F, Quick Reference for Basic Changes, is a quick reference for changes in common commands, files and directories, and daemons and standard processes.The SunDocs(TM) program provides more than 250 manuals from Sun Microsystems, Inc. If you live in the United States, Canada, Europe, or Japan, you can purchase documentation sets or individual manuals using this program.For a list of documents and how to order them, see the catalog section of the SunExpress(TM) Internet site at http://www.sun.com/sunexpress.Table P-1 describes the type changes and symbols used in this guide.Table P-1 Typeface or SymbolMeaningExampleAaBbCc123The names of commands, files, and directories; on-screen computer outputEdit your .login file.Use ls -a to list all files.system% You have mail.AaBbCc123What you type, contrasted with on-screen computer outputsystem% suPassword:AaBbCc123Command-line placeholder:replace with a real name or valueTo delete a file, type rm filename.AaBbCc123Book titles, new words or terms, or words to be emphasizedRead Chapter 6 in User's Guide. These are called class options. You must be root to do this.Code samples are included in boxes and may display the following: prompts% % percent sign (%)UNIX C shell promptsystem%$ $ dollar sign (library routine)UNIX Bourne and Korn shell promptsystem$# # pound sign (#)Superuser prompt, all shellssystem#When commands, system files, or library routine names are first mentioned in the text, the number of the manual page section where the term is fully described is appended; for instance: mv(1). The manual pages are in the man Pages(1): User Commands section. For more information the Solaris 2.6 operating environment, see the following documentation: Solaris 2.6 operating environmentadditional documentation onSolaris User's GuideSolaris Advanced User's GuideInstallation Instructions for Solaris 2.6 (SPARC Platform Edition)System Administration GuideNIS+ Transition GuideNFS Administration GuideSolaris Naming Administration GuideSolaris Naming Setup and Configuration GuideTCP/IP and Data Communications Administration GuideSunOS Reference ManualBinary Compatibility GuideSource Compatibility GuideDeveloper's Guide to InternationalizationMultithreaded Programming GuideLinker and Libraries GuideProgramming Utilities GuideYou can get additional Solaris transition information by accessing the following URL:http://www.sun.com/smcc/solaris-migration/index.htmlThe Solaris Migration Initiative home page is a central point for the distribution of tools, documentation, and information to aid you in your migration to Solaris 2.x. You can always find the most current resources and pointers here. Part IPart I Transition Information for Users and System AdministratorsYou can use this part of the guide to help install Solaris 2.6 software, and to understand changes to the local computing environment and to routine tasks. Chapter 11. IntroductionThe Solaris operating environment enhances your system's capabilities with powerful tools and features. This introduction discusses the benefits of migrating to the Solaris operating environment and summarizes the principal differences between SVR4 and the Solaris operating environment."Advantages of Migrating to the Solaris Operating Environment""Comparison of SVR4 and the Solaris Operating Environment"The UNIX\256 standard, SVR4, accommodates the leading UNIX variants (System V, BSD, SunOS, and XENIX), uniting the majority of the installed base of UNIX users. The Solaris operating environment, based on SVR4, gives software developers, system administrators, and end users the benefits of a standard operating system including broad compatibility, a growth path, and reduced time to market. It also delivers a functional and powerful product reflecting years of refinement. Among the many advantages the Solaris operating environment provides are portability, scalability, interoperability, and compatibility. Solaris operating environmentSVR4 vs. Solaris operating environmentadvantages SVR4Solaris vs. standardizationAlthough the foundation of the Solaris operating environment is based on SVR4, SunSoft has added extensive functionality in areas such as symmetric multiprocessing with multithreads, real-time functionality, increased security, and improved system administration.The Solaris operating environment offers the following features: Solaris operating environmentfeaturesSunOS release 5.6, a full 32-bit operating system based on UNIX System V Release 4 (SVR4) Solaris operating environmentSVR4 vs. SVR4Solaris vs.Cross-functional compatibility, which enables the SunOS release 5.6 software to run on SPARC(TM) as well as Intel 386, 486, Pentium and other DOS-compatible CPUs cross-functional compatibility compatibilitycross-functional hardware SunOS release 5.6cross-functional compatibility Solaris operating environmentcompatibilityIndustry standards including SVR4 and the ONC family of networking protocolsGraphical user interface (GUI) in the OPEN LOOK\256 Window Manager graphical user interfaces (GUIs)for installationCommon Desktop Environment, a desktop graphical interface. This window environment helps you organize and manage your work. The desktop provides windows, workspaces, controls, menus, and a Front Panel allowing simple access to Mail, File Manager, Printers, Image Tool, Calendar Manager, and othersDeskSet Calendar Manager mailmultimedia groupware productivity tools personal productivity tools multimedia mail Image Tool File ManagerCalendar Manager, a time management application that displays appointments and ToDo items at a glance and offers a multibrowse feature that makes scheduling among a group easyFile Manager, a graphical and intuitive way to navigate to local and remote file systems File ManagerImage Tool, which enables you to load, view and save images of over 40 different formats Image ToolAudio, a new, Motif-based audio application for playing and recording AU, WAV, and AIFF files.OPEN LOOK Admintool, the base for local system administration OPEN LOOK admintoolInstallation GUI for easing install and updateLog-based file systems on serversAdvanced architecture that includes fully symmetric multiprocessing and sophisticated multithreadingReal-time priority scheduling and a fully pre-emptible kernel, providing the benefits of open systems while meeting the requirements of control applications real-time priority schedulingNetwork Information Services Plus (NIS+), an upward-compatible version of the NIS name service with simpler hierarchical administration, improved security, and faster updates. NIS+ (Network Information Services Plus)describedStandards conformance for application developers interested in the benefits of application portability standardizationMultimedia Mail, for sending messages that incorporate audio, graphics, and embedded files multimedia mail mailmultimediaJava Virtual Machine(TM), provides access to the Java platform for the Solaris operating environmentspoken messages messages, spokenWebNFS, makes it possible to make a file system accessible through a Web browser.AnswerBook2(TM) Viewer, Sun's premier online documentation system that uses a web-browser-based interfaceThe Solaris operating environment is portable, scalable, interoperable, and compatible.The SunSoft SunOS product is portable across multiple vendor platforms. Software conforming to an application binary interface (ABI) runs as shrink-wrapped software on all vendor systems with the same microprocessor architecture. This enables application developers to reduce software development costs and bring products to market quickly, and enables users to upgrade hardware while retaining their software applications and minimizing conversion costs. Solaris operating environmentportability portabilityOver time, applications become more widely used, and require more powerful systems to support them. To operate in a growing environment, software must be able to run in a wide power range and must be able to take advantage of the additional processing power. SunSoft's operating system runs on machines of all sizes, from laptops to supercomputers. Solaris operating environmentscalability scalabilityHeterogenous computing environments are a reality today. Users purchase systems from many vendors to implement the solutions they need. Standardization and clear interfaces are critical to a heterogeneous environment, enabling users to develop strategies for communicating throughout their network. Solaris systems can interoperate with every popular system on the market today, and applications running on UNIX can communicate easily. Solaris operating environmentinteroperability interoperability standardizationComputing technology continues to advance rapidly, but the need to remain competitive requires vendors to minimize their costs and to maximize their investments. SunSoft will ensure that as new technology is introduced, the existing software investment is preserved. Users can take advantage of today's solutions and still be compatible with tomorrow's technologies. Solaris operating environmentcompatibility compatibilitycross-functional hardwareThe Solaris operating environment provides a number of sound business reasons for transitioning to an industry-standard-based UNIX operating system. Application development and maintenance costs are lower, and application portability is enhanced. Solaris operating environmentlarge organizations and large organizations, advantages of Solaris for Solaris operating environmentadvantagesThis section describes the main differences between SVR4 and the Solaris operating environment. It points out features that the Solaris operating environment includes that are not available in SVR4 and a few SVR4 features that are not available in the Solaris operating environment. Solaris operating environmentfeatures SVR4Solaris vs. Solaris operating environmentSVR4 vs.The Solaris operating environment offers value-added components in addition to the SVR4-based operating system. These make computing easier and create new opportunities for users, system administrators, and developers.In general, the merge of established UNIX variants into SVR4 and the Solaris operating environment was done by consolidating the existing functionality while maintaining compatibility for existing applications. As a result, features and commands were added to the product with few features being withdrawn.For users, the Solaris operating environment incorporates a suite of powerful DeskSet applications to enhance personal productivity. All DeskSet applications rely on the drag-and-drop metaphor, enabling users to carry out complex UNIX commands with a mouse. Specifically, some of the features are: personal productivity tools DeskSet users, Solaris features for Solaris operating environmentuser featuresA workspace manager. Provides basic window management services (open, close, move, and so on), as well as tools that enables user to customize their workspace. workspace manager window management servicesDesktop integration services. These include ToolTalk, drag and drop, and cut and paste, providing the foundation that enables applications to seamlessly integrate with one another. desktop integration services cut and paste ToolTalk drag and dropGraphics libraries. These include XGL(TM), Xlib, PEX(TM), and XIL(TM), providing support for 2D and 3D graphics applications. graphics librariesCalendar Manager. A time management application that displays appointments and ToDo items for a day, week, or a month at a glance. It also contains a multibrowse feature that makes scheduling meetings among a group of users easy. Multiple calendars can be overlaid simultaneously to determine convenient meeting time slots at a glance. Calendar ManagerImage Tool. Enables you to load, view and save images of over 40 different formats including PICT, PostScript(TM), TIFF, GIF, JFIF, and many more. Image ToolOther tools include a print tool, audio tool, shell tool, clock, and text editor. DeskSet personal productivity tools Solaris operating environmentuser features users, Solaris features forFor system administrators, the Solaris operating environment offers a variety of new tools to simplify the administration of a distributed computing environment. These include: system administratorsSolaris features for Solaris operating environmentsystem administrator featuresDevice information. Administrators can use these optional utilities to obtain information about installed devices including device names, attributes, and accessibility. Administration can be simplified by creating device allocation pools, a feature not previously found in UNIX systems. information reportingdevice administration device administrationinformation reportingFile system administration. These utilities enable administrators to create, copy, mount, debug, repair, and unmount file systems; create and remove hard file links and named pipes; and manage volumes. file systemsutility overviewInterprocess communication. Two interprocess communication utilities create, remove, and report on the status of the system's interprocess communication facilities (message queues, semaphores, and shared memory IDs). They provide information helpful in tuning the system. interprocess communication utilitiesProcess management. The process management utilities help you control system scheduling. Using these utilities, administrators can generate reports on performance, logins, disk access locations, and seek distances to better tune system performance. In addition, you can change the system run level, kill active processes, time the execution of commands, and change the default scheduling priorities of kernel, timesharing, and real-time processes. process managementutilitiesSystem accounting. The accounting utilities enable system administrators to track system usage by CPU, user, and process for better resource allocation. system accountingutilities overviewSystem information. These utilities report system memory and system configuration. The system administrator can use the utilities to change the names of the systems and the network node. system information utilitiesUser and group management. With these utilities, a system administrator can create and delete entries in group and password databases, specify default home directories and environments, maintain user and system logins, and assign group and user IDs. The utilities support both primary and supplementary user groups. user management utilities groups, administeringAdmintool. Admintool, which runs under the OpenWindows environment, provides system management facilities to help add hosts, manage the network, and perform many other routine tasks on local systems. SunOS release 5.6admintool admintooldescribedAuto configuration. The Solaris operating environment has a dynamic kernel, which means that it loads drivers and other modules into memory when the devices are accessed. You no longer need to rebuild the kernel after installation, nor must you add or remove drivers. configurationauto auto configuration kerneldynamic dynamic kerneldefinedNetwork Information Services Plus (NIS+). An upward-compatible version of the NIS name service with simpler hierarchical administration, improved security, and faster updates. NIS+ (Network Information Services Plus)describedInstallation. The Solaris operating environment has an install GUI to ease installation or upgrades. Automatic installations and upgrades are also possible over the network. installationoverview graphical user interfaces (GUIs)for installationSecurity. The automated security enhancement tool (ASET) is a utility that improves security by allowing system administrators to check system file settings including permissions, ownership, and file contents. ASET warns users about potential security problems and, where appropriate, sets the system file permissions autonomically according to the specified security level. automated security enhancement tool (ASET) ASET (automated security enhancement tool) securitylevel of securityASET Solaris operating environmentsystem administrator features system administratorsSolaris features forFor application developers, the Solaris operating environment includes a variety of toolkits and features to simplify the development of complex applications with graphical user interfaces. Solaris operating environmentdeveloper features developersSolaris features forMultithreaded (MT) kernel. MT provides for a symmetric multiprocessing kernel where multiple processors can execute the kernel at the same time. Applications can be structured as several independent computations rather than as one thread of control. Independent computations execute more efficiently because the operating system handles the interleaving of the independent operations. This benefit of multithreading is known as application concurrency. application concurrency kernelMT (multithreaded) concurrency multithreaded (MT) kernel MT (multithreaded) kernelSTREAMS. STREAMS is a flexible framework for character input and output (I/O) that has been implemented throughout SVR4. It is easily customized for applications. STREAMSdescribedExpanded fundamental types. ID data types (uid, pid, device IDs, and the like) and certain other data types are expanded to 32 bits. This improves the scalability of the operating system in large systems and for use in large organizations. ID data types, expanded data types, expanded Solaris operating environmentscalability scalabilityDevice driver interfaces. There are three types of interfaces for Solaris device drivers: Device Kernel Interface (DKI) Device Driver Interface/Device Kernel Interface (DDI/DKI), and Sun Device Driver Interface (Sun DDI). The DDI/DKI conformance means that device drivers have better source and binary compatibility across SPARC platforms so developers can write one driver to support a peripheral on all SPARC platforms. DKI (Driver Kernel Interface) Driver Kernel Interface (DKI) Solaris 2.6 DDI/DKI Solaris 2.6 SPARC DDI/DKI SPARC DDI/DKI SPARC platforms, Solaris features and Sun DDI (Sun Device Driver Interface) DDI (Device Driver Interface) device driversinterface types Device Driver Interface (DDI) DDI/DKI (Device Driver Interface/Driver Kernel Interface) device driversinterface compatility Device Driver Interface/Driver Kernel Interface (DDI/DKI)Automatic device driver loading. This makes drivers easier to install and devices easier to access. loading device drivers device administrationloading devices device administrationautomatic loading automatic loading, device driversDynamic linking. The Solaris application environment supports static and dynamic linking of libraries. The linker uses the version numbers of the libraries and executables to link applications with the proper libraries, routines, and interfaces. linkersdynamic linking librariesdynamic linking of dynamic linking Solaris operating environmentfeatures developersSolaris features for Solaris operating environmentdeveloper featuresIn a few instances, features in SVR4 were not include in the Solaris operating environment. These features are specific to AT&T hardware, or features included primarily for backward compatibility with SVR3 features and therefore, are of little value to SunOS users. AT&T systemsSVR4 features excluded from Solaris operating environmentThe Solaris operating environment does not include the System V file system and associated utilities because of their limitations compared to the UNIX file system. The SVR4 boot file system was not included because of its maintenance burden when compared to the SunOS traditional boot model. System V file system (S5) file systemsSystem VThe generic AT&T SVR4 model for device auto-configuration and for rebuilding kernels was replaced with a fully dynamically configurable kernel better suited to the needs of present and future users of SPARC systems.Because there is no installed base of SPARC XENIX programs, the SPARC release of the Solaris operating environment does not include compatibility for XENIX applications. XENIX, Solaris SPARC release andThe Solaris operating environment does not include the AT&T SVR4 sysadm utility. Because the sysadm menu utility was designed primarily for use with terminal devices on freestanding systems, SunSoft chose to concentrate its efforts on tools with graphical user interfaces that simplify the administration of distributed systems across a network. The Solaris operating environment provides the utilities and configuration directories that underlie the SVR4 sysadm utility but not the sysadm utility itself. sysadm menu utility menus, sysadm menu utility AT&T systemssysadm menu utility Solaris operating environmentSVR4 vs. SVR4Solaris vs. AT&T systemsSVR4 features excluded from Solaris operating environment AT&T systemssysadm menu utility menus, sysadm menu utility sysadm menu utilityChapter 22. Overview of Major ChangesAs you use the Solaris 2.6 operating environment, you will find similarities to the SunOS release 4.x operating environment; however, you will also notice some differences. The rest of this guide focuses on the procedures, tools, commands, and concepts that have changed between releases. This chapter is an overview of some of the principal changes. It provides background information for topics in subsequent chapters. Some topics receive sufficient coverage here, while others require more in-depth technical background. In the latter case, the text directs you to a chapter that more fully describes the changes."Software Packages and Clusters""Disk Slices (or Partitions)""Device Naming""File Systems""Kernel Configuration""Automounting""Admintool""Network Information Service Plus (NIS+)""Print Subsystem""Service Access Facility""Volume Management"SunOS release 4.xoverview of major changes in Solaris 2.6Solaris 2.6 operating environmentoverview of major changesSolaris 2.6 system software is delivered in units known as packages. A package is a collection of files and directories required for a software product. A cluster is a collection of packages. packagesdefined clustersThe list below describes four clusters. Note that as you progress through the list, each cluster contains the software of the preceding cluster plus additional software.Core System Support is the minimum software configuration; it contains only the software necessary to boot and run the Solaris 2.6 operating environment. Core System SupportEnd User System Support contains Core System Support plus end user support such as the OpenWindows windowing system and the related DeskSet application files; this cluster includes the recommended software for an end user.Developer System Support contains End User System Support plus the libraries, include files, and tools needed to develop software in the Solaris 2.6 operating environment. Compilers and debuggers are not included in the Solaris 2.6 operating environment. End User System Support Developer System SupportEntire Distribution contains the entire Solaris 2.6 environment. Entire DistributionFor more information about this section's topics, see System Administration Guide.Software package management simplifies installing and updating software. Administration is simplified because the method for managing system software and third party applications is now consistent. The tools for creating software packages are in an application packaging tools library. removingsoftware packages remote systemssoftware package administration packagesadvantages packagesinstalling installationsoftware packagesThere are two tools you can use to install and remove packages: packagesremoving addingsoftware packagesA graphical user interface program (see the admintool(1M) man page) swmtool commanddescribed graphical user interfaces (GUIs)Software ManagerThe command-line utilities (see the pkgadd(1M) and pkgrm(1M) man pages) pkgrm command pkgadd command command-line utilities, for software package administrationYou can install software on your local system or on a remote system with Admintool (started with the admintool command). The default location for the installation is the local system. swmtool commanddescribed graphical user interfaces (GUIs)Software ManagerUse Admintool to:Look at the software installed on the local systemInstall or remove software on a local systemIf you want to install or remove the software, you must run Admintool as superuser or as a user in the sysadmin group (group 14). You do not need to be superuser to look at the software packages that are already installed on a system.You can use command-line utilities to install, remove, and check the installation of software packages. The commands are: command-line utilities, for software package administrationpkgadd(1M) for installing a package pkgadd commandpkgrm(1M) for removing a package pkgrm commandpkgchk(1M) for checking the installation of a package pkgchk command checkingsoftware package installationpkginfo(1M) for listing the packages installed on a system pkginfo command packagesinformation reporting listingsoftware packages installed information reportingsoftware packages installationsoftware packages packagesinstalling packagesremoving removingsoftware packages remote systemssoftware package administrationThe patchadd(1M) and patchrm(1M) commands are used to install and remove patches from a Solaris 2.x system. You can add one or more patches to a system, client, service or net install image.See patchadd(1M) and patchrm(1M) for more information.A single range of contiguous blocks or a physical subset of a disk is known as a disk partition in the SunOS release 4.x software. In the SunOS release 5.x software, a physical subset of a disk is known as a disk slice. Before you can create a file system on a disk, you must format and divide it into slices. This is usually done when the Solaris release is installed using the Solaris 2.x installation program. See System Administration Guide if you need to install and format a disk after installation. file systemsdisk slices and partitions disk slicesNote - In some Solaris documentation, Solaris slices are still referred to as "partitions". The Solaris 2.x documentation distinguishes between fdisk partitions (for Intel systems) and the divisions within an fdisk partition, referred to interchangeably as slices or partitions.See System Administration Guide for information about Solaris fdisk partitions.A slice can be used as a raw device for swap space or to hold one and only one UFS file system, unless you are using a product like Solstice(TM) DiskSuite(TM). Table 2-1 describes how disk slices can be set up on each Solaris 2.x platform.Table 2-1 SPARCIntel-basedThe whole disk is devoted to the Solaris operating environment.The disk is divided into four fdisk partitions, one per operating environment.The disk is divided into eight slices, numbered 0-7.The Solaris fdisk partition is divided into 10 slices, numbered 0-9. Only 0-7 can be used to store user data.See System Administration Guide for a description of customary disk slice assignments for each platform.You create a UFS file system on a disk slice, which is divided into one or more areas called cylinder groups. A cylinder group is composed of one or more consecutive disk cylinders (the set of tracks on a group of platters that have the same radial distance from the center of the platter). See System Administration Guide for a complete description of disk geometry. Unix file systems (UFS)cylinder groups and file systemscylinder groups and cylinder groupsA cylinder group map is created for each cylinder group. The cylinder group map records the block usage and available blocks. cylinder group maps Figure 2-1 shows the relationship between disk slices and cylinder groups.

Figure 2-1

SunOS release 5.6 device names make it easier to infer certain device characteristics from a device name. SunOS release 4.x systems convey type rather than device attributes, which makes it difficult for programs and scripts to derive necessary information about devices. SunOS release 5.6 conventions are slightly different from AT&T SVR4 device names because SunOS release 5.6 allows only eight user-configurable slices on a disk. SunOS release 5.6device naming SunOS release 4.xdevice naming and namesdevicechanges in device namingchanges in device administrationnaming conventions AT&T systemsdevice namingIn addition, special device files are now stored in the hierarchical /devices directory, with symbolic links to the hierarchical /dev directory, which is used by administrators and users to access devices. The /dev directory contains subdirectories, such as /dev/dsk/*, used to access disk devices, and /dev/rdsk/*, used to access raw disk devices. For more information, see "Device Naming Conventions". For discussions on device naming conventions, see "Device Naming From a Developer's Perspective". /dev directorychanges inSunOS release 5.6 and SunOS release 4.x file systems are similar, but there are changes in the locations and names of system directories and files. There are also new file systems, new pseudo file systems, and one directory is not used. SunOS release 5.6file systems"File System Changes", describes file system changes. System Administration Guide describes file system concepts and administration in detail.Some of the changes to file system locations and names are: The /dev directory has changed from a flat directory to a hierarchical one.The /etc directory contains system configuration information. Several files and subdirectories have been added, removed, or changed.The /etc/vfstab tab file replaces /etc/fstab.The /etc/lp directory replaces /etc/printcap.The SunOS release 5.6 /sbin directory contains the rc scripts used to alter system run levels as well as the rcs script used to initialize the system prior to mounting file systems. The SunOS release 5.6 /usr directory contains sharable files and executables provided by the system. The /var directory contains files that change sizes during normal operation. Several files and subdirectories in the /var directory have been added, removed, or changed.The /var/mail directory replaces /var/spool/mail.The /sys directory is no longer needed because the kernel is dynamically loaded. /sysThe terminfo database replaces termcap.The SunOS release 5.6 core kernel is called genunix, and the kernel modules are stored in the /kernel, /usr/kernel, /platform, and /usr/platform directories. unix kernel name SunOS release 5.6kernel name in nameskernel name kernelname of kernelmoduleslocation kernel unix kernelmodules /kernelPseudo file system types are logical groupings of files that reside in disk-based systems. The TFS pseudo file system is not included in the SunOS release 5.6 software.The SunOS release 5.6 pseudo file systems are:CACHEFS pseudo file system - can be used to improve performance of slow devices such as a CD-ROM drive.PROCFS pseudo file system - resides in memory and contains a list of active processes, by process number, in the /proc directory. See the proc(4) man page.FDFS pseudo file system - provides explicit names for opening files using file descriptors.FIFOFS pseudo file system - contains pipe files that give processes common access to data. NAMEFS pseudo file system - used mostly by STREAMS for dynamic mounts of file descriptors on top of files.SWAPFS pseudo file system - the default swap device when the system boots, or you create additional swap space.The following file systems are included in the SunOS release 5.6 directory structure:The optional /opt file system, which can be used to store third-party or unbundled software. If /opt is not a separate file system, it may be a symbolic link to /usr/opt.The /vol file system, which provides the default file system for the Volume Management daemon, vold(1M). See the volfs(7) man page. SunOS release 5.6file systemsSupport for the RFS file system type has been removed.Unlike in the SunOS release 4.x software, the SunOS release 5.6 kernel is dynamically configured. This means that you no longer need to rebuild it manually when you make changes to the system configuration. SunOS release 5.6kernel configuration kerneldynamic kernelconfiguration dynamic kerneldefined configurationkernelStarting with release 5.5 of the SunOS software, the kernel and its modules were separated into platform-independent and platform-dependent objects. The platform-independent kernel consists of a small static core, called /kernel/genunix, and its dynamically loadable kernel modules are stored in the /kernel and /usr/kernel directories if they are platform independent, and /platform and /usr/platform if they are platform independent. See System Administration Guide for a description of the platform-dependent directories and their contents.Drivers, file systems, STREAMS module, and other modules are loaded automatically as needed, either at boot time or at run time. These modules are unloaded when they are no longer in use. The modinfo(1M) command provides information about the modules currently loaded on a system.The modload(1M) and modunload(1M) commands are still available in this release but they perform differently. These commands have more limited usage, and are no longer sufficient to correctly install a loadable driver onto the system. The modunload(1M) command is similar to the SunOS release 4.x command, but it includes the capability to unload all unloadable (and not busy) modules, as the following example illustrates. modload command loading device drivers kernelmodulesunloading kernelmodulesloading device administrationunloading devices device administrationloading devices modunload command unloading, device drivers# modunload -i 0Chapter 18, System and Device Configuration, discusses these topics in more detail.The contents of the kernel, which were formerly in a single file, /vmunix, are now contained in modules in a platform-independent and platform-dependent directory hierarchy. By default, the directory hierarchy is: /vmunix file /kernel directory kernelmoduleslocation kernellayout directorieskernel module/kernel/usr/kernel/platform/usr/platformThe directory search path for modules can be set by the moddir variable in the /etc/system file. Typically, /kernel/genunix is the first portion of the kernel to be loaded. See system(4) and kernel(1M) for more information. search pathskernel modules moddir variable kernelmodulesdirectory search path /etc/system filemoddir variableA new version of the automounter, called AutoFS, has been included. In the SunOS 4.X releases, the automounter mounted everything under /tmp_mnt and used symbolic links to redirect the lookups. AutoFS allows for file systems to be mounted in place (for instance, /home). file systemsmountingautomounting file systemsmounting file systemsautomounting directoriesremote, automounting automounting file systemsremoteautomounting mountingfile systems mountingfile systemsautomounting NFSautomounting of file systems shared through remote file systemsautomounting SunOS release 5.6automounting autofs programIn SunOS 4.X, the maps for the automounter were named auto.master and auto.home. For Solaris 2.6, these maps have been renamed to auto_master, auto_home, and so on. The NIS+ name service, which is included with the release, requires this change. A default copy of these maps is included in the release, so that the AutoFS service is started when the system is booted. The SunOS 4.X releases did not include the maps, so additional installation steps were required. The Solaris 2.6 release provides the ability to select the name service that is being used through /etc/nsswitch.conf. The automount entry can be changed to select local files, NIS+, NIS or some combination of these.Earlier releases supported a home directory naming convention like: /home/server/login. With the AutoFS maps it is much easier to use /home/login for each entry. This new naming convention also provides for location independence. The old convention can still be used, but once a transition to using the AutoFS maps has been made, it will be easier to administer the shorter paths.The following paths were reserved for use by AutoFS:/net - for mounting file systems from a known host/home - for mounting the home directory of a known user/xfn - for mounting file systems which support the X/Open XFN standardOn home directory servers, the actual home directories should be moved to /export/home rather than /home, so that they do not conflict with the automounter directory structure. This also means that you cannot mount file systems on /home while the automounter is running.The AutoFS software now has two programs. The first program is automount that runs at boot time to establish AutoFS mount points. This command can also be run anytime by superuser to change the mount points. The second command is automountd which is a stateless daemon which answers AutoFS file system mount and unmount requests. These two programs replace the 4.1.X automount daemon.The automount daemon is now fully multi-threaded. Multiple automatic mount requests can be serviced concurrently, which makes AutoFS more reliable. In short, one mount request could block connecting to a slow server, while a second request is processed without waiting.The Solaris 2.6 release supports browsability of indirect AutoFS maps. All mountable entries under an AutoFS mount point (for example, /home) are now visible without the overhead of mounting them first.Also provided is improved on-demand automounting of hierarchically related file systems. Previous releases would automount an entire set of file systems if they were hierarchically related (for example, /net/server) even if only one of the file systems was referenced. The file system that is referenced will be dynamically mounted without mounting all of the other file systems in the hierarchy. Other file systems will be mounted when they are individually referenced.See "Mounting File Systems and autofs"for more detailed information. Also, NFS Administration Guide describes how to use AutoFS.The version of sendmail that is included on the release is Version 8 compatible. The new version fixes some security holes and includes several improvements to Version 5. Several extensions to the standard BSD release have been added, including name service switch and NIS+ support. mail administration sendmail commandTo further support NIS+, a new command, aliasadm, has been included. The command will aid in the administration of NIS+ alias lists. aliasadm commandThe mailbox spooling directory has been moved from /var/spool/mail to /var/mail. A new directory, /var/mail/:saved, is used for creating locks and temporary files by the mailx program. Also, the mail configuration files are now all located in /etc/mail. The new directory includes the aliases and the sendmail.cf files. mailbox spooling directory mailx programThe mailbox locking mechanism has been enhanced so that Solaris 2.6 clients can safely mount mailboxes from both Solaris 2.X and SunOS 4.X mail servers. This enhancement eases administration of mail, especially in large sites. In the Solaris 2.6 release, /usr/bin/mailx supersedes /usr/ucb/mail. The mailx program has been enhanced to behave the same way as the SunOS 4.x version of /usr/ucb/mail. The /usr/ucb/mail file is now a symbolic link to /usr/bin/mailx.In SunOS 4.X releases, a program called sendmail.mx was used in DNS sites to access mail exchange records. The new version of sendmail includes the needed functionality and can be configured through /etc/nsswitch.conf.Mail Administration Guide describes the administration of sendmail.One of the major changes between SunOS release 4.x and SunOS release 5.6 that affects system administration is the availability of Admintool to perform basic system administration tasks. This tool employs a graphical user interface to simplify tasks, such as managing users, hosts, printers, and serial devices, on local desktop systems. SunOS release 5.6admintool graphical user interfaces (GUIs)admintool admintool command admintooldescribedAdmintool applications enable you to manage the following tasks on a local system:System database files such as aliases and netmasksUser account and group information, including tasks such as adding users and groups, modifying password aging features, and removing user account informationPrinter setup for local and remote printersTerminal and modem setupPackage managementUsing a graphical user interface (GUI) like Admintool to perform administration tasks has the following benefits:It is faster than using numerous SunOS commands to perform the same tasksSystem files are updated automatically without the risk of making editing errorsThe application programs interact with appropriate system daemons and notify you when the two are out of syncNote - You do not need to be root to start Admintool but you do need to be a member in the sysadmin group (GID=14). Use the groups(1) command to display your group membership.To display Admintool, type the following command in any window. SunOS release 5.6admintool graphical user interfaces (GUIs)admintool admintool command admintooldescribed$ admintool &NIS+ is the preferred network information service for Solaris networks. Solaris networks can also use NIS either as an alternative to NIS+ or as a supplement to NIS+. NIS+ (Network Information Services Plus)describedNIS+ is a name service built on top of the ONC transport-independent remote procedure call (RPC) interface. NIS+ has significant benefits compared to NIS in the areas of security, performance, scalability, and administration. Some of the advantages of using NIS+ are:NIS+ shares data with the NIS environments, allowing a smooth migration.Domains are hierarchical; you can create subdomains.You can use the name service switch (/etc/nsswitch.conf) to set which name service a system will try to use first: NIS+, NIS, /etc, or DNS. Name Service SwitchYou can use AdminSuite to make changes to NIS+ tables for adding, modifying, deleting, and searching for information. removingNIS+ information NIS+ (Network Information Services Plus)updating NIS+ (Network Information Services Plus)searching changingNIS+ information addingNIS+ information searchingNIS+ tablesNIS+ enables you to create and maintain an enterprise-wide name service, even across geographically separated sites connected by WAN links.You can use the NIS+ backup and restore feature to quickly and easily preserve your name space data set. This feature can also be used to quickly bring additional replica servers on line.See Chapter 13, Using Name Services, in this guide and NIS+ Transition Guide and NFS Administration Guide for more information.The print management commands have changed between the SunOS release 4.x and Solaris 2.6 operating environments. In the Solaris 2.6 operating environment, you can use command-line procedures or Admintool to set up printers, and you can use administrative commands or the PrintTool to control print jobs. SunOS release 5.6print subsystem printerscommandschanges in printerschanges in print subsystemdescribedSee Chapter 11, Managing Printers, Terminals, and Modems, and System Administration Guide for more information.Users can accomplish the same basic tasks using PrintTool or commands in a shell. PrintToolPrintTool is a software tool available in the Solaris 2.6 user environment. It provides a graphical user interface within OpenWindows or CDE through which a user can monitor printers and monitor and cancel print jobs. OpenWindowsPrintToolThe following list summarizes command changes: printerscommandschanges inlp(1) replaces lpr lpr command lp command /etc/printcap database, replacement of databasesprintcaplpstat(1) replaces lpq lpstat command lpq commandcancel(1) replaces lprm printerscanceling print jobs lprm command cancel commandtroff(1) requires a printer name troff commandchanges inTEX, pscat (C/A/T), and raster image filters are not available in the Solaris 2.6 environment TEX filters raster image filters image filters, unsupported pscat (C/A/T) filters filters, image, unsupportedThe lp service consists of several daemons, or processes, that monitor system work, a hierarchy of configuration files in the /etc/lp directory, and a set of administrative commands. /etc/lp directory print subsystemdescribed SunOS release 5.6print subsystemThe Service Access Facility (SAF) is the tool used for administering terminals, modems, and other network devices. In particular, the SAF enables you to: networksservice administration port monitorsadministering port monitor services, administering network devices, administering modems, managing addingnetwork devices removingnetwork devices serial ports, controlling Service Access Facility (SAF) Service Access Facility (SAF)described terminals, managingAdd and administer ttymon and listen port monitors (using the sacadm command) ttymon port monitor sacadm command listen port monitorAdd and administer ttymon port monitor services (using the pmadm and ttyadm commands) ttyadm command pmadm commandAdd and administer listen port monitor services (using the pmadm and nlsadmin commands) nlsadmin commandAdminister and troubleshoot TTY devices TTY devices, administering and troubleshooting troubleshootingTTY devicesAdminister and troubleshoot incoming network requests for printing service troubleshootingprinting service requests from network printersnetwork requests for services, administering and troubleshootingAdminister and troubleshoot the Service Access Controller (using the sacadm command) troubleshootingService Access Controller (SAC)The SAF is an open systems solution that controls access to system and network resources through TTY devices and local-area networks (LANs). The SAF offers well-defined interfaces so you can easily add new features and configure existing ones.The SAF is not a program. It is a hierarchy of background processes and administrative commands. The top-level SAF program is the SAC. The SAC controls port monitors that you administer through the sacadm command. Each port monitor can manage one or more ports. Service Access Facility (SAF)Service Access Controller (SAC) and Service Access Controller (SAC) SAC (Service Access Controller)You administer the services associated with ports through the pmadm command. While services provided through SAC may differ from network to network, SAC and the administrative programs sacadm and pmadm are not tailored to network types.Table 2-2 illustrates the SAF control hierarchy. The sacadm command is used to administer the SAC, which controls the ttymon and listen port monitors. ttymon port monitor Service Access Facility (SAF)commands sacadm command listen port monitorTable 2-2 FunctionProgramDescriptionOverall administrationsacadmCommand for adding and removing port monitorsService Access ControllersacSAF's master program SAC (Service Access Controller) Service Access Controller (SAC) Service Access Facility (SAF)Service Access Controller (SAC) andPort monitors logins, administeringttymon listenMonitors serial port login requestsMonitors requests for network servicesPort monitor service pmadm commandadministratorpmadmControls port monitor servicesServices remote procedure calls, administeringlogins, remote procedure calls, and so onServices to which SAF provides accessThe services of ttymon and listen are in turn controlled by pmadm. One instance of ttymon can service multiple ports and one instance of listen can provide multiple services on a network interface.See Chapter 11, Managing Printers, Terminals, and Modems for more information.Beginning with the Solaris 2.2 software, a new layer of software manages CD-ROM and diskette devices: Volume Management. This software automates the interaction between you and your CDs and diskettes. Volume Managementoverview diskette devices, managing device administrationVolume Management for CD-ROM devicesmanagingCDE OpenWindows File Manager has been modified to use Volume Management to provide immediate user access to CDs and diskettes with file systems on them. See Solaris User's Guide for more information on File Manager's new features. OpenWindowsFile Manager changes File ManagerThere are also several new commands to help you administer Volume Management on your system.For more information, see "Using Volume Management " in Chapter 7, Device Administration. Solaris 2.6 operating environmentoverview of major changes SunOS release 4.xoverview of major changes in Solaris 2.6Chapter 33. Converting a SunOS 4.x System to the Solaris 2.6 EnvironmentConverting a SunOS 4.x system to the Solaris 2.6 environment is a three-phase process that includes pre-installation (backing up data), installing the Solaris environment, and post-installation (restoring data). This chapter provides information about the pre-installation and post-installation phases for a single system or an entire network. See Chapter 10, Setting Up a Solaris 2.6 Server to Support SunOS Release 4.x Diskless/Dataless Clients, for information about creating an environment that serves both Solaris 2.6 and SunOS release 4.x clients."What's New About Installing""What to Do Before You Install Solaris Software""Backing Up Files and File Systems Before You Install""Installing Solaris Software""Restoring Files and File Systems After You Install "installationoverviewinstallationpre-installation phaseoverviewinstallationpost-installation phaseinstallationinstall phaseinstallationThe Solaris 2.6 environment introduces a number of changes in the way you install software on systems, which makes it different than installing the SunOS 4.x software. These include: Solaris 2.6 operating environmentinstallation features installationnew features configurationnew featuresThe Solaris 2.6 software is distributed on compact disc (CD) only. This means you must have access to a CD-ROM drive before you can install the software. For systems without local CD-ROM drives, you can set up a system that has a CD-ROM drive to act as an install server on the network. For more information about network installations, see Solaris Advanced Installation Guide.CD-ROM devicesSolaris 2.6 requirement forThe Solaris 2.6 software is bundled into modules called packages. You can select which packages to install on your system and control the amount of space each installation requires. packagesadvantagesAlso, related packages are grouped into clusters. This means that you can select a cluster to install without having to select each package separately. clustersSolaris 2.6 installation also provides a set of software groups, which are groups of packages and clusters for typical users (for example, there is an end-user software group). You can select a software group to get systems running without selecting individual packages and clusters. This can be useful when you are first installing the Solaris 2.6 software in a limited environment for testing. You can add or remove packages later as you gain more experience with the system. software groupsThe Solaris 2.6 environment includes architecture-specific kernels rather than the generic kernel configuration provided in earlier SunOS software releases. You will find the installed kernel in /kernel instead of /vmunix. kernelarchitecture-specific /vmunix file /unix directory /kernel/unix directory kernelmoduleslocation configurationnew features installationnew featuresThe Solaris 2.6 installation program guides you step-by-step through the installation process.The Solaris 2.6 environment provides custom JumpStart(TM) technology to automate installations. This can save you time when you need to install many systems. For more information, see Solaris Advanced Installation Guide.Converting a SunOS 4.x system to the Solaris 2.6 software involves more than just running the Solaris installation program and loading the software. Usually, there is data on the SunOS 4.x system that needs to be transferred to a Solaris 2.6 system. This data may be full file systems, such as /home, or locally customized system files, such as /etc/hosts or /etc/passwd. installationpre-installation phase data transfersavingNo matter how you plan to handle the data transfer, you should back up all disk partitions by doing full dumps before you begin the installation process. Because the device naming conventions are different in the Solaris 2.6 operating environment, you might inadvertently choose the wrong disk when you install the Solaris 2.6 software. Backing up the file systems before you begin the installation procedure offers some protection should this occur. For information about device naming conventions, see "Device Naming Conventions". SunOS release 4.xbacking up file systems installationpre-installation phasebacking up file systems filesbacking up file systemsbacking up backing upinstallation andNote about file system formats:If the Solaris 2.6 Extended Fundamental Types (EFT) are not used, the SunOS release 4.x file system format is upwardly compatible with, and in some cases identical to that used in, the software. file systemschanges informat Extended Fundamental Types (EFT) EFT (Extended Fundamental Types)If you are running SunOS 4.1.1 software with QuickCheck or Backup Copilot(TM) utilities installed or the SunOS 4.1.2 software, the file system formats are identical. SunOS release 4.xQuickCheck SunOS release 4.xBackup Copilot QuickCheck Backup CoPilotIf you are running SunOS 4.1.1 software without QuickCheck or Backup Copilot utilities, SunOS 4.0.x, or SunOS 4.1 software, the file systems are upwardly and backwardly compatible, although not identical in all cases. Before you begin the installation process, you should save a hard copy of the system's existing disk partitions. It can serve as a reference for many decisions that are made about configuring the Solaris 2.6 system. The following procedure is one way to obtain the disk partition information. SunOS release 4.xsaving disk partition information savingdisk partition information installationpre-installation phasesaving disk partition information disk devicespartition information, savingObtain the names of the disks attached to the system. namesdisks attached to system disk devicesnames of disks attached to systemTo obtain the names of the disks attached to the system, use the format(8) command. format commandSave the disk partition information. To obtain the partition information encoded on each disk, use the dkinfo(8) command. You can pipe the output to a printer or to a file that you can save to another system. dkinfo commandNote - Using the previous command provides you with information only on the configured partitions. All nonconfigured partitions are displayed with the message: "No such device or address." SunOS release 4.xsaving disk partition information savingdisk partition information disk devicespartition information, saving installationpre-installation phasesaving disk partition informationSunOS release 4.xsaving file system informationsavingfile system informationinstallationpre-installation phasesaving file system informationfile systemssaving informationThe mappings between file system names (for example, /usr, /home) and device names (for example, /dev/sd0g) reside in the configuration file /etc/fstab. Before proceeding, you should make a printed copy of the /etc/fstab file to help you construct the Solaris 2.6 file. /etc/fstab filedescribedUse this section only if you are upgrading a system running the SPARCserver(TM) Manager or Solstice DiskSuite unbundled products. (These products are used to mirror, concatenate, or stripe multiple disks.) SPARCServer Manager, installation and savingmetadevice configuration information Solstice DiskSuite, installation and metadevice configuration information, saving installationpre-installation phasesaving metadevice configuration information SunOS release 4.xsaving metadevice configuration informationTo upgrade your system without this product, you have to modify your multiple-partition configurations to use single partitions. In particular, a concatenated or striped file system must be reorganized onto a single disk, and partitions and mirrors can no longer be used. If the system is running SPARCserver Manager or Solstice DiskSuite utilities, you should save the metadevice configuration information before installing Solaris 2.6 software. This enables you to recover the state of the metadevices when you install Solaris 2.6 software, and serves as a reference as you construct the list of disks attached to your system. Use the metastat(8) command to save information, as in the following example. metastat command# /etc/metastat -p | lprSave the output of the metadb(8) command. metadb commandFor example.# /etc/metadb -i | lprThe output of metadb tells you the state database configuration information. This information is necessary to reconstruct the state databases if you reinstall the Solstice DiskSuite product. installationpre-installation phasesaving metadevice configuration information metadevice configuration information, saving Solstice DiskSuite, installation and savingmetadevice configuration information SPARCserver Manager, installation and SunOS release 4.xsaving metadevice configuration informationYou should create a list of the SunOS 4.x files and file systems that you want to back up and restore after installing Solaris 2.6 software.Make a list of all the system components in the existing SunOS release 4.x environment and decide which are critical to the user's system. Consider: installationpre-installation phaselisting system components to saveLocally developed applicationsAny unbundled software productsThird-party applicationsThird-party peripheral devices and drivers (8 mm tape drives and SBus cards, for example)Use the following guidelines to make the list of file systems to save: listingfile systems to save installationpre-installation phaselisting files and file systems to save fileslisting files to save file systemslisting systems to saveAs a general rule, do not transfer file systems containing "system" files (for example, the /usr or / file systems) in their entirety. /usr file systemtransitioning /tmp file system (TMPFS)transitioning root file system (/) / file systemDo not save temporary file systems, such as /tmp. temporary file systemstransitioningDo extract and transfer the data files that have changed locally or those on which the server depends for administrative data, such as some /etc files (for example, /etc/hosts), exported file systems (use the exportfs command to list them), and /tftpboot directory, which you should save as a safety precaution. /tftpboot directory shared file systemstransitioningDo completely preserve file systems containing only locally generated data, such as spool and user home directories. Save file systems that contain information about clients if you are migrating a server for SunOS release 4.x clients. Typically, /export would be such a file.There are a number of SunOS 4.x system configuration files that can be merged or converted for the Solaris platform. Use the example list that follows to help select the system configuration files you want to back up.Note - The list contains suggestions. You should study the items carefully and add to or delete from the list depending on the configuration at your site. For example, if you have special files in directories from third-party software vendors, you may need to save them.If the system is an NIS master server, you should save all the files that reside in the NIS master directory (for example, /etc). Additionally, save any other master files that you added to NIS. The suggestions for files to back up include: NIS (Network Information Services)master serverssaving system data for./.cshrc./.profile./.login./.logout./.rhosts./etc (if the system is an NIS client or has no name service)./var/spool/calendar./var/spool/cron./var/spool/uucp./var/nis (if the system is an NIS master server)Boot programs in./tftpbootMake a list of how much disk space each file system that you want to move to the Solaris 2.6 upgrade, uses. Refer to this list when installing the Solaris 2.6 software, since you can partition disk space for your SunOS 4.x file systems when running the Solaris 2.6 installation program.If you are converting a network of SunOS 4.x systems to the Solaris 2.6 software, decide the order of the systems to convert to maximize convenience for the users. For example, you might want to convert all client systems before you convert any servers. The first system you convert should be a standalone system with a locally attached CD-ROM drive. prioritizing, Solaris 2.6 installation for networks networksorder of installing Solaris 2.6 on installationpre-installation phasenetwork installation orderFor a while, you will probably manage a network consisting of both SunOS 4.x and Solaris 2.6 systems, and part of your planning should involve determining priorities. For example, you may want to convert one domain and use it for system administration testing and for porting internally developed applications before you convert the entire network environment.Once you decide which files or file systems you need to back up from the SunOS 4.x system, you can use the standard commands and procedures given in the SunOS 4.x documentation to do backups. The command you use depends on whether the tape drive is local or remote. SunOS release 4.xbacking up file systemsNo matter how you plan to handle the data transfer, it is still a good idea to back up all disk partitions by doing full dumps before you begin the installation process. installationpre-installation phasebacking up file systems filesbacking up file systemsbacking up backing upinstallation andInstall the Solaris 2.6 software on the server or standalone system using the software installation procedures given in Installation Instructions for Solaris 2.6 (SPARC Platform Edition) or Installation Instructions for Solaris 2.6 (Intel Platform Edition).installationinstall phaseThe Solaris 2.6 installation program has a preserve screen that enables you to preserve existing file systems during installation. This is a good way to preserve any SunOS 4.x file systems so you don't have to restore them. If you cannot preserve a SunOS 4.x file system or you choose not to (because you want to change how the system's disks are partitioned), you should create new file systems with sufficient disk space for the SunOS 4.x file system that you want to restore (using the disk space requirements you recorded earlier). Then you can restore the SunOS 4.x file systems into the new file systems after Solaris is installed.This section describes issues related to restoring SunOS 4.x files and file systems you backed up before installing the Solaris 2.6 software. restoring files and file systems installationpost-installation phase data transferrestoringYou can restore the SunOS 4.x file systems that you could not or chose not to preserve into the new file systems you created during the Solaris 2.6 installation. For information about backup and restore procedures, see System Administration Guide.Note - Before proceeding make sure that the target slice is large enough to accommodate the file system being restored.Restore any SunOS 4.x user files that you backed up, and copy them to the new system.First, you must restore the SunOS 4.x system configuration files to a temporary directory on the Solaris 2.6 system. After the information is back on the system in the temporary directory, you need to make it available in the Solaris 2.6 operating environment. Some of the data can just be merged into the files, while some types of data must be converted to new formats.The system's configuration defines which files you need to work with. Complete the restore by merging or converting files as follows: Systems with no name service: If the system has no name service, merge or convert all the relevant system files located in /etc and /var.Systems that are NIS clients: If the system is an NIS client, merge or convert only the local system configuration files located in /etc and /var that are not provided via the NIS name service. NIS (Network Information Services)clients, restoring system data forSystems that are NIS master servers: If the system is an NIS master server, merge or convert all the files that reside in the NIS master directory (for example, /etc). Additionally, update other local configuration files in /etc and /var. NIS (Network Information Services)master serversrestoring system data forTo make data from any of the following files available, merge the changes into the Solaris 2.6 version of the same file. Note, however, that not all of these files were modified on the SunOS 4.x system. Identify files that were changed on the SunOS 4.x system and merge these only. As you read the list, note that some of the file names are slightly different. For example, /etc/auto.* files are now /etc/auto_*. merging files filesmerging file systemschanges innames filesnames namesfileThe following is an example list of the SunOS release 4.x files backed up using the instructions in the first part of this chapter. These files are candidates for merging into the Solaris 2.6 operating environment. See Appendix D, System Files Reference Table, to examine SunOS release 4.x files for changes. All automounter maps, including /etc/auto.master and any others /etc/aliases/etc/bootparams/etc/ethers/etc/hosts/etc/format.dat/etc/inetd.conf/etc/netmasks/etc/networks/etc/protocols/etc/publickey/etc/rpc/etc/services/etc/hosts.equiv/etc/remote/.cshrc/.profile/.login/.logout/.rhosts/var/spool/cron/var/spool/mail/var/spool/calendar/var/spool/uucp filesmerging merging filesMany system files, such as the /etc/fstab file, have been replaced and do not exist under the Solaris 2.6 operating environment. Information from these files must be extracted and manually converted in the Solaris 2.6 environment. See Appendix D, System Files Reference Table, to examine SunOS release 4.x files for changes. filesconverting /etc/vfstab filemerging /etc/fstab file into /etc/fstab file/etc/vfstab vs. convertingfilesCaution - Do not restore operating system executable files (such as system commands in /usr/bin) from the SunOS release 4.x system to your system after installing the Solaris 2.6 software.You must change the following files before merging the data onto the Solaris 2.6 system: installation/etc/uucp - There have been some changes to the UUCP system. The Config, Grades, and Limits files are new in the Solaris 2.6 operating environment. The files Devconfig, Devices, Dialcodes, Dialers, Permissions, Poll, Sysfiles, and systems are the same in the Solaris 2.6 operating environment as they were in the SunOS release 4.x software. These files can be merged together. There are also several SunOS release 4.x files that are not used in the Solaris 2.6 operating environment. UUCP (Unix-to-Unix Copy) Unix-to-Unix Copy (UUCP) /etc/uucp directory/etc/group - The basic format of this file is the same as it was in the SunOS 4.1 and SunOS 4.1.x releases. However, previous releases used a group entry beginning with a plus sign (+) or minus sign (-) to selectively incorporate entries from NIS maps for group. See the group(4) man page if that compatibility is needed under the Solaris 2.6 operating environment. group system file /etc/group file/etc/netgroup - There is no /etc/netgroup file in the SunOS release 5.6 environment. netgroup system file /etc/netgroup file/etc/exports - File systems to be shared on the network under the Solaris 2.6 operating environment use the /etc/dfs/dfstab file instead of /etc/exports. The format of entries in this file follows. shared file systemstransitioning exports file /etc/exports file /etc/dfs/dfstab fileshare -F fstype -o options -d "text" pathname resourceSee the dfstab(4) man page for additional information./etc/fstab - File systems to be mounted under the Solaris 2.6 operating environment use the /etc/vfstab file instead of /etc/fstab. The format of entries in the /etc/vfstab file follows. mountingfile systems file systemsmounting /etc/vfstab filemerging /etc/fstab file into /etc/fstab file/etc/vfstab vs.dev raw_dev mnt_pt fs_type fsck_pass auto_mnt mnt_optionRefer to the vfstab(4) man page for additional information./etc/passwd - The format of the passwd file is the same as that under the SunOS release 4.x software. However, user passwords are now stored in the /etc/shadow file. Refer to the passwd(4) and shadow(4) man pages for additional information. passwordslocation of passwd file /etc/passwd file shadow file /etc/shadow file/etc/sendmail.cf - The format of sendmail.cf is the same as that under the SunOS release 4.x structure. The location of the file is now /etc/mail/sendmail.cf. sendmail.cf file /etc/sendmail.cf file /etc/mail/sendmail.cf file/etc/ttytab - Under the SunOS release 4.x system, ttytab was used to control serial ports and the characteristics of the terminals on those serial lines. Under the Solaris 2.6 operating environment, the Service Access Facility is used to configure this capability. ttytab system file serial ports, controlling /etc/ttytab file/etc/printcap - Under the Solaris 2.6 operating environment, printers are configured using the SunOS release 5.6 LP print service. See System Administration Guide for additional information. printersconfiguration /etc/printcap database, replacement of device configuration databasesprintcap filesconverting convertingfiles system configurationrestoring data SunOS release 4.xrestoring system data restoringSunOS release 4.x system data restoring installationpost-installation phase installation data transferrestoringChapter 44. Using the Compatibility PackagesThe SunOS release 5.6 software is neither source nor binary compatible with the SunOS release 4.x software. This means that SunOS release 4.x programs and user applications based on those releases may not run correctly under the Solaris 2.6 operating environment. Compatibility packages make it possible for these programs to run on a Solaris 2.6 system.This chapter briefly discusses two compatibility packages: the SunOS/BSD Source Compatibility Package and the Binary Compatibility Package. These packages make the transition easier by enabling you to use SunOS release 4.x commands and applications while your environment and applications migrate to the Solaris 2.6 operating environment."Why Port Applications?""SunOS/BSD Source Compatibility Package ""Binary Compatibility Package "Some SunOS release 4.x commands are not available in the Solaris 2.6 operating environment. Others exist, but have changed. For information about changes to SunOS release 4.x commands in the Solaris 2.6 operating environment, see Appendix A, Commands Reference Table. SunOS release 5.6compatibility packagesSunOS release 4.xwork environment, using with Solaris 2.6SunOS release 4.xcompatibility with SunOS release 5.6packagescompatibility packagescompatibility packagescompatibilitySunOS release 4.x with release 5.6user environment administrationSunOS 4.x work environment used with Solaris 2.6tools (developer)Binary Compatibility PackageSunOS/BSD Source Compatibility PackageBSD Source Compatibility PackageBinary Compatibility PackageSunOS release 5.6command changesSunOS release 4.xcommand changescommandschanges inAlthough the SunOS Binary Compatibility Package and the SunOS/BSD Source Compatibility Package allow you to use applications as they are, you should port applications as soon as possible. Long-term reliance on the compatibility packages is not advised for the following reasons: porting applications, reasons for applicationsporting, reasons forThe application's performance is reduced.You will not be able to take advantage of the Solaris 2.6 operating environment's increased range of operations and portability.Compatibility packages are temporary aids to help sites through the transition.The SunOS BSD/Source Compatibility Package is an optional package available with the Solaris 2.6 operating environment. The package contains a collection of SunOS release 4.x and BSD commands, library routines, and header files otherwise not available with the Solaris 2.6 operating environment. The Binary Compatibility Package must be installed in order to use the SunOS/BSD Source Compatibility Package. SunOS/BSD Source Compatibility Package BSD Source Compatibility PackageThe interfaces in the SunOS/BSD Source Compatibility Package are installed in the /usr/ucb directory, thereby avoiding conflicts with existing SunOS release 5.6 interfaces. These interfaces provide a familiar SunOS environment while your environment and applications are migrating to the SunOS release 5.6 software. To use these interfaces, you must either specify the full path name or modify your PATH environment variable. When modifying your PATH environment variable, note that /usr/ucb should precede /usr/bin. /usr/ucb directoryFor detailed information about the Source Compatibility Package, see Source Compatibility GuideThe Binary Compatibility Package is an optional package available with the Solaris 2.6 operating environment. The package allows existing SunOS release 4.x applications, both statically and dynamically linked, to run under the Solaris 2.6 operating environment without modification or recompilation. It handles most binary interface discrepancies between the two releases transparently. This results in a Solaris 2.6 operating environment where SunOS release 4.x applications can run properly. Binary Compatibility Package tools (developer)Binary Compatibility PackageSee Binary Compatibility Guide for procedures about setting up your environment to access this package. This guide also details the limitations of the Binary Compatibility Package.The Binary Compatibility Package allows most applications to run under the Solaris 2.6 operating environment, making them available for use before they are ported to SunOS release 5.6. With this package, well-behaved application binaries based on SunOS release 4.x system software will run under the SunOS release 5.6 software without modifications or recompilation. The Binary Compatibility Package is intended for end-user environments, not for use as a development environment. All SunOS release 5.6 application development should be done under the base SunOS release 5.6 environment. developersBinary Compatibility Package andChapter 55. Security Security for the Solaris 2.6 operating environment combines several features from SunOS release 4.x and AT&T SVR4 with capabilities added specifically for the new environment. There are also changes in the packaging of some SunOS release 4.x security programs.This chapter describes major differences between SunOS release 4.x and Solaris 2.6 operating environment security, and points out how those changes may affect system administration procedures. System Administration Guide describes the administration and use of these features more fully."Solaris 2.6 Security Features""Password Aging Changes""Automated Security Enhancement Tool (ASET)""Security Options"securityoverviewsystem administratorssecurity proceduresSunOS release 5.6securitysecuritychanges insecurityMost of the security features from SunOS release 4.x systems are also available in the Solaris 2.6 operating environment. These include: securityfeaturesInternet security.rhosts and.rhosts.equiv files .rhosts.equiv files .rhosts filesSecure RPC and NFS NFSsecure RPC, secureNFS Administration Guide documents secure NFS and the .rhosts files. TCP/IP and Data Communications Administration Guide describes administering Internet security. Internet servicessecuritySecurity for local SunOS release 5.6 systems includes storing encrypted passwords in a separate file, controlling login defaults, and restricted shells. Equivalent NIS+ security, described in NIS+ Transition Guide and NFS Administration Guide, controls network-wide access to systems.The subsections below summarize security features under local system control.The SunOS release 5.6 passwd command stores encrypted versions of passwords in a separate file, /etc/shadow, and allows only root access to it. This prevents general access to the encrypted passwords that formerly appeared in the /etc/passwd file, which anyone could read. passwordslocation of /etc/shadow file /etc/passwd file passwd fileThe /etc/shadow file also includes entries that force password aging for individual user login accounts. The mechanism for changing entries to the passwd and shadow files is described in System Administration Guide. shadow file passwordsaging aging passwords passwordschanging changingpasswordsSeveral files that control default system access are stored in the /etc/default directory. These files limit access to specific systems on a network. Table 5-1 summarizes the files in the /etc/default directory. logins, administering /etc/default directory defaultsdirectory forTable 5-1 /etc/default/login root access, defaults login file /etc/default/login fileControls system login policies, including root access. The default is to limit root access to the console./etc/default/passwd passwordsaging passwd file /etc/default/passwd file aging passwordsControls default policy on password aging/etc/default/su su file /etc/default/su file defaultsroot accessControls which root (su) access to the system will be logged and where it will be displayedSystem administrators can use restricted versions of the Korn shell (rksh) and Bourne shell (rsh) to limit the operations allowed for a particular user account. rsh command rksh command login shellsrestricted Korn shellrestricted Bourne shellrestricted securityrestricted shells shellsrestricted /usr/bin/rksh command /usr/bin/rsh command /usr/lib/rsh commandRestricted shells do not allow the following operations:Changing directoriesSetting the $PATH variableSpecifying path or command names beginning with "/"Redirecting output See the ksh and sh man pages for a description of these shells.Note that the restricted shell and the remote shell have the same command name (rsh) with different path names:/usr/lib/rsh is the restricted shell/usr/bin/rsh is the remote shellThe SunOS release 5.6 system features password aging. This feature assigns a limited lifetime to each user password to maintain password secrecy. As a password reaches the end of its life, the password owner is notified and prompted to select a new one. passwordsaging aging passwordsYou can implement password aging using one of the following methods:Method 1 - Use Admintool to manage users if you are running an X-window environment. For information about this method, see Solaris Advanced User's Guide.Method 2 - Use new passwd or nispasswd command options (depending on which name service stores the account). passwd command nispasswd commandA system administrator can also set up password aging.You can change a user password in one of two ways: passwordschanging changingpasswordsMethod 1- Use either passwd or nispasswd, depending on which name service is used to store your account.Method 2 - Use Admintool to manage users if you are running an X-window environment. For information about this method, see Solaris Advanced User's Guide. User Account Manager (Administration Tool)password changes andFor more information on passwd and nispasswd, see the command tables in Appendix D, System Files Reference Table.Access control lists (ACLs), supported in both UFS and NFS, provide greater flexibility in managing file permissions than traditional UNIX file protection. The traditional UNIX file protection provides read, write, and execute permissions for three user classes: owner, group, and other.Using ACLs allows you to define file permissions for the owner, owner's group, others, specific users and groups, and default permissions for each of those categories. For example, you can set up an ACL that defines read permission to a group of users and write permission to only one user in the group. You could not do this with standard UNIX file permissions.The setfacl(1) command sets, adds, modifies, and deletes ACL entries, and the getfacl(1) command displays ACL entries.See System Administration Guide for more information about using ACLs.The Automated Security Enhancement Tool (ASET), available as a separate option with SunOS release 4.x systems, is included with the Solaris 2.6 operating environment. ASET enables you to specify an overall system security level (low, medium, or high) and automatically maintain systems at those levels. This tool can be set up to run on a server and all its clients or on individual clients. securitylevel of securityASET automated security enhancement tool (ASET) ASET (automated security enhancement tool)ASET performs these tasks:Verifies system file permissionsVerifies system file contentsChecks integrity of group file entriesChecks system configuration filesChecks environment files (.profile,.login, and .cshrc)Verifies EEPROM settings to restrict console login accessAllows establishment of a firewall or gateway systemSystem Administration Guide describes ASET setup and monitoring in detail. ASET (automated security enhancement tool) automated security enhancement tool (ASET) securityASET securitylevel ofCurrently available bundled security options are Kerberos security, the SunSHIELD(TM) package, and Pluggable Authentication Module (PAM). securityunbundledThe Solaris 2.6 operating environment includes support for Kerberos V4 authentication for secure RPC. (Kerberos source code and administrative utilities are available from MIT.) Included in this release are: securityKerberos RPC, secure Kerberos securityClient applications library that can use KerberosKerberos option to Secure RPCSun's NFS(TM) distributed computing file system application with Kerberos Commands to administer user tickets on the clientSystem Administration Guide describes the client-side utilities. included in the release. NFS Administration Guide describes the use of Kerberos with the NFS application.The Solaris 2.6 release includes the SunSHIELD Basic Security Module (BSM) package. This product provides the security features defined as C2 in the Trusted Computer System Evaluation Criteria (TCSEC). The features provided by the BSM are a security auditing subsystem and a device allocation mechanism. C2 discretionary access control and identification and authentication features are provided in the operating system. securitySunShield SunShield Basic Security Module (BSM)The administration of BSM is included in SunSHIELD Basic Security Module Guide.The Pluggable Authentication Module (PAM) framework enables new authentication technologies to be "plugged-in" without changing commands, such as login, ftp, telnet and so on. The framework enables a system administrator to choose any combination of services to provide authentication. Mechanisms for account, session, and password management can also be "plugged-in" using this framework. securityPAM Pluggable Authentication Module (PAM)System Administration Guide describes the administration of PAM.Chapter 66. User Environment AdministrationThis chapter describes differences in tasks you may perform to set up the local user environment after installing the Solaris 2.6 software."Selecting a Default Shell""Customizing User Environments""Window Systems ""User and Group Administration "" Using Mail""Using Document Tools""Man Page Organization Differences"user environment administrationThe login shell is the command interpreter that runs when you are logged in. The Solaris 2.6 operating environment offers three shells: Korn shell defaultsshell csh command changingshells ksh command C shell Bourne shell login shellsselecting default sh command shellsselecting default user environment administrationdefault shell selection /usr/bin/csh command /usr/bin/ksh command /usr/bin/sh commandBourne shell, the default shell (/bin/sh)C shell (/bin/csh)Korn shell (/bin/ksh) If you use the shell often, you may prefer to use the C shell or the Korn shell because of their interactive capabilities. Failed Cross Reference Format lists the features of all three shells.Table 6-1 FeatureBourneCKornSyntax compatible with shYesNoYesJob controlYesYesYesHistory listNoYesYesCommand-line editingNoYesYesAliasesNoYesYesSingle-character abbreviation for login directoryNoYesYesProtect files from overwriting (noclobber)NoYesYesIgnore Control-D (ignoreeof)NoYesYesEnhanced cdNoYesYesInitialization file separate from .profileNoYesYesLogout fileNoYesNoTo change from one shell to another, use one of the following methods:Method 1 - Edit the information in the last field of the line in the /etc/passwd file that begins with your login name. If this entry is blank or sh, the login shell is the Bourne shell. If the entry is csh, the login shell is the C shell. If the entry is ksh, the login shell is the Korn shell.Method 2 - In a windows environment, use Admintool. See Solaris Advanced User's Guide for information.After you change to a new shell, log out and log in again to activate the shell. /usr/bin/sh command /usr/bin/ksh command /usr/bin/csh command user environment administrationdefault shell selection shellsselecting default sh command login shellsselecting default ksh command defaultsshell csh command changingshells Korn shell C shell Bourne shellThis section describes how to determine which initialization files you can edit to customize the local environment based on your choice of login shell, and where to find them in the SunOS release 5.6 file systems. Set up your environment by editing the variables in the initialization files. The default shell determines which files you need to edit: .profile, .login, or .cshrc. Table 6-2 shows the initialization files for the Bourne, C, and Korn shells. customizinguser environments csh command Korn shell C shell Bourne shell environment initialization filescustomizing user environments filesenvironment initialization ksh command login shellsinitialization files sh command shellsinitialization files /usr/bin/csh command /usr/bin/ksh command /usr/bin/sh command .profile file .login file .cshrc fileTable 6-2 ShellInitialization FilePurposeBourne /etc/profile file/etc/profileDefines system profile at login$HOME/.profile $HOME/.profile fileDefines user's profile at loginC $HOME/.login file /etc/.login file/etc/.loginDefines system environment at login$HOME/.cshrc /local.cshrc file $HOME/.cshrc fileDefines user's environment at login$HOME/.loginDefines user's profile at loginKorn/etc/profileDefines system profile at login$HOME/.profileDefines user's profile at login$HOME/ksh_env $HOME/ fileDefines user's environment at login in the file specified by the ksh_env variableIn this release, the shell initialization-file templates have moved to the /etc/skel directory from /usr/lib, where they were in the SunOS release 4.x software. The template file locations are shown in Failed Cross Reference Format. Copy the template file (or files) for the appropriate default shell to your home directory before you modify it. template files, shell initialization /skel directory /etc/skel directoryTable 6-3 ShellFileBourne /local.profile file/etc/skel/local.profileC /local.login file/etc/skel/local.login/etc/skel/local.cshrcKorn/etc/skel/local.profileFor information on setting up initialization files, see System Administration Guide.The SunOS release 5.6 software can use the old SunOS release 4.x system files and initialization files such as .login, .cshrc, and.profile to re-create the look and feel of the SunOS release 4.x work environment. Many of these SunOS release 4.x files can be converted, or used as they are, and executed easily. user environment administrationSunOS 4.x work environment used with Solaris 2.6 SunOS release 5.6compatibility packages SunOS release 4.xwork environment, using with Solaris 2.6 SunOS release 4.xcompatibility with SunOS release 5.6 compatibilitySunOS release 4.x with release 5.6The installation process in Chapter 3, Converting a SunOS 4.x System to the Solaris 2.6 Environment, explains how to re-create the SunOS release 4.x environment within the Solaris 2.6 operating environment. filesenvironment initialization environment initialization filescustomizing user environments customizinguser environmentsThe Common Desktop Environment (CDE) is the default Solaris 2.6 windowing environment and offers a simple and intuitive interface. See Chapter 14, Solaris Common Desktop Environment, for more information about CDE.The OpenWindows 3.1 software can also be used as your preferred desktop with the Solaris 2.6 environment. If you have been using the OpenWindows 2.0 environment, you will notice that the OpenWindows 3.1 icons have changed and some applications are not compatible with the OpenWindows 3.1 platform. window system, default user environment administrationwindow system defaultswindow system OpenWindowsversion differencesThe OpenWindows Developer's Guide File Chooser (gfm) regular-expression file-pattern matching code (filter_pat) is slightly different from the regular-expression file-pattern matching code in the XView(TM) File Chooser object. This could result in the same regular expression matching slightly different sets of files in the two different choosers. The XView File Chooser uses /usr/include/reexp.h in the SunOS release 5.6 software and its usage is correct. XView File Chooser, OpenWindows Developer's Guide File Chooser vs. OpenWindowsDeveloper's Guide File Chooser vs. XView File ChooserSunView(TM) software is not part of the Solaris 2.6 operating environment. SunView applications are incompatible with the OpenWindows environment and must be converted. SunViewSee OpenWindows Version 3.1 User's Guide for information about:Features of the OpenWindows 3.1 environmentThe applications that are not compatible between OpenWindows Version 2.0 and 3.1 platformsGuidelines for modifying incompatible applicationsThis section describes your options for performing user and group administration. user environment administrationuser and group administration groups, administeringYou can add, modify, and remove users and groups through the command-line interface using useradd, userdel, and usermod. Although these commands are not as robust as Admintool, they do enable you to do most of the tasks supported by Admintool from the command line without running the OpenWindows or CDE software. admintoolfor user and group administration user and group administration administration of users and groupsThe useradd, userdel, and usermod commands are similar to editing the /etc files in that they also affect only the local system. These commands cannot be used to change any information in the network naming service. However, you can use useradd to verify the uniqueness of the user name and user ID and the existence of group names in the network naming service. usermod command userdel command useradd command command-line interfacefor user and group administrationThis section describes changes to the general procedure for adding user accounts.The general procedure for adding new users to a SunOS release 4.x system was:Edit the /etc/passwd file and add an entry for the new user.Create a home directory and set the permissions for the new user.Set up skeletal files for the new user (.cshrc, .login, .profile, and so on).Add the new user to the naming service (NIS).In the Solaris 2.6 operating environment, there are three ways to add (and maintain) user accounts:Use Admintool - This is the most straightforward method to use if the system is running the OpenWindows environment.Use command-line interfaces (useradd, usermod, and userdel) - Use this method if you don't want to use Admintool. usermod command userdel command useradd commandManually edit files (similar to the SunOS release 4.x procedure with a few exceptions)Note - Because the SunOS release 5.6 software uses a shadow password file, simply editing the /etc/passwd file is no longer sufficient. You should not attempt this method unless you have ample experience with this type of administration.System Administration Guide describes in detail the policy decisions you should consider before you begin to set up accounts. It also explains security considerations for controlling user access to systems and networks. user access, controlling groupsadministeringThe SunOS release 4.x mail programs are different in the Solaris 2.6 operating environment; however, procedures for setting up mail are still the same. The SunOS release 4.x version of mail is included in the SunOS/BSD Source Compatibility Package. Its user interface is different from the Solaris 2.6 operating environment's version of mail. Additionally, some useful mail facilities are included for compatibility. /usr/ucb/mail command /usr/bin/mail command user environment administrationmail usage mail command mailusingIn the Solaris 2.6 operating environment, there are three programs for sending and retrieving your mail. All three are backward compatible and can be used to read your SunOS release 4.x mail. They are:mailtool, the OpenWindows interface for the mail program. New Solaris 2.6 mailtool options enable you to attach files to your messages, include third-party messages with your mail, deliver mail to multiple recipients, and send audio messages. OpenWindowsmail interface mailtool interfaceSee OpenWindows Version 3.1 User's Guide for a complete discussion of mailtool.mailx, which is installed under /usr/bin/mailx. This is the Solaris 2.6 mail reading program. It is an enhanced version of SunOS release 4.x /usr/ucb/mail. In the Solaris 2.6 operating environment, /usr/ucb/mail is a link to /usr/bin/mailx. mailx offers message headers that enable you to preview the sender and subject of each message before you read them. You can also switch between reading, sending, and editing mail messages. /usr/bin/mailx command mailx commandSee the mailx(1) man page for more information on mailx.mail refers to the mail program under /usr/bin/mail. The Solaris 2.6 interface is similar to the SunOS release 4.x /usr/bin/mail version (see the bin-mail(1) manual page in SunOS 4.x Reference Manual).See the mail(1) man page for more information on mail.For a complete discussion of all Solaris 2.6 mail programs, see Mail Administration Guide. mailusing mail command user environment administrationmail usage /usr/bin/mail command /usr/ucb/mail commandThis section outlines the main differences in using document tools between SunOS release 4.x and the Solaris 2.6 operating environment. user environment administrationdocument tool usage document tools, usingThe Solaris 2.6 operating environment provides a set of PostScript filters and device-independent fonts. However, most SunOS release 4.x TranScript filters have SunOS release 5.6 equivalents while a few less common ones do not. In SunOS release 5.6 systems, there is no TEX filter, no pscat (C/A/T) filter, and no raster image filter. PostScript filters fontsdevice-independent TEX filters raster image filters pscat (C/A/T) filtersThe Solaris 2.6 operating environment provides device-independent troff, with the following features: SunOS release 4.x troff input files work with Solaris 2.6 troff; troff default output goes to the standard output instead of the printer. Therefore, you must specify a printer when you send troff output to the printer. troff commandchanges in document tools, using user environment administrationdocument tool usageMan page organization has changed to be compatible with SVR4 organization. As a result, some sections have been renamed. For example, man(8) is now man(1M). /usr/share/man directory user environment administrationman page directory organization changes man pagesdirectory organization changes /man directoryTable 6-4 shows SunOS release 5.6 man page directories. Table 6-4 /man DirectoryContentsSuffixesman1User commands1B - SunOS/BSD compatibility commands1C - Communication commands1F - FMLI commands1S - SunOS commandsman1MSystem administration commandsman2System callsman3Library functions3B - SunOS/BSD compatibility libraries3C - C library functions3E - ELF library functions3G - C library functions3I - Wide Character functions3K - Kernel VM library functions3M - Math library3N - Network functions3R - RPC services library3S - Standard I/O functions3T - Threads library functions3X - Miscellaneous library functionsman4File formats4B - SunOS/BSD compatibility file formatsman5Headers, tables, and macrosman7Special filesman9DDI/DKIman9EDDI/DKI entry pointsman9FDDI/DKI kernel functionsman9SDDI/DKI data structuresman pagesdirectory organization changes user environment administrationman page directory organization changesUnlike in the SunOS release 4.x software, which searched the individual man directories according to a predetermined order, the SunOS release 5.6 software lets you determine the search path. The man command uses the path set in the man page configuration file, man.cf. user environment administrationman command search path customization man command customizingman command search path man.cf filesEach component of the MANPATH environment variable can contain a different man.cf file. You can modify man.cf to change the order of the search; for example, to search 3b before 3c. The configuration file for the /usr/share/man directory follows. MANPATH environment variable# # Default configuration file for the on-line manual pages. # MANSECTS=1,1m,1c,1f,1s,1b,2,3,3c,3s,3x,3i,3t,3r,3n,3m,3k,3g, \ 3e,3b,9f,9s,9e,9,4,5,7,4b,6,l,nThe arguments to MANSECTS are derived from the man subdirectories available. The number of subdirectories has increased dramatically in this release because each subsection has its own directory. This new structure improves the performance of the man command and gives you finer control over the search path. The next two figures compare the man directories for the two releases. MANSECTS environment variablesunos4.1% ls /usr/share/man man1/ man2/ man3/ man4/ man5/ man6/ man7/ man8/ manl/ mann/sunos5.6% ls /usr/share/man man.cf man1f/ man3/ man3g/ man3n/ man3x/ man6/ man9f/ man1/ man1m/ man3b/ man3i/ man3r/ man4/ man7/ man9s/ man1b/ man1s/ man3c/ man3k/ man3s/ man4b/ man9/ manl/ man1c/ man2/ man3e/ man3m/ man3t/ man5/ man9e/ mann//man directory/usr/share/man directorycustomizingman command search pathman commanduser environment administrationman command search path customizationThe SunOS release 4.x man page table of contents and keyword database is called whatis. In the SunOS release 5.6 software, this information is in the windex file. In both releases, the database is created by the catman command, and is used by the man, apropos, and whatis commands. whatis database man pageswindex database man pageswhatis database databaseswindex databaseswhatis windex databaseThe windex file also has a slightly different format than the whatis file, as you can see from the following comparison of the two release versions.sunos4.1% man -k tset tset, reset (1) - establish or restore terminal characteristicssunos5.6% man -k tset reset tset (1b) - establish or restore terminal characteristics tset tset (1b) - establish or restore terminal characteristicsman commandTable 6-5 shows that SunOS release 5.6 version of the man command has additional search options.Table 6-5 OptionDescription-aDisplays all man pages that match file name. The pages are displayed sequentially in the order they are found.-lLists all man pages that match file name. You can use the output of this command to specify a section number with the -s option.-s section-numberSearches section-number for file name. In the SunOS release 4.x software, the man command accepted the section number as an option; in this release, the section number must be preceded by -s.-FForces the man command to search all directories until file name is found. This option overrides the windex database and the man.cf file.See the man(1) man page for a complete description of the SunOS release 5.6 man command. user environment administrationChapter 77. Device AdministrationThis chapter explains SunOS release 5.6 device naming conventions and discusses changes to device-related tasks such as getting information about disks, adding devices to a system, and using Volume Management."Device Naming Conventions""Obtaining Disk Information""Adding Devices to the System""Using Volume Management "device administrationDevice naming conventions have changed between the SunOS release 4.x and SunOS release 5.6 platforms. In addition, the /dev directory, which contains the special device names, has been changed from a flat directory to a hierarchical one, with a separate subdirectory for each category of device. For example, the location of disk device files is /dev/dsk, while raw disks are located in /dev/rdsk. namesdevicechanges in device namingchanges in device administrationnaming conventions /dev directorychanges inSunOS release 5.6 commands that take device names as arguments must use the SunOS release 5.6 device naming conventions. However, you can still use and recognize the SunOS release 4.x device names if you install the SunOS/BSD Source Compatibility Package. See Source Compatibility Guide for additional information. The disk partition slice numbers (0 through 7) correspond to partitions a through h of previous SunOS releases. namesdevicedisks disk devicesnaming conventions device namingdisksNote - Most SCSI disks have embedded controllers. This means that the drive number will always be 0 but the target number varies. For example, if an external disk drive has its rear switch set to 2, the device name for the first slice is /dev/dsk/c0t2d0s0, not /dev/dsk/c0t0d2s0. SCSI disksnaming conventionsBecause the names for SCSI targets 0 and 3 were reversed on some sun4c systems, device naming can be confusing. Under the SunOS 4.1.x software, SCSI target 3 was called sd0(), but it is now properly named c0t3d0. SCSI target 0 was called sd3(), but it is now named c0t0d0. Other SCSI disk names translate normally. For example, in the SunOS release 5.6 software, sd2a is c0t2d0s0 and sd2b is c0t2d0s1.Table 7-1 provides some examples that compare the SunOS release 4.x and SunOS release 5.6 device naming conventions. Table 7-1 Device DescriptionSunOS release 4.x Device NameSunOS release 5.6 Device Name namesdevicedisksDisk devices disk devicesnaming conventions device namingdisks/dev/sd0g/dev/dsk/c0t3d0s6/dev/rsd3b/dev/rdsk/c0t0d0s1/dev/rsd3a/dev/rdsk/c0t0d0s0Magnetic tape devices/dev/nrmt8/dev/rmt/8hn/dev/rst0/dev/rmt/0CD-ROM device namesdeviceCD-ROMs device namingCD-ROMS CD-ROM devicesnaming conventions/dev/sr0/dev/dsk/c0t6d0s2 device administrationnaming conventions device namingchanges in namesdevicechanges inThe commands that report disk information in the SunOS release 5.6 software have changed. df(1M) and du(1M) are still available, but have changed. dkinfo(8), and devinfo(1M) are replaced by prtvtoc and sysdef -d. This section provides an overview of those changes. information reportingdisk devices information reportingdevice administration disk devicesinformation reporting device administrationinformation reporting sysdef command prtvtoc command dkinfo command devinfo commandIf you have installed the compatibility packages, SunOS release 4.x command versions can be found under /usr/ucb/df and /usr/ucb/du. /usr/ucb/df command /usr/ucb/du command du command df commandThe df command has been changed to support the VFS architecture. As with the other VFS commands, there are generic and file-system versions of the command. The syntax in the SunOS release 5.6 command differs significantly from that used in the SunOS release 4.x version (see Appendix A, Commands Reference Table, for more information). For more information on VFS, see "Virtual File System Architecture". /usr/ucb/df command df commandThe df command now reports disk space in 512-byte blocks instead of kilobytes, but the -k option can be used to report disk space in kilobytes. Also, the -t option behaves differently; formerly, it restricted the output to file systems of a specified type (for example, "nfs" or "4.2"). The SunOS release 5.6 version produces a full listing with totals.Finally, use the SunOS release 5.6 device naming conventions when specifying special device names to this command. See "Device Naming Conventions" for details.Like df, the du command reports disk usage in 512-byte blocks instead of kilobytes. There's also a -r option that causes the normally "silent" command to generate messages when it has difficulty reading a directory or opening a file. /usr/ucb/du command du commandThe SunOS release 4.x dkinfo command is no longer available. To print device information, use prtvtoc(1M) instead of dkinfo. dkinfo command prtvtoc commandThe prtvtoc command reports the important information stored on a disk's label, including information on the disk's partitions. For more information about prtvtoc, see System Administration Guide.The following screen shows sample output for the SunOS release 5.6 prtvtoc command.# prtvtoc /dev/rdsk/c0t2d0s2 * /dev/rdsk/c0t2d0s2 partition map * * Dimensions: * 512 bytes/sector * 36 sectors/track * 9 tracks/cylinder * 324 sectors/cylinder * 1272 cylinders * 1254 accessible cylinders * * Flags: * 1: unmountable * 10: read-only * * First Sector Last * Partition Tag Flags Sector Count Sector Mount Directory 0 0 00 0 32724 32723 / 1 0 00 32724 65448 98171 2 0 00 0 406296 406295 6 0 00 98172 308124 406295 /usrThe SunOS release 4.x version of devinfo is incompatible with the SunOS release 5.6 version. To produce output similar to the SunOS release 4.x version, use prtconf with the -v option. devinfo command prtconf command device administrationinformation reporting disk devicesinformation reporting information reportingdevice administration information reportingdisk devicesAt boot time, the system does a self-test and checks for all devices that are attached to it. After you add a new device to the system, use boot -r to activate dynamic reconfiguration of the kernel. A reconfiguration script is run to load all the device drivers listed in the module's directories and to create the corresponding hardware nodes. See the kernel(1M) man page for more information. device administrationadding devices boot commanddevice additions and addingdevicesYou can also use boot -a to interactively add drivers or modules to the system, but if you do, you will be asked to provide other boot parameters, including what to boot and where the root file system is.Paths to the system files and kernel modules are stored in /etc/system. When the system boots, it reads the information in /etc/system to determine which modules to load. You can specify a different path by using the MODDIR syntax of the system(4) file or by using boot -a. /etc/system filedescribedFor more information about boot(1m) or about adding devices and drivers, see System Administration Guide. addingdevices boot commanddevice additions and device administrationadding devicesBeginning with the Solaris 2.2 software, a new layer of software manages CD-ROM and diskette devices -- Volume Management. This software automates the interaction between you and your CDs and diskettes. Volume Managementusing Volume Managementoverview diskette devices, managing device administrationVolume Management for CD-ROM devicesmanagingThe OpenWindows and CDE File Manager applications have been modified to use Volume Management to provide immediate user access to CDs and diskettes with file systems. See Solaris User's Guide for more information on File Manager's new features. OpenWindowsFile Manager changes File ManagerThere are also several new commands to help you administer Volume Management on your system.Volume Management automatically mounts CD and diskette file systems when removable media are inserted into the devices. Any CD or diskette file system will be automatically mounted in the locations described in Table 7-2. HSFS (CD-ROM file system) file systemsdiskette devices with file systemsCD-ROM devices with diskette file system, automounting of CD-ROM file system (HSFS)Table 7-2 MediaLocationCD /cdrom directory/cdrom/cdrom_nameDiskette /floppy directory/floppy/floppy_nameIf the CD or diskette does not contain a file system, it will be accessible in the locations described in Table 7-3.Table 7-3 MediaLocationCD /vol/dev/aliases/cdrom0 file system/vol/dev/aliases/cdrom0Diskette /vol/dev/aliases/floppy0 file system/vol/dev/aliases/floppy0For security reasons, these file systems are mounted setuid. See the mount(1M) man page for a description of this and other mount options.For more information on configuring Volume Management and on using diskettes and CDs, see System Administration Guide.Man pages for Volume Management components are also available, See rmmount(1), rmmount.conf(4), volcancel(1), volcheck(1), vold(1M), volmgt(3), vold.conf(4), volfs(7), and volmissing(1).Note - Volume Management now controls these CD-ROM paths: /dev/dsk/c0t6d0s0 and /dev/rdsk/c0t6d0s0; and these diskette paths: /dev/diskette and /dev/rdiskette. Attempts to mount or access a CD or diskette using these paths will result in an error message. Volume Managementerror messages error messagesVolume ManagementThere are several new commands to help you administer Volume Management on your system, as described in Table 7-4. Volume Managementcommands commandsVolume ManagementTable 7-4 CommandDescription rmmount(1) rmmount commandRemovable media mounter. Used by vold to automatically mount /cdrom and /floppy when a CD or diskette is installed.volcancel(1) volcancel commandCancels a user's request to access a particular CD-ROM or diskette file systemvolcheck(1) volcheck commandChecks drive for installed media. By default, checks drive pointed to by /dev/diskette.volmissing(1) volmissing commandNotifies user when an attempt is made to access a CD or diskette that is no longer in the drivevold(1) vold commandVolume Management daemon, controlled by /etc/vold.confThere are also two configuration files to define Volume Management's actions: /etc/vold.conf and /etc/rmmount.conf. See the vold.conf(4) and rmmount.conf(4) man pages for descriptions of these files, and see System Administration Guide for information on managing CD-ROM and diskette devices. Volume Managementconfiguration files vold.conf file rmmount.conf file /etc/vold.conf file /etc/rmmount.conf file Volume Managementusing diskette devices, managing device administration device administrationVolume Management for CD-ROM devicesmanagingChapter 88. Startup and ShutdownThis chapter describes changes to procedures for booting and shutting down a system."Booting""Using the init Command""Shutting Down"See System Administration Guide for detailed descriptions of boot procedures. Man pages for each command are available on line in the "User Commands" section of SunOS 4.x Reference Manual, or in man Pages(1): User Commands.startupbootingThe Solaris 2.6 boot process makes system administration easier. Some of the major changes include: bootingchanges inThe kernel is self-configuring so you no longer need to rebuild it manually.Kernel memory consumption is reduced by automatic loading of devices when first opened.File systems are checked only when necessary, improving boot time.The boot block can read UNIX file systems, eliminating boot errors when the boot program moves.Third-party bootable devices are supported.Secondary boot programs, ufsboot and inetboot, have been modified to read CacheFS file systems. This new booting capability enables Solstice AutoClient(TM) systems to boot more quickly and with less impact on network resources.The SunOS release 4.x fastboot command is available only on Solaris 2.6 systems that have the SunOS/BSD Source Compatibility Package installed. The fastboot command is obsolete in Solaris 2.6 systems because file systems are only checked if the file system state is identified as not clean. shutting downfastboot command fastboot commandThe SunOS release 4.x halt and reboot commands have shutdown(1M) and init(1M) equivalents in the SunOS release 5.6 software. shutting downreboot command shutting downhalt command /sbin/init command init commandcommands replaced by halt command shutting downshutdown commandIn the Solaris 2.6 operating environment, the shutdown and init commands are the preferred way to halt, shut down, or reboot your system. While the reboot command is available in the Solaris 2.6 operating environment, it brings the system down quickly without shutting down services in an orderly way. Table 8-1 shows the SunOS release 5.6 commands that replace SunOS release 4.x commands. shutdown command reboot commandTable 8-1 SunOS release 4.x CommandSunOS release 5.6 Command Replacementrebootshutdown -i -6, init 6 fastbootboot, init 6 The SunOS release 5.6 software has these additional options for the boot command: boot commandchanges inType boot -r when you add new hardware or alter its location. This option creates the physical and logical device names, with the logical device name linked to the physical device name. boot commanddevice additions andType boot -v when you want to see all the system bootup messages; the default is to boot silently. The messages are always stored in the /var/adm/messages file.Type boot -a when you want to be prompted for the name of an alternate kernel, /etc/system file, or path name for kernel module directories. bootingchanges inBe aware of these changes when booting from PROM: PROM, booting from bootingfrom PROMThe PROM loads bootblk from the disk. This file is similar to the previous SunOS release 4.x boot block except that it is specific to the UFS file system. boot blockAs in the SunOS release 4.x software, you need to use installboot(1M) to install boot blocks on a partition to be used for booting.installboot commandbootblk opens the boot device and, using the file system you specify, finds and loads ufsboot.The boot PROM loads the kernel, /kernel/genunix, after ufsboot is loaded into memory. SunOS release 4.x systems used /vmunix; however, in the SunOS release 5.6 software the /kernel directory contains all platform-independent kernel modules, including unix, needed to boot the system. ufsboot commandThe kernel, in turn, loads other drivers, such as esp, from the /kernel/drv directory. These drivers had to be built as part of the SunOS release 4.x kernel but can be dynamically loaded in SunOS release 5.6 systems when they are needed. The /sbin/init command generates processes to set up the system based on the directions in /etc/inittab. The next section describes the run levels that init uses. /sbin/init command inittab file init commanddescribed /etc/inittab file bootingfrom PROM PROM, booting fromTable 8-2 summarizes booting differences. bootingchanges in boot commandchanges inTable 8-2 SunOS release 4.xSunOS release 5.6Featurebootsd bootsd commandbootblk ufsbootblk commandNow loads ufsboot from diskboot programufsbootNow loads unix from disk/vmunix /vmunix file kernelbooting and/kernel/genunix /kernel/unix directory /unix directoryBootable kernel imageboot.sun4c.sunos.4.1 networksbooting over boot.sun4c.sunos.4.1 commandinetboot inetboot commandMounts and copies unix from networkrc.boot rc.single scriptsrc rc.boot script rc scripts /etc/rc.boot script /etc/rc scripts rc.single script /etc/rc.single script/etc/rcS /etc/rcS script rcS scriptMounts /usr and checks file systemsrc.local rc.local script /etc/rc.local script/etc/rc2 /etc/rc3 /etc/rc scripts rc scriptsSystem config scripts/etc/config system command kernelcustomizing /etc/config command customizingkernel config commandmodload /etc/system /etc/system filedescribedCustomizes system kernel, loads modules as neededProm monitor, single user, multiuserRun states 0 - 6, and SSystem run levels/dev/sd1g sd1g command /dev/sd1g command /dev directorychanges in/dev/dsk/c0t1d0s6More descriptive logical device names. See "Device Naming Conventions".MAKEDEV MAKEDEV environment variableboot -r,add_drv add_drv commandMakes device nodes bootingchanges inThe init(1M) command replaces the SunOS release 4.x fasthalt command in the SunOS release 5.6 software. Use it to shut down a single-user system. You can use init to place the system in a power-down state (init 0) or into single-user state (init 1). /sbin/init command initialization states, changing fasthalt command init commandusing shutting downfasthalt command single-user systems, shutting downNote the following changes to the init command: init commandchanges inSunOS release 5.6 system software has eight initialization states (init states or run levels). The default init state is defined in the /etc/inittab file. inittab file /etc/inittab fileThe SunOS release 5.6 init command uses a different script for each run level instead of grouping all the run levels together in the /etc/rc, /etc/rc.boot, and /etc/rc.local files. The files, named by run level, are located in the /sbin directory. scriptsrc /sbin/rc scripts rc scriptsSystem Administration Guide describes this command in detail. The SunOS release 5.6 init command enables you to control the run level (initialization state) of your system and move easily between various modes of operation. The SunOS release 5.6 /sbin/rc scripts control each individual run level instead of putting all system states into one file. This enables you to make changes in a unique file if you create new scripts or modify existing ones. SunOS release 4.x systems controlled run levels using /etc/rc, /etc/rc.boot, and /etc/rc.local files. changingsystem run levels booting startup rc.local script rc.boot script /etc/rc.local script /etc/rc.boot script /etc/rc scriptsThe SunOS release 4.x software had three run levels: prom monitor, single user, and multiuser. These correspond to run levels 0, 1, and 3 in the SunOS release 5.6 software. single-user run levels /sbin/rc scripts rc scripts multiuser run levelsTable 8-3 gives an overview of what each run level's /sbin/rc script does.Table 8-3 Run LevelDefault SunOS release 5.6 Function0Shuts down the system so it is safe to turn off power. Stops system services and daemons. Terminates all running processes. Unmounts all file systems.1Single-user (system administrator) state for tasks that allow only one user on the system. Stops system services and daemons. Terminates all running processes. Unmounts all file systems.2Normal multiuser operation without NFS systems exported. Sets the timezone variable. Mounts the /usr file system. Cleans up the /tmp and /var/tmp directories. Loads the network interfaces and starts processes. Starts the cron daemon. Cleans up the uucp tmp files. Starts the lp system. Starts the sendmail daemon.3Normal multiuser operation of a file server with NFS systems exported. Completes all of the tasks in run level 2. Starts the NFS system daemons.4Alternative multiuser state (not used).5Software reboot, prompts for a boot device other than the EEPROM default.rReboot. Kills all active processes. Unmounts the file systems and reboots to the initdefault entries in /etc/inittab. rc scripts /sbin/rc scriptsS,s single-user run levels /sbin/rcS scripts rcS scriptSingle-user state, running with some file systems mounted and accessible. changingsystem run levels init commandusing initialization states, changing rc scripts /sbin/init command /sbin/rc scripts scriptsrcUse the shutdown(1M) command when shutting down a system with multiple users. The command sends a warning to all logged-in users and, after 60 seconds, shuts the system down to single-user state. shutting downshutdown command shutdown command multiuser systems, shutting downThe SunOS release 4.x fasthalt commands are available only on SunOS release 5.6 systems that have the SunOS /BSD Source Compatibility Package installed. shutting downfasthalt command fasthalt commandThe SunOS release 4.x halt and reboot commands have shutdown and init equivalents. shutting downreboot command shutting downhalt command reboot command halt commandSee System Administration Guide for detailed descriptions of shutdown procedures. .In the SunOS release 5.6 software, the shutdown command is the preferred way to halt or shut down a system. shutdown and init use rc scripts to kill running processes. While the halt command is available in the SunOS release 5.6 software, it stops the system quickly without shutting down services in an orderly way. Table 8-4 shows the SunOS release 5.6 commands that replace those in the SunOS release 4.x system. Table 8-4 SunOS release 4.x CommandSunOS release 5.6 Command Replacementhaltshutdown -i 0, init 0fasthaltshutdown -i 0, init 0The shutdown and init commands accept a numerical "run-level" argument that controls the shutdown sequence. See the shutdown and init man pages for information about the run-level numbers. multiuser systems, shutting down shutdown command shutting downshutdown commandThe SunOS release 5.6 shutdown command includes only the options in Table 8-5. This command and its options are described in System Administration Guide.Table 8-5 OptionDescription-gSelects "grace" period before shutdown begins.-i [init state]Specifies an initial run level (see Table 8-3).-yRuns shutdown without asking confirmation questions.Assumes a "yes" response to all questions.-messageSpecifies user-supported message. If more than one word, use quotes around the message.By default, the SunOS release 5.6 shutdown command asks you to confirm before an actual shutdown begins. You can use the -y option to run it without operator intervention.The shutdown options are available only in BSD source compatibility mode on Solaris 2.6 systems.See Appendix A, Commands Reference Table, for a summary of changes. See shutdown(1M) for information about how the command works.The SunOS release 4.x fastboot and fasthalt commands are available if you are running the SunOS/BSD Source Compatibility Package on Solaris 2.6 systems. The file-system checking features of these commands are not appropriate to a Solaris 2.6 system. shutting downfasthalt command shutting downfastboot command fasthalt command fastboot commandThe halt and reboot commands do not run the rc scripts in /sbin, so they are not recommended. Since the halt and reboot commands in SunOS release 5.6 systems are not available on other AT&T SVR4 systems, both commands have shutdown and init equivalents. shutting downreboot command shutting downhalt command reboot command halt commandChapter 99. File System AdministrationThis chapter familiarizes you with changes to file system layout and the changes to file systems, virtual file systems, directories, and files. The chapter also describes changes to file system administration including:Mounting file systemsMonitoring file systemsSharing file systemsCreating new file systemsChecking file systemsBacking up and restoring files"File System Changes""Default File Systems and Directories""Virtual File System Architecture""Directory and File Changes"" Using File System Administration Commands"For more information on understanding and managing file systems, see System Administration Guide. file systemsSunOS release 5.6 and SunOS release 4.x file systems are similar, but there are changes in the locations and names of system directories and files. There are also new file systems and new pseudo file systems, and one directory was removed. file systemschanges innames file systemschanges inlocation file systemschanges in directoriesnames directorieschanges in filesnames namesdirectories namesfileSome of the changes to file system locations and names are: The /dev directory has changed from a flat directory to a hierarchical one.The /etc directory has changed and contains specific system configuration information. Several files and subdirectories have been added, removed, or changed. /etc directorychanges inThe /etc/vfstab tab file replaces /etc/fstab.The /etc/lp directory replaces /etc/printcap. /etc/printcap database, replacement of /etc/lp directory databasesprintcapThe SunOS release 5.6 /sbin directory contains the rc scripts used to alter system run levels as well as the rcs script used to initialize the system prior to mounting file systems. /sbin/rc scripts /sbin/rc scripts /sbin directorychanges in rcS script rc scripts /sbin/rcS scripts scripts scriptsrcThe SunOS release 5.6 /usr directory contains sharable files and executables provided by the system. /usr directorydescribedThe /var directory contains files that change size during normal operation. Several files and subdirectories in the /var directory have been added, removed, or changed. /var directorydescribed /var directorychanges inThe /var/mail directory replaces /var/spool/mail. /var/spool/mail directory /var/mail directoryThe /sys directory is no longer needed because the kernel is dynamically loaded. /sys directory /sysThe /RFS file system has been removed. /RFS file systemThe terminfo database replaces termcap. /usr/share/lib/terminfo database terminfo database termcap database databasesterminfo databasestermcapThe TFS pseudo file system is not included in the SunOS release 5.6 software. translucent file system (TFS) TFS (translucent file system) pseudo file systems file systemspseudoThe added pseudo file systems are:The CACHEFS pseudo file system can be used to improve performance of slow devices such as CD-ROM. speed of devices, improving slow devices, improving performance device administrationimproving performance CD-ROM devicesimproving performance CACHEFS (cache file system)The PROCFS pseudo file system resides in memory and contains a list of active processes, by process number, in the /proc directory. See the proc(4) man page. PROCFS (process access file system) process managementpseudo file systems for /proc directoryThe FDFS pseudo file system provides explicit names for opening files using file descriptors. opening files, using file descriptors namesexplicit, for opening files using file descriptors filesopening using file descriptors file descriptor file system (FDFS) FDFS (file descriptor file system)The FIFOFS pseudo file system contains pipe files that give processes common access to data. pipe files, pseudo file system for filespipe, pseudo file system for FIFOFS (FIFO/pipe file system) data access, commonThe NAMEFS pseudo file system is used mostly by STREAMS for dynamic mounts of file descriptors on top of files. STREAMSpseudo file system for NAMEFS (name file system)The SWAPFS pseudo file system is the default swap device when the system boots or you create additional swap space. SWAPFS (swap file system) swap device, default defaultsswap device file systemspseudo pseudo file systemsThe following file systems are included in the SunOS release 5.6 directory structure: file systemsaddedThe kernel (now called unix) and the kernel modules are stored in the /kernel directory. unix kernel name /kernel directory kernel unix kernelmodules /kernelThe optional /opt file system can be used to store third-party or unbundled software. If /opt is not a separate file system, it may be a symbolic link to /usr/opt. unbundled software, file system for third-party software, file system for softwarethird-party and unbundled /opt file system /opt unbundled software /usr/opt file /usr/optThe /vol file system provides the default file system for the Volume Management daemon, vold(1M). See the volfs(7) man page. vold command /vol file system Volume Managementdefault file system for device administrationVolume Management for defaultsVolume Management file system file systemschanges inThe SunOS release 5.6 file system is hierarchical. Figure 9-1 graphically depicts SunOS release 5.6 default directories and file systems (indicated by dotted lines). Subdirectories shown are just a sample of what the directory or file system actually holds. Table 9-1 gives a brief description of each.file systemsdefaultdirectoriesdefaultdefaultsfile systemsdefaultsdirectories

Figure 9-1

The Solaris 2.6 software contains a default set of file systems and directories, and uses a set of conventions to group similar types of files together. Table 9-1 lists the default file systems and directories with a brief description.Table 9-1 File System or DirectoryTypeDescription/ root file system (/) / file systemFile systemThe top of the hierarchical file tree. The root directory contains the directories and files critical for system operation, such as the kernel (/kernel/unix), the device drivers, and the programs used to boot the system. It also contains the mount point directories where local and remote file systems can be attached to the file tree./etc /etc directorydescribedDirectoryContains system files used in system administration/usr /usr file systemdescribedFile systemContains architecture-dependent and -independent sharable files. Files such as man pages that can be used on all types of systems are in /usr/share./home /home file systemFile systemThe mount point for the users' home directories, which store users' work files. By default, /home is now an automounted file system. defaultsautomounting/var /var directorydescribedDirectoryContains system files and directories that are likely to change or grow over the life of the local system. These include system logs, vi and ex backup files, and uucp files./opt unbundled software, file system for third-party software, file system for softwarethird-party and unbundled /opt file systemFile systemMount point for optional third-party software. On some systems /opt may be a UFS file system on a local disk partition./tmp /tmp file system (TMPFS)describedFile systemTemporary files, cleared each time the system is booted or /tmp is unmounted/vol /vol file systemFile systemContains directories for removable media, managed by vold(1M)/proc /proc file systemFile systemContains a list of active system processes, by number. Does not use any disk space./sbin /sbin directorydescribedDirectoryEssential executables used in the booting process and in manual system recovery defaultsdirectories defaultsfile systems directoriesdefault file systemsdefaultThe SunOS release 5.6 software features a virtual file system (VFS) architecture that simplifies file system management for systems that support multiple file systems. virtual file-system architecture (VFS) VFS (virtual file-system architecture) file systemsvirtual architecture (VFS)Over the years, several different UNIX file systems were developed, with each its own set of commands for file system management. Learning all the variations can be confusing and difficult. The SunOS release 5.6 software addresses this issue with a set of generic commands for file system management. These commands are a part of a common VFS interface that makes differences between file systems transparent with respect to maintenance. The subsections below list a summary of supported file systems and the generic file system commands.Most file system types included in the SunOS release 4.x software are also included in the SunOS release 5.6 software. There is one exception: The translucent file system (TFS) type has been withdrawn from the SunOS release 5.6 software. Table 9-2 summarizes file-system type availability in the SunOS release 4.x and SunOS release 5.6 environment. file systemssupported typesTable 9-2 CategoryNameDescriptionSunOS release 4.xSunOS release 5.6Disk-basedUFS Unix file systems (UFS)support forUNIX file systemYesYesHSFS HSFS (CD-ROM file system) CD-ROM file system (HSFS)CD-ROM file systemYesYesPCFS PCFS (PC file system)PC file systemYesYesNetwork-based NFSsupport forNFSSun's distributed computing file systemYesYesPseudo pseudo file systems file systemspseudoSPECFS SPECFS (device special file system) device special file system (SPECFS)Device special file systemYesYesTMPFS /tmp file system (TMPFS)support for/tmp temporary file systemYesYesLOFS loopback file system (LOFS) LOFS (loopback file system)Loopback file systemYesYesTFS translucent file system (TFS) TFS (translucent file system)Translucent file systemYesNoPROCFS PROCFS (process access file system)Process access file systemNoYesFDFS file descriptor file system (FDFS) FDFS (file descriptor file system)File descriptor file systemNo YesFIFOFS FIFOFS (FIFO/pipe file system)FIFO/Pipe file systemNo YesNAMEFS NAMEFS (name file system)Name file systemNoYesSWAPFS SWAPFS (swap file system)Swap file systemNoYesCACHEFS CACHEFS (cache file system)Cache file systemNoYes file systemspseudo pseudo file systemsFor more information on file systems, see the proc(4) and fd(4) man pages and System Administration Guide.The Cache File System can be used to improve performance of remote file systems or slow devices such as CD-ROM. When a file system is cached, the data read from the remote file system or CD-ROM is stored in a cache on the local system. slow devices, improving performance device administrationimproving performance CACHEFS (cache file system) CD-ROM devicesimproving performance speed of devices, improvingIn the SunOS release 5.6 software SWAPFS is the default swap device when the system boots or you create additional swap space. This swap device uses physical memory as swap space, but also requires physical swap space on disk. swap device, default defaultsswap device SWAPFS (swap file system)In SunOS release 4.x systems, the default physical swap device depends on the system configuration. Standalone systems default to sd0b and diskless systems get their swap files from the bootparam server. The SunOS release 5.6 software uses the swap file as the default dump device instead of specifying a file on disk.Table 9-3 shows SVR4 file system types that are not supported in the SunOS release 5.6 software. SVR4unsupported file system types file systemsunsupported SVR4Table 9-3 NameDescriptionBFS boot file system (BFS) BFS (boot file system)Boot file systemS5 System V file system (S5) S5 (System V file system) file systemsSystem VSystem V file systemxnamefs xnamefs XENIX semaphore file system (xnamefs)XENIX semaphore file system file systemssupported typesMost file system administration commands have a generic and a file system component. Use the generic commands, which call the file system component. Table 9-4 lists the generic file-system administrative commands, which are located in the /usr/bin directory. generic file system commands file systemscommandsdescribed commandsfile system /usr/bin directorygeneric file system administrative commands in /usr/bin directorydescribedTable 9-4 CommandDescriptionclri(1M) inodes, clearing clri command clearing inodesClears inodesdf(1M) /usr/ucb/df command information reportingdisk devices filesinformation reporting disk devicesinformation reporting df commandReports the number of free disk blocks and filesff(1M) namesfile listingfile names and statistics information reportingfile systems filesnames ff commandLists file names and statistics for a file systemfsck(1M) fsck command file systemschecking checkingfile systemsChecks the integrity of a file system and repairs any damage foundfsdb(1M) fsdb command file systemsdebugger developersdebuggers debuggersFile system debuggerfstyp(1M) fstyp command file systemstype determinationDetermines the file-system typelabelit(1M) labelit command file systemslabelsLists or provides labels for file systems when copied to tape (for use by the volcopy command only)mkfs(1M) mkfs command file systemscreating creatingfile systemsMakes a new file systemmount(1M) mountingremote resources mountingfile systems mount command file systemsremotemounting file systemsmounting remote file systemsmountingMounts file systems and remote resourcesmountall(1M) mountall commandMounts all file systems specified in a file-system tablencheck(1M) path namesgenerating for file systems ncheck command file systemspath name list generation directoriespath name generation for file systemsGenerates a list of path names with their i-numbersumount(1M) unmountingremote resources unmountingfile systems umount command remote file systemsunmounting file systemsunmounting file systemsremoteunmountingUnmounts file systems and remote resourcesumountall(1M) umountall commandUnmounts all file systems specified in a file-system tablevolcopy(1M) volcopy command image copy, file systems file systemsimage copy ofMakes an image copy of a file system /usr/bin directorygeneric file system administrative commands inMost of these commands also have a file system counterpart.Caution - Do not use the file system commands directly. If you specify an operation on a file system that does not support it, the generic command displays this error message: command: Operation not applicable for FSType type. "Operation not applicable for FSType " message file systemserror message error messagesfile system commandsMost of these commands use this syntax: syntax, file system commands file systemscommandssyntaxcommand [-F type] [-V] [generic-options] [-o specific-options] [special|mount-point] [operands] The options and arguments to the generic commands are:-F type Specifies the type of file system. If you do not use this option, the command looks for an entry that matches special or mount point in the /etc/vfstab file. Otherwise, the default is taken from the file /etc/default/fs for local file systems and from the file /etc/dfs/fstypes for remote file systems.-VEchoes the completed command line. The echoed line may include additional information derived from /etc/vfstab. Use this option to verify and validate the command line. The command is not run.generic-optionsOptions common to different types of file systems.-o specific-options A list of options specific to the type of file system. The list must have the following format: -o followed by a space, followed by a series of keyword [=value] pairs separated by commas with no intervening spaces.special|mount-pointIdentifies the file system. The name must be either the mount point or the special device file for the slice holding the file system. For some commands, the special file must be the raw (character) device; for other commands it must be the block device. In some cases, this argument is used as a key to search the file /etc/vfstab for a matching entry from which to obtain other information. In most cases, this argument is required and must come immediately after specific-options. However, the argument is not required when you want a command to act on all the file systems (optionally limited by type) listed in the /etc/vfstab file.operandsArguments specific to a type of file system. See the specific man page of the command (for example, mkfs_ufs(4) for a detailed description. file systemscommandssyntax syntax, file system commandsThe default remote file system type is /etc/dfs/fstype. The default local file system type is /etc/default/fs. See the default_fs(4) man page for more information. file systemsdefault /etc/dfs/fstype file /etc directorychanges in defaultsfile systems file systemsremotedefault type remote file systemsdefault type /etc/default/fs fileIn previous SunOS releases, all file system commands were located in the /etc directory. In the SunOS release 5.6 software, file system commands are organized into separate hierarchies for convenience. All of the file system commands are included in /usr/lib/fs/fstype. Commands needed before /usr is mounted are duplicated in /etc/fs/fstype. file systemscommandslocations /fs directory /usr/lib/fs directory /etc/fs directoryThe generic commands are located in /usr/sbin. The commands needed before /usr is mounted are duplicated in /sbin. /usr/sbin directory /sbin directorydescribedTable 9-5 lists the locations of the file-system commands.Table 9-5 TypeLocation of Primary VersionLocation of Duplicate Version (root)Generic/usr/sbin/sbinSpecific/usr/lib/fs/etc/fs file systemsvirtual architecture (VFS) VFS (virtual file-system architecture) virtual file-system architecture (VFS) commandsfile system file systemscommandsdescribed generic file system commandsThis section describes the changes to directories and files between the SunOS release 4.x and SunOS release 5.6 environment. directorieschanges inThe /dev directory has changed from a flat directory to a hierarchical one. Table 9-6 describes the subdirectories that have been added. /dev directorychanges inTable 9-6 SubdirectoryDescription/dev/dsk /dsk directory disk devicesdirectories for /dev/dsk directory block disk devices, directory forContains block disk devices/dev/rdsk /rdsk directory raw disk devices, directory for /dev/rdsk directoryContains raw disk devices/dev/pts /pts directory pseudo terminal (pty) slave devices, directory for /dev/pts directoryContains pseudo terminal (pty) slave devices/dev/rmt raw tape devices, directory for tape devicesdirectory for raw /rmt directory /usr/sbin directory /dev/rmt directoryContains raw tape devices/dev/sad STREAMS Administrative Driver, entry point directory /sad directory /dev/sad directoryContains entry points for the STREAMS Administrative Driver/dev/term terminal devices, directory for /term directory /dev/term directoryContains terminal devicesThe /etc directory contains system configuration information. Several files and subdirectories have been added, removed, or changed. /etc directorydescribed /rdsk directory /etc directorychanges inFile system commands, such as mount*, have been moved to subdirectories of the /usr/lib/fs directory. /usr/lib/fs directory /fs directoryThe SunOS release 4.x /etc/fstab file has been replaced by /etc/vfstab.Initialization scripts, such as rc, rc.boot, rc.local, and rc.single, are not available in the SunOS release 5.6 software. They are replaced by the scripts shown in Table 9-7, which are run by their corresponding run control files. Table 9-8 describes the subdirectories that have been added to the SunOS release 5.6 /etc directory. /etc/rc.single script /etc/rc.local script /etc/rc.boot script /etc/rc scripts rc scripts rc.boot script rc.local script rc.single script /sbin/rc scripts scriptsrcTable 9-7 ScriptsRun Control Files/etc/rc0.d rc.d scripts rc scripts /etc/rc.d scripts /etc/rc scripts /sbin/rc scripts/sbin/rc0/etc/rc1.d/sbin/rc1/etc/rc2.d/sbin/rc2/etc/rc3.d/sbin/rc3/etc/rc4.d/sbin/rc4/etc/rc5.d/sbin/rc5/etc/rc6.d/sbin/rc6/etc/rcS.d rcS.d script rcS script /etc/rcS.d script /etc/rcS script /sbin/rcS scripts/sbin/rcS Table 9-8 SubdirectoryDescription/etc/default system configurationdefault /etc/default directory defaultsdirectory forDefines default system configuration/etc/inet Internet servicesconfiguration information directory /inet directory /etc/inet directoryDefines Internet services configuration/etc/lp printersconfiguration /etc/lp directory device configurationDefines LP system configuration/etc/opt /opt directory /etc/opt directoryDefines installed optional software/etc/rcn.d run-state transition operations, directory forDefines run-state transition operations/etc/saf Service Access Facility (SAF)directory for /etc/saf directoryDefines Service Access Facility (SAF) configurationIn the SunOS release 5.6 software, the virtual file system file /etc/vfstab replaces the /etc/fstab file. In the virtual file system architecture, the /etc/vfstab file provides default file system parameters used by the generic commands for file system management. For information about these commands, see "Generic File System Commands". /etc/vfstab filedescribed /etc/fstab file/etc/vfstab vs.In addition to the name change, the /etc/vfstab file is different from the /etc/fstab file in the following ways: /etc/vfstab filefieldsA device to fsck field has been added to specify the names of raw devices to be checked by fsck.An automount field has been added to control the routine mounting of file systems by mountall (the automount daemon does not use this field).The freq field, which specified the number of days between dumps, has been eliminated.The file system table has seven fields, each separated by a tab. Table 9-9 explains the field entries. directorieschanges in /etc directorychanges inNote - You must have an entry in each field in the /etc/vfstab file. If there is no value for a field, be sure to type a dash (-).Table 9-9 Field NameContentdevice to mountThe entry in this field may be any of the following:The block special device for local UFS file systems (for example, /dev/dsk/c0t0d0s0)The resource name for remote file systems (for example, myserver:/export/home for an NFS system)The name of the slice on which to swap (for example, /dev/dsk/c0t3d0s1)The /proc directory and proc file system typeCD-ROM as hsfs file system type/dev/diskette as pcfs or ufs file system typeThis field is also used to specify swap file systems. For more information on remote file systems, see NFS Administration Guide .device to fsckThe raw (character) special device that corresponds to the file system identified by the device to mount field (for example, /dev/rdsk/c0t0d0s0). This field determines the raw interface that is used by fsck. Use a dash (-) when there is no applicable device, such as for a read-only file system or a network-based file system.mount pointThe default mount-point directory (for example, /usr for /dev/dsk/c0t0d0s6).FS typeThe type of file system identified by the device to mount field.fsck passThe pass number used by fsck to determine whether to check a file system. When the field contains a dash (-), the file system is not checked. When the field contains a value of 1 or more, the file system is checked; non-UFS file systems with a 0 fsck pass are checked. For UFS file systems only, when the field contains a 0, the file system is not checked. When fsck is run on multiple UFS file systems that have fsck pass values greater than 1 and the preen option (-o p) is used, fsck automatically checks the file systems on different disks in parallel to maximize efficiency. When the field contains a value of 1, the file system is checked sequentially. Otherwise, the value of the pass number does not have any effect. In SunOS 5.6 system software, the fsck pass field does not explicitly specify the order in which file systems are checked.automount?yes or no for whether the file system should be automatically mounted by mountall when the system is booted. An auto in the fourth column of your SunOS release 4.x /etc/fstab would translate to a "yes" in this column; a noauto, a "no." Note that this field has nothing to do with the automount program.mount optionsA list of comma-separated options (with no spaces) that are used in mounting the file system. Use a dash (-) to show no options. See the mount(1M) man page for a list of the available options.For detailed information about the /etc/vfstab file, see System Administration Guide. /etc/vfstab filefieldsshadow file/etc/shadow fileThe SunOS release 5.6 software contains an /etc/shadow file, which includes entries that force password aging for individual user login accounts. The /etc/shadow file also contains encrypted passwords. The /etc/shadow file does not have general read permissions. This prevents general access to the encrypted passwords that formerly appeared in the /etc/passwd file. The SunOS release 5.6 /sbin directory contains the rc scripts used to alter system run levels as well as the rcs script used to initialize the system prior to mounting file systems. See the rc man pages and "Changing System Run Levels" for a description of the scripts. /sbin/rc scripts /sbin/rc scripts /sbin directorydescribed rcS script rc scripts /sbin/rcS scripts scriptsrcThe SunOS release 5.6 /usr directory contains sharable files and executables provided by the system. Table 9-10 describes the subdirectories that have been added to the SunOS release 5.6 /usr directory. /usr directorydescribed /usr directorychanges inTable 9-10 SubdirectoryDescription/usr/ccs /usr/ccs directory C compilation system, directory forC compilation systems/usr/snadm /usr/snadm directory /snadm directory Administration Toolfiles directoryExecutables and other files used by admintool Table 9-11 shows files that were in the SunOS release 4.x /usr directory but have been moved in the SunOS release 5.6 software. /usr/bin directorySunOS release 4.x files moved toTable 9-11 SunOS release 4.x LocationSunOS release 5.6 Location/usr/5bin /usr/5bin directory /5bin directory/usr/bin /usr/sbin directory/usr/5include /usr/5include directory /5include directory/usr/include /usr/include directory /include directory/usr/5lib /usr/5lib directory /5lib directory/usr/lib /usr/lib directory