Semi-blind guess: what about exercising 'pkg list'? Are any packages on Nevada installed via pkg or are they all via SVR4? Maybe an empty or failed output would indicate Nevada... ?? --emk [1][email protected] wrote:
On Thu, May 14, 2009 at 01:10:04PM -0600, Jim Walker wrote: Danek Duvall wrote: There's no interface we've specifically made available for this, and I'm not sure what to suggest that won't change. Not knowing the architecture of what you're trying to do, my suggestion would be to simply install different bits on OpenSolaris than on Nevada, which should be easy enough since you'll be installing different packages. But maybe it's not that straightforward for some reason? It's not a big deal. Like I said, if beadm is there I can assume it's opensolaris and not nevada. I was just wondering if there was anything better to use or an os id code somewhere in memory. What happens when beadm gets integrated into ONNV? That'll break any code that depends upon this assumption. -j _______________________________________________ pkg-discuss mailing list [2][email protected] [3]http://mail.opensolaris.org/mailman/listinfo/pkg-discuss References 1. mailto:[email protected] 2. mailto:[email protected] 3. http://mail.opensolaris.org/mailman/listinfo/pkg-discuss _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
