OpenSolaris snv_134 dev build Release Notes

Recently I posted the release notes for a release of OpenSolaris that I mistakenly thought was publicly release. I have since located the release notes for the snv_134 developer build of OpenSolaris that is publicly available via . Here are those notes:
The OpenSolaris development package repository

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

has been updated to reflect the changes up to and including snv_134 for
both the x86/x64 and SPARC platforms.

Starting with build 133, almost all packages in the development package
repository have been renamed with hierarchical. smf(5)-style names[1].
For general information on the the format of package names, see the
pkg(5) manual page[2].

Before updating a system, review the "New issues" and "Existing issues"
sections of this document for all of the known issues that may affect
the update.

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/

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.

Existing issues in this repository update or in updating to it
==============================================================
3106 action upgrade needs to consider a missing origin
http://defect.opensolaris.org/bz/show_bug.cgi?id=3106

	When using image-update or the Package Manager to update, the
	packaging operation may fail with messages of the form

		Action removal failed for 'path/to/some/file'
		(pkg:/):
		 OSError: [Errno 2] No such file or directory:
		'/tmp/tmp3E7vFO/path/to/some/file'
		.
		.
		.
		  File "/usr/lib/python2.4/vendor-packages/pkg/misc.py",
		  line 85, in copyfile
		  fs = os.lstat(src_path)
		OSError: [Errno 2] No such file or directory:
		'/tmp/tmp3E7vFO/path/to/some/file'

	Work-around: This failure occurs if an "editable" file has been
	removed from the system prior to updating to build 133 or
	later.

	To restore the file in question

		user@host$ pfexec pkg fix 

	At this point the above packaging operation can be restarted.

