linux-kernel - CONFIG_NETWORK_FILESYSTEMS not set in /proc/config.gz

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <200807091622.m69GMjnH025474@wildsau.enemy.org>
Date:	Wed, 9 Jul 2008 18:22:45 +0200 (MET DST)
From:	"K. Ernel" <kernel@...dsau.enemy.org>
To:	linux-kernel@...r.kernel.org
Subject: CONFIG_NETWORK_FILESYSTEMS not set in /proc/config.gz

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/