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] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 9 Jul 2008 15:41:41 +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:
>
>  hponcfg - configuration
>  hpdiags - ???
>  hp-snmp-agents - ??? Do they provide sensor information?
>  iLO Flash - Firmware upgrade

hpdiags and hp-snmp-agents both use this driver to gather basic
management processor info, stuff like MP NIC config and stats,
serial number, etc (but no sensors).

>
>  OK, so this is really Proliant and likely Blades only? No
> chance that this will show up elsewhere?
>
I know of no plans to use this elsewhere.

>> Yeah, those are most common.  This driver will also surface data
>> through HPSMH or HPSIM, if the proper packages are installed.
>>
>
>  Hmm. I am a bit out of touch. What are they doing?

HPSMH is "System Management Homepage", and SIM is
"Systems Insight Manager".  They both are web based management
consoles, and show the info gathered by hp-snmp-agents and hpdiags,
along with lots of other system info.

>
>  I really believe that if the HP-ILO driver is only needed
> for configuration and FW upgrades, it is OK in the current
> state. I do not think that anybody really wants to write
> another hponcfg or iLO-flash.

That is true.  Even if there was a management processor framework,
I would still want a simple read/write interface, to support
our existing software.

>  But if it is also needed to obtain sensor information, your
> colleagues should really think about supporting the
> lm_sensors framework.

It isn't needed/used for sensor info.
--
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/