The guide provides an introduction to the OpenSolaris operating system, as well as instructions for installing the current OpenSolaris release on your system.If you are a new OpenSolaris user, review the following information: If you are already familiar with the OpenSolaris releases, you can go to . OpenSolaris has several meanings, depending on the context in which it is used.For example, OpenSolaris is:An operating system code base originally based on Sun's proprietary Solaris Operating System. An open source development project. A free binary distribution of the OpenSolaris software that is available for redistribution under the terms of the Common Development and Distribution License (CDDL). This guide is intended to help you install and set up the free binary distribution of the OpenSolaris software and make your initial experience with it a successful one.For more information, see . OpenSolaris includes, among other things, the GNOME desktop, GNU tools, and a network-based software management system. OpenSolaris also includes state-of-the art technology: the ZFS file system, Dynamic Tracing (DTrace) framework, containers and zones for running applications in protected environments, and advanced network virtualization capabilities.Those who love technology, simply for technology's sake, will enjoy the many features that OpenSolaris has to offer. However, from a practical standpoint, these features are meant to simplify, improve, and streamline your application development and system management.Some examples include:Using Time Slider to easily browse and recover files from ZFS backup snapshots, without the assistance of a system administrator. (ZFS is the default file system type in the OpenSolaris release.) Speeding up your application development and debugging your system by using DTrace, a tracing infrastructure that provides visibility into system performance. By using built-in measurement points in the operating system, DTrace can display detailed performance characteristics about the operating system or user programs that are running on the OpenSolaris release. Organizing and isolating workloads by using containers and zones. Leveraging ZFS for unprecedented scalability, reliability, and management simplicity. Using sophisticated network virtualization capabilities to maximize resource control, network performance and utilization, utility computing, and server consolidation. Managing system services through the Service Management Facility (SMF), a Windows-like service management capability that supports managing service dependencies, service startup order, and service failures. All of these capabilities are available through a simple installation. OpenSolaris can be easily upgraded through a networked package repository. You can also explore OpenSolaris on a Live CD, without actually installing it on your system. Or, you can run OpenSolaris in a virtual machine, for example VirtualBox.For more information, see . Each OpenSolaris release is a free binary distribution that can be redistributed.The OpenSolaris distribution enables you to do the following:Explore an OpenSolaris environment on a Live CD.Each OpenSolaris release provides a Live CD for x86 platforms. This Live CD includes a basic, core OpenSolaris operating system, and the GNOME desktop environment. You can explore the OpenSolaris operating system from this Live CD without actually installing it on your system.A minimum of 512 Mbytes of memory is required to run the Live CD and the GUI installer. See Explore the OpenSolaris Live CD. Install the OpenSolaris operating system on your system. You can install the current OpenSolaris release on your system from the OpenSolaris Live CD. Or, you can download a bootable image of the OpenSolaris operating system and run it in a virtual machine on your system. An image is a collection of software in a package that comprises an entire operating system in one file. An image is bootable and usable for installations.See Installation Roadmap. Add and update software on your system.After the OpenSolaris operating system is running on your system, additional software packages, including developer tools, can be downloaded to your system by using the Image Packaging System (IPS). IPS accesses software packages from network repositories and installs them.The Image Packaging System offers both the Package Manager GUI and command-line utilities, such as the pkg command, to install and manage the software packages on your installed system. The Package Manager is a graphical user interface (GUI) for IPS that enables you to easily install, update, and manage software packages.For both the Live CD and an installed OpenSolaris system, Package Manager can be started from the desktop's Main Menubar by selecting System > Administration > Package Manager. On an installed OpenSolaris system, you can also start the application by clicking the Package Manager icon that is located on the desktop.Use Package Manager or the IPS command-line utilities to:Add new packages to your system from network repositories. Update the existing packages individually on your system. Update all of the packages on your system at once. Select a build version with components for managing or creating your own custom OpenSolaris image. For information about using the Image Packaging System and Package Manager, see Getting Additional Software. See, also the pkg(1) man page. Upgrade your OpenSolaris operating system.To upgrade an existing OpenSolaris release to the OpenSolaris 2009.06 release, see Upgrading to the Next OpenSolaris Release. Create and manage multiple boot environments on your system.A boot environment is a bootable instance of an OpenSolaris operating system image, plus any other application software packages installed into that image. You can maintain multiple boot environments on your system, and each boot environment could have different software versions installed.With multiple boot environments, the process of updating software becomes a low risk operation, because you can create backup boot environments before making any software updates to your system. If necessary, you have the option of booting a backup boot environment.See Managing Multiple Boot Environments on Your System. Set up a customized application development environment on your system.The OpenSolaris software offers complete support for developing and deploying applications. Tools that are required for application development are available for download and installation through Package Manager. You can easily download and install tools, such as Sun Studio compilers, debuggers, performance analyzers, NetBeans, source code management, and the make utility.You can also download and install Web Stack development tools, such as Apache web server, Hypertext Preprocessor (PHP), Lighttpd web server, and the Squid caching proxy.See Setting Up Your Application Development Environment. Install custom OpenSolaris images on multiple client systems. System administrators can use the automated installer tool that is available with OpenSolaris releases to provide simplified setup and configuration for multiple installations of the OpenSolaris operating system.The automated installer enables system administrators to create an installation service that provides blueprints for specific x86 based, and starting with OpenSolaris 2009.06 release, SPARC based installations. This installation service includes a web server, which stores a list of manifest files with installation specifications that have been made available by the administrator.To locate an installation blueprint that matches the client's system specifications, clients can contact the web server and review the available services by using associated manifest files. When a matching blueprint or manifest file is found, the service installs the client with the OpenSolaris release, according to the specifications that are in the manifest file.See the Automated Installer Guide. Build a custom, OpenSolaris image that can be redistributed.System administrators and operating system developers can use the distribution constructor tool that is available with OpenSolaris releases to build preconfigured, bootable OpenSolaris images. This tool takes an XML manifest file as input, and then builds an ISO image based on the parameters that are specified in the manifest file. Or, a USB image can be created, based on a generated ISO image. These images can then be distributed to contacts and customers.An ISO image or a USB image is a collection of software that comprises an entire operating system in a single file. These images are bootable and are usable for installations, for creating a bootable CD or DVD, and for other purposes. An ISO image can be made available for distribution from the Internet. A USB image can be copied to a USB flash drive.See Distribution Constructor Guide. For additional resources, see . Each OpenSolaris release provides a Live CD for x86 platforms.The Live CD boots to a minimal OpenSolaris operating system, with a GNOME desktop environment. The desktop includes the Firefox Web Browser, Thunderbird Mail/Calendar, and other core applications.The network auto‐magic (NWAM) daemon, nwamd, and the GNOME network-manager applet are enabled to automatically manage your network interfaces.For a general description of the purpose and function of the Live CD, see What Is a Live CD?To explore OpenSolaris on the Live CD, without affecting the existing operating system that is installed on your system, follow these guidelines:If you have an OpenSolaris Live CD, insert the OpenSolaris Live CD into your system and reboot.This procedure assumes that the CD drive is booted before the hard drive in the BIOS boot order. However, if this is not the case, enter the system BIOS by typing the appropriate keystroke combination for your system type, then change the boot order. If you do not have an OpenSolaris Live CD, you can download an ISO image of the current OpenSolaris Live CD.You can then burn this image to a CD and boot to it. Or, you can save the image on your system and then run it in a virtual machine. See Virtualization Options. The following are the OpenSolaris Live CD options:You can choose another language for the OpenSolaris Live CD. OpenSolaris has language support for more than 40 languages. Input and output support for these additional languages can be activated on the Live CD in the following ways:Log out of the Live CD desktop. Use the Option button on the login screen to choose a language. Log in to the Live CD. If you need to use OpenSolaris accessibility features, use the Magnifer and Screen Reader boot options. If you are prompted to log in to the Live CD, both the user name and password are jack. The root login is not enabled on either the Live CD or on an installed system. The root password for the Live CD is opensolaris. You can install the OpenSolaris release from the Live CD onto your system, which is described in .If you proceed to install the OpenSolaris release, you will create a new user during the installation. After the installation, log in as that user, and then become superuser to configure the system.Because the root user is a role, you must assume this role by using the su command. Or, you can use the pfexec sh command to run commands in a privileged shell. The OpenSolaris Live CD includes an installer that enables you to install the OpenSolaris operating system on your x86 based system. To start the installer, select the Installer icon on the Live CD desktop.Using the installer tool on the OpenSolaris Live CD, you have these installation choices:Install OpenSolaris as the only operating system on your system. Install OpenSolaris on a partition that is separate from your existing operating system.Be aware that the installation overwrites all software and data on the selected partition. Install OpenSolaris inside a virtual machine. For complete installation instructions, see Installation Roadmap. For more information, see the following additional resources:For More Information Where To Go To find out more about new OpenSolaris features. To download OpenSolaris. To find out more about using OpenSolaris. To find out more about joining the OpenSolaris community and participating in the development of OpenSolaris and other related projects. To find out more about using accessibility features on the Live CD. This document is in development for an upcoming release. Review the following installation options and requirements for the OpenSolaris 2009.06 release. You have a number of options for installing the current OpenSolaris release from the OpenSolaris Live CD to your system.Choose one of the following options:To install the OpenSolaris 2009.06 release from the Live CD onto your system, continue to Steps 2 and 3. If you do not have the OpenSolaris 2009.06 Live CD, go to the site and select a link to download the image for the current OpenSolaris release to your system. Once you have downloaded the image, choose one of the following options:Burn this image to a CD and continue to Steps 2 and 3. Save the image on your system and mount it in a virtual machine as described in . To install or mount the OpenSolaris release from the Live CD into a virtual machine, see . If you already have an OpenSolaris release installed on your system, and you want to upgrade to the OpenSolaris 2009.06 release, do not use these installation instructions. Instead, go to . Check the requirements and limitations for running the installer on your x86 based system:Verify that your x86 based system meets the . Review the Installer Restrictions. Verify that you have installed all necessary device drivers by using the Device Driver Utility 1.1. See . Choose one of the following alternatives for installing from the Live CD on your system:If the OpenSolaris operating system will be the only operating system installed on your x86 based system, see instructions for . If you will be setting up a multiboot environment, review the specifications in .Back up your system. This step is strongly recommended when repartitioning your system. See the backup instructions in step one for . Continue with the steps for . If you already have a Solaris fdisk partition on your system, the installation overwrites this partition. After you have partitioned your system, see the instructions to . For installation issues, see . Installing the OpenSolaris 2009.06 release has the following restrictions:At this time, the OpenSolaris 2009.06 installer on the Live CD is for 32-bit or 64-bit x86 platforms only. If you want to install the OpenSolaris 2009. 06 release to SPARC systems, use the automated installer tool.See the Automated Installer Guide. The installer cannot upgrade an existing operating system. The installer can perform an initial installation into a Solaris partition or use an entire disk. The installation overwrites all the software and data on the selected target.However, you can upgrade all installed packages on your installed system by using the Image Packaging System. See . The entire content of a preexisting Solaris partition is overwritten during the installation. Existing file systems cannot be preserved. The OpenSolaris operating system installs a ZFS root file system, not a UFS root file system, on the disk selected during installation. The ZFS pool installed initially consists of the entire Solaris fdisk partition on the selected disk. After the initial installation is complete, you can add additional disks to this pool to create a mirrored pool configuration. For further information, see ZFS Documentation. A maximum of 2 Tbytes on a disk or on a partition is usable for installing the OpenSolaris 2009.06 release, even if the disk or partition is larger than 2 Tbytes. Review the following system requirements for installing the OpenSolaris 2009.06 release to your system.Requirement Description Memory The minimum requirement is 512 MB. Disk space Recommended size is at least 9 GB. A minimum of 3.2 GB is required. Multiboot capability If you are installing OpenSolaris on a system that will have more than one operating system, use the fdisk command or a third-party partitioning tool to create a new partition or to make adjustments to preexisting partitions. See .For multibooting information about specific operating systems, see . To mount or install the OpenSolaris ISO image as a “guest” in a VirtualBox, see . If you are installing on a system that is running the Mac OS X, and you have installed Parallels on that system, see . If you are using VMware with Windows, see the following resources:Test-driving OpenSolaris 2008.11 (B99) With VMware Workstation 6 Getting Started With OpenSolaris Using VMWare To install an OpenSolaris “guest” on a hypervisor, based on the Xen open source project, see the following resources:Installing OpenSolaris on Xen OpenSolaris xVM Documentation OpenSolaris 2008.11 as a Para-Virtual Xen Guest Use the Device Driver Utility to identify a known Sun or third-party driver for a device that you need on your system. Open the utility by selecting the Device Driver Utility on the OpenSolaris desktop for either the Live CD or an installed system.Use the Device Driver Utility to perform the following functions:Get information about devices installed on your native system, and check whether their corresponding device drivers exist. Search the IPS repositories for your system devices that do not have corresponding drivers attached. Download and install device drivers from the IPS repositories for devices on your system. Get the details of the third-party drivers that exist for your system devices, and install them manually from the corresponding third-party web site. Submit system configurations to the OpenSolaris Operating System Hardware Compatibility List (HCL). You must have an Internet connection to use all the functionality of the Device Driver Utility. For more information, see the online help in the utility tool menu. If you have any questions, send an email to driver-utility-feedback@sun.com.For additional driver resources, see . If you are installing an OpenSolaris release as part of a multiboot environment, review the following multibooting specifications for various operating systems.Existing OS Description Microsoft Windows If you have Windows installed, and you set up enough space to install the OpenSolaris operating system, the installation should be straightforward. All versions of the OpenSolaris release for the x86 platform use the GRUB bootloader. These OpenSolaris releases recognize Windows and ensure that the Windows partitions remain unchanged by default. When the OpenSolaris installation is finished, the GRUB menu gives you the option to boot either Windows or OpenSolaris.If you are using VMware, see Test-driving OpenSolaris 2008.11 (B99) With VMware Workstation 6. See also Getting Started With OpenSolaris Using VMWare. Linux, or Windows and Linux If you have either Linux or Windows installed on your system, and you boot through GRUB, before installing OpenSolaris, save a copy of the menu.lst file that shows the Linux and Windows boot entry information. You will need to manually update the menu.lst file to replace this information after the system boots. See the grub(5) man page.If you are installing OpenSolaris on a multiboot system that also contains the Linux operating system, the Solaris partition must precede the Linux swap partition. Solaris 10 OS The installer cannot be used to multiboot the OpenSolaris operating system. However, the installer can be used to replace instances of the Solaris 10 1/06 and later OSes, and instances of Solaris Express, in an existing multiboot Solaris system. Extended Partitions If you have another operating system on an extended partition, the existing extended partition is not changed and is not lost during an OpenSolaris release installation. Existing extended partitions are not visible during the OpenSolaris release installation, but the primary fdisk partition in which the extended partition resides is visible. No data in these partitions is lost due to the installation. The operating system on an extended partition is not displayed on the GRUB menu. For information about updating the GRUB menu, see x86: Administering the GRUB Bootloader. See also menu.lst file specifics at x86: Booting a Solaris System with GRUB. The OpenSolaris installer uses the open source GRUB bootloader, which supports installing multiple operating systems on one drive. Prior to installing, you need to create a partition for installing the OpenSolaris software. After partitioning and installing the operating systems, one of the operating systems can be deployed by choosing between the different operating systems at boot time.Back up your system!Backing up your system is strongly recommended before repartitioning your hard drive. See the Backing Up the Disk Media Content demo. The G4U open source tool was designed to back up x86 based operating systems. This demo provides sample step-by-step instructions for using the G4U open source tool to back up a system that has Windows XP installed on it. Create a partition on your hard drive for installing the OpenSolaris operating system.If you are installing OpenSolaris on a system that will have more than one operating system, use the fdisk command or a third-party partitioning tool to create a new partition or to make adjustments to preexisting partitions. Choose one of the following options:Use the fdisk command to create or modify a Solaris fdisk partition.For instructions, see x86: How to Create a Solaris fdisk Partition. See, also, the fdisk(1M) man page. Use commercial products or open-source tools to partition your hard drive.GParted is an open-source tool for disk partitioning. The ISO image for the GParted tool can be downloaded from the GParted web site. Use this download to burn a CD that includes the GParted tool.See the dual-boot partitioning video. This video provides sample step-by-step instructions that explain how to shrink a Windows XP system in order to make room for a Linux swap partition.Linux-swap is the same partition ID that Solaris uses. During the installation, in the disk partitioning step, you can change this Linux-swap partition to a Solaris partition. Use the installer to install the OpenSolaris operating system to the Solaris fdisk partition as described in the next section. The demos that are referenced in this section show you how to partition a system that has Windows XP installed on it. See Backing Up the Disk Media Content and dual-boot partitioning.Additional sample instructions are posted in the OpenSolaris community for the following dual-boot procedures:OpenSolaris with MacOS on MacBook Pro OpenSolaris and Ubuntu Linux Dual-Boot Installation Instructions OpenSolaris and Microsoft Vista Dual-Boot Installation Instructions Recovering OpenSolaris/Solaris/Linux After Windows Installation This document is in development for an upcoming release. Select an installation procedure from one of the following options: You can install the OpenSolaris to your hard driver. An existing Solaris fdisk partition is overwritten during the initial installation.Before installing the OpenSolaris operating system, review the system requirements and limitations described in the preceding sections of this document.Before you install the OpenSolaris operating system on a system that is running the Linux operating system, save a copy of the menu.lst file. The contents of the GRUB menu.lst file determine what is displayed in the GRUB menu when you boot the system. You will need to update the GRUB menu after the installation. For further information, see menu.lst file specifics at x86: Booting a Solaris System with GRUB. The following are the default settings that are used by the OpenSolaris installer:The installation uses an existing partition or a new created Solaris fdisk partition to create a ZFS storage pool. If a second disk is available, you can add a second disk to the ZFS pool to create a mirrored configuration. This release installs an OpenSolaris system that is automatically networked by using DHCP with DNS name resolution. The nwamd daemon is enabled by default. nwamd introduces an alternate instance of the network or physical SMF service that enables automated network configuration.For further information, see the nwamd(1M) man page. The nwamd(1M) man page provides instructions about how to disable or enable the network/physical:nwam instance. IPv6 is disabled. The DNS domain and server IP addresses are retrieved from the DHCP server. The NFSv4 domain is dynamically derived. Kerberos is disabled. To start the installer from the Live CD desktop, select the Install OpenSolaris icon on the Live CD desktop.If you are prompted to log in to the Live CD, both the user name and password are jack. The root password is opensolaris. A text prompt enables you to select an installer language before the installer begins. The default language is English.The installer begins. Complete any additional selections in the preliminary installation panels.Note the following important considerations:The installation overwrites the whole disk layout if one of the following is true:The disk table cannot be read. The disk was not previously partitioned. If an existing Solaris fdisk partition is on a multiboot system, and the user makes no modifications to the existing partitions, the installation overwrites the Solaris fdisk partition only. Other existing partitions are not changed. In the Disk panel, select disk and partition location for the OpenSolaris operating system.In the top portion of the Disk panel, select the disk where the OpenSolaris operating system will be installed.The top portion of this panel displays the internal disks, external disks, and solid-state drives that are available on the system. This panel also displays the size of each disk in gigabytes.To be recognized by the installer, the disks and solid-state drives must be plugged in before the installer begins. The recommended size and minimum size for the OpenSolaris operating system installation are displayed. Disks that are too small for a successful installation are labeled as such. The recommended size is at least 9 Gbytes.A maximum of 2 Tbytes on a disk or on a partition is usable for installing the OpenSolaris 2009.06 release, even if the disk or partition is larger than 2 Tbytes. In the bottom portion of the Disk panel, click either Use the whole disk or Partition the disk.The bottom portion of this panel displays the existing disk partitioning.If the existing partition table cannot be read, a warning is displayed, and the panel displays proposed partitioning. In this case, all data on the disk is destroyed. If you choose to partition the disk, review the following partitioning guidelines, then revise the partitioning panel settings as needed.Only one Solaris partition is allowed. If an existing Solaris partition is available, that Solaris partition will be the target for the installation. Or, if you do not have an existing Solaris partition, you can change any existing partition to a Solaris partition. You can resize existing partitions, delete partitions, and create new partitions in this panel. For this option, one existing Solaris partition must be available as the target for the installation.The partitions are displayed in physically sequential order as they are laid out on the disk. Resizing a Solaris partition destroys the data on that partition and all physically subsequent partitions. Existing data is not moved to conform to a new partition layout. However, resizing the last partition or appending a new partition does not affect the data that already exists in other partitions. Non-Solaris partitions cannot be resized. To make additional space available, you can change an existing partition to Unused. However, if you change an existing partition to Unused, all subsequent non-Solaris partitions are also changed to Unused. New partitions can only use the available space that follows the last defined partition. The installer cannot utilize unallocated chunks of space between existing defined partitions. Use the fdisk(1M) command to create new partitions that use the free space between exiting partitions. If you used a third-party partitioning tool such as GParted, then the Disk panel displays a partition named Linux-swap on which you can install the OpenSolaris operating system.In this panel, use the drop-down list for the Linux-swap partition name to change the partition name to Solaris. Manual control of the OpenSolaris file system layout is not supported. During the installation, the Solaris fdisk partition is reformatted with a default ZFS file system layout. All existing file systems on the Solaris partition are destroyed.The installation uses a Solaris fdisk partition to create a ZFS storage pool.If a second disk is available, you can, after the installed system has been booted, add a second disk to the ZFS pool to create a mirrored configuration. To create a mirrored configuration, use the ZFS attach command to add a second disk to the storage pool. For example:# zpool attach rpool c0t2d0s0 c0t4d0s0The following example illustrates a ZFS file system setup with a redundant configuration:# zpool status pool: rpool state: ONLINE scrub: none requested config: NAME STATE READ WRITE CKSUM rpool ONLINE 0 0 0 mirror ONLINE 0 0 0 c0t2d0s0 ONLINE 0 0 0 c0t4d0s0 ONLINE 0 0 0 errors: No known data errors In the same panel, you can choose instead to install the OpenSolaris operating system on the whole disk.This option erases the existing disk. The entire disk is overwritten with the new OpenSolaris operating system. When you have revised the partitioning as needed, click Next. Complete time zone, date, and time settings.The next panel enables you to type the correct time zone, date, and time for the system to be installed. Select a time zone or location where the computer is typically used. The top half of the panel displays a world map with major cities marked. The bottom half of the panel provides drop-down selections. You can choose the time zone either from the map or from the drop-down list.If you select the time zone from the map, click on a city or click anywhere on the map.If you click on the map, but not on a city, the map automatically magnifies that area. You can click on a location within that magnified area. You can drag the cursor to move the magnified area to a different location on the map. When you select a site on the map, the drop-down selections automatically populate with the time zone, date, and current time for that map selection. You can right-click to deselect magnification. Instead of using the map, you can make your selections in the drop-down fields.Select your region, then select Location. Finally, select time zone. The options for each drop-down field are determined by the selection made in the prior drop-down field. You can edit the default date and time that is provided. When the settings are correct, click Next. Select language and locale, then click Next.The next panel enables you to select a language and locale. These selections determine the language support, the default date and time, and other data formats for the installed system.You can accept the default language selection or change the selection. A language selection is required. You can select “no default language support.” The language chosen automatically determines the available locales in the drop-down list. Only one locale can be selected. Any time that you log in to the installed system, you can change either the locale for that particular session or the default locale by using the Options button in the Login dialog box. Complete the user settings and click Next.Review the following guidelines:Root login is not enabled either on the Live CD or on the installed system. You must log in as the user that you create in this panel. After you log in, you can then become root to configure the system.If you do not create a user account in this panel, root is set up as a normal account on the installed system, instead of as a role. This is the only situation where you can log in to the installed system as root. For further information, see . Both the root password and user account are optional. However, for better security, complete these fields.If the root password is not defined, a reminder is displayed when you click Next. If you do not want to define a root password, you can proceed. A user account requires only a Login name for the account to be valid. For better security, however, do complete all fields.If the user account information is not valid, a reminder is displayed when you click Next. If you do not want to define a user account, you can proceed. Type a computer name or accept the default. The computer name field cannot be blank. For further information, see Setting Up Users. In the Install panel, review and confirm installation specifications.The installation begins when you click Install. Do not interrupt an installation in progress. During the installation, a progress bar is displayed.The final panel displays completion messages. You can review the installation log in this panel. You can either quit or reboot from this panel.After a successful installation, to start the installed system, select Reboot. The reboot process might take a few minutes.Eject the Live CD as the next boot begins. Or, select the “Boot from Hard Disk” option in the GRUB menu. To exit, select Quit and shut down your system. After you have installed the OpenSolaris software, if you have another operating system on your system, you might need to manually update the GRUB menu. The GRUB menu displays a list of operating systems that can be booted. Solaris and Windows operating systems are displayed automatically in the GRUB menu. The contents of the GRUB menu.lst file determine what is displayed in the GRUB menu when you boot the system. If you have installed an additional OpenSolaris release, or the Linux operating system, you will need to edit the GRUB menu.lst file to manually add these entries. For more information, see x86: Booting a Solaris System with GRUB.If you are unable to log in to your installed system, or if you want to customize the roles that were set up during the installation, see . The VirtualBox software runs as an application in your operating system, providing an environment called a virtual machine, which enables you to install other operating systems as “guests” inside the virtual machine.The VirtualBox software supports the following host operating systems.Host Operating Systems Supported Versions Windows Windows XP – All service packs Windows Server 2003 Windows Vista – 32-bit and 64-bit Linux on 32-bit and 64-bit systems Debian GNU/Linux 3.1 at minimum Fedora Core 4 at minimum Gentoo Linux Red Hat Enterprise Linux 3 at minimum SuSE Linux 9 at minimum OpenSuSE 10.1 at minimum Ubuntu 5.10 at minimum Mandriva 2007.1 and 2008.0 Apple Mac OS X (Intel) All Before running OpenSolaris inside your existing operating system, you must first install the VirtualBox application. After VirtualBox is successfully installed on your computer, you can run the OpenSolaris ISO image or the Live CD as a virtual guest “in the box.” You do not need to burn a DVD.A minimum of 10 GB of disk space or virtual disk space is recommended in order to install the VirtualBox and to install the OpenSolaris release inside the VirtualBox. To set up and run OpenSolaris inside VirtualBox, use the following procedure: Download the VirtualBox application for your operating system from the Sun Download Center.Save the application to your desktop or local disk. Download an OpenSolaris ISO image from or order a free Live CD.For convenience, save the file to the same location where you placed your VirtualBox files.The ISO image requires about 685 Mbytes on your hard drive. The download can take several minutes. Install VirtualBox, following the specific instructions for your “host” operating system: Configure VirtualBox, per instructions at . Start OpenSolaris, per the instructions at . Navigate to the downloaded VirtualBox installation files or folder.For Macintosh, this is a .dmg image file. To start the installation, double-click the VirtualBox installation file and click Next or Continue. Accept the license agreement and click Next or Continue Choose a location for the VirtualBox software, accepting the default location or modifying the location.You need 10 Gbytes or more disk space to install both VirtualBox and the OpenSolaris image. Click the Install button.If requested, enter your user password. When the completion message is displayed, click Close or Finish. Download the latest version of VirtualBox as described previously, even if your Linux distribution comes with a VirtualBox version preinstalled. The preinstalled VirtualBox software is usually the Open Source Edition (OSE), which might not be suitable for running the OpenSolaris 2009.06 release. Open a terminal window and become the root user. Navigate to the downloaded VirtualBox installation file. Depending on your Linux distribution, start the installation process by using one of the following commands:On rpm-based systems, such as Fedora, SuSE, or Red Hat, type the following:rpm -ihv filenameReplace filename with the name of the downloaded installation file. On deb-based systems, like Debian, or Ubuntu, type the following:dpkg -i filenameReplace filename with the name of the downloaded installation file. You might need to install additional packages to fulfill dependencies. The installer searches for a precompiled kernel module. If no kernel module is available that is precompiled for your system, the installer attempts to compile and install a kernel module.You need to have basic build utilities, such as gcc, make, binutils, and kernel header, installed for the installer to be able to build the kernel module. Usually, these utilities are part of the standard installation of your Linux system. If these utilities are not present, the installer will be unable to build the kernel module. In this case, install the build utilities and manually start the kernel module compilation later by running /etc/init.d vboxdrv setup as root user. Add the current user to the vboxusers group.In a terminal window, type:sudo usermod -G vboxusers -a usernameReplace username with the name of the current user. Log out and log in again to apply the changes. Open a terminal window, type VirtualBox, and press Enter to start the VirtualBox. Accept the license agreement. If you have the OpenSolaris Live CD, boot to your host operating system, then insert the Live CD. Then, open the VirtualBox application. Start VirtualBox by using one of the following steps:On Windows, click the Start button, and select VirtualBox from the list of programs. On Linux, open a terminal window, type VirtualBox, and press Enter. On Mac OS X, open Applications in the Finder and double-click VirtualBox. On the first start of VirtualBox, type your registration information and click Confirm.The main VirtualBox window appears. Click the New icon on the left side of the GUI, and click Next in the pop-up window. Type a name for your virtual machine, and from the drop-down list, select OpenSolaris as the operating system. Click Next. Select the amount of RAM to allocate to the OpenSolaris installation inside VirtualBox. Click Next.512 Mbytes is the recommended minimum size. If you have 2 Gbytes or more of memory on your system, you should choose 1 Gbyte for optimum performance. See substep C of the next step. Add a Virtual Disk Image (vdi) by selecting a name or adding a new name to the list. For the initial installation, follow these substeps:Select New and click Next. Accept the default Dynamically Expanding Image and click Next. Accept the default name, or type a path and name, and allocate space for the image. When you've completed the settings, click Next. Click Finish to create the disk image. When the initial Virtual Disk Manager GUI appears with your new vdi file selected, click Next. In the Summary screen, click Finish.The main VirtualBox window appears. Your virtual OpenSolaris machine is displayed in the left panel, and is ready to use as a virtual machine. Click the CD/DVD-ROM link on the right-hand side, in the Details tab. Check Mount CD/DVD Drive and select one of the following:If you are using the OpenSolaris Live CD, select Host CD/DVD Drive and close the Settings screen. Skip step 11. If you are using a downloaded OpenSolaris ISO image, select ISO Image File and go to step 11. In the drop-down list, select the downloaded OpenSolaris ISO image. If the ISO image is not in the list, add the image as follows:Click the Select icon in the right of the drop-down list. Click the CD/DVD Images tab. Click the Add icon. Navigate to the downloaded OpenSolaris ISO image file and click Open. Click Select and close the Settings screen. Close the Settings screen. Start VirtualBox by using one of the following options:On Windows, click the Start button and select VirtualBox from the list of programs. On Linux, select VirtualBox from the System Tools menu (GNOME desktop) or from the System menu (KDE desktop). On Mac OS X, open Applications in the Finder and double-click VirtualBox. Double-click your virtual machine icon or select it and click Start.Unless you have the ISO on a CD, click the CD/DVD-ROM link and verify that the OpenSolaris ISO image file is selected. The GRUB boot menu with three options is displayed. Then a SunOS Release message is displayed. Finally, a list of languages appears. When the list of keyboard layouts appears, press Enter to accept the English default. Or, type the number for your keyboard layout and press Enter.When you click inside the VirtualBox window with your virtual machine running, the mouse cursor is trapped inside the virtual desktop. Use the Host Key to release the mouse cursor again. The Host Key is indicated at the lower right corner of the VirtualBox window. By default, the Host Key is the right Ctrl key on Windows and Linux, and the left Cmd key on Mac OS X. When the list of desktop languages appears, press Enter to accept the English default, or type the number to select another language and then press Enter.The application takes one or two minutes to load.When the desktop screen appears, you are “in the box,” running the OpenSolaris 2009.06 release.You should install OpenSolaris to your virtual hard drive in order to be able to install programs and save configurations. To install OpenSolaris 2009.06 on your virtual hard disk, click the Install OpenSolaris icon on the OpenSolaris desktop.For installation instructions, see . If you are installing on a system and are running the Mac OS X and have installed Parallels, use the following procedure to install an OpenSolaris operating system.See “Solaris Network Driver Installation” instructions in the Parallels Desktop for Mac User Guide. During the Parallels pseudo environment setup, set the networking choice to Ethernet bridge. Using Parallels, boot the Live CD. Continue the installation of the OpenSolaris operating system.For installation instructions, see . After installation of the OpenSolaris 2009.06 release, install the network driver.For a sample installation that includes instructions for installing the network driver, see OpenSolaris in Parallels VM on Mac OS X. The following resources provide supplemental information about how to use OpenSolaris in a VirtualBox environment.Sun xVM VirtualBox Best Practices OpenSolaris VirtualBox on MacOS See the following blog for specific instructions for setting up OpenSolaris in a VirtualBox on Ubuntu.Install VirtualBox on Ubuntu Getting Started With OpenSolaris on Ubunto and VirtualBox Installing OpenSolaris on Ubuntu using VirtualBox For information about ZFS in the OpenSolaris environment, see the ZFS Documentation Hub. This document is in development for an upcoming release. Use the following information to check the set up on your installed OpenSolaris system. For information on this topic, see Administering Your Automatic Network Connection.See, also, “Networks and NWAM” topics in the OpenSolaris System Administration Topics List. For information on this topic, see How to Manually Modify the Automatic Network Configuration.See, also, “Networks by Hand” topics in the OpenSolaris System Administration Topics List. After an initial installation of OpenSolaris operating system, you will find that many of the software applications that you use on a regular basis are not immediately available to you. These software applications are available as packages in a repository for downloading and installing over the internet. A repository is a source for packages.The Image Packaging System enables users to connect to the repository and download and install packages.OpenSolaris uses IPS for its packaging system. Besides installing packages from a repository, users can create and publish their own IPS packages, set up an OpenSolaris repository, mirror an existing repository, and publish existing packages to a repository.Once you have installed packages, IPS enables you to search, update, and manage packages on your system.With IPS , you can upgrade your system to a newer build of OpenSolaris, install and update your software to the latest available versions in a repository, and retrieve packages from mirror repositories. If the system on which IPS is installed is on the network, IPS can automatically access the OpenSolaris repository. Your IPS client can access the packages from . The following repositories are available for the OpenSolaris release: – Users can access this repository to download and install software that is specifically built to run on OpenSolaris 2009.06. See the table and information in for a list of repositories that contain security fixes, access to encumbered packages and third-party non-redistributable packages. Access to these repositories may require a key and a certificate. The Package Manager application is a GUI for the IPS software. The Package Manager enables you to search, install, and remove packages; add, and modify repositories; and create and remove boot environments.You can start the Package Manager in the following ways:Desktop Menu:Select System > Administration > Package Manager. Command line:Execute the following command at the prompt:$ gksu packagemanager & The Package Manager documentation is available from the Help menu. To learn how to use the Package Manager, select About > Help.View the screencast (http://webcast-west.sun.com/>interactive/09B01790/index.html) to learn how to use the Package Manager. To locate additional Sun and third-party drivers and devices OpenSolaris, see the following resources:Wireless drivers: Select the driver name to get a list of devices supported by the driver and to get download, installation, and configuration instructions. OpenSolaris Device Drivers Community: Open Source Software Sites on the Solaris Community: Third Party Products & Solutions: Select the technology on the left side of the page, such as Ethernet or USB. Hardware Drivers on the Sun Download Center: Select the tab View by Category. Select the Hardware Drivers category. See OpenSolaris System Administration for additional instructions for setting up an installed system, including:Set up audio and video Set up printing Using basic commands Introduction to file systems Troubleshooting To explore OpenOffice word processing and spreadsheet capabilities, see Getting Started With OpenOffice.org 2.x. This document is in development for an upcoming release. The OpenSolaris release includes user accounts and RBAC roles as described in the following section. When you install the OpenSolaris release to your system, you are prompted to create a user account and a root password for your system.Review the following login, user account, and root specifications.Root login is not enabled either on the Live CD or on the installed system. You must log in as the user that you created during the installation. After you log in, you can then become root to configure the system. Because root is a role, open a terminal window and use the su command to assume the role, or the pfexec sh command to run commands in a privileged shell.If you try to log in to the installed system as root, an error message displays. Click OK and log in as the local user that you created during the installation. Root is a role per Role-Based Access Control (RBAC) specifications. However, if you do not create a user account during the installation, root is set up as a normal account on the installed system, instead of as a role. This is the only situation where you can log in to the installed system as root without manually changing the role assignment for root. After you install the OpenSolaris release, if you wish to manually change the installed system to permit root logins, remove root as an assigned role for users. Then, type the following at the command line:# rolemod K type=normal rootThis command converts root to a normal account. If you forget the local user name or password that you entered during the installation, you must boot the system into Maintenance Mode as described in . For additional instructions, see the following resources.Resource Topic rbac(5) man page Instructions for Role-Based Access Control RBAC: An Alternative to the Superuser Model Introduction to roles in the OpenSolaris environment Using RBAC (Task Map) Instructions about using existing roles or customizing roles The OpenSolaris operating system exploys the pfexec utility to execute commands with predefined attributes that the system administer specifies in user profiles. The system administrator assigns privileges to groups of users in a user profile. These privileges can restrict or permit file access for the group, restrict or permit the group's ability to perform various tasks, and so on.See the pfexec man page for complete information about using this utility. This document is in development for an upcoming release. The OpenSolaris operating system includes services such as delivering email, responding to FTP requests, or permitting remote command execution. The Service Management Facility (SMF) simplifies management of these system services. For information about managing the services on your system, see the “Service Management Facility” topics on . This document is in development for an upcoming release. The OpenSolaris 2009.06 release offers complete support for developing and deploying applications for the web. The applications needed for development of web applications are available as packages in the pkg.opensolaris.org repository. To learn how to download and install applications such as Sun Studio compilers, NetBeans, and get the tools required to set up a Web Stack Development environment, see the Setting up Your OpenSolaris Development Environment (http://wikis.sun.com/display/OpenSolarisInfo/>OpenSolaris+2008.11+Development+Environment+Guide).Additional resource include the following:Web Stack Getting Started Guide for OpenSolaris 2008.11 OpenSolaris 2008.11 Memory Thread Placement and Optimization Developer's Guide OpenSolaris 2008.11 Programming Interface Guide Getting Started With Sun Studio Software Introduction to Developing General Java Applications Develop a simple device driver with Device Driver Tutorial. Dtrace is a dynamic tracing facility that can display relevant information about kernel or user processes. See OpenSolaris 2008.11 Dynamic Tracing Guide. This document is in development for an upcoming release. After you have installed the OpenSolaris release, you can add, remove, and update packages on the system as described in the following sections. In the OpenSolaris releases, you upgrade an entire image or boot environment by using the pkg image-update command to update all the packages in that image that have available updates.To upgrade from the OpenSolaris 2008.11 release to the OpenSolaris 2009.06 release, you must use a particular procedure, which is described at Updating Your System to OpenSolaris Development Builds. Use one of the following methods to upgrade an image or boot environment:You can use the Package Manager GUI to update all installed the packages in your image to the latest available version for each package. You accomplish this task by selecting the Update All option in the GUI.For information, see The Package Manager. The OpenSolaris operating system includes an Update Manager tool on the desktop that notifies users when updates are available for the packages that are installed on their system. You can use this tool to update all the packages in your image.To manually start the Update Manager, from the Main Menubar, select System > Administration > Update Manager.For information, see The Update Manager. Alternately, you can use the pkg image-update command to perform that same task.pkg image-update [-nv]The pkg image-update command updates all packages installed on your image that have available updates. Use the -n option to perform a test run of the updates. With the -n option, the command executes, but makes no persistent changes to the image. Or, you can use the -v option. With the -v option, the update is performed with progress messages displayed during the operation.The pkg image-update command does not support zones in boot environments prior to the OpenSolaris 2008.11 release. Delete these zones before you upgrade your image to the OpenSolaris 2009.06 release. If you are using the OpenSolaris developmental builds, the pkg image-update command has no support for zones prior to build 98. Using either the Package Manager or the pkg image-update command, the process of updating all the packages automatically creates a clone: a new, bootable environment (BE). The process of updating all the packages applies the changes to the clone instead of to the original boot environment. After the successful completion of the changes to the clone and reboot of the system, the new clone is provided as the default, active boot environment in the GRUB menu. The original boot environment remains on the GRUB menu as an alternate selection.A clone of the boot environment includes everything hierarchically under the main root dataset of the original boot environment. Shared file systems are not under the root dataset and are not cloned. Instead, the boot environment accesses the original shared file systems.The pkg image-update process does not upgrade zones. If you have included zones in your OpenSolaris environment, the pkg image-update process clones these existing zones into the new boot environment, but these zones are not upgraded. You must manually upgrade each of these zones. After upgrading an image or boot environment, you can use the beadm list command to see a list of the boot environments on the system, including the new boot environment that was created by the pkg image-update command. See the following example.os# pkg image-update A clone of opensolaris exists and has been updated and activated. On next boot the Boot Environment opensolaris-1 will be mounted on '/'. Reboot when ready to switch to this updated BE. os# beadm list BE Active Active on Mountpoint Space Name reboot Used ---- ------ --------- ---------- ----- opensolaris yes no legacy 57.5K opensolaris-1 no yes - 2.59G In this example, the initial boot environment created by the installer is named “opensolaris.” The boot environment created by the pkg image-update command is automatically named “opensolaris-1.”After rebooting to the changed boot environment, any inactive boot environment can be destroyed to save space by running the beadm destroy command. For instructions, see Managing Boot Environments..For further information about the pkg command, see the OpenSolaris 2009.06 Image Packaging System Guide or the pkg(1) man page.As an alternative to upgrading an entire image or boot environment, you can update specific installed packages or package groups in the image or in the active boot environment by using either the Package Manager GUI or the pkg install command. Either method automatically checks for newer versions of specific packages or package groups, and installs them if they are available. Any dependent packages are also automatically updated.For further information about updating specific packages, see The Package Manager, the OpenSolaris 2009.06 Image Packaging System Guide, or the pkg(1) man page. A boot environment is a bootable instance of an OpenSolaris operating system image plus any other application software packages installed into that image. You can maintain multiple boot environments on your system, and each boot environment could have different software versions installed.Upon the initial installation of OpenSolaris onto your system, a boot environment is created. Use the beadm1M utility to administer additional boot environments on your system.With multiple boot environments, the process of updating software becomes a low risk operation because you can create backup boot environments before making any software updates to your system. If needed, you have the option of booting a backup boot environment.Here are some specific examples where having more than one OpenSolaris boot environment, and managing them with the beadm utility, is useful:When you use either the Package Manager tool or the pkg image-update command to update all the packages in your active OpenSolaris boot environment, this process automatically creates a clone of that boot environment. The packages are updated in the clone rather than in the original boot environment. After successfully completing the updates, the new clone is activated. Then, the clone will become the new default boot environment on the next reboot. The original boot environment remains on the GRUB menu as an alternate selection.For more information, see .You can use the beadm list command to see a list of all the boot environments on the system, including the backup boot environment that still has its original, unchanged software. If you are not satisfied with the updates made to the environment, you can use the beadm activate command to specify that the backup will become the default boot environment on the next reboot. If you are modifying a boot environment, you can take a snapshot of that environment at any stage during modifications by using the beadm create command. A snapshot is a read-only image of a dataset or boot environment at a given point in time.You can create custom names for each snapshot that identify when or why the snapshot was created. For example, if you are doing monthly upgrades to your boot environment, you can capture snapshots for each monthly upgrade. You can use the beadm list s command to view the available snapshots for a boot environment.A snapshot is not bootable. But, you can create a boot environment, based on that snapshot, by using the e option for the beadm create command. Then you can use the beadm activatecommand to specify that this boot environment will become the default boot environment on the next reboot. You can maintain more than one boot environment on your system, and perform various upgrades on each of them as needed. For example, you can clone a boot environment by using the beadm create command. A clone is a bootable copy of a boot environment. Then, you can install, test, and update different software packages on the original boot environment and on its clone.Although only one boot environment can be active at a time, you can mount an inactive boot environment by using the beadm mount command. Then you can use the pkg image-update command with the R option to update all the packages in that inactive, mounted environment. Or, use the pkg install packagename with the R option to update specific packages on that environment. You can manage the boot environments on your system either by using the beadm command or by using the Package Manager.The Package Manager is a GUI that enables you to install, update, and manage packages on your installed system. If you use the Package Manager to update all the packages on your system, a clone of the active boot environment is created. This clone enables you to, if necessary, boot into the boot environment state that existed before the update process was started.In addition, starting with the OpenSolaris 2009.06 release, you can use the Package Manager to manage your boot environments as follows:You can delete old and unused boot environments, in order to make the disk space available. You can change the default boot environment on your system. You can activate a boot environment. For instructions, see the online help that is available in the Package Manager.The Package Manager is available on the Main Menubar of the desktop, for both the OpenSolaris Live CD and the installed OpenSolaris 2009.06 system. From the Main Menubar, select System > Administration > Package Manager. Or, select the Get Software icon on the desktop.The Package Manager, however, does not provide the full range of options for managing your boot environments that is available by using the beadm command as described in the following sections.For complete instructions about managing boot environments, see Managing Boot Environments.. Or, see the . To upgrade from the OpenSolaris 2008.11 release to the OpenSolaris 2009.06 release, you must use a particular procedure, which is described at Updating Your System to OpenSolaris Development Builds. This document is in development for an upcoming release. Review the OpenSolaris Release Notes for the current release, per link at . Email troubleshooting questions to indiana-discuss@opensolaris.org. Review the troubleshooting information below. If you are unable to log in to your installed system, use the following procedure. Boot the system in single user mode.For instructions, see x86: How to Boot a System to Run Level S (Single-User Level) with two changes specific to the OpenSolaris 2009.06 release.In the instructions at this URL, use the kernel$ line option in the instructions instead of kernel line option. Before you are prompted to enter the root password using these instructions, you will need to enter an account name. The account name can be root, or any other privileged account, such as “jack” on the Live CD, or an account that you created during the installation. Optional: To view the existing users and roles, type:-bash-3.2# cat /etc/user_attr Optional: To delete a user, type:-bash-3.2# userdel username Create the user name that you want.-bash-3.2# useradd username Assign a password for the user name.-bash-3.2# passwd usernameYou will be prompted to type the password twice. Assign the root role to that user.-bash-3.2# usermod R root username Type Exit to return to the installed system. This document is in development for an upcoming release. In this OpenSolaris release, the nwamd daemon is enabled by default. nwamd introduces an alternate instance of the network or physical SMF service that enables automated network configuration. NAME: nwamd - network auto-magic daemonSYNOPSIS: /lib/inet/nwamdDESCRIPTION: nwamd is a system daemon to manage network interfaces. This daemon is started automatically and should not be invoked directly. It does not constitute a programming interface.OPERATION: Whether this daemon is enabled or not depends on your installation medium. To check, enter the following at the command line: % svcs svc:/network/physical The two instances will be listed: one as disabled, the other as online. If the nwam instance is online then this daemon will be running. The two instances correspond to the two modes of network configuration: the default instance is for manual mode, while the nwam instance is for the automatic mode. To go from manual mode to automatic mode:% svcadm disable svc:/network/physical:default % svcadm enable svc:/network/physical:nwam To go from automatic mode to manual mode:% svcadm disable svc:/network/physical:nwam % svcadm enable svc:/network/physical:defaultCAUTION: When switching modes like this, all network interfaces will be brought down then back up, thus if a different IP address is configured in this process, existing applications and sessions may be disrupted. In automatic mode, there is a limitation that only one link is active at a time. This mode is thus not recommended for machines which use more than one link at once. For machines with wired and wireless links, wired is preferred by default, although this can be adjusted by altering the order of the lines in the plain text file /etc/nwam/llp. Note, however, that this interface is Volatile and may change in a future release. PROFILES: Note that all interfaces listed in this section are Volatile and may change in a future release. They are documented here so that those wishing to experiment with this may do so. Profiles are a mechanism for making multiple related changes to the system configuration after IP service is available. There is not direct support for them yet, but a “roll your own” mechanism is provided for now. Once an interface is brought up and an IP address is configured for it, the daemon looks for /etc/nwam/ulp/check-conditions; if it exists and is executable, it is run. This is expected to print a single line of output, which is the name of the profile which the user wishes to be activated based on the current conditions. If such a line is read successfully (foo in this example), then /etc/nwam/ulp/foo/bringup is executed. Likewise, when the interface gets torn down for whatever reason, /etc/nwam/ulp/foo/teardown is executed. The bringup and teardown scripts are invoked via pfexec1 with default basic privileges. Samples for each of these scripts can be found at: WIRELESS: When no wired link is available, a scan for wireless LANs will be done, and the resulting list offered via a GUI pop-up to prompt the console user to select his/her preference. If a successful connection is made, the WLAN in question will be stored in the plain text file /etc/nwam/known_wifi_nets and subsequently the daemon may connect to any WLAN in that list without prompting again. Should a user wish to revoke his/her preference for a WLAN in that list, editing the file and deleting the line with the entry should suffice. Note, however, that this interface is Volatile and may change in a future release.ATTRIBUTE: See attributes5 for descriptions of the following attributes:ATTRIBUTE TYPE ATTRIBUTE VALUE Availability SUNWcsr Interface Stability Volatile SEE ALSO: svcs1, svcadm1M, attributes5, smf5NOTES: The networking service is managed by the service management facility, smf5, under the service identifier: svc:/network/physicalAdministrative actions on this service, such as enabling, disabling, or requesting restart, can be performed using svcadm1M. The service's status can be queried using the svcs1 command. This document is in development for an upcoming release. The new beadm utility enables you to perform the following tasks:Create a new boot environment based on the active boot environment Create a new boot environment based on an inactive boot environment Create a snapshot of an existing boot environment Create a new boot environment based on an existing snapshot Create a new boot environment and add a custom title to the GRUB menu. Activate an existing, inactive boot environment Mount a boot environment Unmount a boot environment Destroy a boot environment Destroy a snapshot of a boot environment Rename an existing, inactive boot environment Display information about your boot environment snapshots and datasets The beadm command, /usr/sbin/beadm, enables users to manage their boot environments. The following table summarizes the subcommands and options for the beadm utility.Subcommands Description beadm Displays command usage. beadm activate Makes beName the active boot environment on next reboot.Syntax: beadm activate beName beadm create Creates a new boot environment name, beName. Unless the e option is provided, the new boot environment is created as a clone of the currently running boot environment.Syntax: beadm create [-a] [-d description] [-e non-activeBeName | beName@snapshot] [-o property=value] beName-a – Activate the newly created boot environment upon creation. The default is to not activate the newly created boot environment. -d description – Use this description as the title in the GRUB menu that describes this new boot environment. If this option is not used, beName is used for the title. -e non-activeBeName – Create a new boot environment from an existing, inactive boot environment. The default is to create the boot environment from the active boot environment. -e beName@snapshot – Create a new boot environment from an existing snapshot of the boot environment named beName. -o property=value – Create the datasets for new boot environment with specific ZFS properties. Multiple -o options can be specified. See zfs(1M) for more information on the o option. beName – Name of the boot environment to create. beName@snapshot – Name of an existing snapshot of the boot environment named beName. beadm create beName@snapshot Creates a snapshot of the existing boot environment named beName.Syntax: beadm create beName@snapshotbeName@snapshot – The snapshot name must use the format, beName@snapshotdescription, where beName is the name of an existing boot environment that you want to make a snapshot from. Enter a custom snapshotdescription to identify the date or purpose of the snapshot. beadm destroy Destroys the boot environment named beName or destroys an existing snapshot, beName@snapshot, of a boot environment. Prompts for confirmation before destroying the boot environment.Syntax: beadm destroy [-fF] beName | beName@snapshot-f – Forces destruction of the boot environment even if it is mounted. -F – Forces destruction of the boot environment without prompting for confirmation. beadm list Lists information about the existing boot environment, which is beName, or lists information for all boot environments if beName is not provided. The default is to list boot environments without any additional information.Syntax: beadm list [-a | [-ds] [-H] [beName]-a – Lists all available information about the boot environment. This information includes subordinate datasets and snapshots. -d – Lists information about all subordinate datasets hat belong to the boot environment. -s – Lists information about the snapshots of the boot environment. -H – Prevents listing header information. Each field in the output is separated by a semicolon.The example is displayed without a header:BE2:no:yes:mounted:/pool1/BE/BE2:6.2G;;;Without header information, the display information is identified by the following delimiters:; – Delimits boot environments, datasets, zones, and snapshots. : – Delimits attributes for boot environments, datasets, zones, and snapshots. , – Delimits multiple datasets, zones, and snapshots. Multiple boot environments are delimited with a return, a blank line. The p option can be combined with the other options. beName – If beName is not provided, the command results display information for all boot environments. beadm mount Mounts a boot environment named beName at mount point. The mount point must be an already existing, empty directory.Syntax: beadm mount beName mountpoint beadm rename Renames the boot environment named beName to newBeName.Syntax: beadm rename beName newBeName beadm unmount Unmounts the boot environment named beName.Syntax: beadm unmount [-f] beName-f – Forcefully unmounts the boot environment even if it is currently busy. For detailed instructions about the beadm utility, see the beadm1M man page. tbd TBD