Index index by Group index by Distribution index by Vendor index by creation date index by Name Mirrors Help Search

cpqarray-2.6.1-1 RPM for i586

From SourceForge / c / cp / cpqarray / cpqarray-sles9 / 2.6.1

Name: cpqarray Distribution: SUSE LINUX Enterprise Server 9
Version: 2.6.1 Vendor: Hewlett-Packard Company
Release: 1 Build date: Mon Oct 25 07:07:21 2004
Group: System Environment/Kernel Build host:
Size: 109115 Source RPM: cpqarray-2.6.1-1.src.rpm
Packager: Hewlett-Packard Company
Summary: HP Smart Array Driver v2.6.1
This RPM will install the Hewlett-Packard cpqarray
version 2.6.1-1 driver.

It will install a gzipped tar file, cpqarray-2.6.1-1_2004_10_24.tar.gz
into /opt/hp/storage_drivers.  (The destination directory may be changed
vi RPM's --prefix or --relocate options, provided you have rpm
v. 4.0.3 or better.  Additionally, by default, it will install the
driver object modules under the appropriate /lib/modules subdirectory,
attempt to create a new initrd image, and modify your LILO or GRUB
configuration.  If you do no wish to have your LILO or GRUB
configuration or initrd image modified, you have several options.

You can install the RPM wil the "--noscripts" option, which will
suppress all actions except for installation of the gzipped tar
file, so, LILO and GRUB configurations will not be disturbed and a
new initrd image will no be created.  Then, you can unpack the
gzipped tar file and install the drivers yourself using the "install"
script contained within the tar archive.  (Documentation for the
"install" script is contained in the tar archives as well.  Alternatively
you could manually copy the cpqarray.ko files into the appropriate
/lib/modules subdirectory and manually modify your boot loader's
configuration if you so choose.)

Or, there are several environment variables which will suppress
various aspects of the RPM package's post (un)installation behavior:

    Suppress making multiple initrd images for all base and errata
    kernels.  Create the initrd image for the currently active
    kernel only.

    Suppress initrd, LILO, and GRUB modifications.

    Perform only a "dry run" of the post-install steps.  Copying of
    driver object modules, and LILO, GRUB, and initrd configuration
    changes will be "simulated" but not actually performed.  (Note,
    normally a "dry run" is done automatically once prior to
    performing the real installation as a safeguard.  If the "dry run"
    fails, the real installation is not performed.  Setting the "DRYRUN"
    variable simply makes the installation halt after the "dry run"
    even if the "dry run" succeeds.)  Note also that the RPM is still
    considered to be "installed" and "rpm" will refuse to install it
    again, so if you use the "DRYRUN" option, you'll have to uninstall
    the RPM via:

      rpm -e --noscripts cpqarray-2.6.1-1

    before reinstalling it without the "DRYRUN" variable set to enable
    LILO, GRUB and initrd modifications to proceed.  Alternately, you
    could manually unpack the gzipped tar file and use the "install"
    script to install the driver object modules, make a new initrd
    image and change your boot loader configuration, or manually
    perform those steps yourself.

NOTE:  The /etc/modules.conf file will not be updated.  Most of the time,
  this will not be a problem, as the drivers installed by this RPM will
  be updates to previously installed drivers.  If, for whatever reason,
  the RPM installs a driver for which there is not already an entry in
  /etc/modules.conf, then the driver will not be loaded automatically at
  boot time, and it will be necessary to use insmod manually, or modify
  /etc/modules.conf manually.  If /etc/modules.conf must be modified
  manually to add an entry for the driver, then a new initrd image
  must also be created, since mkinitrd uses modules.conf to determine
  what to put into the initrd image.
NOTE:  The above holds true to SUSE distributions as well, except that
  the file that contains the list of modules to be placed in the initrd
  is /etc/sysconfig/kernel rather than /etc/modules.conf.  Likewise the
  initrd command is "mk_initrd" rather than "mkinitrd".







Generated by rpm2html 1.8.1

Fabrice Bellet, Sun Apr 13 23:12:56 2014