OpenSolaris is een community gebasseerd open-sourcebesturingssysteem dat gebruikmaakt van code die afkomstig is van Solaris. Zojuist is de eerste versie voor het grote publiek online gezet. Deze release kan vanaf deze pagina voor verschillende platformen gedownload worden, eveneens zijn er een aantal torrent-bestanden beschikbaar om de binaries via BitTorrent naar binnen te halen. OpenSolaris wordt verspreid onder de Common Development and Distribution License. In de release notes vinden we de volgende lijst met veranderingen en problemen:
Changes since the OpenSolaris PilotKnown Issues
- Updated to Solaris Nevada build 17, plus a few changes that will be in build 18.
- libc now builds from source.
[break]
- The sources cannot be used to generate Solaris (pkgadd(1m)) packages.
- The following make(1) targets are known not to work:
- make lint
- 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 plug-in.
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 (e.g., 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.
