From: <doiggl@velocitynet.com.au>
To: reiserfs-devel@vger.kernel.org
Subject: Has anyone got a working kernel .config file [2.6.35 series] with reiser4 enabled I could use.
Date: Sat, 02 Oct 2010 00:48:22 +1000 [thread overview]
Message-ID: <258c2600dce1260610f905a5839ba7b1@mail.velocitynet.com.au> (raw)
Hello,
Can anyone post a kernel .config file based on kernel 2.6.35 series with
reiser 4 enabled
I need one so I can complete a rpm compilation of a r4 based kernel done
in opensuse build service.
If anyone wants to view the efforts done so far see following sample links
below {falls over on various .config parameters}
Really appreciate a working .config file.
Thanks Glenn
[1] log ->
https://build.opensuse.org/package/live_build_log?arch=x86_64&package=kernel-vanilla&project=home%3Adoiggl&repository=openSUSE_11.3
[2] specfile ->
https://build.opensuse.org/package/view_file?file=kernel-vanilla.spec&package=kernel-vanilla&project=home%3Adoiggl&srcmd5=4e131dcbd7eb565a7a42aea7dbac8ef4
[3] project ->
https://build.opensuse.org/package/show?package=kernel-vanilla&project=home%3Adoiggl
reply other threads:[~2010-10-01 14:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=258c2600dce1260610f905a5839ba7b1@mail.velocitynet.com.au \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).