Software Update: OpenSolaris 20050612

By admin On Jun 14, 2005

Spread the love

OpenSolaris is a community-based open source operating system that uses code sourced from Solaris. The first version has just been released to the general public put online† This release is available from this page for different platforms, there are also a number of torrent files available to bring in the binaries via BitTorrent. OpenSolaris is distributed under the Common Development and Distribution License† In the release notes we find the following list of changes and issues:

Changes since the OpenSolaris Pilot

Updated to Solaris Nevada build 17, plus a few changes that will be in build 18.
libc now builds from source.

Known Issues

The sources cannot be used to generate Solaris (pgadd(1m)) packages.

The following make(1) targets are known not to work:

make ribbon
make check

Non-DEBUG kernel builds have not been tested.

“Install -i” has not been tested on all platforms. It is known not to work for the lw8 platform.

Cross-compilation between SPARC and x86 is not supported. But builds on x86 systems (amd64 or i386) will build both amd64 and i386 binaries.

This is unlikely to be fixed any time soon. If you want to build both SPARC and x86, your choices are (a) create two workspaces, or (b) access a single workspace using NFS. If you use a single workspace, you’ll want to do a “make clean” or “make clobber” before building the other platform. Note that nightly(1) will do a “make clobber” for you.

You may see console warnings like

Feb 26 13:55:48 magneto sshd[100804]: libpkcs11: Cannot load PKCS#11
library /usr/lib/security/pkcs11_softtoken_extra.so. dlerror:
ld.so.1: /usr/lib/ssh/sshd: fatal:
/usr/lib/security/pkcs11_softtoken_extra.so: open failed: No
such file or directory. See cryptoadm(1M). Skipping this plugin.
Feb 26 13:55:48 magneto sshd[100804]: Kerberos mechanism library
initialization error: unknown error.

These messages can be ignored unless you need working crypto (eg, Kerberos). To fix, change pkcs11_softtoken_extra.so to pkcs11_softtoken.so in /etc/crypto/pkcs11.conf and do “svcadm restart cryptosvc”.

When BFUing, you may see error messages like

bfu: could not copy /net/greenline.eng/meta0/smf/post-5090532/kdmconfig.xml

These messages can be ignored, as long as you’re BFUing on top of Build 16 or later, as recommended above.

bfu needs to be cleaned up so that it can easily handle flag days when run externally. This has been coded and mostly tested (CR 4865419). This will also fix the “could not copy” error messages.

[break]

Version number	20050612
Operating systems	solaris
Website	OpenSolaris.org
Download
License type	Conditions (GNU/BSD/etc.)