[osol-announce] OpenSolaris package repository update, development build 126, x86/x64/SPARC (11 new packages)
David.Comay at Sun.COM
David.Comay at Sun.COM
Thu Oct 29 09:55:47 PDT 2009
The OpenSolaris development package repository
http://pkg.opensolaris.org/dev/
has been updated to reflect the changes up to and including snv_126 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 or in updating to it
===========================================================
9568 image-update produces driver removal of policy warnings
http://defect.opensolaris.org/bz/show_bug.cgi?id=9568
When using image-update or the Package Manager to update from
builds prior to 123, warnings of the following form may appear
during a packaging update
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
user at 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 throughput
to the repository and the size of the files in the package in
question
user at host$ PKG_CLIENT_TIMEOUT=900
user at host$ export PKG_CLIENT_TIMEOUT
user at 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 or the Package Manager 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 <mount point> pcie_pci' and
removing line 2 from <mount point>/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 or the Package Manager 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-<time stamp>
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
user at host$ beadm list -Ha | grep <YYYY-MM-DD-HH:MM:SS> | \
cut -d\; -f2
The snapshot in question can then be destroyed using
user at host$ pfexec zfs destroy <full name of ZFS snapshot>
11221 beadm create core dumps on OpenSolaris 122 SPARC
http://defect.opensolaris.org/bz/show_bug.cgi?id=11221
When using builds 122 or 123, an attempt to create a new boot
environment (BE) via beadm(1M) or indirectly through "pkg
image-update" may result in a "segmentation fault".
Work-around: Boot into an earlier boot environment and then
manually create the desired BE from there. For example, to
image-update from build 122 or 123 the following set of
commands can be used
<reboot into the earlier BE>
user at host$ pfexec beadm create -e <name of build 122 BE> \
<name of new BE>
user at host$ pfexec beadm mount <name of new BE> /mnt
user at host$ pfexec pkg -R /mnt image-update
user at host$ pfexec beadm unmount <name of new BE>
user at host$ pfexec beadm activate <name of new BE>
At this point, the new BE can be booted into.
11602 Failures seen after rebooting from a image-update from 2009.06 to snv_124
http://defect.opensolaris.org/bz/show_bug.cgi?id=11602
When booting the system the first time after updating to build
124, messages of the following form may be displayed
inetd[5503]: Failed to update state of instance
svc:/application/x11/xfs:default in repository: entity not found
Work-around: These messages can be ignored.
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.
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.
6877673 add_drv fails with a permissions entry with a minor name including a
http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6877673
When using image-update or the Package Manager to update,
messages of the following form may be displayed
driver (clone) upgrade (removal of minor perm
'vnic 0666 root sys') failed with return code 252
command run was: /usr/sbin/update_drv -b /tmp/tmp65jZ-x -d
-m vnic 0666 root sys clone
command output was:
------------------------------------------------------------
No entry found for driver (clone) in file
(/tmp/tmp65jZ-x/etc/minor_perm).
------------------------------------------------------------
or
driver (asy) upgrade (addition of minor perm
'*,cu 0600 uucp uucp') failed with return code 255
command run was: /usr/sbin/update_drv -b /tmp/tmp65jZ-x -a
-m *,cu 0600 uucp uucp asy
command output was:
------------------------------------------------------------
Option (-m) : missing token: (*)
------------------------------------------------------------
Work-around: These messages can be ignored.
6894651 bash default path should not have '.' in its path, especially at the
http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6894651
In build 126, the new 4.0 version of Bash includes "." in the
default PATH. This poses a security risk particularly for the
"root" user.
Work-around: Set a secure PATH by adding a line of the form
export PATH=/usr/gnu/bin:/usr/bin:/usr/X11/bin:/usr/sbin:/sbin
to the $HOME/.bashrc file and then logging out and back in
again (for example, in the file /root/.bashrc for the "root"
user.)
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, 280MB
http://dlc.sun.com/torrents/info/osol-1002-126-ai-sparc.iso.torrent
x86/x64 Automated Installer image, 213MB
http://dlc.sun.com/torrents/info/osol-1002-126-ai-x86.iso.torrent
x86/x64 All Languages CD, LZMA compression, 771MB
http://dlc.sun.com/torrents/info/osol-1002-126-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, 926MB
http://dlc.sun.com/torrents/info/osol-1002-126-x86.usb.torrent
The ISO images are also available for HTTP download from
http://www.genunix.org/
MD5 checksums for these images can be downloaded from
http://hub.opensolaris.org/bin/download/Project+indiana/files/md5sums126.txt
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
======================================
OSOLvpanels-firewall Visual Panels Firewall Panel
OSOLvpanels-hypervisor Visual Panels Hypervisor panels
SUNWfakeroot A tool to simulate a fake root environment
SUNWgnome-l10ndocument-cs GNOME document files for Czech
SUNWgnome-l10ndocument-hu GNOME document files for Hungarian
SUNWgnome-l10ndocument-pl GNOME document files for Polish
SUNWgtk2-print-cups GTK+ - GIMP toolkit libraries - CUPS Print
SUNWgtk2-print-papi GTK+ - GIMP toolkit libraries - PAPI (LP) Print
SUNWmwl Marvell 88W8363 IEEE802.11b/g Wireless Network
SUNWmysql-python26 A MySQL database adapter for the Python
SUNWpmcs PMC-Sierra SAS-2 HBA driver
Image Packaging System (IPS) specific bugs addressed in this repository update
==============================================================================
1935 '?' not supported in pkgmap(4) field entries
2663 imported SVR4 packages do not have BASEDIR visible in pkginfo et al
3961 Test suite should have a flag that makes it stop after encountering a
5321 package manager dependencies tab could show installation status
10223 Disabling other then currently selected publisher should not switch the
10518 pkgdep should check that manifest is a file, proto is a dir
11034 Packagemanager hangs if quit during catalog refresh
11278 PackageManager should maintain selections across searches and publishers
11459 test suite should have way to resume from a particular test
11517 pkgdep resolve needs to catch bad opts exceptions
11646 Restoring All Publisher should also restore last viewed publisher
11773 ldtp can't make connection (thus can't run test suite)
11801 Fixup localization package classifications for img-editor and openoffice
11806 PM installs packages even if they are not checked
11817 VSU: localedef generates a file that is missing 2 header files
11821 Some translatable strings in Package Manager are wrong
11829 pkgdep needs to catch bad manifest actions
11854 transport access by concurrent threads is not permitted
11965 stub signature action needed
11970 ipkg zones need to catch up with many ON changes
12014 incorrect package dependency for SUNWapch22m-php5
12032 SUNWgtk2-print-papi needs to be added to slim_install for b126
12073 Need an A11Y name for the Publisher list in the Manage Publishers dialog
12090 run.py -o broken
12150 "pkg info SUNWPython26" reports version 2.6.1, "/usr/bin/python2.6 -V"
12153 resync repository to snv_126
12155 driver action for amd_iommu is delivered in the wrong package
12156 /etc/inet/{hosts,services} are delivered with the wrong mode
12200 AI installs fail with wget error - libidn.so.11 required in microroot as
Caiman installer specific bugs addressed in this repository update
==================================================================
4526 delete-service is not deleting service as described in section 4.3.2 ai_design_doc
5558 RFE: Install-finish ICT_FIX_BROWSER_HOME_PAGE_FAILED must be soft
5623 Scrollbar in artwork frame during livecd Russian installation
6587 delete-service shouldn't remove the source image if there's other services actives 'linked' to the same source image
7915 libtd shouldn't delete swap during discover targets
8666 create-service: prints out SMF messages no matter what's going on
8773 create-service followed quickly by delete-service hangs
10740 Need way to interact with SMF from Python for installadm components in Python
11214 AI image web server won't run if apache22 is already enabled
11292 delete-client: should remove SPARC clients too
11486 delete-service/delete-client: should check inetd.conf for tftp root
11933 AI install issue with nightly build of 10/12 with the fix of 4152.
11958 namespace collision with dump_nvlist in slim_source as of build 125
12016 Need to use SIGTERM and check for last service in delete_service
[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
More information about the opensolaris-announce
mailing list