Sysop: | Amessyroom |
---|---|
Location: | Fayetteville, NC |
Users: | 27 |
Nodes: | 6 (0 / 6) |
Uptime: | 46:56:19 |
Calls: | 632 |
Calls today: | 3 |
Files: | 1,187 |
D/L today: |
24 files (29,813K bytes) |
Messages: | 176,788 |
On Sep 1, 2025, at 04:29, Marcin Cieslak <saper@saper.info> wrote: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 havenrCOt found a proper license file per-se.
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.
In the Yocto Linux build tree of iDRAC 7.20.30.50 (available from opensource.dell.com) they download argtable 2.13 from SourceforgeIn the blog entry I linked, I point out that dell ships a copy of argtable.
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.
racadm seems to be embargoed, i.e. the iDRAC tree contains some binary components pre-built by Dell.Yes, I said that as well. Also, the current port wonrCOt work with any of the current openssl stuff, so a new version needs to be pulled in.
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.
But there is also one more possibility to deal with the Dell machines: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://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.
But a full racadm port can be useful anyway.. I think we are prettyLetrCOs hope.
close to get this committed....
Marcin--
On Sep 1, 2025, at 03:53, Kurt Jaeger <pi@freebsd.org> wrote:I found the old conversation rCo it wasnrCOt with you, it was bdrewery. It was that poudriere tries at the end to delete files it has installed in the jail, specifically it tries to remove /compat/linux and the like as part of the cleanup step, and something with those failed because the file was in use somehow. (i.e. nothing was broken with my port, it was entirely a poudriere bug related to Linux). Brian offered a poudriere bulk command that could be used to force it to build when testport wouldnrCOt return clean at the time.
Hi!
IrCOve had a PR in place to generate a port that basically extracts
a single binary and library from the dell Linux RPMs.
I think it is this PR:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201799
and I looked at it in 2021. At that time it failed to build
using poudriere.
I have not found the time to look at it again since then.
On Sep 1, 2025, at 12:03, Kurt Jaeger <pi@freebsd.org> wrote:Yeah, that was a typo. Linux moved from linux_base-c7 (centos) to linux_base-rl9 (rocky linux). I think rl7 never existed.
Hi!
You wouldnrCOt want to use whatrCOs there, it wonrCOt dlopen a modern
ssl library anyway, so at most it would run and produce some output,
but would fail when you told it to connect to something. I donrCOt
know if this issue is now fixed, but when I remake the makefile
with linux-rl7 and modern versions of the dell RPMrCOs, werCOll find
out.
The most recent version is linux-rl9, there's no linux-rl7 anymore in the ports tree -- does your patch work with rl9 ?
----
pi@FreeBSD.org +49 171 3101372 Now what ?
On Sep 1, 2025, at 16:48, Marcin Cieslak <saper@saper.info> wrote:--
Dear Dan,
can you check if the port below works?
I don't have any Dell machines around but it established an SSL
connection to my port 443 successfully.
Marcin
# This is a shell archive. Save it in a file, remove anything before
# this line, and then unpack it by entering "sh file". Note, it may
# create directories; files and directories will be owned by you and
# have default permissions.
#
# This archive contains:
#
# racadm9
# racadm9/Makefile
# racadm9/pkg-plist
# racadm9/distinfo
# racadm9/pkg-descr
# racadm9/pkg-message
#
echo c - racadm9
mkdir -p racadm9 > /dev/null 2>&1
echo x - racadm9/Makefile
sed 's/^X//' >racadm9/Makefile << '747e38b00e309df20a6f016e31b0a896'
X# $FreeBSD$
X
XPORTNAME= racadm
XPORTVERSION= 11.3
XCATEGORIES= sysutils linux
XMASTER_SITES= https://linux.dell.com/repo/hardware/DSU_25.08.25/os_dependent/RHEL9_64/racadm/
XDISTNAME= srvadmin-idracadm7-11.3.0.0-795
XDISTFILES= srvadmin-argtable2-11.3.0.0-795.el9.x86_64.rpm \
X srvadmin-idracadm7-11.3.0.0-795.el9.x86_64.rpm
X XMAINTAINER= dmahoney@isc.org
XCOMMENT= Dell remote access controller admin utility
X
XLICENSE= DELL
XLICENSE_NAME= Dell Proprietary License
XLICENSE_TEXT= This program is NOT in the public domain.\
X Dell allows free downloads and mirroring of the linux RPMs this port is based on,\
X but you should read the full license here:\
X https://www.dell.com/learn/us/en/uscorp1/legal_terms-conditions_dellgrmwebpage/art-software-license-agreements\
X and determine if it is right for you or your organization.
XLICENSE_PERMS= dist-mirror no-dist-sell pkg-mirror no-pkg-sell auto-accept X
XONLY_FOR_ARCHS= amd64
XWRKSRC= ${WRKDIR}/${PORTNAME}
XNO_WRKSUBDIR= yes
X
XRUN_DEPENDS= linux_base-rl9>=0:emulators/linux_base-rl9
X
XUSE_LINUX= rl9
XUSE_LINUX_PREFIX=YES
XUSE_LINUX_RPM=YES
XNO_BUILD=YES
X
Xdo-install:
X cd ${WRKSRC}; ${CP} -pR * ${STAGEDIR}${PREFIX}
X ${RLN} ${PREFIX}/lib64/libssl.so.3 ${STAGEDIR}${PREFIX}/opt/dell/srvadmin/lib64/openmanage/private/libssl.so
X
X.include <bsd.port.mk>
747e38b00e309df20a6f016e31b0a896
echo x - racadm9/pkg-plist
sed 's/^X//' >racadm9/pkg-plist << '1cc4b16233ee29344102051bde6b0bae' Xetc/ld.so.conf.d/srvadmin-idrac7.conf
Xopt/dell/srvadmin/bin/idracadm7 Xopt/dell/srvadmin/lib64/openmanage/private/libargtable2.so.0 Xopt/dell/srvadmin/lib64/openmanage/private/libargtable2.so.0.1.6 Xopt/dell/srvadmin/lib64/openmanage/private/libssl.so Xopt/dell/srvadmin/sbin/racadm-wrapper-idrac7 Xopt/dell/srvadmin/share/man/man3/argtable.3 Xopt/dell/srvadmin/share/man/man3/argtable2.3 Xusr/lib/.build-id/ca/690910e69bfe67f0f4bd2e4b155adfcf8627d3 Xusr/lib/.build-id/51/8f7b88f8e092b14c16c3454fa89b3e0541645f Xusr/share/doc/srvadmin-argtable2/AUTHORS Xusr/share/doc/srvadmin-argtable2/COPYING Xusr/share/doc/srvadmin-argtable2/ChangeLog Xusr/share/doc/srvadmin-argtable2/README
1cc4b16233ee29344102051bde6b0bae
echo x - racadm9/distinfo
sed 's/^X//' >racadm9/distinfo << '4146598f28ba0d447745a4554e995d8b' XTIMESTAMP = 1756768563
XSHA256 (srvadmin-argtable2-11.3.0.0-795.el9.x86_64.rpm) = 1db4a3431dd6b90a668467a0e623961f8bde9d975f268f6dbb59fde10bece165
XSIZE (srvadmin-argtable2-11.3.0.0-795.el9.x86_64.rpm) = 66651
XSHA256 (srvadmin-idracadm7-11.3.0.0-795.el9.x86_64.rpm) = 9aaa86556fba84088494618d58a92d0e9ab0949eeb201ec7b0d91d17ffce9047
XSIZE (srvadmin-idracadm7-11.3.0.0-795.el9.x86_64.rpm) = 1142062 4146598f28ba0d447745a4554e995d8b
echo x - racadm9/pkg-descr
sed 's/^X//' >racadm9/pkg-descr << '60f89da3ebc0f64cfdeec27b55288bef' XLinux's cli to interface with Dell's Remote Access Controller (DRAC).
X
XThis is probably only useful in "remote" mode. 60f89da3ebc0f64cfdeec27b55288bef
echo x - racadm9/pkg-message
sed 's/^X//' >racadm9/pkg-message << '3c369757d3be1edeaff655d0e079611f'
X[
X{ type: install
X message: <<EOM
Xracadm7 has been installed under the linux "compat" tree:
X(by default, /compat/linux/opt/dell/srvadmin/bin/idracadm7) due to linux library dependencies.
X
XIt is left to the user to alias/symlink this path in their scripts.
XNote that under FreeBSD this will not work as a "local" racadm (to operate on an iDrac installed in the machine where it is run).
XEOM
X}
X]
3c369757d3be1edeaff655d0e079611f
exit
can you check if the port below works?
I don't have any Dell machines around but it established an SSL
connection to my port 443 successfully.
Testbuild on 14.3 and 15.0 was fine.
On Sep 2, 2025, at 12:56, Kurt Jaeger <pi@freebsd.org> wrote:TLDR: Yes, and it works.
Hi!
can you check if the port below works?
I don't have any Dell machines around but it established an SSL
connection to my port 443 successfully.
Testbuild on 14.3 and 15.0 was fine.
Well, as building works, someone needs to test on a Dell box
with that stuff. Anyone ?
can you check if the port below works?
I don't have any Dell machines around but it established an SSL
connection to my port 443 successfully.
On Sep 1, 2025, at 22:38, Kurt Jaeger <pi@freebsd.org> wrote:
Hi!
can you check if the port below works?
I don't have any Dell machines around but it established an SSL
connection to my port 443 successfully.
Testbuild on 14.3 and 15.0 was fine.
--
pi@FreeBSD.org +49 171 3101372 Now what ?
On Sep 2, 2025, at 15:54, Marcin Cieslak <saper@saper.info> wrote:My bad, because you sent it in-line, I just copy-pasted into the shell. YourCOve also rewritten the symlink back to relative, and itrCOs working for you, but not for me, and I canrCOt figure out why.
On Tue, 2 Sep 2025, Dan Mahoney (Ports) wrote:
TLDR: New .shar attached to fix a few port weirdnesses involving what looks like specifically a weird interaction between poudriere, the linux emulation layer and long symlinks. I think werCOre ready to go, but people should read the following.
You .shar file had Windows CRLF at the end.
I have also installed linux-rl9-ca-certificates package.I am sure it didnrCOt previously, but letrCOs see what happens when I build this with poudriere bulkrCa.
Since I don't have any iDRAC, I have tested it via
# /compat/linux/opt/dell/srvadmin/bin/idracadm7 -r localhost getsysinfo
connecting to "openssl s_server -port 443 -key key -cert cert" running on localhost
given that my certificate is signed by Let's Encrypt,
I get no warnings from racadm and the SSL connection is established.
That strange relative symbolic link seeps to work:
# find /compat/linux -name 'libssl*' -ls--
599103 1266 -rwxr-xr-x 1 root wheel 1023516 Feb 11 2025 /compat/linux/usr/lib/libssl.so.3.2.2
599102 1 lrwxr-xr-x 1 root wheel 15 Feb 11 2025 /compat/linux/usr/lib/libssl.so.3 -> libssl.so.3.2.2
599722 1161 -rwxr-xr-x 1 root wheel 957488 Feb 11 2025 /compat/linux/usr/lib64/libssl.so.3.2.2
599721 1 lrwxr-xr-x 1 root wheel 15 Feb 11 2025 /compat/linux/usr/lib64/libssl.so.3 -> libssl.so.3.2.2
603089 1 lrwxr-xr-x 1 root wheel 83 Sep 2 22:48 /compat/linux/opt/dell/srvadmin/lib64/openmanage/private/libssl.so -> ../../../../../../../../../../../../../../../compat/linux/usr/lib64/libssl.so.3.2.2<racadm3.shar>
On Sep 2, 2025, at 18:05, Marcin Cieslak <saper@saper.info> wrote:Realpath works:
On Tue, 2 Sep 2025, Dan Mahoney (Ports) wrote:
On Sep 2, 2025, at 17:15, Marcin Cieslak <saper@saper.info> wrote:
find /compat/linux -name 'libssl*' -ls
root@poudriere-pkb:/home/dmahoney # find /compat/linux -name 'libssl*' -ls >> 227550 1201 -rwxr-xr-x 1 root wheel 957488 Feb 11 2025 /compat/linux/usr/lib64/libssl.so.3.2.2
227549 1 lrwxr-xr-x 1 root wheel 15 Feb 11 2025 /compat/linux/usr/lib64/libssl.so.3 -> libssl.so.3.2.2
226805 1 lrwxr-xr-x 1 root wheel 15 Feb 11 2025 /compat/linux/usr/lib/libssl.so.3 -> libssl.so.3.2.2
226806 1305 -rwxr-xr-x 1 root wheel 1023516 Feb 11 2025 /compat/linux/usr/lib/libssl.so.3.2.2
241928 1 lrwxr-xr-x 1 root wheel 83 Sep 2 23:17 /compat/linux/opt/dell/srvadmin/lib64/openmanage/private/libssl.so -> ../../../../../../../../../../../../../../../compat/linux/usr/lib64/libssl.so.3.2.2
And it does not stat? Maybe there is some another symbolic link accross the tree...
What does the realpath say>
On Sep 2, 2025, at 18:21, Dan Mahoney (Ports) <freebsd@gushi.org> wrote:
--On Sep 2, 2025, at 18:05, Marcin Cieslak <saper@saper.info> wrote:
On Tue, 2 Sep 2025, Dan Mahoney (Ports) wrote:
On Sep 2, 2025, at 17:15, Marcin Cieslak <saper@saper.info> wrote:
find /compat/linux -name 'libssl*' -ls
root@poudriere-pkb:/home/dmahoney # find /compat/linux -name 'libssl*' -ls >>> 227550 1201 -rwxr-xr-x 1 root wheel 957488 Feb 11 2025 /compat/linux/usr/lib64/libssl.so.3.2.2
227549 1 lrwxr-xr-x 1 root wheel 15 Feb 11 2025 /compat/linux/usr/lib64/libssl.so.3 -> libssl.so.3.2.2
226805 1 lrwxr-xr-x 1 root wheel 15 Feb 11 2025 /compat/linux/usr/lib/libssl.so.3 -> libssl.so.3.2.2
226806 1305 -rwxr-xr-x 1 root wheel 1023516 Feb 11 2025 /compat/linux/usr/lib/libssl.so.3.2.2
241928 1 lrwxr-xr-x 1 root wheel 83 Sep 2 23:17 /compat/linux/opt/dell/srvadmin/lib64/openmanage/private/libssl.so -> ../../../../../../../../../../../../../../../compat/linux/usr/lib64/libssl.so.3.2.2
And it does not stat? Maybe there is some another symbolic link accross the tree...
What does the realpath say>
Realpath works:
root@poudriere-pkb:/etc/pkg # realpath /compat/linux/opt/dell/srvadmin/lib64/openmanage/private/libssl.so
/compat/linux/usr/lib64/libssl.so.3.2.2
And again, if I use something like md5 (ignoring weaknesses in md5) it shows the same checksum as /compat/linux/usr/lib64/libssl.so.3.2.2
HererCOs my current mysteries:
1) Why am I hitting this and you arenrCOt?
2) Why does the hard link work and this not?
3) Why does it work if I add the *correct* number of ../?
-Dan
While I'm very glad you're doing this work (thank you!) Would you mind providing something other than a .shar (that's quite "old-school" and no longer suggested.) Maybe a git diff? Or, really, any diff/patch would be easier to test with these days (at least for me.)
On Sep 4, 2025, at 23:01, Gleb Popov <arrowd@freebsd.org> wrote:Okay. I originally read the -devel in poudriere-devel as sort of rCLbetarCY but itrCOs pretty clear that itrCOs what I should be using. (Maybe the porterrCOs handbook should recommend this, in case a person hits a problem).
I didn't read the whole thread, sorry upfront. Just want to point out that
1. poudriere-devel now handle linuxulator ports correctly
2, Some care should be taken to make Linux binaries act on
${LINUXBASE} rather than native files. I mainly talk about the FS
paths resolution algorithm there.
3. Symlinks are the pain and should be treated with extreme care.
Here's an example that took me a while to fix properly: https://github.com/freebsd/freebsd-ports/blob/6b4bc2602018ec1d81800bb1fb22ef55fc0b814c/security/linux-rl9-ca-certificates/Makefile#L60-L63
Let me know if you still have a problem with your port and need help with that.
On Sep 4, 2025, at 22:22, Janky Jay, III <jankyj@unfs.us> wrote:https://users.isc.org/~dmahoney/racadm.tar.gz
Hi Dan,
While I'm very glad you're doing this work (thank you!) Would you mind providing something other than a .shar (that's quite "old-school" and no longer suggested.) Maybe a git diff? Or, really, any diff/patch would be easier to test with these days (at least for me.)
On 9/4/25 10:05PM, Dan Mahoney (Ports) wrote:
Marcin or Kurt,Regards,
Can one of you please try using our most current shar to do a pkg build so I can test? IrCOd like to eliminate any weirdness with my own poudriere setup. I have a dell machine and can test on either 14 or 15 amd64.
-Dan
Janky Jay, III