An alternative in this particular case would be to install the RPM with
the "--nodeps" option to ignore dependencies. AFAIK, the /usr/bin/ksh
dependency is only there for the dsmj Java GUI client wrapper script,
which isn't usable on ESX anyway since Java isn't installed (on either
2.x or 3.x of ESX).
One could argue that Tivoli should replace it with /bin/bash in the
Linux RPMs, since the Linux distributions supported by TSM have bash
installed by default, but not (necessarily) ksh. In the case of ESX
3.x, VMware doesn't even provide any ksh RPM (I think they included
pdksh on the 2.5 CDs/ISOs, but didn't install by default).
The "enabler package" from VMware was to fix an X11 dependency with
ESX 3.0 and TSM 5.2 or earlier clients. According to the VMware site,
it's not needed for TSM 5.3 clients or ESX 3.0.1 or newer.
> Which ESX?
> On 2.5.x you scholud use older version, up to 5.3.5. New esx release,
> above 3.0 (for example 3.0.2) need installed special rpm from vmware
> which add needed dependencies (I'm not sure name, but it is easy to
> find them).
> So - which version of ESX you use?
> On 8/27/07, David Browne <dbrowne AT humana DOT com> wrote:
> > I have very little Linux knowledge. So any suggestions will be appreciated.
> > We are attempting to test TSM backups for Linux.
> > When installing v5.3.4
> > the API module installs correctly
> > but the BA module results in the following:
> > package TIVsm-API-5.3.4-0 is already installed
> > [[email protected] tsm]# rpm -i TIVsm-BA.i386.rpm
> > error: Failed dependencies:
> > /usr/bin/ksh is needed by TIVsm-BA-5.3.4-0
Hello World. David Bronder - Systems Admin
Segmentation Fault ITS-SPA, Univ. of Iowa
Core dumped, disk trashed, quota filled, soda warm. david-bronder AT uiowa