mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "K. Ernel" <kernel@wildsau.enemy.org>
To: linux-kernel@vger.kernel.org
Subject: CONFIG_NETWORK_FILESYSTEMS not set in /proc/config.gz
Date: Wed, 9 Jul 2008 18:22:45 +0200 (MET DST)	[thread overview]
Message-ID: <200807091622.m69GMjnH025474@wildsau.enemy.org> (raw)


hello list,

I usually switch to a new kernel version using the
old .config file by doing:

    # zcat /proc/config.gz > .config
    # make oldconfig

however, with the last two (or so) versions, I always lost the network
file system configuration. It's not present in config.gz,
while in the old .config of the previous release, it _is_
present, plus I'm abble to use network file system support
in the current (before the update) kernel.

e.g.:

(1) kernel version:
    # uname -r
    2.6.25.9

(2) this kernel version's configuration in the sources:
    # grep NETWORK_FILE linux-2.6.25.9/.config
    CONFIG_NETWORK_FILESYSTEMS=y

(3) this kernel version's configuration in /proc/config.gz
    # zcat /proc/config.gz | grep NETWORK_FILE
    # CONFIG_NETWORK_FILESYSTEMS is not set

(4) to proof this kernel version has indeed network filesystem:
    # lsmod| grep nfs
    nfs                    86896  1 
    lockd                  38280  2 nfs
    nfs_acl                 1792  1 nfs
    sunrpc                101884  10 nfs,lockd,nfs_acl


to me, this looks like "CONFIG_NETWORK_FILESYSTEMS" is "forgotten" in
config.gz, but what do I know ...

please fix if possible,
thanks,
h. rosmanith

             reply	other threads:[~2008-07-09 16:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-09 16:22 K. Ernel [this message]
2008-07-10  4:44 ` Randy Dunlap
2008-07-11 14:51   ` K. Ernel

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=200807091622.m69GMjnH025474@wildsau.enemy.org \
    --to=kernel@wildsau.enemy.org \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®