From: "Fred -- Speed Up --" <speedup@free.fr>
To: ReiserFS ML <reiserfs-list@namesys.com>
Subject: Getting Reiser4 without bk
Date: Thu, 12 Jun 2003 06:36:06 +0200 [thread overview]
Message-ID: <000f01c3309c$24860460$0200a8c0@xpstation> (raw)
[-- Attachment #1: Type: text/plain, Size: 936 bytes --]
Hello !
I'd like to patch my 2.5 kernel in order to get Reiser4 working. I tried the bk way, but I got compilation errors, it needs a very long time to get all the kernel tree, and I don't got enough disk space to keep a Reiser4 bk kernel tree in /usr/src. I'd want to know how important the kernel patches are, and if Reiser4 should compile and run well without these (I allways use -mm patches), or if you'd have a global patch against official 2.5.70 source that could orevent me from using Bitkeeper (I suppose the kernel code you're using is not changing everyday, only the Reiser4 code should ...). Now can I just put the reiser4 folder in my fs/ folder of the 2.5 kernel tree and config & compile or do I need these patches ? Where do I find them without using bk ?
Another question : I also downloaded the reiserprogs sources, and made an autoconf but I got error messages ... how do you build the ./configure script ?
Fred
reply other threads:[~2003-06-12 4:36 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='000f01c3309c$24860460$0200a8c0@xpstation' \
--to=speedup@free.fr \
--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.