From: Jeff Mahoney <jeffm@suse.com>
To: doiggl@velocitynet.com.au
Cc: reiserfs-devel@vger.kernel.org,
Edward Shishkin <edward.shishkin@gmail.com>
Subject: Re: Reiser4 module and 2.6.29-x-default kernel
Date: Fri, 22 May 2009 09:37:41 -0400 [thread overview]
Message-ID: <4A16AAA5.9040105@suse.com> (raw)
In-Reply-To: <13991.202.168.22.19.1242997798.squirrel@webmail.velocity.net.au>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
doiggl@velocitynet.com.au wrote:
> Hello,
> How can I manually create a installable reiser4 rpm module for a new
> kernel, because the opensuse build service seems stuck on a older kernel .
> I need all of the steps please, (commands please) so I can create the
> installable rpm module.
Hi Glenn -
I'm afraid it's not as simple as a series of commands. I do need to
update the patch to the 2.6.29 version which doesn't have the
- ->commit_write and ->prepare_write hooks that have been removed. The
other thing is that it needs more support in the kernel itself.
Previously it was limited to exports and adding a new hook, which I
could accept without much worry. I'm concerned about whether
set_buffers_dirty_notag() will make it upstream and I'm uncertain of the
interactions.
Edward - What's the reasoning behind it? Has it been submitted upstream
yet? Is it possible to use reiser4_set_dirty_pages creatively to get
the same effect?
- -Jeff
> 2. In the past, I've used the reiser4-kmp-default-0.1_2.6.27.7_9.1-27.3
> (2.6.27.7-9-default) opensuse 11.1 with good success and has worked well
> for me.
>
> # uname -a
> Linux test 2.6.27.7-9-default #1 SMP 2008-12-04 18:10:04 +0100 x86_64 x86_64
> x86_64 GNU/Linux
>
> # rpm -ivhU reiser4-kmp-default-0.1_2.6.27.7_9.1-27.3.x86_64.rpm
> warning: reiser4-kmp-default-0.1_2.6.27.7_9.1-27.3.x86_64.rpm: Header V3 DSA
> signature: NOKEY, key ID 74de2879
> Preparing... ###########################################
> [100%]
> 1:reiser4-kmp-default ###########################################
> [100%]
> 24831 blocks
> 24831 blocks
>
> # modprobe -v reiser4
> insmod
> /lib/modules/2.6.27.7-9-default/kernel/lib/zlib_deflate/zlib_deflate.ko
> insmod /lib/modules/2.6.27.7-9-default/kernel/lib/lzo/lzo_compress.ko
> insmod /lib/modules/2.6.27.7-9-default/kernel/lib/lzo/lzo_decompress.ko
> insmod /lib/modules/2.6.27.7-9-default/updates/reiser4.ko
>
> # rpm -qlp reiser4-kmp-default-0.1_2.6.27.7_9.1-27.3.x86_64.rpm
> warning: reiser4-kmp-default-0.1_2.6.27.7_9.1-27.3.x86_64.rpm: Header V3
> DSA signature: NOKEY, key ID 74de2879
> /lib/modules/2.6.27.7-9-default
> /lib/modules/2.6.27.7-9-default/updates
> /lib/modules/2.6.27.7-9-default/updates/reiser4.ko
>
> 3. My new system details with 11.2-Milestone1 (new)
> ===================================================
> I want to install reiser 4 on it reiser4-kmp-default with 2.6.29-XX-default
>
> 3a. System installed with 11.2-Milestone1 -
> http://download.opensuse.org/distribution/11.2-Milestone1/iso/openSUSE-KDE4-LiveCD-Build0067-i686.iso
> # uname -a
> Linux linux 2.6.29-6-default #1 SMP 2009-03-24 15:38:18 +0100 x86_64
> x86_64 x86_64 GNU/Linux
>
> How can I manually create a installable reiser4 rpm module.
> I need all of the steps please, (commands please) so I can create the rpm
> module with the three files (see below).
>
> Other references I looked at but I did not understand the reiser4.spec and
> how the files (see below) are generated and packaged for a newer kernel..
>
> # rpm -qlp reiser4-kmp-default-0.1_2.6.27.7_9.1-27.3.x86_64.rpm
> warning: reiser4-kmp-default-0.1_2.6.27.7_9.1-27.3.x86_64.rpm: Header V3
> DSA signature: NOKEY, key ID 74de2879
> /lib/modules/2.6.27.7-9-default
> /lib/modules/2.6.27.7-9-default/updates
> /lib/modules/2.6.27.7-9-default/updates/reiser4.ko
>
> https://build.opensuse.org/package/view_file?file=reiser4.spec&package=reiser4-kmp&project=drivers%3Afilesystems
>
> Thankyou for your help and time.
> Glenn
>
- --
Jeff Mahoney
SUSE Labs
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org
iEYEARECAAYFAkoWqqUACgkQLPWxlyuTD7IPGACZAWHkFYlr/FwNCUbW4XaDOhPW
qNkAn2XgJ2ycLXHzQ/pH1ETux6J3O2NH
=nchX
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2009-05-22 13:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-22 13:09 Reiser4 module and 2.6.29-x-default kernel doiggl
2009-05-22 13:37 ` Jeff Mahoney [this message]
2009-05-22 15:47 ` Edward Shishkin
2009-05-22 16:13 ` Jeff Mahoney
2009-05-28 0:32 ` doiggl
2009-05-28 3:10 ` Jeff Mahoney
2009-05-30 14:07 ` doiggl
2009-05-22 15:42 ` Ralph Ulrich
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=4A16AAA5.9040105@suse.com \
--to=jeffm@suse.com \
--cc=doiggl@velocitynet.com.au \
--cc=edward.shishkin@gmail.com \
--cc=reiserfs-devel@vger.kernel.org \
/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.