linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Olaf Dietsche <olaf+list.linux-kernel@olafdietsche.de>
To: rob@landley.net
Cc: linux-kernel@vger.kernel.org, zippel@linux-m68k.org
Subject: Re: More fun with menuconfig...
Date: Sat, 02 Aug 2003 18:46:28 +0200	[thread overview]
Message-ID: <87ispgknx7.fsf@goat.bogus.local> (raw)
In-Reply-To: <200308020605.58423.rob@landley.net> (Rob Landley's message of "Sat, 2 Aug 2003 06:05:58 -0400")

Rob Landley <rob@landley.net> writes:

> So I have a .config with CONFIG_ADVANCED_PARTION not set, and 
> CONFIG_MSDOS_PARTITION=y.  (I.E. the default from arch/i386/defconfig.)
>
> I fire up make menuconfig and expand the advanced partition menu (setting 
> CONFIG_ADVANCED_PARTITION to y).  MSDOS partition support is NOT set in the 
> newly opened menu, I.E. opening the menu has the side effect of deselecting 
> CONFIG_MSDOS_PARTITION.
>
> If I do nothing else, and save with the menu open, it's off.  (Saved as "not 
> set".)  If I fire it up again and close the menu, CONFIG_MSDOS_PARTITION 
> becomes Y again.
>
> What magic am I failing to understand here?  (This sort of seems intentional, 
> but it would make more sense for MSDOS partition support to default to on 
> when you first open the menu...)

Maybe it's this default definition in fs/partitions/Kconfig(101):

config MSDOS_PARTITION
        bool "PC BIOS (MSDOS partition tables) support" if PARTITION_ADVANCED
        default y if !PARTITION_ADVANCED && !AMIGA && !ATARI && !MAC && !SGI_IP22 && !ARM && !SGI_IP27

Regards, Olaf.

      parent reply	other threads:[~2003-08-02 16:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-02 10:05 More fun with menuconfig Rob Landley
2003-08-02 16:08 ` Roman Zippel
2003-08-02 23:52   ` Rob Landley
2003-08-02 16:46 ` Olaf Dietsche [this message]

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=87ispgknx7.fsf@goat.bogus.local \
    --to=olaf+list.linux-kernel@olafdietsche.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rob@landley.net \
    --cc=zippel@linux-m68k.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;
as well as URLs for NNTP newsgroup(s).