Perl 5.10 will become the default when the various perl modules delivered for 5.8.4 have had a chance to deliver for 5.10 and parts of the system that use Perl have been tested and verified to not break with the switch.

   -Norm

Sriram Natarajan wrote:
Upgrading to build 122 has been pretty smooth and I have been pretty impressed with the overall experience of using build 122. Kudos to the entire team.However, I do have to note that I was disappointed that Perl v5.10 is not the default perl when you upgrade. One has to explicitly download and install SUNWperl510core to use this new version of perl. Also, installing Perl v.10 does not change /usr/bin/perl to this new version. To use Perl v 5.10, one has to explicitly invoke this binary by doing /usr/perl5/5.10.0/bin/perl . Unless, one has a very strong reason for using this new version of perl, no one will be motivated to install , try and provide feedback regarding this new version. Any particular reason why this was decided to be this way ?

- Sriram

[email protected] wrote:
The OpenSolaris development package repository

    http://pkg.opensolaris.org/dev/

has been updated to reflect the changes up to and including snv_122 for
both x86/x64 and SPARC platforms.  This update includes fixes to the
Caiman "Slim Install" and the Image Packaging System (IPS).

Users who wish to update their system to the development build can do
so by setting their preferred publisher to the above URL and using the
"image-update" facility provided by the pkg(1) command or by the
"Update All" facility of the Package Manager GUI.

IMPORTANT NOTE: Before updating a system, please review this document
for all of the known issues that may affect the update.

IMPORTANT NOTE: The development builds have undergone limited testing
and users should expect to uncover issues as the next release is
developed.  Bug reports and requests for enhancement are welcome
through http://defect.opensolaris.org/

