[Ocfs2-users] 1.2.5 compile

[Jeff Mahoney]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jeff Mahoney wrote:
> This is by luck. The emergency_restart change won't help here. The
> problem is a bug in depmod where it will look in /lib/modules/`uname
> -r`/extra for override modules, but won't scan for its dependencies
> there. The result is that he's using the OCFS2 v1.2.5 ocfs2.ko, but the
> SUSE Linux 10.1 ocfs2_nodemanager.ko and ocfs2_dlm.ko modules.
> 
> I've reported the depmod bug to our Bugzilla, but in the meantime his
> options are to move the old OCFS2 modules out of the way, or use the
> SLES 10 SP1 kernel from
> ftp://ftp.suse.com/pub/projects/kernel/kotd/sle10-sp-i386/SLES10_SP1_BRANCH.
> The SP1 kernel includes OCFS2 1.2.5 with a few changes. I've restored
> the old panic-on-fence behavior as the default, and it contains the
> userspace cluster patches.

Ok, after talking this over, here's the answer: The modules shouldn't be
put in extra/. They should be put in updates/, and then the overrides
work as expected.

The "right" way to generate kernel modules for SUSE Linux systems at
version 10.0 or newer is via the Kernel Module Package (KMP) mechanism.
This ends up making the spec file ridiculously simple on these systems,
but doesn't really work all that well with the OCFS2 tarball in its
current form. I'm hacking on the configure stuff a bit to make this work
with the KMP process.

To get around the problem for now, do an "export
INSTALL_MOD_DIR=updates" before starting the build. That will install
the modules in the correct location.

- -Jeff

- --
Jeff Mahoney
SUSE Labs
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org

iD8DBQFGIobMLPWxlyuTD7IRAlGNAKCiQS3hCyeBE1GdPJGJFu6/93QA1ACglRVQ
v4SoACogSHR+P79qqWTt/T0=
=qFyb
-----END PGP SIGNATURE-----