On Thu, Oct 8, 2009 at 4:55 PM, Garrett D'Amore <gdamore at sun.com> wrote: > Peter Tribble wrote: > >> I am seeing use of ?/usr/ucblib/libtermcap.so.1 and >> /usr/ucblib/libucb.so.1 on x86, >> and given that this location has only ever seen Solaris 10 on x86 that >> must have >> been due to software built recently. (Not by myself, either, so I may >> have to track >> it down.) >> > > Wow. ?That's really unfortunate. ?I can only imagine this is fallout from > /usr/ucb/cc being in people's paths. ?This is a the main reason I've always > advised against having /usr/ucb on your path at all, but only at the *end* > if you absolutely must have it.
Unfortunately, that's not so. I've removed cc/lint/ld from /usr/ucb during installation on any system I've used for many years; no user would have logged into a system here and been able to build software using /usr/ucb/cc because it plain doesn't exist. Something must be explicitly linking against it rather than accidentally getting it via /usr/ucb/cc. >> On sparc, I can see usage of all the libraries in /usr/ucblib that isn't >> due to >> binary compatibility. (More recent than /usr/4lib, in other words.) >> > > Can you help us identify some of the culprits? ?Are these locally compiled > open source applications? ?Commercial applications? ?Or home grown software? I can try. On the systems I'm currently evaluating for migration onto something more modern, it's mostly commercial applications by the looks of it. Almost nothing locally compiled or home grown, although there may be some stuff imported from elsewhere. If I have anything I'm allowed to share I'll follow up; I'm still doing a preliminary audit. > Would any of these applications be seriously impaired by a requirement to > either recompile "with the right flags", or to use S10 containers? No source, so no recompile, in many cases. Sometimes it's just been lost. Not everything runs in containers. Take clearcase as an example; you need a certain patch level to run it on S10 in the global zone; you need to go further to run it in a native zone; branded zones are out. And sometimes you have to run multiple applications together. Sometimes you have to co-locate an NFS server. (It's a shame you can't apply a brand to a process: that would be a very neat way to get linux apps to run alongside normal apps; and would provide an elegant way to get compatibility for certain applications without prejudicing the entire OS.) > Its possible that if this problem is as widespread as you claim, then this > case cannot go forward. It's more widespread than I feared, at any rate. -- -Peter Tribble http://www.petertribble.co.uk/ - http://ptribble.blogspot.com/
