Frustration
Posted on March 11, 2010
root@quatro src$ uname -a SunOS quatro 5.11 snv_133 i86pc i386 i86pc Solaris root@quatro src$ pkg search gcc Segmentation Fault (core dumped) root@quatro src$ exit exit benr@quatro src$ pkg search gcc Segmentation Fault benr@quatro src$ pfexec pkg search gcc INDEX ACTION VALUE PACKAGE description set GCC pkg:/SUNWgccruntime@3.4.3-0.97 description set GCC pkg:/developer/gcc/gcc-libgfortran@4.3.3-0.133 description set GCC pkg:/developer/gcc/gcc-libssp@4.3.3-0.133 description set GCC pkg:/developer/gcc/gcc-libgcc@4.3.3-0.133
Why does IPS still suck? Seriously, we can’t catch errors before segfaulting? And people wonder why I claim that IPS and AI are so immature. I just can’t wait for Oracle to cram this down my throat.
I want SX:CE back. Anybody in MPK17 listening!?!? Stop telling customers they are stupid for using post-install scripts, stop pontificating about how you know better. ZFS made claims to rightness and proved itself. IPS has yet to convince me…. its had years, and still has yet.
Update:
I’m getting email from folks asking about the underlying problem here. The issue is that Python freaks if you have alternate version installed an in your LD_LIBRARY_PATH or PYTHONPATH.
root@quatro ~$ pkg search virsh Segmentation Fault (core dumped) root@quatro ~$ unset PYTHONPATH root@quatro ~$ pkg search virsh Segmentation Fault (core dumped) root@quatro ~$ unset LD_LIBRARY_PATH root@quatro ~$ pkg search virsh INDEX ACTION VALUE PACKAGE basename file usr/bin/amd64/virsh pkg:/SUNWlibvirt@0.5.11-0.128 basename file usr/bin/i86/virsh pkg:/SUNWlibvirt@0.5.11-0.128
But that’s not the point I’m making… the point is that there isn’t a wrapper to catch these types of issues. IPS is a critical system utility and shouldn’t be derailed by something so simple. Its just immaturity.