> On Sep 1, 2025, at 04:29, Marcin Cieslak <[email protected]> wrote:
>
> Dear Dan,
>
> as some who has had a pull request open with some open source
> project for 11 years I share your frustration.
>
> I have you have dealt with all of the legalese stuff properly in your recent
> shar file.
Somewhat. When you search around for racadm license, what you get is info
about how to use racadm to upload a license key file to a machine. I haven’t
found a proper license file per-se.
> In the Yocto Linux build tree of iDRAC 7.20.30.50 (available from
> opensource.dell.com) they download argtable 2.13 from Sourceforge
> and simply build it without any change. The RPM files you have contain
> probably argtable 2.11 from the year 2009. But given you need
> a Linux build anyway, this is of no help here.
In the blog entry I linked, I point out that dell ships a copy of argtable.
> racadm seems to be embargoed, i.e. the iDRAC tree contains some binary
> components pre-built by Dell.
>
> I think it perfectly makes sense to use the old bug and submit the
> git diff there (as an attachment), you can also push the patch to
> https://reviews.freebsd.org/differential/
>
> Probably it might be worth switching to the Red Hat 9 userland
> instead of the already dead CentOS 7.
Yes, I said that as well. Also, the current port won’t work with any of the
current openssl stuff, so a new version needs to be pulled in.
> But there is also one more possibility to deal with the Dell machines:
>
> https://github.com/dell/iDRAC-Redfish-Scripting provides the information
> how to script some functionality of iDRAC using the Redfish protocol.
>
> There is even a guide mapping some racadm commands to the Redfish APIs
> available.
Yes, but most of the guides out there and a lot of the tooling out there, and
*all* the dell documentation talk about racadm.
https://xkcd.com/927/
> But a full racadm port can be useful anyway.. I think we are pretty
> close to get this committed....
Let’s hope.
>
> Marcin
