OpenSolaris
Collectives
Discussions
Documentation
Download
Source Browser
Free CD
Log-in
|
en
Project indiana
:
ReleaseNotes2008.11
Top Menu
Show
:
Comments
Attachments
History
Information
Print
:
Print
Print preview
Export as PDF
Export as RTF
Export as HTML
Export as XAR
Wiki code for
ReleaseNotes2008.11
Hide Line numbers
1: == Release Notes for the OpenSolaris 2008.11 Release 2: 3: Languages**Translation for this page** 4: EnglishDeutschEspañolFrançaisItaliano日本語한국어Português BrasileiroPусский简体中文繁體中文 5: 6: This page lists the Release Notes for the OpenSolaris 2008.11 release. For additional information on the following issues, look up the bug number in [[Bugzilla>>http://defect.opensolaris.org/bz/]]. 7: 8: For information about the new features in the OpenSolaris 2008.11 release, see [[What’s New in OpenSolaris 2008.11>>http://www.opensolaris.com/learn/features/whats-new/200811/]]. 9: 10: **Note:** For information about upgrading your system to the OpenSolaris 2008.11 release from a previous release, see [[ Upgrading OpenSolaris 2008.05 to Later Versions of OpenSolaris>>Project indiana.image-update]]. 11: 12: [[Installing OpenSolaris on Systems With Low Memory.>>#Low_Mem]] 13: 14: [[64 - Installer, but not Desktop, Allows Empty Passwords.>>#64]] 15: 16: [[1156 - Booting a BE That Was Left Mounted Before the Reboot Fails. >>#1156]] 17: 18: [[1161 - GUI Installer Shrinks the Solaris Partition to be Created Even if Enough Available Space is Reported on the Disk Screen.>>#1161]] 19: 20: [[1559 - GRUB Entry for Windows Incorrect From USB Stick Install. >>#1559]] 21: 22: [[1565 - Nautilus Process Hangs After GNOME Login.>>#1565]] 23: 24: [[1685 - Renaming a Busy BE Might Fail.>>#1685]] 25: 26: [[2656 - Enabling the printers:snmp Service Causes System to Revert to Maintenance State.>>#2656]] 27: 28: [[2900 - Firefox dumps core in NV95.>>#2900]] 29: 30: [[3691 - Using Fast Reboot When Specifying the Name of a BE Fails.>>#3691]] 31: 32: [[3783 - Installer Fails if the User Creates or Imports the ZFS Pool rpool.>>#3783]] 33: 34: [[3947 - Distribution Constructor Does Not Recognize ZFS File System Mountpoints for Build Areas.>>#3947]] 35: 36: [[4061 - Only the First GRUB menu.lst Entry of the Source BE Is Created When Creating a New BE.>>#4061]] 37: 38: [[4166 - Automated Installer Hangs on a 1 GB System Without Swap.>>#4166]] 39: 40: [[4215 - Automatic Install Does Not Set the root Role and the Primary Administrator Profile to the Created User Account.>>#4215]] 41: 42: [[4246 - User and Root Passwords are Not Encrypted in the SC Manifest.>>#4246]] 43: 44: [[4248 - ICT reset_image_UUID Fails for Automated Installer if authname is Not Set to opensolaris.org.>>#4248]] 45: 46: [[4282 - Trackerd Does Not Start by Default on OpenSolaris.>>#4282]] 47: 48: [[4294 - Distribution Constructor Fails if Compressed ZFS Dataset Is Used as the Build Area.>>#4294]] 49: 50: [[4300 - Automated Installer Fails to Access the IPS Repository.>>#4300]] 51: 52: [[4488 - Automated Installer Services Should be Started Manually if the Install Server Is Reboooted.>>#4488]] 53: 54: [[4586 - Distribution Constructor Pause and Resume Functionality Might Fail.>>#4586]] 55: 56: [[4589 - Exception Message Generated by Distribution Constructor Upon Successful Termination.>>#4589]] 57: 58: [[4629 - Timezone Cannot be Customized if Automated Installer is Used for Installation.>>#4629]] 59: 60: [[4636 - Distribution Constructor Might Dump Core When Running the br-config Finalizer Script.>>#4636]] 61: 62: [[4645 - The Graphical Boot Progress Bar Hides sys-unconfig Questions at Boot Time.>>#4645]] 63: 64: [[4881 - Input Language Cannot be Switched When Russian Keyboard Layout Is Selected.>>#4881]] 65: 66: [[5003 - Crash Dumps Are Not Saved to the File System at Boot Time By Default.>>#5003]] 67: 68: [[5012 - Using sys-unconfig to Unconfigure the Network Fails.>>#5012]] 69: 70: [[5092 - pkg and packagemanager Fail to Start.>>#5092]] 71: 72: [[5146 - Live CD With Primary Languages Contains Default Locales Only.>>#5146]] 73: 74: [[5277 - Issues With the IIIM Daemon.>>#5277]] 75: 76: [[5302 - Automated Install Manifest Criteria Are Lost.>>#5302]] 77: 78: [[5473 - en_US/es_ES/fr_FR/de_DE UTF-8 Locales Might Not be Installed by pkg image-update.>>#5473]] 79: 80: [[5492 - pkg(1) Does Not Uninstall Packages When The System Is Installed From a Global Live CD.>>#5492]] 81: 82: [[5543 - Tracker Does Not Index the Home Directory by Default.>>#5543]] 83: 84: [[5544 - Tracker Cannot Search Evolution Emails.>>#5544]] 85: 86: [[5588 - Cannot Use the su(1M) to Get root Privileges in the Automated Installer.>>#5588]] 87: 88: [[6464201 - Loop Back Mounts of the ZFS File Systems Causes the svc:/system/filesystem/local:default SMF Service to Fail.>>#6464201]] 89: 90: [[6670311 - Installer Might Fail if the Linux Swap Primary Partition Precedes the Solaris Partition.>>#6670311]] 91: 92: [[6687328 - vim Command Cannot Display Multibyte Characters.>>#6687328]] 93: 94: [[6694783 - Input Method Duplicate Causes IDE Crash.>>#6694783]] 95: 96: [[6696145 - Install Might Cause Panics on Intel 965 With GM965 Chipset.>>#6696145]] 97: 98: [[6742850 - CJK Characters Do Not Display Correctly in the Java Application Environment.>>#6742850]] 99: 100: [[6773520 - Issues With the Slovak Keyboard.>>#6773520]] 101: 102: [[6775600 - Audio Is Unavailable After Installation of OpenSolaris 2008.11 RC2.>>#6775600]] 103: 104: ==== Installing OpenSolaris on Systems With Low Memory 105: 106: ===== Description 107: 108: OpenSolaris supports installation through its Live CD on systems or virtual machines that contain at least 512 MB of RAM. The following limitations exist on systems with low memory. 109: 110: While basic desktop functions and installation functions work well, attempting to use the Live CD as a full-blown user environment might cause issues. However, an installed system functions normally with 512 MB of RAM. 111: 112: The Live CD supports booting the OpenSolaris kernel in either 32-bit mode or 64-bit mode depending on the capabilities of the underlying hardware. The OS will boot in the 64-bit mode only if the system has atleast 1000 MB of RAM. Systems with less than this amount will boot in the 32-bit mode. This limitation does not apply to the installed system. 113: 114: It is not possible to start the **’Read the Release Notes’** link from within the GUI Installer on systems with 512 MB of RAM. Attempting to open this link causes the system to freeze while loading Firefox. Therefore users are recommended to read the Release Notes prior to launching the GUI Installer. 115: 116: On systems with less than 700 MB of RAM the installer will create a dedicated swap slice instead of a ZFS volume to use for system swap. 117: 118: For more information about the enhancements that were made for the OpenSolaris 2008.11 release to support installation on systems with low memory, see [[# 3597>>http://defect.opensolaris.org/bz/show_bug.cgi?id=3597]] Unable to install OpenSolaris with 512 MB Base Memory. 119: 120: ==== [[# 64>>http://defect.opensolaris.org/bz/show_bug.cgi?id=64]] Installer, but not Desktop, Allows Empty Passwords 121: 122: ===== Description 123: 124: If, during installation, no root password is entered and no user account is created, you will not be able to log in to the installed system. 125: 126: ===== Workaround 127: 128: Choose one of the following workarounds: 129: 130: * Enter a root password as follows: 131: *1. During boot, type “e” in the grub menu twice, in order to edit the boot entry. 132: *1. Add -s to the end of the boot entry, and boot with this line. 133: *1. Log in as root and use the passwd command to enter a password. 134: *1. Restart the system. Boot normally, and log in with the new password. 135: * Set root so that it does not require a password as follows: 136: *1. During boot, type “e” in the grub menu twice, in order to edit the boot entry. 137: *1. Add -s to the end of the boot entry, and boot with this line. 138: *1. Log in to the system as root. 139: *1. Edit the /etc/X11/gdm/custom.conf file so that the value of PasswordRequired is false. 140: 141: ==== [[# 1156>>http://defect.opensolaris.org/bz/show_bug.cgi?id=1156]] Booting a BE That Was Left Mounted Before the Reboot Fails 142: 143: ===== Description 144: 145: If a boot environment (BE) is mounted by using the beadm mount command and the system is rebooted before that BE is unmounted, selecting that BE from the GRUB menu causes a boot failure. 146: 147: If a BE is activated by using the beadm activate command, this BE is the default selection in the GRUB menu. Therefore, leaving this BE mounted before a reboot causes a boot failure. 148: 149: A typical boot error message is: 150: 151: {{{ 152: Use is subject to license terms. 153: Hostname: opensolaris 154: Apr 28 16:05:08 svc.startd[7]: svc:/system/sysevent:default: Method 155: "/lib/svc/method/svc-syseventd start" failed with exit status 95. 156: Apr 28 16:05:08 svc.startd[7]: system/sysevent:default failed fatally: 157: transition to maintenance (see ’svcs -xv’ for details) 158: ’/usr/sbin/pmconfig: cannot open/create "/etc/.cpr_config", Bad file number 159: Requesting System Maintenance Mode 160: (See /lib/svc/share/README for more information.) 161: Console login service(s) cannot run 162: 163: Root password for system maintenance (control-d to bypass): 164: }}} 165: 166: ===== Workaround 167: 168: Use the following procedure: 169: 170: 1. Reboot the system and select the previously active BE. 171: 1. When the system is up, reset the mount point of the activated BE by typing the following command as root user: 172: 173: {{{ 174: # beadm unmount //boot_environment// 175: }}} 176: 177: 1. Reboot the system. 178: 179: ==== [[# 1161>>http://defect.opensolaris.org/bz/show_bug.cgi?id=1161]] GUI Installer Shrinks the Solaris Partition to be Created Even if Enough Available Space is Reported on the Disk Screen 180: 181: ===== Description 182: 183: When creating a Solaris partition, the GUI installer only utilizes the free space at the end of the disk after the last primary partition. However, the sum of the total space available including gaps between partitions is reported on the disk screen. If the user tries to create a Solaris partition which is larger than the amount of free space available at the end of the disk, the size of Solaris partition is adjusted. 184: 185: A warning message is displayed when the Next button is pressed on the disk screen and the Solaris partition is shrunk. The title of the warning message is as follows: 186: 187: {{{ 188: Adjustments were made to the new partitions 189: }}} 190: 191: ===== Workaround 192: 193: Use the Solaris fdisk(1M) tool or the GParted tool to create a Solaris2 partition. These tools enable the utilization of unallocated space between already defined partitions. Select the newly created Solaris2 partition as the target for the installation on the installer disk screen. 194: 195: ==== [[# 1559>>http://defect.opensolaris.org/bz/show_bug.cgi?id=1559]] GRUB Entry for Windows Incorrect From USB Stick Install 196: 197: ===== Description 198: 199: When the OpenSolaris 2008.11 release is installed from a USB stick, the GRUB entry for Windows does not reference the correct disk device. 200: 201: ===== Workaround 202: 203: Edit the /rpool/boot/grub/menu.lst file. Modify the rootnoverify entry in that file. 204: 205: Typically a USB installed system will have the following entry: 206: 207: {{{ 208: rootnoverify 209: 210: (hd1,0) 211: }}} 212: 213: This entry should be changed to the following: 214: 215: {{{ 216: rootnoverify (hd0,0) 217: 218: #~---------- ADDED BY BOOTADM - DO NOT EDIT ~---------- 219: title Windows 220: rootnoverify (hd0,0) 221: chainloader +1 222: #~------------------- END BOOTADM ~-------------------- 223: }}} 224: 225: If a diagnostic partition exists, a similar change is required. 226: 227: ==== [[# 1565>>http://defect.opensolaris.org/bz/show_bug.cgi?id=1565]] Nautilus Process Hangs After GNOME Login 228: 229: ===== Description 230: 231: When you log in to the GNOME desktop, Nautilus might hang. In this case, the desktop background is a solid, blue-gray color and right-clicking on the background does not open a menu. The nautilus-debug-log.txt is added in your home directory. 232: 233: If Nautilus hangs, it can consume 50% of the CPU time. 234: 235: ===== Workaround 236: 237: Manually kill the broken Nautilus process as follows: 238: 239: 1. Launch a GNOME terminal by selecting Applications->System Tool->Terminal on the menu bar. 240: 1. Kill the oldest nautilus process in the gnome-terminal. For example: 241: 242: {{{ 243: bash$ ps -ef | 244: grep naut 245: test 13425 13374 0 19:59:30 ? 0:00 nautilus ~--no-default-window 246: ~--sm-client-id default2 247: test 13227 1 50 17:39:39 ? 39:36 nautilus ~--no-default-window 248: ~--sm-client-id default2 249: bash$ kill 13227 250: }}} 251: 252: 1. Log out. 253: 254: ==== [[# 1685>>http://defect.opensolaris.org/bz/show_bug.cgi?id=1685]] Renaming a Busy BE Might Fail 255: 256: ===== Description 257: 258: Renaming a boot environment (BE) might fail if the BE has a dependent clone that is currently mounted or otherwise busy. 259: 260: A typical example of this situation is when the live BE has been successfully upgraded. If you then try to rename the auto-generated and upgraded BE, the renaming fails. The renaming fails because the upgraded BE has been activated and the live BE is now its clone. 261: 262: ===== Workaround 263: 264: Use the following procedure: 265: 266: 1. Activate the live BE. 267: 1. Rename the upgraded BE. 268: 1. Activate the upgraded BE. 269: 270: For example, if the live BE name is “opensolaris”, and the auto-generated BE name of the upgraded BE is “opensolaris-1,” use the following commands: 271: 272: {{{ 273: # beadm activate //opensolaris// 274: # beadm rename //opensolaris-1 new_name// 275: # beadm activate //new_name// 276: }}} 277: 278: ==== [[ # 2656>>http://defect.opensolaris.org/bz/show_bug.cgi?id=2656]] Enabling the printers:snmp Service Causes System to Revert to Maintenance State 279: 280: ===== Description 281: 282: After installing the OpenSolaris 2008.11 release, the hald-addon-network-discovery agent cannot be enabled. This failure occurs whether you try to enable the service from the desktop or from the command line. 283: 284: Note - This problem does not occur on systems running a supported Solaris Express Community release. 285: 286: An error message similar to the following is displayed in the service log: 287: 288: {{{ 289: [ Jul 24 21:09:32 Executing start method 290: ("/lib/svc/method/svc-network-discovery start snmp"). ] 291: /usr/bin/dbus-send ~--system ~--print-reply ~--dest=org.freedesktop.Hal 292: ~--type=method_call /org/freedesktop/Hal/devices/network_attached 293: org.freedesktop.Hal.Device.NetworkDiscovery.EnablePrinterScanningViaSNMP 294: int32:60 string:public string:<IP_ADDRESS> 295: Error org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible 296: causes include: the remote application did not send a reply, the message bus 297: security policy blocked the reply, the reply timeout expired, or the network 298: connection was broken. 299: [ Jul 24 21:09:40 Method "start" exited with status 1. ] 300: }}} 301: 302: ===== Workaround 303: 304: Use the following procedure: 305: 306: 1. Add the SUNWSmmgr package. 307: 308: {{{ 309: # pkg install SUNWSmmgr 310: }}} 311: 312: 1. Restart the HAL add-on module. 313: - To restart the add-on module from the desktop, perform these steps: 314: 11. Open the Services settings application from the main menu. 315: System-> Administration-> Services 316: The Services settings window is displayed. 317: 11. Select the Hardware Abstraction Layer network attached device discovery option (network/device-discovery/printers:snmp). 318: 11. Click OK to save the changes. 319: - To restart the add-on module from the command line, type: 320: 321: {{{ 322: # svcadm restart 323: hal 324: }}} 325: 326: 1. Clear the printers:snmp service. 327: 328: {{{ 329: # svcadm clear printers:snmp 330: }}} 331: 332: ==== [[ # 2900>>http://defect.opensolaris.org/bz/show_bug.cgi?id=2900]] Firefox crashes on NV 95 333: 334: ===== Description 335: 336: Firefox dumps core in NV build 95 due to Flash Player bug. Flash plugin v9.0 r124 has a bug that causes Firefox to crash. This issue has been fixed in the flash plugin v 9.0 r125. 337: 338: Note - This affects only users of Flash Player v9.0 r124 and below. 339: 340: ===== Workaround 341: 342: 1. Start firefox. 343: 1. From the Menu bar, click on Tools -> Add-ons -> Plugins. 344: 1. Right click on Shockwave Flash and choose the Disable option to disable the plugin. 345: 1. Manually install the updated version from the following url: [[http://www.adobe.com/products/flashplayer/productinfo/instructions/#section-4>>http://www.adobe.com/products/flashplayer/productinfo/instructions/#section- 346: 4]] 347: 348: ==== [[# 3691>>http://defect.opensolaris.org/bz/show_bug.cgi?id=3691]] Using Fast Reboot When Specifying the Name of a BE Fails 349: 350: ===== Description 351: 352: The new fast reboot feature enables you to provide a ’-e’ option to specify the name of the boot environment (BE) to which you need to fast reboot. Attempting to do a fast reboot and specifying the name of a BE fails in the OpenSolaris 2008.11 release. The following error message is displayed: 353: 354: {{{ 355: # reboot -f -e opensolaris-7 356: reboot: cannot mount BE opensolaris-7 357: 358: }}} 359: 360: ===== Workaround 361: 362: Specify the full root dataset path to the BE to which you need to fast reboot. For example: 363: 364: {{{ 365: # reboot -f rpool/ROOT/opensolaris-7 366: }}} 367: 368: ==== [[# 3783>>http://defect.opensolaris.org/bz/show_bug.cgi?id=3783]] Installer Fails if the User Creates or Imports the ZFS Pool rpool 369: 370: ===== Description 371: 372: If a ZFS pool named rpool is already present on the system because it was manually imported or created by the user during the current boot of the live CD, the install process fails. The last message in the installation log is as follows: 373: 374: {{{ 375: Root pool rpool exists, we can’t proceed with the installation. 376: }}} 377: 378: This behavior is intentional and ensures that the installer does not inadvertently corrupt the user’s data. 379: 380: The installer can recognise cases when rpool was created by the installer itself but the installation process failed or was interrupted. In such cases the installer destroys rpool automatically after it is restarted. 381: 382: ===== Workaround 383: 384: Choose one of the following workarounds: 385: 386: * To preserve data in the rpool, reboot the system and do not import the pool. The pool remains invisible to the installer. However, if the pool was created on the target disk then the pool cannot be preserved. 387: * If you do not want to preserve data in the rpool, destroy the pool before you start the installer, using the following command: 388: 389: {{{ 390: $ pfexec zpool destroy -f rpool 391: }}} 392: 393: ==== [[# 3947>>http://defect.opensolaris.org/bz/show_bug.cgi?id=3947]] Distribution Constructor Does Not Recognize ZFS File System Mountpoints for Build Areas 394: 395: ===== Description 396: 397: If a system has a ZFS file system, the Distribution Constructor does not recognise or treat a build area as a ZFS file system in the following cases: 398: 399: * A new sub-directory of the ZFS file system is specified as a build area, but the mountpoint is specified instead of the zpool. 400: * The build area already exists as a ZFS file system but the mountpoint is specified instead of the zpool 401: 402: For example, in the following zpool: 403: 404: {{{ 405: $ zfs list | grep "disk2_pool/ib/pia" 406: disk2_pool/ib/pia 1.90G 355G 18K /export/home/ib/pia 407: }}} 408: 409: When you run the following command: 410: 411: {{{ 412: # distro_const build -p 1 slim_cd.xml 413: }}} 414: 415: Where the build area in slim_cd.xml is specified as <build_area>/export/home/ib/pia</build_area>, the following message error message is displayed: 416: 417: {{{ 418: Checkpointing is not available 419: Rerun the build without -p 420: 421: }}} 422: 423: ===== Workaround 424: 425: Specify the zpool in the manifest. For example, <build_area>disk2_pool/ib/pia</build_area>. 426: 427: ==== [[# 4061>>http://defect.opensolaris.org/bz/show_bug.cgi?id=4061]] Only the First GRUB menu.lst Entry of the Source BE Is Created When Creating a New BE. 428: 429: ===== Description 430: 431: When a new boot environment (BE) is created, the new BE will only have one entry in the GRUB menu.lst file regardless of how many entries the source BE has. The source BE’s first menu.lst entry is used to create the entry for the new BE. All other entries are ignored. This issue occurs when you create the new BE either through beadm or pkg image- update. 432: 433: If the user needs the other entries for the new BE they are not available. 434: 435: ===== Workaround 436: 437: Edit the /rpool/boot/grub/menu.lst file and copy the desired entries from the original BE. Replace the BE name in the source entries with the BE name of the target. 438: 439: ==== [[# 4166>>http://defect.opensolaris.org/bz/show_bug.cgi?id=4166]] Automated Installer Hangs on a 1 GB System Without Swap 440: 441: ===== Description 442: 443: On a system with 1 GB of physical memory, the Automated Installer might not create swap space which causes the installation to hang due to insufficient memory. 444: 445: ===== Workaround 446: 447: Ensure that the fdisk partition is bigger than 12 GB if you are specifying the target disk. 448: 449: ==== [[ # 4215>>http://defect.opensolaris.org/bz/show_bug.cgi?id=4215]] Automatic Install Does Not Set the root Role and the Primary Administrator Profile to the Created User Account. 450: 451: ===== Description 452: 453: When doing Automatic Install, the user is not assigned the Primary Administrator profile and root is not set up as a role. 454: 455: ===== Workaround 456: 457: Use the following procedure: 458: 459: 1. After the install completes log in to the newly installed client as the specified user. 460: 1. Become superuser. 461: 462: {{{ 463: % su - 464: }}} 465: 466: 1. Change the role to root. 467: 468: {{{ 469: # usermod -K type=role root 470: }}} 471: 472: 1. Assign the Primary Administrator profile to the user account. 473: 474: {{{ 475: # usermod -P "Primary 476: Administrator" -R root //user_login_name// 477: }}} 478: 479: ==== [[# 4246>>http://defect.opensolaris.org/bz/show_bug.cgi?id=4246]] User and Root Passwords are Not Encrypted in the SC Manifest 480: 481: ===== Description 482: 483: The Automated Installer enables setting the root password and creating a new user/password during installation. These passwords should be specified in plain-text and the installer encrypts them. Specifying passwords in plain-text is a security risk. 484: 485: ===== Workaround 486: 487: Use the standard password for root and user. Change the password once installation is complete by using the **/usr/bin/passwd** command. 488: 489: ==== [[# 4248>>http://defect.opensolaris.org/bz/show_bug.cgi?id=4248]] ICT reset_image_UUID Fails for Automated Installer if authname is Not Set to opensolaris.org 490: 491: ===== Description 492: 493: The Automated Installer enables setting an authority name. If an authority name other than opensolaris.org is set, the ICT reset_image_UUID displays the following error in the install_log file: 494: 495: {{{ 496: 497: <ICT Oct 25 20:43:43> current task:reset_image_UUID 498: <ICT_I Oct 25 20:43:43> _cmd_status: executing cmd=pkg -R /a set-authority 499: ~--reset-uuid opensolaris.org 500: pkg: set-authority: authority does not exist. Use -O to define origin URL for 501: new authority 502: <ICT_I Oct 25 20:43:45> _cmd_status: return exitstatus=256 503: <ICT_E Oct 25 20:43:45> Reset uuid failed - exit status = 256, command was pkg 504: -R /a set-authority ~--reset-uuid opensolaris.org 505: <ICT_E Oct 25 20:43:45> Failure. Returning: ICT_PKG_RESET_UUID_FAILED 506: 507: }}} 508: 509: The install_log file is located at /a/var/sadm/system/logs/install_log. 510: 511: ===== Workaround 512: 513: In the Automated Installer manifest set authname to opensolaris.org. For example: 514: 515: {{{ 516: <main url="http://ipkg.sfbay:29047" authname="opensolaris.org"/> 517: }}} 518: 519: ==== [[# 4282>>http://defect.opensolaris.org/bz/show_bug.cgi?id=4282]] Trackerd Does Not Start by Default on OpenSolaris 520: 521: ===== Description 522: 523: Trackerd does not start by default in the GNOME desktop. 524: 525: ===== Workaround 526: 527: Use the following procedure: 528: 529: 1. Go to System->Preferences->Session and enable trackerd, and tracker-applet. 530: 1. Log out of your system. 531: 1. Log in again. 532: 533: For more information, see the FAQs at the [[Tracker community page>>Project jds.MetaTracker]]. 534: 535: ==== [[# 4294>>http://defect.opensolaris.org/bz/show_bug.cgi?id=4294]] Distribution Constructor Fails if Compressed ZFS Dataset Is Used as the Build Area 536: 537: ===== Description 538: 539: If a compressed ZFS dataset is specified as the build area for the Distribution Constructor, the bootroot_archive step fails. An error message indicating that the device ran out of space when creating the pkg.lib archive is displayed. 540: 541: ===== Workaround 542: 543: Ensure that the ZFS dataset specified as the build area is not compressed. 544: 545: ==== [[# 4300>>http://defect.opensolaris.org/bz/show_bug.cgi?id=4300]] Automated Installer Fails to Access the IPS Repository 546: 547: ===== Description 548: 549: If the DHCP server is not set up correctly, the Automated Installer client might not get the required DNS and router information. The Automated Installer might fail to access the IPS repository. The following error message is displayed: 550: 551: {{{ 552: pkg image-create failed 553: }}} 554: 555: ===== Workaround 556: 557: If the installadm command is used to setup the DHCP server as part of installadm create-service, ensure that the following conditions are met in the install server before running the command: 558: 559: * /etc/resolv.conf is populated with correct DNS information on the server 560: * Your name service is DNS by checking the /etc/nsswitch.conf configuration file. The hosts and IP nodes value should be set to dns in the file. 561: * The DNS client SMF service /network/dns/client:default is enabled 562: * The default router is set 563: 564: ==== [[# 4488>>http://defect.opensolaris.org/bz/show_bug.cgi?id=4488]] Automated Installer Services Should be Started Manually if the Install Server Is Rebooted 565: 566: ===== Description 567: 568: The Automated Installer starts the Apache Web server at port 5555 to serve Automated Installer images to the clients. When you create a service using installadm create-service, an installer service is started. If the install server on which the command was used reboots for any reason, the install services and the Apache Web server will not be restarted automatically. This will stop the Automated Installer clients from using the install server to boot and install successfully. 569: 570: ===== Workaround 571: 572: Use the following procedure: 573: 574: 1. Restart the Apache Web server: 575: 576: {{{ 577: # /usr/apache/2.2/bin/apachectl -f 578: /var/installadm/ai-webserver/ai-httpd.conf -k start 579: }}} 580: 581: 1. Get the configured services from the /var/installadm/service_data file. For example, the configured services might displayed as shown: 582: 583: {{{ 584: # cat /var/installadm/service_data 585: new1;/tmp/directory/test1;new1;aiwebserver=kumbam:46501 586: _install_service_46501;/tmp/target/test1;_install_service_46501;aiwebserver=kumbam:46501 587: }}} 588: 589: Here, the first parameter is the name of the service. 590: 1. Start each service using the installadm start command: 591: 592: {{{ 593: #installadm start new1 594: #installadm start _install_service_46501 595: }}} 596: 597: ==== [[# 4575>>http://defect.opensolaris.org/bz/show_bug.cgi?id=4575]] Automated Installer Fails If the Target Disk Does Not Contain an fdisk Partition 598: 599: ===== Description 600: 601: If a target disk is specified in the AI manifest and if the disk does not have an fdisk partition, the Automated Installer fails to install the OpenSolaris 2008.11 operating system. 602: 603: ===== Workaround 604: 605: Choose one of the following workarounds: 606: 607: * Create an fdisk partition using fdisk tool. 608: * Create an fdisk partition by specifying partition information in the AI manifest. See Automated Installer documentation on how to specify partition creation information in AI manifest. 609: 610: ==== [[# 4586>>http://defect.opensolaris.org/bz/show_bug.cgi?id=4586]] Distribution Constructor Pause and Resume Functionality Might Fail. 611: 612: ===== Description 613: 614: If you use the resume and pause functionality on the same command line, the Distribution Constructor will not allow the -r option to precede the -p option. The Distribution Constructor wrongly decides that you have specified a resume step that is invalid. The following error message is displayed: 615: 616: {{{ 617: You must specify an earlier step to resume at. 618: }}} 619: 620: ===== Workaround 621: 622: Specify the -p option before the -r option. 623: 624: ==== [[# 4589>>http://defect.opensolaris.org/bz/show_bug.cgi?id=4589]] Exception Message Generated by Distribution Constructor Upon Successful Termination 625: 626: ===== Description 627: 628: The Distribution Constructor might display the following error message after successfully performing its function: 629: 630: {{{ 631: Unhandled exception in thread started by 632: Error in sys.excepthook: 633: 634: Original exception was: 635: }}} 636: 637: ===== Workaround 638: 639: This error message is displayed just before termination and can be safely be ignored. 640: 641: ==== [[# 4629>>http://defect.opensolaris.org/bz/show_bug.cgi?id=4629]] Timezone Cannot be Customized if Automated Installer is Used for Installation 642: 643: ===== Description 644: 645: Due to the bug in Automated Installer, timezone is always set to PST8PDT on an installed system. The value defined by the tag in the SC manifest is not taken into account. 646: 647: ===== Workaround 648: 649: Choose one of the following workarounds: 650: 651: * Use the Automated Installer and boot the system. Go to System->Administration->Time and Date application on the Desktop and set the timezone. 652: * Use the GUI installer for installation. 653: 654: ==== [[# 4636>>http://defect.opensolaris.org/bz/show_bug.cgi?id=4636]] Distribution Constructor Might Dump Core When Running the br-config Finalizer Script 655: 656: ===== Description 657: 658: The Distribution Constructor might dump core during the br-config finalizer script when running the mkrepo script. This occurs if the mount point associated with the build area specified in the manifest exceeds 26 characters. The following error message is displayed: 659: 660: {{{ 661: ==== br-config: Boot root configuration 662: /usr/share/distro_const/mkrepo: line 51: 13909: Abort(coredump) 663: 664: Stopping at br-arch: Boot root archiving 665: 666: }}} 667: 668: ===== Workaround 669: 670: Change the mount point associated with the build area to not exceed 26 characters. 671: 672: For more information on the core dump, see [[ CR 6721855 - svccfg Dumps Core.>>http://bugs.opensolaris.org/view_bug.do? 673: bug_id=6721855]] 674: 675: ==== [[# 4645>>http://defect.opensolaris.org/bz/show_bug.cgi?id=4645]] The Graphical Boot Progress Bar Hides sys-unconfig Questions at Boot Time 676: 677: ===== Description 678: 679: The graphical boot feature has been enabled for the OpenSolaris 2008.11 release. This feature provides the user with a graphical horizontal scrolling progress bar during system boot instead of the boot messages. 680: 681: If the user uses the sys-unconfig command, the graphical boot progress bar hides the sys-unconfig questions at boot time. 682: 683: ===== Workaround 684: 685: Select the text boot option from the GRUB menu. 686: 687: ==== [[# 4881>>http://defect.opensolaris.org/bz/show_bug.cgi?id=4881]] Input Language Cannot be Switched When Russian Keyboard Layout Is Selected 688: 689: ===== Description 690: 691: IIIM does not work correctly when the Russian keyboard layout is set as physical keyboard. As a result, if you log in to the Russian locale and activate Input Method, upper case ASCII letters are input instead of lower case ASCII letters. 692: 693: ===== Workaround 694: 695: Select English layout as physical keyboard. Then if you log in to the Russian locale, you can switch input languages between Russian and ASCII by using the IM trigger key. The default key is Shift_L+Control_L for Russian locale. 696: 697: ==== [[# 5003>>http://defect.opensolaris.org/bz/show_bug.cgi?id=5003]] Crash Dumps Are Not Saved to the File System at Boot Time By Default 698: 699: ===== Description 700: 701: To reduce the time required for a reboot, crash dumps are not saved to the file system at boot time. 702: 703: ===== Workaround 704: 705: Use the dumpadm(1M) command to enable crash dumps at boot time: 706: 707: {{{ 708: # dumpadm -y 709: }}} 710: 711: Alternatively, create a cron job which enables the saving of crash dumps at any given later point. 712: 713: ==== [[# 5012>>http://defect.opensolaris.org/bz/show_bug.cgi?id=5012]] Using sys-unconfig to Unconfigure the Network Fails 714: 715: ===== Description 716: 717: If you have installed the OpenSolaris 2008.11 release from media, using the sys-unconfig to unconfigure the network settings on your system fails. The nwam service will still be enabled after the system reboots. 718: 719: ===== Workaround 720: 721: Ensure that you change your current working directory to "/" before using the sys- unconfig command. 722: 723: {{{ 724: # cd / 725: # sys-unconfig 726: }}} 727: 728: ==== [[# 5092>>http://defect.opensolaris.org/bz/show_bug.cgi?id=5092]] pkg and packagemanager Fail to Start 729: 730: ===== Description 731: 732: pkg and packagemanager dump stack and fail to start if the current //LANG// variable is en_US.UTF-8, es_ES.UTF-8, fr_FR.UTF-8 or de_DE.UTF-8 and if these locales are not installed. These locales might not be installed due to bug [[# 5473>>https://www.opensolaris.org/os/project/indiana/resources/relnotes/200811/x86/#5473]]. 733: 734: ===== Workaround 735: 736: Install the missing locale packages. Execute the following commands: 737: 738: 1. If your current //LANG// variable is any one of the locales listed above: 739: 740: {{{ 741: $ export LANG=C 742: }}} 743: 744: 1. {{{ 745: $ pfexec pkg install SUNWlang-enUS SUNWlang-frFR SUNWlang-esES SUNWlang-deDE 746: }}} 747: 748: ==== [[# 5146>>http://defect.opensolaris.org/bz/show_bug.cgi?id=5146]] Live CD With Primary Languages Contains Default Locales Only 749: 750: ===== Description 751: 752: When using the Live CD with primary languages only default territories can be selected in the installer on the language screen. This issue is due to space constraints. 753: 754: ===== Workaround 755: 756: Use the Global version of the Live CD for installation. 757: 758: ==== [[# 5277>>http://defect.opensolaris.org/bz/show_bug.cgi?id=5277]] Issues With the IIIM Daemon 759: 760: ===== Description 761: 762: If the IIIM daemon is not running in the background, typing moderately fast in gtk+/gnome applications causes a delay in the display of text. 763: 764: This issue occurs if you uncheck the ’Start IIIM Daemons’, in gnome-session-properties under System->Preferences->Sessions, log out of the desktop session, and log back in. Starting a gtk+/gnome application and typing moderately fast in the application causes the text characters to appear after some delay. 765: 766: ===== Workaround 767: 768: Currently there is no workaround to remove the IIIM deamon from an active session without side effects. If the reason for removing the IIIM daemon is to make the iiim-panel not visible on the gnome-panel and to disable Input Method trigger keys, use the procedure described below. 769: 770: 1. Start iiim-properties under System->Preferences->Input Methods. 771: 1. Select None from the drop-down menu of ’Input Method status switcher placement’ in the ’General’ tab. 772: 1. Remove all trigger keys in ’Trigger Keys’ tab. 773: 1. Click on Apply or OK button. 774: 775: To ensure that IIIM daemons are running in the background, start gnome-session-properties from a terminal window. Check the ’Start IIIM Daemons’ check box and close gnome-session- properties. Log out of the desktop session. When you re-login, the desktop session will not have the input methods applet. 776: 777: ==== [[# 5302>>http://defect.opensolaris.org/bz/show_bug.cgi?id=5302]] Automated Install Manifest Criteria Are Lost 778: 779: ===== Description 780: 781: When you run installadm start on a service, all Automated Install manifest criteria for the Automated Install Web Server are lost. 782: 783: ===== Workaround 784: 785: Use the installadm add command to add the install manifest criteria again. The following error message is displayed when you add the install manifest criteria: 786: 787: {{{ 788: Error: Not copying manifest, source and current versions differ ~-- criteria in place. 789: }}} 790: 791: This error message can be safely ignored. 792: 793: ==== [[# 5473>>http://defect.opensolaris.org/bz/show_bug.cgi?id=5473]] en_US/es_ES/fr_FR/de_DE UTF-8 Locales Might Not be Installed by pkg image-update 794: 795: ===== Description 796: 797: The following locales will not be installed if the slim_install cluster is uninstalled before you upgrade your system to the OpenSolaris 2008.11 release using the pkg image-update command: 798: 799: * en_US.UTF-8 800: * es_ES.UTF-8 801: * fr_FR.UTF-8 802: * de_DE.UTF-8 803: 804: ===== Workaround 805: 806: Install the missing locale packages. Execute the following commands: 807: 808: 1. If your current //LANG// variable is any one of the locales listed above: 809: 810: {{{ 811: $ export LANG=C 812: }}} 813: 814: 1. {{{ 815: $ pfexec pkg install SUNWlang-enUS SUNWlang-frFR SUNWlang-esES SUNWlang-deDE 816: }}} 817: 818: ==== [[# 5492>>http://defect.opensolaris.org/bz/show_bug.cgi?id=5492]] pkg(1) Does Not Uninstall Packages When The System Is Installed From a Global Live CD 819: 820: ===== Description 821: 822: If the system was installed using the global version of the Live CD, which contins all supported languages, the pkg(1) command does not uninstall any package from the installed system. The following error message is displayed: 823: 824: {{{ 825: $ pfexec pkg uninstall SUNWswmt 826: Creating Plan \pkg: Cannot remove ’pkg:/SUNWswmt@0.5.11,5.11-0.101:20081119T230254Z’ 827: due to the following packages that depend on it: 828: pkg:/slim_install@0.1,5.11-0.101:20081119T235636Z 829: }}} 830: 831: ===== Workaround 832: 833: Remove the slim_install cluster from the installed system: 834: 835: {{{ 836: $ pfexec pkg uninstall slim_install 837: }}} 838: 839: You can now remove other packages using the pkg(1) command. 840: 841: ==== [[# 5543>>http://defect.opensolaris.org/bz/show_bug.cgi?id=5543]] Tracker Does Not Index the Home Directory by Default 842: 843: ===== Description 844: 845: When you start Tracker, the home directory is not indexed by default. 846: 847: ===== Workaround 848: 849: Use the following procedure: 850: 851: 1. Go to System->Preferences. 852: 1. Choose ’File Indexing’ to start tracker-preferences. 853: 1. Check the ’Index and watch my home directory’ checkbox in the ’Files’ tab. 854: 1. Click on the OK button. 855: 1. A dialog box prompts that "data must be reindexed". Click on the Reindex button to reindex data. 856: 857: For more information, see the FAQs at the [[Tracker community page>>Project jds.MetaTracker]]. 858: 859: ==== [[# 5544>>http://defect.opensolaris.org/bz/show_bug.cgi?id=5544]] Tracker Cannot Search Evolution Emails 860: 861: ===== Description 862: 863: When you start Tracker, you cannot search for Evolution emails. This is a known issue. 864: 865: ===== Workaround 866: 867: None. 868: 869: ==== [[# 5588>>http://defect.opensolaris.org/bz/show_bug.cgi?id=5588]] Cannot Use the su(1M) to Get root Privileges in the Automated Installer 870: 871: ===== Description 872: 873: When using the Automated Installer for installation of OpenSolaris, you can log in to the console to observe the installation process or reboot the system when installation is complete. You can log in either as a regular user where user name is **jack**, and the password is **jack** or you can log in as a root user where the password is **opensolaris**. Currently, when you are logged in as **jack**, you cannot use the su(1M) command to get root privileges. 874: 875: ===== Workaround 876: 877: Log in as a root user from the console. The password is **opensolaris**. 878: 879: ==== [[# 6464201>>http://bugs.opensolaris.org/view_bug.do?bug_id=6464201]] Loop Back Mounts of the ZFS File Systems Causes the svc:/system/filesystem/local:default SMF Service to Fail 880: 881: ===== Description 882: 883: If the system is rebooted after configuring an install service using the installadm create- service command, the system will not boot in the multi-user milestone. This issue occurs because the svc:/system/filesystem/local:default SMF service fails. When the installadm create- service command is executed, it adds lofs entries of the target or ZFS File System to /etc/vfstab. Since the file systems under /etc/vfstab are mounted before mounting the ZFS file systems, lofs mounts fail. 884: 885: ===== Workaround 886: 887: Log in to the install server and clear the service using the following command: 888: 889: {{{ 890: # svcadm clear system/filesystem/local:default 891: }}} 892: 893: Since the ZFS datasets are already mounted now, the system can recover. 894: 895: ==== [[# 6670311>>http://bugs.opensolaris.org/view_bug.do?bug_id=6670311]] Installer Might Fail if the Linux Swap Primary Partition Precedes the Solaris Partition 896: 897: ===== Description 898: 899: The new Solaris installer installs the Solaris operating system into the Solaris2 partition (0xbf). The installer does not support multiple Solaris partitions on one disk. However, the installer recognizes the Linux swap partition (0x82) correctly and installs successfully if the primary partition is used as the Linux swap partition. 900: 901: Solaris installation fails when the partition configuration is as following: 902: 903: * The Linux swap primary partition precedes the Solaris2 partition 904: * The Solaris2 partition is not active 905: 906: ===== Workaround 907: 908: Choose one of the following workarounds: 909: 910: * Avoid defining a Linux swap partition as a primary partition on the same disk where the Solaris2 primary partition will be created. For example, create the Linux swap partition as logical volume within extended partition. 911: * Ensure that the Solaris2 partition precedes the Linux swap partition. 912: * Create the Solaris2 partition outside the installer and mark it as active. Then install into that preexisting partition. 913: * Before installation, change the Linux swap partition type to another type, excluding (0xbf) or (0x82). After the installation is complete, change the Linux swap partition type back to (0x82). 914: 915: ==== [[# 6687328>>http://bugs.opensolaris.org/view_bug.do?bug_id=6687328]] vim Command Cannot Display Multibyte Characters 916: 917: ===== Description 918: 919: The vim command can not display multibyte characters. This bug affects other commands which symbolically link to /usr/bin/vim such as vi, view, and ex commands. 920: 921: ===== Workaround 922: 923: Add the $HOME/.vimrc file that contains the following line: 924: 925: **set encoding=utf-8** 926: 927: Or, use the /usr/has/bin/vi command instead. 928: 929: ==== [[# 6694783>>http://bugs.opensolaris.org/view_bug.do?bug_id=6694783]] Input Method Duplicate Causes IDE Crash 930: 931: ===== Description 932: 933: On rare occasions, when you log in to the desktop, you may encounter the following issue. 934: 935: The Input Method(IM) status icon is displayed at the bottom of main window. When you open a new child window, such as when you select File->Open, a new IM status icon displays in the main window. When you close this child window, the new IM status icon remains. If you click on an IM status icon at this point, IDE crashes. 936: 937: ===== Workaround 938: 939: 1. Find out if the iiim daemon is running by typing this command. 940: 941: {{{ 942: # ps 943: -ef | grep //iiim// 944: }}} 945: 946: 1. If you do not find a process that is related to iiimx or iiimd, restart the iiim daemon by typing this command. 947: 948: {{{ 949: # iiimx -//iiimd &// 950: }}} 951: 952: 1. Try to use the Internet/Intranet Input Method instead of the X Input Method. You can select this option by right-clicking on the Gnome Applications icon. 953: 954: ==== [[# 6696145>>http://bugs.opensolaris.org/view_bug.do?bug_id=6696145]] Install Might Cause Panics on Intel 965 With GM965 Chipset 955: 956: ===== Description 957: 958: Installing the OpenSolaris release on certain laptops that are equipped with the Mobile Intel GM965 Express chipset (Intel GMA X3100 Graphics) is known to cause panics. 959: 960: This issue has been reproduced on the following models that are equipped with the GM965 chipset. 961: 962: * Dell XPS M1330 963: * Lenovo ThinkPad X61/T61 964: * Toshiba Satellite Pro A200 965: 966: ===== How can I tell if my laptop is running the GM965 chipset? 967: 968: You can use the Device Driver Utility on the LiveCD. Or, open a terminal window and run the following command: 969: 970: {{{ 971: pfexec /usr/X11/bin/scanpci 972: }}} 973: 974: This command identifies which Graphics Controller you have on your laptop. 975: 976: ===== Workaround 977: 978: Use the VESA driver to install the OpenSolaris 2008.11 release onto your system. 979: 980: Use the following procedure for the vesa driver: 981: 982: 1. From the GRUB menu, select the Text Console option. 983: 1. Login with user name, **jack**, and the password, **jack**. 984: 1. Execute the following commands 985: 986: {{{ 987: jack@opensolaris:~$ pfexec 988: Xorg -configure 989: jack@opensolaris:~$ sed //’/Driver.*"intel"/s/"intel"/"vesa"/’// xorg.conf.new > 990: xorg.conf 991: jack@opensolaris:~$ pfexec mv //xorg.conf.new /etc/X11/xorg.conf// 992: jack@opensolaris:~$ svcadm enable //gdm// 993: }}} 994: 995: 1. Install the release, per instructions at [[Installing OpenSolaris 2008.11 >>http://dlc.sun.com/osol/docs/content/2008.11/getstart/gentextid-487.html]]. 996: After the system reboots, the desktop is displayed using the vesa driver. 997: 1. If you want to restart the Xserver using the intel driver, type the following: 998: 999: {{{ 1000: % 1001: pfexec rm ///etc/X11/xorg.conf// 1002: }}} 1003: 1004: Restart the Xserver by logging out of your desktop session or hitting Ctrl-Alt-Backspace. 1005: 1006: ==== [[# 6742850>>http://bugs.sun.com/bugdatabase/view_bug.do;jsessionid=3bc0cf26cdbc06507d037e89b45c? bug_id=6742850]] CJK Characters Do Not Display Correctly in the Java Application Environment 1007: 1008: ===== Description 1009: 1010: Chinese, Japanese, and Korean characters do not display correctly on Java technology-based applications. 1011: 1012: ===== Workaround 1013: 1014: Enable the antialising settings manually. Use one of the following commands: 1015: 1016: * {{{ 1017: java -Dawt.useSystemAAFontSettings=on 1018: }}} 1019: 1020: * {{{ 1021: env _JAVA_OPTIONS=-Dawt.useSystemAAFontSettings=on java 1022: }}} 1023: 1024: For more information about turning on the antialiasing settings, refer to [[ Java 2D API FAQs.>>http://java.sun.com/products/java- 1025: media/2D/reference/faqs/index.html#Q_How_can_I_specify_the_text_ant]] 1026: 1027: ==== [[# 6773520>>http://bugs.opensolaris.org/view_bug.do?bug_id=6773520]] Issues With the Slovak Keyboard 1028: 1029: ===== Description 1030: 1031: During installation of the OpenSolaris OS, if the Slovak Keyboard or Slovak Language is selected, some of the keys of the layout do not work. 1032: 1033: ===== Workaround 1034: 1035: Choose one of the following workarounds: 1036: 1037: * Use IIIMF instead of the Xorg Keyboard map: 1038: *1. Reboot the system after installation and log in as a regular user. 1039: *1. Open a terminal and type kbd -s and select US-English. 1040: *1. Open ’Input Method Preference Editor’ and select ’US/English’ as ’Physical Keyboard Layout’ in the ’Keyboard’ tab. 1041: *1. Add ’Slovak’ Keyboard in the ’Languages / Scripts’ tab and click on the Apply button. 1042: *1. 1043: * Log out of the system and re-login as a regular user. 1044: The US-English keyboard layout has been set. Use IIIMF to set the Slovak Keyboard Layout. 1045: * Use the new Slovak kb layout map: 1046: *1. Reboot the system after installation and log in as a regular user. 1047: *1. Open a terminal and log in as the root user. 1048: *1. Replace /usr/X11/lib/X11/xkb/symbols/sun/sk with the new Slovak kb layout map ’sk’. Click [[ here>>http://defect.opensolaris.org/bz/attachment.cgi?id=1026]] to download the new Slovak kb layout map. 1049: *1. Log out of the system and re-login as a regular user. 1050: *1. (Optional) To switch to the US-English keyboard layout, use the setxkbmap us command. To switch back to the Slovak keyboard layout, use the setxkbmap sk command. 1051: 1052: ==== [[# 6775600>>http://bugs.opensolaris.org/view_bug.do?bug_id=6775600]] Audio Is Unavailable After Installation of OpenSolaris 2008.11 RC2 1053: 1054: ===== Description 1055: 1056: On some laptop models, audio might not work after installation of the OpenSolaris 2008.11 RC2 build. An error message similar to the following is displayed in the output of the dmesg command in the log file at /var/adm/messages: 1057: 1058: {{{ 1059: Nov 24 15:30:59 opensolaris audiosup: [ID 718941 kern.warning] WARNING: audiohd0: init_controller() 1060: 1061: no codec exists 1062: Nov 24 15:30:59 opensolaris audiosup: [ID 592854 kern.warning] WARNING: audiohd0: audiohd_attach() 1063: 1064: couldn’t init controller 1065: Nov 24 15:30:59 opensolaris usba: [ID 723738 kern.info] /pci@0,0/pci1179,1@1a,7/communications@4 1066: 1067: (usb_mid0): can’t support ugen for multiple configurations devices that have attached child interface 1068: 1069: drivers 1070: 1071: }}} 1072: 1073: ===== Workaround 1074: 1075: The BIOS setup screens on some laptop models have an entry called ’Device Config’ that might be set to ’Setup by OS’. Change the setting of ’Device Config’ to ’All Devices’. 1076: 1077: Use the following procedure: 1078: 1079: 1. Enter the BIOS setup. 1080: 1. Ensure that ’Device Config’ is set to ’All Devices’ instead of ’Setup by OS’. Now BIOS will configure all devices and not rely on the OS Software for initial configuration. 1081: 1082: **Note:** If the workaround does not resolve your audio issue, there might be another problem or defect. Please consider discussing the issue through email on the [[laptop-discuss<EMAIL_ADDRESS>forum or filing a defect report at [[http://defect.opensolaris.org/bz/>>http://defect.opensolaris.org/bz/]].
Search
Collectives
Community Group
Academic and Research
Accessibility
Advocacy
Appliances
Approachability
Architecture Process and Tools
BrandZ
Chinese Users
Community Advisory Board
Databases
Desktop
Device Drivers
Distribution
Documentation
DTrace
Emerging Platforms
Fault Management
Games on OpenSolaris
HA Clusters
HPC Developer
Installation and Packaging
Internationalization and Localization
Laptop
Logical Domains
Modular Debugger (MDB)
Networking
NFS
Observability
OpenSolaris Governing Board (OGB)
OpenSolaris Printing
OS/Net (ON)
Performance
Power Management
PowerPC
Security
Service Management Facility (smf(5))
Software Porters
Solaris Volume Manager
Storage
Systems Administration Community Group
Testing
Tools Home
Unix File Systems (UFS)
Website Community
X Window System
Xen
ZFS
Zones
Project
ADSL Modem Enhancement
ARC Process Definition
ARM Platform Port
Automatic Data Migration
BIND Update
Bluetooth Stack & Drivers
Brocade FC HBA - Initiator
Brocade FC HBA - Target
Brussels - unified network link configuration
Caiman, Solaris Install Revisited
Celeste
Český portál
Chime Visualization Tool for DTrace
CIFS client for Solaris
CIFS Server
Clearview: Network Interface Coherence
Cluster Agent: Informix Dynamic Server
Cluster Agent: OpenSolaris Container
Cluster Agent: OpenSolaris xVM
Cluster Agent: Oracle E-Business Suite
Cluster agent: PostgreSQL
Cluster Agent: Samba
Cluster Agent: Tomcat
CMT
Coarse Data Flow Parallelism
Colorado: Open HA Cluster on OpenSolaris
Command Assistant
Common Array Manager
Companion - /opt/sfw: Free and Open Source software
COMSTAR: Common Multiprotocol SCSI Target
Content
Contest
CPU Observability
Credentials Process Groups
Crossbow: Network Virtualization and Resource Control
Crypto KMS Agent Toolkit
Cryptographic Framework
Data Migration Manager
Data Tethers
Deutsches Portal
Device Detection Tool
Device Driver Utility
Device Manager
Device Mapper
Direct Rendering Infrastructure & 3D drivers
DTrace Guide
Duckwater: Simplified name services management
Easy Tools
Emancipation
Emulex Fibre Channel Device Driver
Emulex Advanced Ethernet Device Driver
Enable/Enhance Solaris support for Intel Platform
Enhance the support of USB webcams
Enhanced SMF Profiles
Enhancements for AMD-based Platforms
Erlang DTrace Integration
Ethernet bridge module for Solaris
Evaluate Conary
Events Registry
Ext3 file system support
F/OSS Package Base
Facilitation
Fibre Channel over Ethernet
Fine Grained Access Policy (FGAP)
Fingerprint Authentication
Flexible Mandatory Access Control
Forensic Tools
Fully Open X Project
Fuse on Solaris
gcore
Generic Machine Check Architecture Improvements
Google SOC
HA-JBoss
HA-MySQL
Hadoop Live CD
Hitachi
HoneyComb Fixed Content Storage
HPC Stack
Image Packaging System
Improved Performance MIB
Indiana
Innovation Awards
Input Method
Intel Graphics
Internet Key Exchange, version 2
Interrupt Resource Management
IP Datapath Refactoring
IP over Infiniband
IPsec Tunnel Reform
iSCSI Extensions for Remote DMA (iSER)
iSNS Server
JeOS - Just enough Operating System
JKstat - a java binding for libkstat
Journaled File System (JFS)
K Desktop Environment
Kerberos
Kernel Sockets
Kernel SSL Enhancements
Key Management Framework
Korn Shell 93 integration/migration project
Labeled IPsec
LatencyTOP
Layer 2 Filtering
LDoms Manager
Lending
libMicro - portable microbenchmarks
Link Layer Discovery
Live Media: Technologies for distributions running from CD and other media
Locale Data
lofi compression and cryptography support
lx64 brand
Media Management System
Mega_sas
Mexico
MilaX minimal Live Distribution
MIPS Platform Port
Mozilla DTrace
MRSL.NONsharedDevice
Multi-lingual Glossary
Multi-pathing software (MPxIO)
Multiple disk sector size support
Multiple DOI
Muskoka: An open repository for OpenSolaris technical content
Navigator
Nemo: A Framework for High-Performance Networking
Network Auto-Magic
Network Data Management Protocol
Network MIBs
Network Performance Projects
Network Storage
Network Time Protocol (NTP)
Nevada Globalization
New Design of 4over6 Mechanism Based on OpenSolaris
NFS RDMA transport update and performance analysis
NFS Server in non-Global Zones
NFS version 4.1 pNFS
NFSv4 namespace extensions
Nightingale: Port Songbird to OpenSolaris
NPort ID Virtualization (NPIV)
NUMA
Object Storage Device (OSD) support for Solaris
OHACGE Script Based Plug-in
ON/Nevada (ONNV) Project
Open Development Infrastructure
Open HA Cluster Utilities
Open Sound System
OpenGrok
OpenPegasus CIM Server
OpenRTI
OpenSolaris Busybox
OpenSolaris Desktop
OpenSolaris Hispano
OpenSolaris Security Audit
OpenSolaris support for the QEMU processor emulator: host and guest
PEF: Packet Event Framework
Performance Wrappers
Pkgfactory
Polski Portal
Portail Francophone
Portal Brasil
Portals
Power Management Usability Interfaces
Presto: Automatic Printing Configuration
Printable Many Page Solaris Manuals
Promise SuperTrak RAID HBA Driver
QLogic Converged Network Adapter GLDv3 NIC Driver
Quagga Routing Protocol Suite Integration
RAID Configuration Utility
RBridge (IETF TRILL) support
RDMA Offload Framework
Reno: Login Process Enhancements for Interop
Resource Management
s10brand
SAM/QFS
SCM Migration Project
SCSI RDMA Protocol
SDcard Drivers
Sensor Abstraction Layer
Session Initiation Protocol
SFW
Shell: bourne shell, korn shell, C shell, etc.
Sierra: Intel WiFi Chipsets Support
Simple Panels
SM-HBA Based SAS HBA Management
SMF Documentation
Solaris iSCSI Target
Solaris PowerPC Port
SourceJuicer
Sparks: name service switch/nscd enhancements
Squashfs
Star integration/migration project
Starfish
Starter Kit
Storage Power Management
Sun Security Toolkit
Sun StorageTek Availability Suite
Support for OpenFabrics User Verbs / API on OpenSolaris OS
Support gcc4/GCCfss in Solaris
Suspend/Resume
SVR4 Packaging
Systemz
Tamarack: Removable Media Enhancements in Solaris
Tesla: OpenSolaris Enhanced Power Management
Test Development
Tickless Kernel Architecture
TIPC
Trademarks
Trusted networking interface policy database for Trusted Extensions
Trusted Platform Module support
Use Case
Validated Execution Project
Virtual Console
Virtual Network Machines
Visual Panels
Visualization for HPC
Volo
VRRP: Virtual Router Redundancy Protocol Implementation
VSCAN service
Web Stack
Website
Winchester: Schema mapping and ID mapping for AD Interoperability
Wireless USB Support
Wireless Wide Area Network
X Consolidation
x86 Generic FMA Topology Enumerator
Xen Gate
Xfce: A lightweight desktop environment
ZFS Boot and Install
ZFS on disk encryption support
Zone Manager
Zone Statistics
Русский портал
البوابة العربية
भारतीय पोर्टल
中国门户
日本ポータル
한국 포탈
User Group
Adelaide
Argentina
Arizona
Atlanta
Baltimore-Washington
Bangalore
Bangkok
Bangladesh
Beijing
Bélem
Berlin
Bhimavaram
Bloomington
Campus Ambassadors
Capital Region
Cardiff
Ceara
Charlotte
Chengdu
Chennai
Chihuahua
Chile
Cleveland
Colombia
Columbus
Connecticut
Cracow
Czech
Dallas/Ft. Worth
Danish
Delaware
Edinburgh
Egypt
Finland
Florida
Front Range
FuZhou
Great Lakes
Greece
Hangzhou
Hawaii
HeFei
Houston
Hong Kong
Hyderabad
Indonesia
Irish
Israel
Italian
Jinan
Jogja
Kabul
Kansas City
Latvia
London
Madurai
Manchester
Mato Grosso
Melbourne
Minas Gerais
Minnesota
Montreal
Moscow
Mumbai
Munich
NEA
Netherlands
New England
New York City
New Zealand
NIT Hamirpur
Noroeste
Nuremberg-Erlangen
Oklahoma City
Osnabrück
Peru
Philadelphia
Piaski
Pittsburgh
Porto Alegre
Puget Sound
Pune
Queensland
Rio de Janeiro
Research Triangle Park
Romania
Russia
San Antonio
San Diego
San Francisco
São Paulo
Scottish
Serbia
Shanghai
Shenzhen
Silicon Valley
Singapore
Slovak
South African
Southern Connecticut
St. Louis
Stavanger
Sweden
Switzerland
Sydney
Szczecin
Taiwan
Tecum
Thames Valley
Tokyo
Toronto
Trondheim
Tulsa
Turkey
Ufa
Ukraine
University of Melbourne
Vale do Paraíba
Vancouver
Venezuela
Welsh - Cymru
Wisconsin
Xi'an
Subsites
Code Reviews
Code Repositories
Package Search
Bugster
Bugzilla
Test Machines
Planet
Mailing Lists
Elections & Polls
ARC Case Logs
Source Juicer
Package Factory
User Authentication
Project indiana Pages
Building and testing ON
Documentation
Files
Get OpenSolaris 2008.05
Upgrading OpenSolaris 2008.05 to Later Versions of OpenSolaris
Resources
Documentation Deliverables
Glossary
Problem Statement
Release Notes
Reporting Bugs
Restoring system to original installation
Start Page
Status
Accessibility
ReleaseNotes2008.11
x86


Lesson 3 Part 1: A note of Russian cases
Russian has a grammatical category called case that applies to words to indicate their use in a sentence. They are as follows:
|
Name |
Use |
|
Nominative |
Default case, indicates subject of a sentence. e.g. I ate cheese. я ел сыр |
|
Accusative |
Indicates direct object of a sentence. e.g. I ate cheese. я ел сыр |
|
Dative |
Indicates indirect object of a sentence. Often corresponds to “to” in English. e.g. I gave some cheese to Bob. я дал сыр Бобу |
|
Genitive |
Indicates something to which a noun in another case belongs. i.e. Bob’s car машина Боба |
|
Instrumental |
Indicates that an action is done using something (like a tool). e.g. I ate cheese with a knife. я ел сыр ножом |
|
Prepositional |
Used on a noun that follows a preposition. i.e. I live in a house. я живу в доме |


Jillian Kong is a developing developer and project manager, residing in Seattle, WA. Currently, she is in her second year of practicing to be a competent adult at Microsoft, where she works as a Program Manager. When she is not working, she can be found dancing in her kitchen, trying to make new recipes, and singing in a choir of one (simultaneously).
Originally from Calgary, Jillian enjoys breakfast food, 20th century literature, and attempting to make the web a more beautiful and dynamically resizeable place.
This page is getting an extreme makeover, Breakfast Club-style. Thanks for your patience, and in the meantime, check out a PDF version of my portfolio here!
View Jillian's resumé here.
| jilliankong | |
|<EMAIL_ADDRESS>| |
| </> | GitHub |


Senior Business Analyst
Hybrid consultant: half Analyst, half Coder
I'm a web enthusiast. I started developing when we used to surf the Net with 56k modem, for those who remember, it sounded like this:
Over the years I have learned a lot, I have experimented as much and, whenever I have some free time, I try to upgrade my knowledge (right now I'm struggling with Angular). It is stronger than me, some people like to spend their spare time reading a good book, I prefer a boring manual .
This weirdie passion of mine for technology, programming and whatever the web could possibly produce has gone, so far, hand to hand with my studies. This sinergy, as a matter of fact, brought me to embrace the Business Analyst job as a natural consequence.
A good ICT BA should have a strong technical background in order to do the job to the best of his own ability. My daily 'mantra' is something like this: "try to always keep in mind that there is no joy in achiving a result without experiencing an hard time before".
Below you can find some links that they are also keywords, tags, skills gained during the time, fields of interest, articles, curiosities and whatever...:


"Java Python also and great is"
sen_list = sentence.split(" ")
check = set()
for a_word in sen_list:
check.add(a_word)
return " ".join(sorted(check))
if __name__ == "__main__":
>>> remove_duplicates("Python is great and Java is also great")
"Java Python also and great is"
return " ".join(sorted(set(sentence.split(" "))))
if __name__ == "__main__":


|
|
| Horizontal (chstr name) |
| |
|
| Horizontal (chstr name, unsigned int value) |
| |
|
Horizontal | next () const |
| |
|
Horizontal | previous () const |
| |
|
bool | operator< (const Horizontal &other) const |
| |
|
bool | operator> (const Horizontal &other) const |
| |
|
bool | operator<= (const Horizontal &other) const |
| |
|
bool | operator>= (const Horizontal &other) const |
| |
|
bool | operator== (const Horizontal &other) const |
| |
|
bool | operator!= (const Horizontal &other) const |
| |
|
bool | isLeft () const |
| |
|
bool | isCenter () const |
| |
|
bool | isRight () const |
| |
|
bool | isWrapped () const |
| |
|
bool | isUntrimmed () const |
| |
|
|
static int | getCount () |
| |
|
static hltypes::Array< Horizontal > | getValues () |
| |
|
static hstr | getEnumName () |
| |
|
static hltypes::Map< unsigned int, hstr > | getAsMap () |
| |
|
static Horizontal | fromInt (int value) |
| |
|
static Horizontal | fromUint (unsigned int value) |
| |
|
static Horizontal | fromName (chstr name) |
| |
|
static bool | hasValue (chstr name) |
| |
|
static bool | hasValueFor (int value) |
| |
|
static bool | hasValueFor (unsigned int value) |
| |
|
|
| Horizontal (unsigned int value) |
| |
|
hltypes::Map< unsigned int, hstr > & | _getInstances () const |
| |
The documentation for this class was generated from the following file:


{% extends "base.html" %} {% block content %} Upload an audio file Supported audio file types include .wav, .mp3, .ogg, .opus, .flac, and .webm. Transcribe and play Stop Show filler words
Supported audio file types include .wav, .mp3, .ogg, .opus, .flac, and .webm.


Geert Hofstede is a nobel prize-winning psychologist who developed the “cultural dimensions theory” which describes the effects of a society’s culture on the values of its members. According to Hofstede, one of the five important cultural dimensions is masculinity, which refers to the distribution of roles between genders.
While this theory was initially developed as a tool for navigating cross-cultural communication, it’s been used in this instance to see if the cultural dimension of ‘masculinity’ determines or correlates with gender pay gaps. Here, we’ve taken the data from Hofstede’s masculinity index and compared it to OECD gender pay gap data available from 35 developed countries.
Select countries with the tool below to see how various developed countries compare to one another in terms of gender pay gaps versus masculinity levels.
If you’ve looked through the above tool, you’ll see that the masculinity of a country doesn’t necessarily correlate to gender pay gaps. If anything, it is the opposite, with many countries with lower levels of masculinity having average or above average gender pay gaps.
You can further compare the two metrics below on a geographic scale with the two charts below.
See what all went into making this project via my Github Repository here.


Home of Albert's open source Javascript sailing simulation engine.
In active development, right here on GitHub: https://github.com/leeboardtools/bythelee.
Some notes on browsers:
I did some VERY simple tests on the computers/operating systems I have available to me, and came up with the following suggested browsers when operating in Full Screen mode:
| OS/Computer | Tested Browsers (Bold performed best) |
|---|---|
Windows 10 1703 10.0.15063 3.5 GHz i7, AMD Radeon R9 200/HD 7900 Series GPU Driver GPU is an AMD Sapphire Radeon R9 HD 7970 3GB |
Chrome 61.0.3163.100 Edge 40.15063 Firefox 56.0.1 |
Ubuntu 16.04 LTS 3.5 GHz i7, Gallium 0.4 on AMD TAHITI (DRM 2.43.0 / 4.4.0-97-generic, LLVM 3.8.0) GPU Driver GPU is an AMD Sapphire Radeon R9 HD 7970 3GB |
*Chrome 59.0.3071.109 Firefox 56.0 |
OSX El Capitan 10.11.6, on a mid-2015 MBP 2.5 GHz i7, Radeon R9 M370X graphics card |
Chrome 62.0.3163.100 Firefox 56.0 Safari 11.0 (116<IP_ADDRESS>.7) |
Note that some browsers may require you to enable hardware acceleration (Chrome) or WebGL (Safari)
*For Google Chrome in Ubuntu try the following: https://askubuntu.com/questions/299345/how-to-enable-webgl-in-chrome-on-ubuntu
A simple WebGL report via ThreeJS
(Don't mind this plain website, as I'm focusing on getting ByTheLee going...)


---
title: Tabs
---
***
### Horizontal Tabs
{{> examples_tabs_intro}}
### Vertical Tabs
{{> examples_tabs_vertical_intro}}
***
Basic
You can create a group of horizontal tabs using minimal markup.
HTML
{{#markdown}}
```html
{{> examples_tabs_basic}}
```
{{/markdown}}
Rendered HTML
{{> examples_tabs_basic_rendered}}
***
### Vertical Tabs
You can create a group of vertical tabs using minimal markup. Just adding the class `vertical` changes the orientation of horizontal tabs.
HTML
{{#markdown}}
```html
{{> examples_tabs_vertical_basic}}
```
{{/markdown}}
Rendered HTML
{{> examples_tabs_vertical_basic_rendered}}
***
### Deep linking to tabs or tab contents
The tabs Foundation component can parse the location hash value and open the corresponding tab content pane. To enable deep linking set `data-options="deep_linking:true"`. If the location hash maps to an element ID within a tab content pane, then the appropriate tab will become active and the browser window will scroll to the specified element. If you do not want to scroll to the specified element then set `data-options="scroll_to_content: false"`.
In the following example, deep linking is enabled. If the location hash is `#tabs-deeplink-2` then the second tab will become active. If the location hash is `#tabs-deeplink-content-2` then the second tab will become active, and the browser will scroll to the paragraph tag with ID, tabs-deeplink-content-2.
{{> examples_tabs_deep_linking}}
***
### Callbacks
There are two ways to bind to callbacks in your tabs.
{{#markdown}}
Callback function
```html
```
{{/markdown}}
{{#markdown}}
Toggled Event
```html
```
{{/markdown}}
***
## Accessibility
You can make tabs more accessible by using the code snippet below. The tabs are keyboard accessible meaning that a user can use the tab key or arrow keys to navigate through them. The role of `tablist` tells a screen reader what the element is and reads the necessary content.
HTML
{{#markdown}}
```html
{{> examples_tabs_accessibility}}
```
{{/markdown}}
Rendered HTML
{{> examples_tabs_accessibility}}
***
### Adding New Tab Content After Page Load
If you add new content after the page has been loaded, you will need to reinitialize the Foundation JavaScript by running the following:
{{#markdown}}
```javascript
$(document).foundation();
```
{{/markdown}}
Reflow will make Foundation check the DOM for any elements and re-apply any listeners to them.
{{#markdown}}
```javascript
$(document).foundation('tab', 'reflow');
```
{{/markdown}}
***
## Customize with Sass
Tabs can be easily customized with the Sass variables provided in the `_settings.scss` file.
SCSS
{{> examples_tabs_variables}}
***
##### Sass Errors?
If the default "foundation" import was commented out, then make sure you import this file:
SCSS
```scss
@import "foundation/components/tabs";
```


Repo [In]Activity
This site serves as a small tool to sort a user's repositories by the date of their last commit.
Sort repos
Least recently active at the top, most recently active at the bottom


Queue
Undocumented
-
Undocumented
-
Main Dispatch Queue
Declaration
Swift
public static var main: DispatchQueue
-
Global Dispatch Queue with Specific Priority
Declaration
Swift
public static var global: (_ priority: DispatchQoS.QoSClass) -> DispatchQueue = { (priority) in
-
Custom Dispatch Queue with Specific Identifier and Attributes
Declaration
Swift
public static var custom: (_ identifier: String, _ attributes: DispatchQueue.Attributes) -> DispatchQueue = { (identifier, attributes) in


RECOMMENDED TREATMENTS
- Stubbon Fat Bulge/Non-surgical Body Contouring
- CoolSculpting
- Exilis Skin Tightening
- Vanquish
- Stretch Marks
- Fractional Resurfacing
- Micro Skin Needling
- Platelet Enhanced Plasma Therapy
- Small nose bridge/Uneven Nose Shape
- Collagen Volumiser - R
- Wrinkle Filler
- Sagging Skin
- Exilis Skin Tightening
- Ultherapy
- Pigmentation/Melasma/Freckles/Sun Spots
- Aspect Dr Skincare
- Chemical/Facial Peels
- Fractional Resurfacing
- IPL/BBLTM Treatment
- ZO Medical Skincare
- Maintaining Healthy and Younger Skin
- Aspect Dr Skincare
- Chemical Peels
- IPL/BBLTM Photomodulation
- Vibro Microdermabrasion
- ZO Medical Skincare
- Lines and Wrinkles
- Aspect Dr Skincare
- BBLTM Photomodulation
- Collagen Volumisers - R or S
- Fractional Resurfacing
- Micro Skin Needling
- Platelet Enriced Plasma Therapy
- Vibro Microdermabrasion
- Wrinkle Fillers
- ZO Medical Skincare
- Leg Veins
- Sclerotherapy
- Large Pores
- Aspect Dr Skincare
- Fractional Resurfacing
- Vibro Microdermabrasion
- ZO Medical Skincare
- Facial Volume Loss/Loss of Facial Contour
- Collagen Volumiser - R or S
- Wrinkle Fillers
- Facial Spider Veins/Broken Capillaries/Rosacea
- Aspect Dr Skincare
- IPL / BBLTM Vascular
- ZO Skincare
- Facial Slimming/ Bruxism
- Exilis Skin Tightening
- Ultherapy
- Wrinkle Relaxer B
- Facial hairs/Underarms/Bikini/Others
- IPL Hair Removal
- Facial and Body Resurfacing
- Chemical Peels
- Fractional Resurfacing
- Excessive Sweating
- Wrinkle Relaxer
- Eyebags and Dark Undereye Circles
- Exilis Skin Tightening
- Fillers
- Fractional Resurfacing
- Platelet Enriched Plasma Therapy
- Ultherapy
- ZO Medical Skincare Products
- Cheek, Nose and Lip Enhancement
- Wrinkle Fillers
- Aging Skin
- Aspect Dr Skincare
- BBLTM Photomodulation
- Collagen Volumisers - S or R
- Exilis Skin Tightening
- Fractional Resurfacing
- Micro Skin Needling
- Platelet Enriched Plasma Therapy
- Vibro Microdermabrasion
- Wrinkle Fillers
- Wrinkled Relaxers
- ZO Medical Skincare
- Active Acne
- Aspect Dr
- Topical Creams and/or Medicationr
- Vibro Microdermabrasion
- ZO Medical Skincare
- Acne Scarring
- Chemical Peels
- Fractional Resurfacing
- Micro Skin Needling
BUILD PLAN


Note: This page will not function without JavaScript.
•
•
|
Player 1:
$1500
|
|
|
Player 2:
$1500
|
|
|
Player 3:
$1500
|
|
|
Player 4:
$1500
|
|
|
|
Player 1:
$1500
|
|
|
| $ | $ |


Below all the active connections. Keep in mind that HTTP connections are stateless, so no database is retained and usually after a short timeout (seconds) they are killed. Binary connections, instead, remain in life until the connection client closes it. Binary connections are used by the Orient Console tool and by any Orient Java applications that uses the native Java API
| Remote Client | Remote Address | Database | User | Total Requests | Command Info | Command Detail | Last Command On | Last Command Info | Last Command Detail | Last Execution Time | Total Working Time | Connected Since | Protocol | Client ID | Driver | Commands |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| {{ conn.connectionId }} | {{ conn.remoteAddress }} | {{ conn.db }} | {{ conn.user }} | {{ conn.totalRequests }} | {{ conn.commandInfo }} | {{ conn.commandDetail }} | {{ conn.lastCommandOn }} | {{ conn.lastCommandInfo }} | {{ conn.lastCommandDetail }} | {{ conn.lastExecutionTime }} | {{ conn.totalWorkingTime }} | {{ conn.connectedOn }} | {{ conn.protocol }} | {{ conn.clientId }} | {{ conn.driver }} | Interrupt Kill |


AddressTableMap
class AddressTableMap extends TableMap
This class defines the structure of the 'address' table.
This map class is used by Propel to do runtime db structure discovery. For example, the createSelectSql() method checks the type of a given column used in an ORDER BY clause to know whether it needs to apply SQL to make the ORDER BY case-insensitive (i.e. if it's a text column type).
Traits
Constants
| CLASS_NAME |
The (dot-path) name of this class |
| DATABASE_NAME |
The default database name for this class |
| TABLE_NAME |
The table name for this class |
| OM_CLASS |
The related Propel class for this table |
| CLASS_DEFAULT |
A class that can be returned by this tableMap |
| NUM_COLUMNS |
The total number of columns |
| NUM_LAZY_LOAD_COLUMNS |
The number of lazy-loaded columns |
| NUM_HYDRATE_COLUMNS |
The number of columns to hydrate (NUMCOLUMNS - NUMLAZYLOADCOLUMNS) |
| ID |
the column name for the ID field |
| LABEL |
the column name for the LABEL field |
| CUSTOMER_ID |
the column name for the CUSTOMER_ID field |
| TITLE_ID |
the column name for the TITLE_ID field |
| COMPANY |
the column name for the COMPANY field |
| FIRSTNAME |
the column name for the FIRSTNAME field |
| LASTNAME |
the column name for the LASTNAME field |
| ADDRESS1 |
the column name for the ADDRESS1 field |
| ADDRESS2 |
the column name for the ADDRESS2 field |
| ADDRESS3 |
the column name for the ADDRESS3 field |
| ZIPCODE |
the column name for the ZIPCODE field |
| CITY |
the column name for the CITY field |
| COUNTRY_ID |
the column name for the COUNTRY_ID field |
| STATE_ID |
the column name for the STATE_ID field |
| PHONE |
the column name for the PHONE field |
| CELLPHONE |
the column name for the CELLPHONE field |
| IS_DEFAULT |
the column name for the IS_DEFAULT field |
| CREATED_AT |
the column name for the CREATED_AT field |
| UPDATED_AT |
the column name for the UPDATED_AT field |
| DEFAULT_STRING_FORMAT |
The default string format for model objects of the related table |
Methods
Initialize the table attributes and columns Relations are not initialized by this method since they are lazy loaded
Build the RelationMap objects for this table relationships
Gets the list of behaviors registered for this table
Retrieves a string version of the primary key from the DB resultset row that can be used to uniquely identify a row in this table.
Retrieves the primary key from the DB resultset row For tables with a single-column primary key, that simple pkey value will be returned. For tables with a multi-column primary key, an array of the primary key columns will be returned.
The class that the tableMap will make instances of.
Populates an object of the default type or an object that inherit from the default.
The returned array will contain objects of the default type or objects that inherit from the default.
Add all the columns needed to create a new object.
Returns the TableMap related to this object.
Add a TableMap instance to the database for this tableMap class.
Performs a DELETE on the database, given a Address or Criteria object OR a primary key value.
Deletes all rows from the address table.
Performs an INSERT on the database, given a Address or Criteria object.
Details
at line 210
void
initialize()
Initialize the table attributes and columns Relations are not initialized by this method since they are lazy loaded
at line 243
buildRelations()
Build the RelationMap objects for this table relationships
at line 259
array
getBehaviors()
Gets the list of behaviors registered for this table
at line 277
static
getPrimaryKeyHashFromRow(
array $row,
int $offset,
string $indexType = TableMap::TYPE_NUM)
Retrieves a string version of the primary key from the DB resultset row that can be used to uniquely identify a row in this table.
For tables with a single-column primary key, that simple pkey value will be returned. For tables with a multi-column primary key, a serialize()d version of the primary key will be returned.
at line 299
static
mixed
getPrimaryKeyFromRow(
array $row,
int $offset,
string $indexType = TableMap::TYPE_NUM)
Retrieves the primary key from the DB resultset row For tables with a single-column primary key, that simple pkey value will be returned. For tables with a multi-column primary key, an array of the primary key columns will be returned.
at line 320
static
string
getOMClass(
boolean $withPrefix = true)
The class that the tableMap will make instances of.
If $withPrefix is true, the returned path uses a dot-path notation which is translated into a path relative to a location on the PHP include_path. (e.g. path.to.MyClass -> 'path/to/MyClass.php')
at line 338
static
array
populateObject(
array $row,
int $offset,
string $indexType = TableMap::TYPE_NUM)
Populates an object of the default type or an object that inherit from the default.
at line 365
static
array
populateObjects(
DataFetcherInterface $dataFetcher)
The returned array will contain objects of the default type or objects that inherit from the default.
at line 401
static
addSelectColumns(
Criteria $criteria,
string $alias = null)
Add all the columns needed to create a new object.
Note: any columns that were marked with lazyLoad="true" in the XML schema will not be added to the select list and only loaded on demand.
at line 453
static
TableMap
getTableMap()
Returns the TableMap related to this object.
This method is not needed for general use but a specific application could have a need.
at line 461
static
buildTableMap()
Add a TableMap instance to the database for this tableMap class.
at line 480
static
int
doDelete(
mixed $values,
ConnectionInterface $con = null)
Performs a DELETE on the database, given a Address or Criteria object OR a primary key value.
at line 514
static
int
doDeleteAll(
ConnectionInterface $con = null)
Deletes all rows from the address table.
at line 528
static
mixed
doInsert(
mixed $criteria,
ConnectionInterface $con = null)
Performs an INSERT on the database, given a Address or Criteria object.


5. What is the password for the “cranpi” account on the Cranberry Pi system?
Holly Evergreen, located right next to the warp portal in the beginning of the game has the ZIP File we seek. Unfortunately, she only gives it out to people who have a working Cranberry Pi. You must walk around and find all the pieces and when you hand them in Holly will give you a link to download the firmware image. https://www.northpolewonderland.com/cranbian.img.zip
After unzipping we are left with cranberry-jessie.img
, which binwalk -Me cranberry-jessie.img
will extract. Navigating into the directory binwalk extracted the img file to, reveals a Linix Filesystem. Local User account for linux have hashed version of their passwords stored at /etc/shadow, which we can now crack. The relevant line of the shadow file is:
cranpi:$6$2AXLbEoG$zZlWSwrUSD02cm8ncL6pmaYY/39DUai3OGfnBbDNjtx2G99qKbhnidxinanEhahBINm/2YyjFihxg7tgc343b0:17140:0:99999:7:::
- cranpi indicates the username.
- $6$ indicates that this is a sha512crypt hash
- $2AXLbEoG$ is the salt. This is randomly generated and the main purpose is to ensure that two identical passwords do not create the same hash.
Note: $ are used as a delimiter and not part of the actual salt - The stuff after the salt, up to the colon is the hash.
- The numbers after the hash are used for password expiration. Ex: min/max days password expiration, when to warn the user their password is about to expire, etc..
Cracking Sha512Crypt is not a quick process, so we only want to feed it a small dictionary file. Thankfully, Minty Candycane provides a link to a popular wordlist (RockYou). The same file is also on kali within the /usr/share/wordlist directory, if you want to use this one just be sure to decompress it. Run john --wordlist=rockyou.txt shadow
to crack the file, it may take a few minutes. One odd quirk of John is that it won’t display the password when finished, instead it puts it in an internal database. To view the password run john shadow --show
, which will return yummycookies.
Extra tidbit: The shadow- file contains the user “pi” which has a password of thenorthpole7
6. How did you open each terminal door and where had the villain imprisoned Santa?
This is where it gets fun! There are 5 terminals which when clicking on them bring up an actual terminal in the game. The underlying technology behind it all is WeTTY.
Full text walkthrough is below, but I’ve also recorded myself explaining all the challenges here:
Terminal 1: pcap - https://docker2016.holidayhackchallenge.com:60002
When accessing this terminal, you are logged in as the user scratchy and told the answer is in /out.pcap. The problem is that only itchy can read the file, so first we must switch to that user. One of the first things to check when it comes to linux privilege escalation is what sudo access your current user has. Running sudo -l
, showed that the scratchy user can run both strings and tcpdump as the itchy user.
From here the obvious things to do is use strings to view data inside the capture, or tcpdump to parse the capture. I went a different route and exfiltrated the pcap onto my machine. This is a bit of a puzzle because it appears that we Docker Image that doesn’t have a route to the internet and even if we could just send the file back to us over HTTP, strings or tcpdump do not have that capability.
So the first thing to do is to copy the file and hope the UMASK Settings aren’t locked down. UMASK, is what determines how file permissions are set for newly created files, running umask
showed 0022 which means files will be created with 644 permissions (rw owner, ro group+everyone). To copy the file we can use tcpdump to read it and output it to a new file. sudo -u itchy tcpdump --r /out.pcap /tmp/out.pcap
.
Now there should be a copy at /tmp/out.pcap and scratchy should be able to read it. Which means we can now access the pcap with programs other than just strings and tcpdump. I converted the file to base64, base64 /tmp/out.pcap
. Base64, encodes the file into only english characters which is copy and paste friendly! A tip to copy big files on a terminal is to scroll up to the beginning of the output, highlight the first few characters and while still holding the mouse - hit enter to go all the way to the bottom and select the end of output. Copy with ctrl+c and then open up your favorite text editor and paste the output. I saved the file as out.pcap.b64. We can now decode the file and have an identical copy of what was on the server. base64 -d out.pcap.b64 > out.pcap
I opened the file with Wireshark and began looking into the file. Viewing the very first GET Request, showed the first half of the password was “santasli”. I did this by right clicking on the GET Request, and selecting Follow Stream.
This will open up a window where we can see the entire HTTP Request. The red text indicates the client and blue indicates server. We see the client requested the file /firsthalf.html and within the response we see part1 has a value of santasli.
When you are done looking at that request, click “Filter out this stream” to go back to the original wireshark window and do the same process with the next request.
We see the second request is attempting to download a binary file and wireshark just shows a bunch of gibberish. To examine the contents of the binary file, we can save the request to disk. Before saving it, click the box next to “Show and save data as” and select “raw”.
I saved the file as “secondhalf.bin” and began running strings against it. By default strings just converts hex to ascii and looks for english characters 4 characters or more in length. Running strings -h
, shows other possible encoding methods to use. If you run strings -e b secondhalf.bin
, the output will be ttlhelper.
The full password is santaslittlehelper. This entire challenge was a Simpsons reference. Itchy and Scratchy are characters within simpsons and santaslittlehelper is their dog.
For good measure, we can make sure we didn’t miss any easter eggs in the pcap file by going back to wireshark and filtering both requests out. The following expression will do that: !(tcp.stream eq 0) and !(tcp.stream eq 1)
, and the result shows no more packets. So there isn’t anything in this pcap file that we didn’t analyze.
Terminal 2: Hard to access file - https://docker2016.holidayhackchallenge.com:60003
This challenge is pretty straight forward, it states there is a file hidden deep within directories. Running find .
, will list the file structure of the directory and we see the file key_for_the_door.txt behind a lot of hard to type directories. To top it off they screwed with our TTY settings, so things like tab completion do not work. If you want to fix that just run bash
and your terminal will be fixed. However, we don’t need tab completion to help us here we could use find to cat the file for us! find . -name *.txt -exec cat {} ;\
Got the flag and for good measure I wanted to be sure there weren’t any easer eggs. The output of find looked interesting with secret, files, cookbook, etc. I ran find . -type f
to check if they were files I should look at, turns out they were just empty directories.
Obligatory XKCD:
Terminal 3: Wumpus - https://docker2016.holidayhackchallenge.com:60004
This terminal tells you that you can find the passphrase by playing the game wumpus. This is just a binary file and you can start playing by typing ./wumpus. You could try to beat the game legitimately, but text based dungeon games aren’t the most intuitive of games. The easier way is to “reverse engineer” the game, but to do that you’ll need to exfiltrate (aka steal) the game. Do this the same way as I showed in Terminal 1 (with base64).
Once the game is on your computer, you can use gdb to run it in a debugger. Running info functions
will return functions within the game. The function kill_wump, looks interesting. Instead of playing the game, lets just to call that function. Run the game by entering “r”, then background and return to the debugger it with ctrl+c. From here we can just enter print kill_wump()
and see the output of the function, which turns out to be the password.
Note: In the “real world”, the function names are normally stripped out of the program so don’t expect it always to be this easy.
Terminal 4: Wargames - https://docker2016.holidayhackchallenge.com:60005
When accessing this terminal, “GREETINGS PROFESSOR FALKEN” comes across the screen. If you google that phrase, you’ll find out this is a scene from the movie WarGames. Simply just type the responses that were in the movie and you will get the flag. Everything has to be exact it is even case-sensitive. The responses are:
- Hello.
- I’m fine. How are you?
- People sometimes make mistakes.
- Love to. How about Global Thermonuclear War?
- Later. Let’s play Global Thermonuclear War.
- 2
- Las Vegas
After that it will tell you the password is: LOOK AT THE PRETTY LIGHTS
Terminal 5: Time Traveling Train - https://docker2016.holidayhackchallenge.com:60006
You are greeted with a menu prompt, with a few options.
Running HELP will give the descriptions for what each command does. The description for HELP states: “brings you to this file. If it’s not here, this console cannot do it, unLESS you know something I don’t”.
It’s odd that LESS is capitalized, and looking at the screen it looks like less is actually being used. Less is often used to view text files, output of commands, etc. Many people think that is all it can do.
This is dangerous because less allows people to run system commands, just type !commandhere
and it will execute a command. Entering !/bin/sh
will bring you to a shell. Once at the command prompt run ./ActivateTrain to start the train up and teleport back to the past!
Note: The video below has me running everything on my local desktop.
When poking around on the file system of this docker image there are a few odd things.
- The password to start the train is an MD5Sum, I tried cracking it briefly but had no luck. So there is a potential easter egg there.
- If you run strings on the ActivateTrain binary, it appears to make a web request to an IP. The Oracle, said the IP Address was out of scope so I left it alone. My guess is that it is a middle man between the binary and actual game server and that request is what tells the game server to teleport us in time.
- The ActivateTrain binary calls /usr/game/sl, which has the string “ACCIDENT” in it. For some reason my gdb did not recognize the format and lldb kept hanging so I didn’t poke around too much. Perhaps there is an easter egg there?
Well that’s it for the terminals!


We got solutions!
- unleash cutting-edge e-business
- iterate clicks-and-mortar applications
- streamline rich solutions
- engineer viral platforms
- monetize cross-platform users
- expedite 24/365 supply-chains
- envisioneer B2C networks
- transform e-business technologies
- empower killer interfaces


US Teen Charged With Hate Crime After Listing Black Classmate as 'Slave for Sale' on Craigslist - Photo
The photo from the platform was later broadcast across social media, sparking a massive backlash from many users and resulting in a harsh response by the local police and the school administration.
An American teenager from Naperville, Illinois, has been charged with two counts of felony hate crime and one count of misdemeanour disorderly conduct after listing a black student as a "slave for sale" on Craigslist and adding a racial slur to the appalling post, WGN9 reported on Thursday.
According to the broadcaster, who spoke with the mother of the victim, the two teens used to get along pretty well, but their friendship ended last October.
"They used to be friends, they are not anymore. The moment he started teasing my son, calling him dumb, making fun of his skin colour, saying 'shut up slave' last October", she said.
Naperville Police Chief Robert Marshall has called the post "despicable and extremely offensive”, stating it does not reflect the local community.
The 14-year-old suspect is now set to appear in court on 18 December.


Provides options for returning a list of summary information about the versions in a specified bucket. More...
Inherits S3Request.
Properties | |
| NSString * | prefix |
| Optional parameter restricting the response to keys which begin with the specified prefix. | |
| NSString * | keyMarker |
| Optional parameter indicating where in the sorted list of all versions in the specified bucket to begin returning results. | |
| NSString * | versionIdMarker |
| Optional parameter indicating where in the sorted list of all versions in the specified bucket to begin returning results. | |
| NSString * | delimiter |
| Optional parameter that causes keys that contain the same string between the prefix and the first occurrence of the delimiter to be rolled up into a single result element in the commonPrefixes list. | |
| NSInteger | maxKeys |
| Optional parameter indicating the maximum number of results to include in the response. |
Provides options for returning a list of summary information about the versions in a specified bucket.
Returned version summaries are ordered first by key and then by version. Keys are sorted lexicographically (i.e. alphabetically from a-Z) and versions are sorted from the most recent to the least recent. Versions with data and versions with delete markers are included in the results.
Required Parameters: bucket
- (NSString *) delimiter [read, write, retain] |
Optional parameter that causes keys that contain the same string between the prefix and the first occurrence of the delimiter to be rolled up into a single result element in the commonPrefixes list.
These rolled-up keys are not returned elsewhere in the response. The most commonly used delimiter is "/", which simulates a hierarchical organization similar to a file system directory structure.
- (NSString *) keyMarker [read, write, retain] |
Optional parameter indicating where in the sorted list of all versions in the specified bucket to begin returning results.
Results are always ordered first lexicographically (i.e. alphabetically) and then from most recent version to least recent version. If a keyMarker is used without a versionIdMarker, results begin immediately after that key's last version. When a keyMarker is used with a versionIdMarker, results begin immediately after the version with the specified key and version ID.
- (NSInteger) maxKeys [read, write, assign] |
Optional parameter indicating the maximum number of results to include in the response.
Amazon S3 might return fewer than this, but will not return more. Even if maxKeys is not specified, Amazon S3 will limit the number of results in the response.
- (NSString *) prefix [read, write, retain] |
Optional parameter restricting the response to keys which begin with the specified prefix.
You can use prefixes to separate a bucket into different sets of keys in a way similar to how a file system uses folders.
- (NSString *) versionIdMarker [read, write, retain] |
Optional parameter indicating where in the sorted list of all versions in the specified bucket to begin returning results.
Results are always ordered first lexicographically (i.e. alphabetically) and then from most recent version to least recent version. A keyMarker must be specified when specifying a versionIdMarker. Results begin immediately after the version with the specified key and version ID.


WIAA D6: St. Mary’s Springs secures ninth state title with 7-0 win over Regis
by FOX Sports WisconsinFor the ninth time in school history, St. Mary’s Springs has been crowned state champions in football.
The Ledgers defense dominated Regis on Thursday afternoon, holding the Ramblers to 2.8 yards per play en route to a hard-fought 7-0 win.
Senior running back Marcus Orlandoni led St. Mary’s Springs with 20 carries for 75 yards and a touchdown. David Mueller added 14 carries for 57 yards, a 4.1 average.
To clinch the state title, the Ledgers recovered a Gus Theisen fumble with under two minutes to play and ran out the clock from there.
St. Mary’s Springs set the tone with a 10-minute drive to start the game, capped off by a 1-yard rush for a score by Orlandoni. The Ledgers out-gained Regis 167-134.
It was the Ledgers’ third straight state championship. Last year, the Ledgers defeated Stratford 20-17. And in 2017, St. Mary’s Springs topped Iola-Scandinavia 35-12 at Camp Randall Stadium.