Solaris 1. 0 1/0. Software - Solaris 1. Release Notes. The following bugs and issues apply to Solaris 1. New Minimum Memory Requirement. Beginning with the Solaris 1. Mbytes of RAM to run the Solaris software. Changes in Upgrade Support for Solaris Releases. Starting with the Solaris 1. Solaris OS. only from the following releases: Solaris 8 OSSolaris 9 OSSolaris 1. OSTo upgrade releases previous to the Solaris 8 software to the Solaris. Solaris 10 zones: part one – a working example. Many of you have already heard about Solaris 10 zones. Hello To know if a third party system works with solaris 10 or solaris 11 and the. As a follow up the problem appears to be in recent kernel patch updates. The original Solaris 10. I have added a custom zone. How to create Solaris 8 & 9 Branded Zones in Solaris 10. Branded zones are solaris 8 or solaris 9 containers created in a solaris 10 Global zone. Solaris Container software Patch Name to download. Solaris 10 Kernel PatchID Sequence. The Solaris 10 5/08 Patch Bundle is designed to enable customers to bring. The Zones Update on Attach Feature and Patching in the Solaris 10 OS. Enda O'Connor, June 2009. Since the Solaris 10 5/08 Operating System, system administrators have had the ability to detach and attach zones. Solaris 10 Get latest Installed patches. How to update solaris 10 to be safe from shellshock bug? How to Apply a Patch to the Global Zone Only global# patchadd -G patch Then upgrade to the Solaris 1. Solaris Live Upgrade and Solaris Zones. Using Solaris Live Upgrade in conjunction with Solaris zones is not supported. If. you have installed non- global zones on a Solaris 1. Solaris 1. 0 1/0. Solaris Live Upgrade. If you use the luupgrade command, the following error message is displayed: Unable to upgrade boot environment. Workaround: To upgrade such a system, use either the Solaris interactive installation program. Jump. Start program. These programs apply to your Solaris 1. OS. all the patches and new packages that represent the differences between your current. OS and the Solaris 1. The programs also apply the packages. Both programs have limitations. For example, you cannot customize your upgrade by installing. You must now unpack the miniroot. See the following for the detailed steps: Correct Solaris Data Encryption Supplement Required for Installation of Solaris 1. Release. When you install the Solaris 1. Solaris Data Encryption Supplement that corresponds to the release. The supplement is delivered in. SUNWcry and SUNWcryr packages. If you do not have the correct. Patch ID 1. 18. 56. SPARC based systems. Patch ID 1. 18. 56. To determine your current supplement version, use showrev- p. Additional Procedures Required When Installing Patches for Solaris 1. Release. The following patches are applied to resolve problems that were reported in CR. CR 6. 21. 42. 22: Patch ID 1. SPARC based systems. Patch ID 1. 19. 36. The sections that follow provide further steps that you must perform to completely. Resolving Issues With the GNOME Display Manager (6. Note - Perform this procedure before you use the GNOME Display Manager (GDM) as your. GDM as your login. Otherwise, you can skip this procedure. When applying the patch, load new values into the GDM configuration files. Then you can start the GDM application. Manually merge the differences in the factory- gdm. Perform this step if you have modified the gdm. When merging files, copy the values for the following commands from the factory- gdm. These commands enable you to obtain the best OS performance. Reboot. Command. Halt. Command. Suspend. Command. Default. Path. Root. Path. Graphical. Theme. To restart GDM, perform the following steps: Become superuser. Issue the following command: # svcadm disable application/gdm. In the console that is now displayed, press Return to display a command prompt. To restart GDM, issue the following command: # svcadm enable application/gdm. Resolving Issues With Access. Key. Mouse. Listeners (6. To further resolve problems that are reported in CR 6. Change to the /etc/X1. Copy the files from factory- Access. Dwell. Mouse. Events to Access. Dwell. Mouse. Events. Copy the files from factory- Access. Key. Mouse. Events to Access. Key. Mouse. Events. Restart GDM by following the steps that are provided in the previous section. Cannot Configure Full- Screen Magnification on Systems With One Video Card. If your Solaris 1. For such a configuration, you must use. First, make sure that the Xserver is not running. Then perform the. Log in to a command- line session. If you are using the GNOME Display Manager, follow these steps: Log in to a session as superuser. At the prompt, type svcadm disable application/gdm. Log in again as superuser. If you are using dtlogin, follow these steps: In the dtlogin window, click Options and select Command Line Login. Log in as superuser. Create a new xorg. X1. 1/bin/Xorg - configure. The command creates the file xorg. Copy the new configuration file to the /etc/x. X1. 1/xorg. conf. Modify the configurations in the file by using the following sample configurations: Add a new monitor section. Section . The value in Kbytes must be large enough for the intended screen. For example, you can compute the value by using the formula width * height * bpp/8. Add a new screen section. Section . However, full- screen magnification is now available. Problems Configuring USB Mouse Device as Extension Device for Use With GNOME On- Screen Keyboard. You cannot set up a USB mouse device as an extension device. GNOME On- Screen Keyboard (GOK). The configuration fails when you are setting. USB mouse device while using a PS2 mouse device as the. To properly set up the USB mouse, follow these steps. Log in as superuser. While the USB mouse device is unplugged, type the following in a terminal window: # ls - l /dev/usb/hid*Connect the USB mouse and type the previous command again. Record the path of the USB mouse that is displayed on the screen. Log in to a command- line session. If you are using the GNOME Display Manager, follow these steps: Log in to a session as superuser. At the prompt, type svcadm disable application/gdm. Log in again as superuser. If you are using dtlogin, follow these steps: In the dtlogin window, click Options and select Command Line Login. Log in as superuser. Create a new xorg. X1. 1/bin/Xorg - configure. The command creates the file xorg. Copy the new configuration file to the /etc/x. X1. 1/xorg. conf. Modify the configurations in the file: In the Server. Layout section, add an input device for Mouse. Input. Device . See the following example: Input. Device . Use the path in Step 4 to replace /dev/usb/hid. Save the file and exit. Reboot the system from the appropriate command- line session: If you are using GDM, perform the following: Type svcadm enable application/gdm. Reboot the system. If you are using dtlogin, reboot the system. Log in to the accessible UI user's account. Enable Assistive Technology Support by clicking Launch Menu => Preferences => Accessibility => Assistive Technology Support. Log out of the system then log in to the accessible UI user's account again. Open a terminal window and type the following command: % /usr/sfw/bin/gok - -select- action=switch. In the GOK window, click GOK and select Preferences. If necessary, set up GOK to the accessible UI user's needs. Otherwise, to accept the current setup, click Apply then click OK in the GOK Preferences window. Exit GOK and then restart it by clicking Launch Menu => Applications => Accessibility => On- Screen Keyboard. The following warning message might be displayed: The device you are using to control GOK is. Click OK. Exit GOK and then repeat steps 1. The warning message is no longer displayed. Star. Office Patch Application Requires Additional Steps. The following patches are applied to the Solaris OS to resolve Star. Office. problems that were reported in CR 6. CR 6. 26. 28. 30: For SPARC based systems. Patch ID 1. 19. 41. Patch ID 1. 19. 90. For x. 86 based systems: Patch ID 1. Patch ID 1. 19. 90. To completely resolve the reported problems, perform the following steps after applying the. These steps enable you to use Star. Office 7 Product 5 software to. Open. Document files that were created in Star. Office 8. software. Become superuser. Issue the following command: # update- mime- database /usr/share/mime. Log out of the system and then log in again. SPARC: Upgrade Hangs on Sun Blade 1. Workstations (6. 36. Upgrading to the Solaris 1. DVD media. The problem affects certain Sun Blade. JLMS DVD drive. The error occurs. Solaris interactive installation program. Solaris Live Upgrade. When the system hangs, no error messages are displayed. Workaround: To upgrade such a system, use a network installation image. Failure of BIOS Device Utility Prevents Installation or Upgrade From Being Completed (6. On certain occasions, the utility for BIOS devices (/sbin/biosdev) might fail and. The failure can occur under either of. Patch ID 1. 17. 43. The system contains two or more identical disks that have identical fdisk partitions. The following error message is displayed: biosdev: Could not match any!! Workaround: Make sure that you reboot the system after applying Patch ID 1. To change the layouts, perform the following steps. Become superuser. Start the disk maintenance utility.# format. A list of available disks in the system is displayed. To select the disk whose fdisk partition you want to change, type the disk's number. From the list of Format options, select fdisk. The disk's partition information and a list of fdisk options are displayed. To change the disk's layout, choose one of the following: To specify a different active partition, press 2. To add another disk partition, press 1. To delete an unused partition, press 3. To save your changes and exit the fdisk menu, press 5. To exit the disk maintenance utility, select Quit from the Format options. Reboot the system. After the system reboots, verify that the error message no longer appears. As superuser, type the following command: # /sbin/biosdev. If the error message is still generated, repeat the procedure but select a different option in Step 5. If the system contains other identical disks with identical fdisk- partition layouts, repeat Steps 1- 9 on these disks. Otherwise, you can proceed with your Solaris installation or upgrade. Locale Problem Occurs After You Upgrade a System That Contains Zones (6. A locale problem occurs when you use the GUI- based installation program to. After the installation, the LANG variable in the. If you issue any system command, the. Workaround: As superuser, choose one of the following workarounds: Workaround 1: If you have already upgraded the system, manually edit the /etc/default/init file to set the correct LANG and LC. Then reboot the system. For more information and examples, see the locale(1) man page. Workaround 2: Use the text- based installation program to upgrade the system. Perform either of the following steps that is appropriate to your system: For SPARC systems, use the text flag with the boot command.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2016
Categories |