linux-kernel - RE: [PATCH][resubmit] HP iLO driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Wed, 9 Jul 2008 14:47:14 +0000
From:	"Altobelli, David" <david.altobelli@...com>
To:	Martin Knoblauch <knobi@...bisoft.de>, Pavel Machek <pavel@...e.cz>
CC:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"greg@...ah.com" <greg@...ah.com>
Subject: RE: [PATCH][resubmit] HP iLO driver

Martin Knoblauch wrote:
> Somehow I feel the need to step in, as I believe that this
> thread is really going in the wrong direction.
>
> It is true that David (or HP) definitely could have done a
> better job in describing why this driver is needed and what
> HP-Utilities are depending on it. This might have lead some
> people to misinterpret what ILO is about.

I'm sorry about that.  This driver is needed for tools like:
hponcfg, hpdiags, hp-snmp-agents, and iLO flash utilities.

> ILO (Q: does HP still sell RILOE boards and are they
> supporten by the driver?) is a command processor that allows

RILOE cards are not sold any more, and are not supported by this driver.

>
> ILO can be configured either offline (server OS shut down),
> or via the external interfaces, or from a running OS via some
> HP provided utilities. For this a driver is needed, and that
> is what we are talking about. From my experience as an
> administrator of HP Proliant systems the only local uses for
> the *internal* ILO interface is to set-up the thing, and to
> do firmware upgrades.

Yeah, those are most common.  This driver will also surface data
through HPSMH or HPSIM, if the proper packages are installed.

> To obtain sensor data locally there are other ways, which do
> not need the ILO kernel driver (hplog together with hpasmd,
> which unfortunately are closed source). So , unless the
> HP-ILO driver is just a replacement of the old "cpqci"
> driver, there is no need to pester David on functionality.
> If, of course the HP-ILO driver is needed to get to the
> hpasm/hplog functionality (no driver was needed so far) the
> story might be different. But then HP should provide the
> specs for the Proliant sensor interface anyway and work
> together with the lm_sensors project. But that is a different story.

This is a replacement for cpqci, which was released in the
"hprsm" package, and later replaced by the "hp-ilo" package.
The former package was not GPL, the latter is.
I rewrote the driver to make it (hopefully) more palatable,
in terms of both style and functionality.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/