BMC packages for dell-bmcflash/firmware-tools?

[Michael E Brown]

On Fri, Aug 10, 2007 at 03:39:27PM -0600, Stephen John Smoogen wrote:
> > I will look around and see what I can do about the diagnostics stuff. I
> > know a few people to talk to.
> >
> > I would really like to see something that we can regenerate on a weekly
> > basis with the latest sources rather than something that we simply
> > generate once and see stagnate.
> >
> 
> Yes.. I can see that. The main issue I would want is to see it done
> with a frozen set of tools to make sure that it didnt end up with a
> version of firmware that didnt apply updates :).

Yes, I have repo/testing/ and repo/software/. So theoretically if you
install from repo/software, it should always work, and have the latest
set of tools. I can probably store the latest few isos, in case one set
turns out badly.

> > Details? I can fix if there is something wrong with my RPMs.
> >
> 
> Well the first problem I ran into was trying to do a
> 
> system_bios_* but it would only load 1 package not all of them.
> then I put in the system_bios_<next_name> and I ran into some
> conflicts between various systems like
> system_bios_ven_<blah><blahdity><blah> and system_bios_ven_PowerEdge
> (and some others.) I removed all teh system_bios_ven lines and go a
> package that installed items.

Ah, yes. Yesterday I went and removed most of the conflicting ones. I
put "Obsoletes:" and "Provides:" in the properly-named versions, but
'repomanage' doesnt seem to automatically delete obsolete packages. I
had to whip up my own script to do that. I think it should be ok today.
If not, let me know which is broken and I can remove the conflicting
ones from the repo.

> At the moment, I can't get the OMSA items installed because I am doing
> the development of the cdrom on a system that isnt OMSA (Dell Optiplex
> 745). Once I can get a 2550 or something available.. I can hack on
> that.

OMSA will always install from the repo, even on unsupported machines, if
you properly hack it. Just hardcode a machine type that is supported in
the yum conf. (sys_ven_id=0x1028,  sys_dev_id=0x0185, for example), just
pick one of the ids from http://linux.dell.com/repo/hardware/latest/
(scroll down to the end).

--
Michael