From: Eric Sandeen <sandeen@sandeen.net>
To: m.vandenhout@erasmusmc.nl
Cc: xfs@oss.sgi.com
Subject: Re: Adapted specfile to make kernel-module-xfs rpm build for a RHEL4 largesmp kernel
Date: Tue, 20 May 2008 08:45:59 -0500 [thread overview]
Message-ID: <4832D617.3030005@sandeen.net> (raw)
In-Reply-To: <4832C9DD.6090700@erasmusmc.nl>
Mirjam van den Hout - van Vroonhoven wrote:
> Hello XFS team,
>
> In order to make XFS work on Redhat Enterprise Linux 4, using the stock
> RH largesmp kernel (our server has 16 CPU's) I had to adapt the spec
> file for the kernel-module-xfs source rpm you offer for download at
> ftp://oss.sgi.com/projects/xfs/download/testing/RHEL4/kernel-module-xfs-2.6.9-22.EL-0.1-1.src.rpm
>
> The issue is that largesmp was not recognized as a kernel type, and with
> the original specfile an RPM was build with a dependency
> "requires kernel-smp = 2.6.9-67.0.1.ELlarge" where the dependency should
> have been "requires kernel-largesmp = 2.6.9-67.0.1".
>
> The fix was to add "largesmp" to the list of defined kernel_type at the
> top of the .spec file. I also fixed a typo in this list (default instead
> of deault). The new fixed spec file (kernel-module-xfs.spec), the
> original spec file (kernel-module-xfs.spec.orig) and a diff between the
> two (kernel-module-xfs.spec.patch are attached to this email.
>
> For other users, it might be useful to include this in the next release.
SGI doesn't really maintain those; the xfs kernel modules in the
centosplus repository
(http://mirror.centos.org/centos/4/centosplus/Readme.txt) are probably a
better place to start, as they have some active users and a bit of
maintenance.
(IMHO a fair amount of stuff on the xfs ftp site is so outdated it
should be removed....)
-Eric
>
> Kind regards,
>
> Mirjam van den Hout
>
prev parent reply other threads:[~2008-05-20 13:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-20 12:53 Adapted specfile to make kernel-module-xfs rpm build for a RHEL4 largesmp kernel Mirjam van den Hout - van Vroonhoven
2008-05-20 13:45 ` Eric Sandeen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4832D617.3030005@sandeen.net \
--to=sandeen@sandeen.net \
--cc=m.vandenhout@erasmusmc.nl \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.