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 (on-closed-bins-i386.tar.bz2), there is no "security" directory in the path /export/home/build/b111b/closed/root_i386/usr/lib/security. I have checked the README.ON-BINARIES.i386 and it also doesn’t mention the security directory under the file list. If i skip this closed binary problem resolution steps and continue with all other steps of nightly build and kernel build and install , i get three boot options after machine is rebooted. 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. It seems that due to the problem of closed binary only i am not able to boot machine with b111benv or Solaris sunv_111b x86 options. Please let me know if this (closed binary problem) is the exact reason that machine are not getting booted with b111benv or Solaris sunv_111b x86 boot options. If that is the case , is there any workaround to address this issue.? -- This message posted from opensolaris.org _______________________________________________ opensolaris-help mailing list opensolaris-help@opensolaris.org