Known issues in this repository update
======================================
9568 image-update produces driver removal of policy warnings
http://defect.opensolaris.org/bz/show_bug.cgi?id=9568

    When updating to build 117 or beyond, warnings of the following
    form may appear

        driver (ibd) upgrade (removal of
        policy'read_priv_set=net_rawaccess write_priv_set=net_rawaccess)
        failed: minor node spec required.

    Work-around: These messages can be ignored.

9973 api should gracefully handle updatelogexception
http://defect.opensolaris.org/bz/show_bug.cgi?id=9973

    When starting the Package Manager or performing other packaging
    operations using pkg(1), a message of the following form may
    appear

        UpdateLogException: Package V pkg BRCMbnx
        0.5.11,5.11-0.118:20090707T210528Z
         is already in the catalog

    Work-around: Execute the following command from the command
    line

        u...@host$ pfexec pkg refresh --full

10010 reconfigure transport timeouts
http://defect.opensolaris.org/bz/show_bug.cgi?id=10010

    When installing packages on or updating from builds 118 or 121,
    the operation may fail with messages of the form

        1: Framework error: code: 28
        reason: Operation timed out after 30000 milliseconds
        with <some number> out of <some other number> bytes received

    Work-around: Set the environment variable PKG_CLIENT_TIMEOUT to
    15 minutes (900 seconds) or more, depending on the throughout
    to the repository and the size of the files in the package in
    question

        u...@host$ PKG_CLIENT_TIMEOUT=900
        u...@host$ export PKG_CLIENT_TIMEOUT
        u...@host$ pfexec pkg install <name of packages>

10630 driver action gets confused by driver_aliases entries not covered by an
http://defect.opensolaris.org/bz/show_bug.cgi?id=10630

    When using image-update to update to build 121 or later,
    messages of the following form may be displayed

        The 'pcieb' driver shares the alias 'pciexclass,060400'
        with the 'pcie_pci' driver, but the system cannot
        determine how the latter was delivered.  Its entry on
        line 2 in /etc/driver_aliases has been commented out.
        If this driver is no longer needed, it may be removed
        by booting into the 'opensolaris-2' boot environment
        and invoking 'rem_drv pcie_pci' as well as removing
        line 2 from /etc/driver_aliases or, before rebooting,
        mounting the 'opensolaris-2' boot environment and
        running 'rem_drv -b <mountpoint> pcie_pci' and removing
        line 2 from <mountpoint>/etc/driver_aliases.

    Work-around: These messages can be ignored.

10778 image-update to snv_120 produces warnings about etc/sma/snmp/mibs
http://defect.opensolaris.org/bz/show_bug.cgi?id=10778

    When using image-update to update to build 120 or later, a
    message of the following form may be displayed

        Warning - directory etc/sma/snmp/mibs not empty - contents
        preserved in
        /tmp/<path>/var/pkg/lost+found/etc/sma/snmp/mibs-<timestamp>

    Work-around: This message can be ignored.

10807 beadm destroy fails in build 121
http://defect.opensolaris.org/bz/show_bug.cgi?id=10807

    When using build 121, an attempt to destroy a boot environment
    (BE) using beadm(1M) will cause an error of the following form
    to be displayed

        Unable to destroy <name of BE>.

    Alternatively when installing or uninstalling a package or
    updating an image, an error of the following form may be
    displayed

        pkg: unable to destroy snapshot <YYYY-MM-DD-HH:MM:SS>

    Work-around: To destroy the BE in question, if possible reboot
    into a third boot environment and destroy the BE in question
    from there.

    In the case of a packaging operation, the stale ZFS snapshot
    can be removed.  To determine the name of the ZFS snapshot in
    question, the following set of commands may be used

        u...@host$ beadm list -Ha | grep <YYYY-MM-DD-HH:MM:SS> | \
            cut -d\; -f2

    The snapshot in question can then be destroyed using

        u...@host$ pfexec zfs destroy <full name of ZFS snapshot>

6820576 Kernel panic when booting Nevada and OpenSolaris
http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6820576

    When booting build 121 on a VMware guest instance, the system
    may panic with the following function listed in the kernel
    stack trace

        pcplusmp`ioapic_read

    Work-around: Boot with the "pcieb" driver disabled by editing
    the GRUB "kernel$" entry.  This can be done interactively by
    typing the character "e" when the GRUB menu appears and using
    the arrows key to navigate to the "kernel$" entry.  Entering a
    second "e" will allow one to append to the end of the line the
    string " -B disable-pcieb=true".

    To complete the boot, enter a carriage return followed by the
    "b" character.

    To make this change persistent, edit the file
    /rpool/boot/grub/menu.lst and add the same string to the
    appropriate "kernel$" entries.

6859248 manifest removal should automatically cause repository cleanup
http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6859248

    When updating from builds 116 or 117, the system may fail to
    boot and will enter into system maintenance mode.

    Work-around: If the system ends up in this state, you can login
    as the administrator and type

        u...@host$ pfexec svccfg delete network/fcoe_config

    which will delete the offending service manifest and cause the
    boot to proceed.

    Alternatively after the "pkg image-update" or Package Manager
    or Update Manager has completed the package update but *prior*
    to rebooting, delete the obsolete service as follows

        1. Note the name of the new boot environment (BE) that
        was created (for example, opensolaris-#)

        2. From the command line execute the following steps

            u...@host$ pfexec beadm mount <new BE name> /mnt
            u...@host$ pfexec svccfg
            svc:> repository /mnt/etc/svc/repository.db
            svc:> delete network/fcoe_config
            svc:> end
            u...@host$ pfexec beadm unmount <new BE name>

        3. At this point, the new BE can be booted into.

6875223 'WARNING: emlxs: ddi_modopen drv/fct failed: err 2' when booting snv_122
http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6875223

    When booting the system, the following message may appear on
    the console

        WARNING: emlxs: ddi_modopen drv/fct failed: err 2

    Work-around: This message can be ignored.

ISO image information
=====================
ISO images for the Automated Installer[1], CD-R/CD-RW and USB are being
made available for this build via BitTorrent.  Torrent files are
provided as follows

    SPARC Automated Installer image, 277M
    http://dlc.sun.com/torrents/info/osol-1002-122-ai-sparc.iso.torrent

    x86/x64 Automated Installer image, 207M
    http://dlc.sun.com/torrents/info/osol-1002-122-ai-x86.iso.torrent

    x86/x64 All Languages CD, LZMA compression, 743M
    http://dlc.sun.com/torrents/info/osol-1002-122-x86.iso.torrent
    (NOTE: If burned to media, image should be burned to a DVD-R/DVD-RW)

    x86/x64 All Languages USB, LZMA compression, 892M
    http://dlc.sun.com/torrents/info/osol-1002-122-x86.usb.torrent

    MD5 checksums for these images
    http://www.opensolaris.org/os/project/indiana/files/md5sums_122.txt

The ISO images are also available for HTTP download from
http://www.genunix.org/

USB images can be copied to a USB device using the "usbcopy" program
that is part of the SUNWdistro-const package or by downloading the
script[2].

Automated Installer
===================
The SPARC Automated Installer ISO for this development build is
expected to work on all sun4v-based platforms and on sun4u-based
platforms with an OBP level of 4.17 or greater.  This capability can be
determined on an existing system by executing the command

    # eeprom | grep network-boot-arguments

If the network-boot-arguments parameter is set or if the following
output is displayed

    network-boot-arguments: data not available.

then the OBP can be used with the Automated Installer.

New packages in this repository update
======================================
SUNWfcoei            Sun FCoE Initiator Driver
SUNWfreeipmi            FreeIPMI - in-band and out-of-band IPMI
SUNWperl510core            Perl 5.10 (core)
SUNWperl510usr            Perl 5.10 (non-core)
SUNWrss-glx            XScreenSaver - Really Slick ScreenSaver OpenGL
SUNWxscreensaver        XScreenSaver - Screen Saver/Locker for the X
SUNWzoneint            Solaris Zones Internal Files
developer/opensolaris/pkg5    Dependencies required to build the pkg(5)

Image Packaging System (IPS) specific bugs addressed in this repository update ==============================================================================
8263 misc.setlocale should handle locale.getdefaultlocale failure
8319 show all versions desired when release and branch browsing not available
9887 osnet needs new dependencies for zones and upcoming flag days
10398 need new pkg-dev cluster which contains SUNWzoneint
10662 test suite fails if pygtk, gtk not present
10690 package installed from non-preferred pub include pub prefix in name token
10779 __api_prepare() chokes on transport errors
10808 API shouldn't dump stats twice
10830 Local search test suite doesn't test as much local fmri info as it could
10837 ipkg zone creation will always warn after changeset 7bdf8c791f04
10851 incorrect descriptions for SUNWzoneint and pkg5-dev
10956 resync repository to snv_122
10980 redist_cluster can be specified in terms of slim_cluster

Caiman installer specific bugs addressed in this repository update
==================================================================
1699 no pointer feedback when starting gui-install
2872 assertion error at end of OpenSolaris install_log for gtklabel.c
3837 Return code semantics should be consistent throughout libbe
4279 Target Discovery complains about fsck error 39
6029 Firefox launched from gui-install is not accessable because running as root 8477 [opensolaris-installer title label] in each installation configuration
9841 post_bootroot_pkg_image_mod has incomplete USER_ZLIB_ALG check
10807 beadm destroy fails in build 121
10809 beadm destroy will start failing in build 121

[1] http://dlc.sun.com/osol/docs/content/dev/AIinstall/basic.html
[2] http://src.opensolaris.org/source/raw/caiman/slim_source/usr/src/cmd/install-tools/usbcopy
_______________________________________________
indiana-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
_______________________________________________
indiana-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss

_______________________________________________
indiana-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss

Reply via email to