root inodes in a non-global zone

Anyone know a trick to confuse a process in a non-global zone on the inode numbers for dot and dot-dot at root? I.E.: ls -lair /

         3 drwxr-xr-x  26 root     root          28 Mar 23 09:26 ..

         100  drwxr-xr-x  26 root     root          28 Mar 23 09:26 .

But a global zone: 

         3 drwxr-xr-x  34 root     root          36 Mar 30 10:43 ..

         3 drwxr-xr-x  34 root     root          36 Mar 30 10:43 .

I've got an old flexlm service that for some reason will not start in a non-global zone. I've read complaints online, and a rumor of a way to fix this with other flexlm binaries or a dtrace LD_PRELOAD, but no concrete solutions that I can find.

The only way I've been able to work around this flexlm issue with inodes is to create a filesystem for the non-global zone's root directory and then the inodes will match like a real root filesystem. But the real issue with this is it is not a standard or supported thing to do, it breaks some management things like Live Upgrade. I've got a ticket open on this, but perhaps the community has an answer, like the LD_PRELOAD fixer I could use for the flexlm user.