Jim> The problem is the missing CONFIG_FAT_FS. In linux/fs/Config.in,
Jim> CONFIG_MSDOS_FS, CONFIG_UMSDOS_FS and CONFIG_VFAT_FS are all
Jim> dependent on CONFIG_FAT_FS, so it should be impossible to choose
Jim> them w/o also choosing CONFIG_FAT_FS.
Jon> Huh. It isn't, as you can see. Why is CONFIG_FAT_FS even a
Jon> separate option? Couldn't it be automatically made if any of the
Jon> three CONFIG_ targets that depend on it are selected? Is there
Jon> any use to having CONFIG_FAT_FS enabled without any of the
Jon> others?
Jim> Which fooconfig did you make(1)?
Jon> Menuconfig.
It is clearly a bug in menuconfig. I just tested each of config,
menuconfig and xconfig. In xconfig, MSDOS_FS, UMSDOS_FS and VFAT_FS
are greyed out unless FAT_FS is y or m. In config, you don't get
prompts for MSDOS_FS, UMSDOS_FS and VFAT_FS unless FAT_FS is y or m.
Only in menucaonfig are MSDOS_FS, UMSDOS_FS and VFAT_FS active if
FAT_FS is n.
Oldconfig will even unset MSDOS_FS, UMSDOS_FS and VFAT_FS should
FAT_FS be unset, or change them from y to m if FAT_FS=m.
Note that menuconfig does at least get CONFIG_NLS right: it only get's
set, and you only get prompted for the codepages, if [ CONFIG_JOLIET=y
-o CONFIG_FAT_FS!=n -o CONFIG_NTFS_FS!=n ].
Looking at scripts/Configure and scripts/Menuconfig, the problem is
Menuconfig's dep_tristate() function. Compare it w/ Configure's and
all should become clear. Or at least partly sunny.... :)
-JimC
--
James H. Cloos, Jr.
<cloos@jhcloos.com>
PGP KeyId=0xB84D7D6F <http://www.jhcloos.com/cloos/pgp_public_key.txt>
Fingerprint20 = F265 CF1F 1951 A103 E287 1350 1A0D 598D B84D 7D6F
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html