Go to main content

Transitioning From Oracle® Solaris 10 to Oracle Solaris 11.3

Exit Print View

Updated: December 2018

Additional Installation Tasks

You might need to perform the following additional tasks before or after an installation.

Reconfiguring Date and Time Before and After an Installation

Oracle Solaris 11 keeps the Real Time Clock (RTC) in Coordinated Universal time (UTC) format. The behavior on x86 platforms is different in this release than in Oracle Solaris 10. The interactive installers enable you to configure the date and time during the installation. As part of that process, the RTC is updated with the time in UTC format. However, AI does not adjust the RTC date and time during an installation. To ensure that the time stamp of installed files is correct, configure the time in the BIOS in UTC format before beginning the installation. On x86 platforms, when using the pkg update command, the OS continues to keep time in RTC in the local time format. This method is used to avoid time inconsistencies between Oracle Solaris 11 BEs and BEs from previous releases.

Note -  If you are running Oracle Solaris 11 as an Oracle VM VirtualBox guest, check or uncheck the Hardware Clock in UTC time setting in the system preferences for the virtual machine.

Switching From Local Time Format to UTC Format

To switch from local time format to UTC format, set the time lag between the kernel and RTC to 0 (zero) as follows:

# rtc -z GMT

If the date/time requires an adjustment, use the date command. See date(1).

Switching From UTC Format to Local Time Format

When the switch from UTC to local time is complete, and each time you reconfigure the time zone setting by using the sysconfig command, run the rtc timezone command with the –z option as follows:

# rtc -z timezone

Maintaining Local Time on a System Running Multiple Operating Systems That Keep RTC Time as Local Time

    If you maintain and boot several operating systems on the same Oracle Solaris 11 system, and those operating systems keep RTC time as local time, there are several ways that these operating systems can coexist, from the RTC time point of view:

  • Switch from local time to UTC format in the OS that keeps RTC time in local time format.

    For example, if you are dual-booting Windows 7, set the registry key as follows:

    [HKEY_LOCAL_MACHINESYSTEM\CurrentControlSet\Control\TimeZoneInformation] \
  • Switch from the UTC format to local time on a freshly installed Oracle Solaris 11 system.

  • Enable the Network Time Protocol (NTP) in operating systems that assume that the RTC format is running in local time. In this case, the time is synchronized automatically.

Monitoring the Live Media Startup Process

Switching to the text boot screen is useful if you suspect that the system startup process is not proceeding normally. The text screen might contain informational messages or a request for user input. Switching to the text boot screen has no impact on the boot sequence, other than how the information is displayed on the screen. Initialization of the operating system continues and completes as normal.

To switch to a text boot, press any key a few seconds after the GUI boot screen appears and the progress animation begins. Note that after switching from the GUI boot to a text boot, you cannot switch back to the GUI boot screen.

x86: Adding Custom Entries to the GRUB Menu After an Installation

Starting with Oracle Solaris 11.1, GRUB 2 is the default boot loader on x86 platforms. GRUB 2 uses a different configuration file (grub.cfg) than the menu.lst file that is used by GRUB Legacy. The grub.cfg file contains most of the GRUB configuration, including all Oracle Solaris menu entries. Unlike the menu.lst file, you manage the grub.cfg file solely by using the bootadm command. Do not directly edit this file.

Also, the grub.cfg file does not contain any custom menu entries. For custom menu entries, there is an additional configuration file (custom.cfg) that you can use. Before adding custom menu entries to the custom.cfg first, you first have to create the file and then store it in the same location as the grub.cfg and menu.conf files (/pool-name/boot/grub/) are stored.

During the boot process, GRUB checks for the existence of a custom.cfg file in the toplevel dataset of the root pool, in the boot/grub subdirectory. If the file exists, GRUB sources the file and then processes any commands within the file as though the contents were textually inserted in the main grub.cfg file.

For example, on a system with 64-bit UEFI firmware, custom.cfg file entries might appear as follows:

menuentry "Windows (64-bit UEFI)" {
insmod part_gpt
insmod fat
insmod search_fs_uuid
insmod chain
search --fs-uuid --no-floppy --set=root cafe-f4ee
chainloader /efi/Microsoft/Boot/bootmgfw.efi

On a system with BIOS firmware, entries in this file might appear as follows:

menuentry "Windows" {
insmod chain
set root=(hd0,msdos1)
chainloader --force +1

See Customizing the GRUB Configuration in Booting and Shutting Down Oracle Solaris 11.3 Systems.

Additional Installation Troubleshooting Information