Solaris 2.x

Solaris 2.x

[Ken Moorley]

Please excuse my ignorance, but would someone please advise if the following
paragraph from the zsh FAQ means that this option will NEVER be available
under Solaris 2.x or may be developed in a future version ?

  
*Note for Solaris 2.2 and 2.3*: The UCB versions of the routines for
  reading directories are not usable (the struct definitions are
  incompatible with the ones assumed by zsh).  Make sure you compile
  without any reference to /usr/ucblib in (e.g.) your LD_LIBRARY_PATH.
  The symptom of this is that globbed filenames will be missing the
  first two letters.

Please reply to ken@mitsui.oz.au

Ken Moorley
Mitsui Computer Limited
Unit 1
14 Aquatic Drive
Frenchs Forest NSW 2086 Australia

Re: Solaris 2.x

[Philip Kizer]

ken@mitsui.oz.au (Ken Moorley) wrote:
>Please excuse my ignorance, but would someone please advise if the following
>paragraph from the zsh FAQ means that this option will NEVER be available
>under Solaris 2.x or may be developed in a future version ?

No, the important sentence in the paragraph you quoted is the following:

>  Make sure you compile without any reference to /usr/ucblib in (e.g.) your
>  LD_LIBRARY_PATH.

I use zsh on many Solaris 2.x (SunOS 5.x) machines each day.  All it really
means is that anyone compiling programs on SunOS 5 platforms needs to limit
as much as possible (preferably to nil) all references to the libraries and
commands found in the UCB compatibility packages.

What commands you do use from the UCB compatibility packages, I suggest you
merely alias to refer to them by full path or merely use full path such as
(e.g.) /usr/ucb/renice or /usr/ucb/install.

In fact, for developers, it is best to compile (and test!) all programs
that are to be installed as publicly available with no LD_LIBRARY_PATH set
whatsoever.  This guarantees that any user, no matter how minimal their
environment will be able to execute that program.


-philip

____________________________________________________________ Philip Kizer ___
Texas A&M CIS Operating Systems Group, Unix ( 409.862.4120 ) pckizer@tamu.edu

"Relying on the government to protect your privacy is like asking a peeping
Tom to install your window blinds." -John Perry Barlow, EFF co-founder

Re: Solaris 2.x

[Bart Schaefer]

On Sep 5, 11:30am, Ken Moorley wrote:
} Subject: Solaris 2.x
}
} Please excuse my ignorance, but would someone please advise if the
} following paragraph from the zsh FAQ means that this option will
} NEVER be available under Solaris 2.x or may be developed in a future
} version ?

Option?  What option?  The option to build with /usr/ucblib?  What for?

Zsh should be fully functional provided that you don't use /usr/ucblib.
There isn't anything in /usr/ucblib that can't be accomplished without
it; nothing is lost.

Perhaps there's some confusion with that last sentence:

}   The symptom of this is that globbed filenames will be missing the
}   first two letters.

That sentence means, "If you accidentally compiled with /usr/ucblib,
you'll be able to tell, because globbed filenames will be missing the
first two letters.  If you compiled it the right way, the filenames
will have all the letters."

Peter S., perhaps that paragraph should be reworded:

*Note for Solaris 2.2 and 2.3*: The UCB versions of the routines for
  reading directories are not usable (the struct definitions are
  incompatible with the ones assumed by zsh).  The symptom of this
  is that globbed filenames will be missing the first two letters.
  For correct globbing, make sure you compile without any reference
  to /usr/ucblib in (e.g.) your LD_LIBRARY_PATH.


-- 
Bart Schaefer                                      Vice President, Technology
schaefer@z-code.com                                Z-Code / NCD Software Inc.

What quantity of engineers is required to rotationally reconfigure an
electronically-actuated filament-enabled photon-wave generator?