From: Steve French <smfrench@gmail.com>
To: Suresh Jayaraman <sjayaraman@suse.de>
Cc: Jeff Layton <jlayton@redhat.com>,
linux-cifs@vger.kernel.org,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH] cifs: document 'fsc' mount option
Date: Tue, 27 Jul 2010 11:38:20 -0500 [thread overview]
Message-ID: <AANLkTi=+Y1XdFCT1UfWZW==qusXfs6t-vxa_CYo03TTT@mail.gmail.com> (raw)
In-Reply-To: <4C4F0A71.8020908@suse.de>
On Tue, Jul 27, 2010 at 11:33 AM, Suresh Jayaraman <sjayaraman@suse.de> wrote:
> On 07/27/2010 08:51 PM, Steve French wrote:
>> scripts/extract-ikconfig could be run against the image (or look at
>> /proc/config.gz) - but unless there is an easier way to view kernel
>> config options on particular distros via distro specific tools -
>> probably easier just to note that CONFIG_FSCACHE must be selected in
>> the kernel build (since it forces dependencies on the other kernel
>> options being set)
>
> Does something like
> $zcat /proc/config.gz | grep CONFIG_CIFS_FSCACHE
>
> might work on all distros?
>
> But, Jeff's idea of having a features file in /proc sounds good. Apart
> from using them as a reference to check in documentation, it could be a
> useful information while collecting debugging output as well..?
Seems reasonable - but wondering if other file systems have run into the same
problem - how to view their build/config options - and how they have
solved it (if at all) so ccing fsdevel
--
Thanks,
Steve
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next parent reply other threads:[~2010-07-27 16:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4C4EE408.7070109@suse.de>
[not found] ` <20100727103313.4b730ea8@tlielax.poochiereds.net>
[not found] ` <AANLkTina2EyHkrgNAcrY8ZRK=fXQS71dekWc+kOA0+mz@mail.gmail.com>
[not found] ` <20100727111517.4fe0859e@tlielax.poochiereds.net>
[not found] ` <AANLkTik9JqtqAtKJQsaQR8aC8s0kwmrcU=_=QQei7U07@mail.gmail.com>
[not found] ` <4C4F0A71.8020908@suse.de>
2010-07-27 16:38 ` Steve French [this message]
[not found] ` <AANLkTi=+Y1XdFCT1UfWZW==qusXfs6t-vxa_CYo03TTT-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-07-27 21:59 ` [PATCH] cifs: document 'fsc' mount option Randy Dunlap
2010-07-30 9:49 ` Suresh Jayaraman
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='AANLkTi=+Y1XdFCT1UfWZW==qusXfs6t-vxa_CYo03TTT@mail.gmail.com' \
--to=smfrench@gmail.com \
--cc=jlayton@redhat.com \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=sjayaraman@suse.de \
/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).