From: Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2003@gmx.net>
To: Hans Reiser <reiser@namesys.com>
Cc: Nishant Sharma <nishantt@cse.iitd.ernet.in>,
Nikita Danilov <Nikita@namesys.com>,
Reiserfs mail-list <Reiserfs-List@namesys.com>
Subject: Re: new reiser4 snapshot
Date: Mon, 20 Oct 2003 00:41:49 +0200 [thread overview]
Message-ID: <3F93132D.70206@gmx.net> (raw)
In-Reply-To: <3F92D35D.3090806@namesys.com>
Hans Reiser wrote:
> Nishant Sharma wrote:
>
>> Hi,
>>
>> On Fri, 17 Oct 2003, Nikita Danilov wrote:
>>
>>
>>> Hello,
>>> Reiser4 snapshot against 2.6.0-test7 has been released:
>>> http://namesys.com/snapshots/2003.10.17/
>>> Description is in http://namesys.com/snapshots/2003.10.17/READ.ME
>>>
>> Following is the relevant section of my .config in kernel src-dir.
>>
>> CONFIG_REISER4_FS=m
>> # CONFIG_REISER4_FS_SYSCALL is not set
>> # CONFIG_REISER4_LARGE_KEY is not set
I thought CONFIG_REISER4_LARGE_KEY was force-enabled by now?
>> # CONFIG_REISER4_CHECK is not set
>> CONFIG_REISER4_USE_EFLUSH=y
>> # CONFIG_REISER4_COPY_ON_CAPTURE is not set
>> # CONFIG_REISER4_BADBLOCKS is not set
>>
>> What am I doing wrong? I believe that I followed the instructions
>> in http://namesys.com/snapshots/2003.10.17/READ.ME to the letter.
>>
>>
> Nikita, please determine why reiser4 tells users they can configure it
> as a module when they cannot.
Carl-Daniel
next prev parent reply other threads:[~2003-10-19 22:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-17 15:42 new reiser4 snapshot Nikita Danilov
2003-10-17 18:51 ` Hans Reiser
2003-10-19 14:38 ` Nishant Sharma
2003-10-19 18:09 ` Hans Reiser
2003-10-19 22:41 ` Carl-Daniel Hailfinger [this message]
2003-10-20 9:44 ` Nikita Danilov
2003-10-27 20:25 ` Mike Fedyk
2003-10-27 21:28 ` Hans Reiser
2003-10-20 9:37 ` Nikita Danilov
2003-10-20 9:36 ` Nikita Danilov
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=3F93132D.70206@gmx.net \
--to=c-d.hailfinger.kernel.2003@gmx.net \
--cc=Nikita@namesys.com \
--cc=Reiserfs-List@namesys.com \
--cc=nishantt@cse.iitd.ernet.in \
--cc=reiser@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.