During the course of b111b build/installation , i have read that problem of closed binaries frequently occur. To resolve the closed binary problem following steps have been suggested .
--------------------------------8----------------------------------- # cd /export/home/build/b111b/closed/root_i386/usr/lib/security # mv pkcs11_softtoken.so.1 pkcs11_softtoken.so.1.orig # cp -p /usr/lib/security/pkcs11_softtoken.so.1 . # cd /export/home/build/b111b/closed/root_i386/usr/lib/security/amd64 # mv pkcs11_softtoken.so.1 pkcs11_softtoken.so.1.orig # cp -p /usr/lib/security/amd64/pkcs11_softtoken.so.1 . ----------------------------------8------------------------------- But when i extracted the closed-bins, there is no "security" directory in the path /export/home/build/b111b/closed/root_i386/usr/lib/security. I checked the README.ON-BINARIES.i386 and it also doesn’t mention the security directory under the file list. So i have skipped the above steps and have performed all the other build and installation steps. After machine is rebooted, following three options are shown in boot menu:- 1. OpenSolaris 2009.06 2. b111benv 3. Solaris sunv_111b x86 But the machine is unable to get booted from option 2nd or 3rd. It can be booted only with 1st (Default) option. Please let me know if machine is not getting booted in the b111benv because the closed binary problem is not resolved. If that is the case , is there any work around available for that? -- This message posted from opensolaris.org _______________________________________________ opensolaris-help mailing list opensolaris-help@opensolaris.org
