On Dec 12, 2007, at 10:24 PM, Brad Penoff wrote:
> OK, I've done a commit (r16951) to make it less noisy. Let me know
> how it goes because I can't reproduce this at the moment.
That seemed to do it; thanks.
> I'm really curious about this release of Red Hat though....
> On my Ubuntu system, if I try to create an SCTP socket and the kernel
> module isn't loaded/modprobe'd, the system loads it automatically
> based off the entry in the modules alias file which tells the system
> where to find the appropriate .ko file.
> These mappings seem to be messed up in the Red Hat out-of-the-box
> RHEL4U4 release though, if I'm understanding things correctly... does
> anyone know if this is is a known problem for this particular distro?
> If not, I'll try to get to installing and playing with this release
> eventually (working on Solaris support for the SCTP BTL (1-1) and a
> few other non-OpenMPI things at the moment though...).
I do not know. Keep in mind that RHEL4U4 is fairly ancient.
FWIW, RHEL4Ux are systems that you have to pay for. But the Centos
distros are recompiles of the RHEL4 SRPMs, so they're pretty close in
terms of what official RHEL4 systems are.
BTW, my choice of RHEL4 is because that's what Cisco customers use and
what we support (we see a lot of RHEL usage out in the commercial