From: Jeff Mahoney <jeffm@suse.com>
To: doiggl@velocitynet.com.au
Cc: reiserfs-devel@vger.kernel.org
Subject: Re: Nightly Builds
Date: Thu, 10 Jul 2008 11:51:54 -0400 [thread overview]
Message-ID: <4876301A.6020208@suse.com> (raw)
In-Reply-To: <24383.202.168.22.19.1215703298.squirrel@webmail.velocity.net.au>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
doiggl@velocitynet.com.au wrote:
> Hello,
> Success. I got the reiser4 module installed.
Great!
> # rpm -qa | grep -i reiser4
> reiser4-kmp-default-0.1_2.6.25.9_1.1-22.2
>
> Source was:
> http://download.opensuse.org/repositories/drivers:/filesystems/openSUSE_Factory/x86_64/reiser4-kmp-default-0.1_2.6.25.9_1.1-22.2.x86_64.rpm
>
> # rpm -qa | grep -i kernel
> kernel-default-2.6.25.9-0.2
> kernel-syms-2.6.25.9-0.2
> kernel-source-2.6.25.9-0.2
> linux-kernel-headers-2.6.25-8.1
> nfs-kernel-server-1.1.2-8.1
> kernel-xen-2.6.25.9-0.2
>
> Questions:
> - In order to use the reiser4 module, do I need to boot to a different
> kernel flavor which is installed, if so which one ?
No, you shouldn't even need to reboot if you're currently running the
2.6.25.9-default kernel.
> - How do I verify the reiser4 module is ready for use ?
# modprobe reiser4
If it succeeds, it's working.
> - I've got a spare disk installed but not formatted yet. How do I format
> it with reiser4 ?
You'll need the reiser4 tools, which opensuse ships with.
> - I can run some file system tests I'm happy to do so. Have you got some
> tests I can run ? I'm happy to post the results.
postmark, fsx-linux, dbench, etc. Nothing really in particular. When I'm
testing a file system I usually have specific things I'm trying to test,
but those are the most common ones.
- -Jeff
- --
Jeff Mahoney
SUSE Labs
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org
iEYEARECAAYFAkh2MBoACgkQLPWxlyuTD7LWxwCfZNmzlvzHeHYLR+ZB9ximRLUT
09YAn0eQ8i0gzo96j8Cq8QzW6zrdHs9+
=0N8z
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2008-07-10 15:51 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-20 19:42 Nightly Builds J. Todd Slack
2008-06-20 19:57 ` Jeff Mahoney
2008-06-22 14:51 ` doiggl
2008-06-22 16:06 ` Jeff Mahoney
2008-06-23 4:16 ` doiggl
2008-06-23 14:13 ` Jeff Mahoney
2008-06-24 14:44 ` doiggl
2008-06-24 14:58 ` Jeff Mahoney
2008-06-25 12:59 ` doiggl
2008-06-25 16:11 ` Jeff Mahoney
2008-06-28 7:34 ` doiggl
2008-06-28 15:23 ` Jeff Mahoney
2008-06-29 14:02 ` doiggl
2008-06-29 19:02 ` Jeff Mahoney
2008-06-30 11:49 ` doiggl
2008-06-30 14:55 ` Jeff Mahoney
2008-07-01 13:48 ` doiggl
2008-07-09 15:00 ` doiggl
2008-07-09 15:11 ` Jeff Mahoney
2008-07-10 15:21 ` doiggl
2008-07-10 15:51 ` Jeff Mahoney [this message]
[not found] ` <27342.202.168.22.19.1215840119.squirrel@webmail .velocity.net.au>
2008-07-12 5:21 ` doiggl
2008-07-12 7:10 ` Jeff Mahoney
2008-07-13 14:21 ` doiggl
2008-07-13 17:00 ` Edward Shishkin
2008-07-14 13:39 ` doiggl
2008-07-14 18:21 ` stroetmann
2008-07-14 20:51 ` Edward Shishkin
2008-07-14 20:54 ` J. Todd Slack
2008-07-14 21:20 ` Volker Armin Hemmann
2008-07-14 21:53 ` Christian Stroetmann
2008-07-14 21:42 ` Christian Stroetmann
2008-07-14 22:26 ` Volker Armin Hemmann
2008-07-14 22:37 ` Christian Stroetmann
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=4876301A.6020208@suse.com \
--to=jeffm@suse.com \
--cc=doiggl@velocitynet.com.au \
--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.