From: Calvin Walton <calvin.walton@gmail.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] FILESYSTEMS: Make "advanced partitions" immediately unselectable.
Date: Mon, 28 Jul 2008 18:02:20 -0400 [thread overview]
Message-ID: <1217282540.22927.13.camel@zem.phub.net.cable.rogers.com> (raw)
In-Reply-To: <alpine.LFD.1.10.0807281437070.10586@localhost.localdomain>
On Mon, 2008-07-28 at 14:42 -0400, Robert P. J. Day wrote:
> On Mon, 28 Jul 2008, Randy Dunlap wrote:
> it strikes me that, at least on x86, MSDOS partition support is so
> fundamental that it should take work for someone to turn it *off*.
> perhaps simply have it on by default, and force someone to go under
> "Configure standard kernel features (for small systems)"
> (CONFIG_EMBEDDED) to make it go away?
>
> seriously, how often is someone going to build a kernel for x86 and
> not need MSDOS partition support? just curious.
>
> rday
Naturally, on an architecture other than x86 (e.g. sparc) you'll want to
ensure that the platform's native partitioning format (for sparc,
SUN_PARTITION) is similarly on by default, and difficult to unselect.
In this case, you could get by perfectly without msdos partitions
enabled (although the default is still to enable them), unless you want
to read a usb key or something.
This was the point of the original menu, I think - it allowed each
partition type to have a default based on arch, but to hide away the
mess of other types unless you feel like overriding it.
You'll want to make sure in your patch that arches other than x86 don't
lose their own native partitioning types :)
--
Calvin Walton <calvin.walton@gmail.com>
next prev parent reply other threads:[~2008-07-28 22:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-26 13:20 Robert P. J. Day
2008-07-26 16:47 ` Randy Dunlap
2008-07-26 21:52 ` Robert P. J. Day
2008-07-28 3:11 ` Calvin Walton
2008-07-28 9:38 ` Robert P. J. Day
2008-07-28 17:37 ` Randy Dunlap
2008-07-28 18:14 ` Robert P. J. Day
2008-07-28 18:42 ` Robert P. J. Day
2008-07-28 18:51 ` Randy Dunlap
2008-07-28 18:56 ` Robert P. J. Day
2008-07-28 21:43 ` Grant Coady
2008-07-28 22:02 ` Calvin Walton [this message]
2008-07-28 22:14 ` Randy Dunlap
2008-07-29 10:36 ` Robert P. J. Day
2008-07-29 16:17 ` Randy Dunlap
2008-07-29 20:36 ` Robert P. J. Day
[not found] <aTS0O-4U1-33@gated-at.bofh.it>
[not found] ` <aTV89-39s-5@gated-at.bofh.it>
[not found] ` <aTZYh-4i3-21@gated-at.bofh.it>
[not found] ` <aUrrl-78m-3@gated-at.bofh.it>
[not found] ` <aUxwQ-1Hn-19@gated-at.bofh.it>
[not found] ` <aUERB-Zl-5@gated-at.bofh.it>
[not found] ` <aUFXh-3m9-3@gated-at.bofh.it>
[not found] ` <aUJ4U-1xe-19@gated-at.bofh.it>
[not found] ` <aUJeD-1N6-13@gated-at.bofh.it>
[not found] ` <aUUME-5MM-11@gated-at.bofh.it>
[not found] ` <aV05W-1wO-41@gated-at.bofh.it>
2008-08-02 12:41 ` Bodo Eggert
2008-08-02 14:36 ` Randy Dunlap
2008-08-02 21:16 ` Bodo Eggert
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=1217282540.22927.13.camel@zem.phub.net.cable.rogers.com \
--to=calvin.walton@gmail.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=rpjday@crashcourse.ca \
/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®