From: Steve Jacobson <steve@sourcelabs.com>
To: reiserfs-list@namesys.com
Subject: Building Reiser4 - Symbol problem
Date: Fri, 07 Oct 2005 16:48:26 -0700 [thread overview]
Message-ID: <4347094A.3090801@sourcelabs.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1287 bytes --]
I'm having a problem loading Reiser4 on my centOS4 box. The following
message shows up in the system logs when I run "modprobe reiser4":
reiser4: Unknown symbol find_get_pages_tag
My build, etc... process is:
1) Start with clean install of centOS 4.1 x86_64 version
2) Install kernel sources from centOS distro
3) Patch sources:
a) in /usr/src/linux-2.6.9-11.EL
b) run: patch -p0 < reiser4-for-2.6.9-4
NOTE - is this my complete problem right here? Are the differences
between 2.6.9-11 and 2.6.9-4 significant enough to account for this?
4) make menuconfig - enabling reiser4 as a module
5) make
6) make binrpm-pkg
7) Install the resultant RPM
8) run mkinitrd /boot/initrd-2.6.9-11.ELcustom.img 2.6.9011.ELcustom
9) Update grub.conf:
title CentOS-4 x86_64 Resier (2.6.9-11.ELcustom)
root (hd0,0)
kernel /vmlinuz-2.6.9-11.ELcustom ro root=LABEL=/1
initrd /initrd-2.6.9-11.ELcustom.img
10) reboot, and select the custom kernel
11) Run mkfs.reiser4
12) run modprobe reiser4, or just try to mount the new file system
Any thoughts? Has anyone had any success using Resier4 on centOS 4.1?
If so, did you follow this process, or another?
thanks!
-Steve J
--
Steve Jacobson
Support Manager
SourceLabs, Inc.
steve@sourcelabs.com
(206) 322-0099 x110
next reply other threads:[~2005-10-07 23:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-07 23:48 Steve Jacobson [this message]
2005-10-08 0:36 ` Building Reiser4 - Symbol problem michael chang
[not found] ` <434AB282.3010408@sourcelabs.com>
2005-10-10 18:32 ` Steve Jacobson
2005-10-10 19:14 ` Steve Jacobson
2005-10-10 19:02 ` michael chang
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=4347094A.3090801@sourcelabs.com \
--to=steve@sourcelabs.com \
--cc=reiserfs-list@namesys.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.