14570 file install logic discommoded by excessive cleverness if preserve=rename\*
http://defect.opensolaris.org/bz/show_bug.cgi?id=14570

	When using image-update or the Package Manager to update, the
	packaging operation may fail with messages of the form

		Action upgrade failed for 'etc/mail/sendmail.cf'
		(pkg://opensolaris.org/service/network/smtp/sendmail):
		 OSError: [Errno 2] No such file or directory
		.
		.
		.
		 File
		 "/usr/lib/python2.6/vendor-packages/pkg/portable/os_unix.py",
		 line 232, in rename
		   os.rename(src, dst)
		OSError: [Errno 2] No such file or directory

	Work-around: This failure occurs if an "editable" file that has
	been marked "renameold" has been modified from the system prior
	to updating to build 133 or later.

	An example of such a file is the sendmail(4) configuration
	file, /etc/mail/sendmail.cf.  Special instructions[3] are
	available in cases where /etc/mail/sendmail.cf has been
	modified.

	In other cases, first preserve the contents of the existing
	file

		user@host$ cp -p /path/to/file /path/to/file.orig

	Restore the modified file by searching for the package that
	delivers it

		user@host$ pkg search -l /path/to/file
		INDEX      ACTION VALUE              PACKAGE
		path       file   /path/to/file      pkg:/@ ...

	Then restore the file as follows

		user@host$ pfexec rm /path/to/file
		user@host$ pfexec pkg fix 

	At this point the above packaging operation can be restarted.

	Once booted into the new boot environment, changes recorded in
	/path/to/file.orig can be merged, if necessary, into the
	/path/to/file.

6914346 upgrade from OpenSolaris 2009.06 (111b2) to 130 fails with stale
http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6914346

	After updating to build 130 or beyond, the system may panic
	with messages of the form

		/kernel/misc/amd64/pci_autoconfig:
		undefined symbol 'pcie_get_rc_dip'
		WARNING: mod_load: cannot load module 'pci_autoconfig'

		panic[cpu0]/thread=fffffffffbc2e3a0:
		failed to load misc/pci_autoconfig

	Work-around: Boot the original boot environment (BE) instead
	and correct the boot archive as follows

		
		user@host$ pfexec beadm mount  /mnt
		user@host$ pfexec bootadm update-archive -F -R /mnt
		user@host$ pfexec beadm unmount 

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

12380 image-update loses /dev/ptmx from /etc/minor_perm
http://defect.opensolaris.org/bz/show_bug.cgi?id=12380

	When using image-update or the Package Manager to update to
	build 125 or greater, remote access to the system via ssh(1) or
	rlogin(1) may become unavailable.  Alternatively, using
	terminal programs such as gnome-terminal(1) or xterm(1) may
	result in characters not being echoed or commands unable to be
	typed.

	Work-around: Boot the original boot environment (BE) instead
	and correct the /etc/minor_perm file contained within as
	follows

		
		user@host$ pfexec beadm mount  /mnt
		user@host$ pfexec sh -c \\
			"grep \^clone: /etc/minor_perm >> /mnt/etc/minor_perm"
		user@host$ pfexec touch /mnt/reconfigure
		user@host$ pfexec bootadm update-archive -R /mnt
		user@host$ pfexec beadm unmount 

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

13534 "Could not update ICEauthority file /.ICEauthority" on bootup of build 130
http://defect.opensolaris.org/bz/show_bug.cgi?id=13534

	After the system boots, the following warning dialog boxes may
	be displayed

		Could not update ICEauthority file /.ICEauthority

		There is a problem with the configuration server
		(/usr/lib/gconf-sanity-check-2 exited with status 256)

	Work-around: Clicking on the "Close" button for each dialog box
	will permit one to login normally.  Once logged in, enter the
	following command to correct the home directory for the "gdm"
	user

		user@host$ pfexec usermod -d /var/lib/gdm gdm

11051 default ai 121 dev ai build should point to /dev
http://defect.opensolaris.org/bz/show_bug.cgi?id=11051

	When using the Automated Installer (AI) to install development
	builds over the network, the manifest used for the install
	service should be updated to reflect that packages should be
	installed from the development repository.

	First copy the default manifest from your install image.
	Assuming the name of the create AI service is , then
	AI represents the name of the smf(5) property group
	that contains the path to the image

		user@host$ image_path=`svcprop -c -p AI/image_path`

	Next copy the default.xml file from that image and change the
	"main url" attribute of the "ai_pkg_repo_default_publisher"
	element from "http://pkg.opensolaris.org/release" to
	"http://pkg.opensolaris.org/dev"

		user@host$ cp ${image_path}/auto_install/default.xml /tmp
		user@host$ 

	Finally associate the modified manifest with the install
	service

		user@host$ pfexec installadm add -m /tmp/default.xml \\
			-n 

	Note that users of the "bootable" AI CD and USB ISO should make
	a similar change to the custom manifest that can specified as
	part of its installation procedure.

13233 /contrib packages should not depend on "entire"
http://defect.opensolaris.org/bz/show_bug.cgi?id=13233

	If packages from the "/contrib" repository have been installed
	on the system, attempts to update the system may cause the
	following error to occur

		pkg: Requested "install" operation would affect files that
		cannot be modified in live image.
		Please retry this operation on an alternate boot environment.

	Work-around: Uninstall the packages from "/contrib" which are
	causing the issue.  The list can be found through the following
	command

		user@host$ pkg contents -Ho pkg.name,action.raw -t depend | \\
			grep fmri=entire@ | cut -f1

	Once these packages have been uninstalled, repeat the packaging
	update.

11523 only permit FMRIs from same publisher for network repositories
http://defect.opensolaris.org/bz/show_bug.cgi?id=11523

	When performing certain packaging operations, errors of the
	following form may be displayed

		pkg: The following pattern(s) did not match any
		packages in the current catalog.  Try relaxing the
		pattern, refreshing and/or examining the catalogs:

	or

		The catalog retrieved for publisher '' only
		contains package data for these publisher(s):
		opensolaris.org.  To resolve this issue, update this
		publisher to use the correct repository origin, or add
		one of the listed publishers using this publisher's
		repository origin.

	These both reflect that the name of publisher has been
	incorrectly set to a value other than "opensolaris.org".  When
	using http://pkg.opensolaris.org/dev/ as an origin URI, the
	name of the publisher must be "opensolaris.org" and there
	should be no other publishers with that name.

	In addition, specifying a publisher for both the
	http://pkg.opensolaris.org/dev/ and
	http://pkg.opensolaris.org/release/ origin URIs is an error as
	only one of them should be in use at a time, using a publisher
	of "opensolaris.org".

	Work-around: If there is a publisher "publisher name" defined
	for the http://pkg.opensolaris.org/release/ origin URI, remove
	this first

		user@host$ pfexec pkg unset-publisher 

	Then reset the publisher back to the correct value

		user@host$ pfexec pkg set-publisher \\
			-O http://pkg.opensolaris.org/dev/ opensolaris.org

8347 Move boot archive from /boot/x86.microroot to /platform/i86pc/boot_archive
http://defect.opensolaris.org/bz/show_bug.cgi?id=8347

	Automated Installer servers must themselves be updated to at
	least build 128a in order to serve build 128a or greater
	images.  In addition, systems running the Distribution
	Constructor should also be updated in order to build images
	based on build 128a or greater.

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  pcie_pci' and
		removing line 2 from /etc/driver_aliases.

	Work-around: These messages 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.

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 be
	displayed 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.

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//var/pkg/lost+found/etc/sma/snmp/mibs-
Comments:

this means a new release is near?

Posted by Edward Martinez on August 01, 2010 at 01:28 PM CDT #

I did not intend to imply anything about future releases. I am just trying to make it easier to find the release notes for the developer build of OpenSolaris that is publicly available.

Posted by William Fiveash on August 02, 2010 at 03:07 AM CDT #

Good, now, where outside of SWAN(publicly) can download build 134b then? ;)

Posted by Henrik Johansson on August 02, 2010 at 09:40 AM CDT #

You can get this developer release from: http://pkg.opensolaris.org/dev

Posted by William Fiveash on August 02, 2010 at 09:49 AM CDT #

Yes, but nothing after snv_134 have been released externaly including the respins of 134, including 134b... That was just my point, I no longer expect it to be released, something else is going on.

Posted by Henrik Johansson on August 02, 2010 at 10:12 AM CDT #

I assumed the public dev. release was based on snv_134b.

Posted by William Fiveash on August 02, 2010 at 10:24 AM CDT #

It's kind of irratating to read a public blog post about an update, given how critical some of the newer fixes are, then to see the urls aren't public urls.

It would have been nice if the subject of the blog post said something to signify internal progress report or something similar so we know:
a) It's being worked on
b) This isn't ready for the public, but is proof "something" is happening..

Steve

Posted by Steve Radich on August 03, 2010 at 02:44 PM CDT #

I think somebody got ahead of oracle and opensolaris will only be available in the form of developer builds, if that is the new way osol will come. i can live with that)

Posted by Edward Martinez on August 05, 2010 at 09:55 PM CDT #

Post a Comment:
Comments are closed for this entry.
About

user12615206

Search

Categories
Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today