On Thu, 2007-04-19 at 15:51 -0700, Al Chu wrote:
I'd like the ability to enter the key in hexadecimal
and have it treated as a 20-byte binary field instead of a string, which
matches how the key is handled in the Dell utilities.
I faced a similar issue/dilemma early on. Honestly, I went
On Mon, 2007-04-23 at 13:04 -0600, Levi Pearson wrote:
Patching bmc-config to support either does seem tricky. The Dell
utilities to read/set the key deal only in hex. Allowing both opens the
possibility for two different keys to be specified simultaneously.
I agree it would be a non-perfect
Al Chu wrote:
Here's an idea. How about if the user prefixes his input with a '0x',
then we assume the user wants to do up to 20 bytes of hex. If not
prefixed by '0x', then we assume the user is inputting a string?
You could use the syntax that's used for specifying WEP keys in
iwconfig:
Hi Levi,
Firstly, I would say thanks for your appreciation.
We'd also like some more extensive PEF configuration options in
bmc-config, but I haven't looked into that with any detail yet.
In the current FreeIPMI development CVS branch has separate tool called
ipmi-pef. The tool is under
Hi Levi,
We'd definitely be interested in splitting the workload with you if Bala
is open to it.
Fantastic. It will be great help for us.
The current status of ipmi-pef tool is, it just dumps Event Filter Table
and Alert Policy Table in commented texts in stdout or filename like
