Philip Blundell wrote:
>
> >With philb kernels, It doesn't crash but it ALWAYS defines
> >CONFIG_MSDOS_FS and CONFIG_VFAT_FS, even when CONFIG_FAT_FS is unset
>
> Does it define them to M or Y? If the former I suspect this is because
> menuconfig has a different idea about dep_tristate to the other config
> systems, and they need wrapping in a 'if [ $CONFIG_FAT_FS != "n" ]' type
> construct.
>
> If the latter I've no idea.
>
> p.
#
# Filesystems
#
# CONFIG_QUOTA is not set
# CONFIG_AUTOFS_FS is not set
# CONFIG_ADFS_FS is not set
# CONFIG_AFFS_FS is not set
# CONFIG_HFS_FS is not set
# CONFIG_FAT_FS is not set
CONFIG_MSDOS_FS=y
# CONFIG_UMSDOS_FS is not set
CONFIG_VFAT_FS=y
# CONFIG_ISO9660_FS is not set
And we can't say that it is because FAT_FS has just been turned off
Before entering menuconfig Filesystem submenu, it was not set,
And I've just entered and exited Filesystem submenu, not played with
FAT_FS
christophe
unsubscribe: body of `unsubscribe linux-arm' to [EMAIL PROTECTED]
