From: Hannes Reinecke <hare@suse.de>
To: devzero@web.de
Cc: linux-kernel@vger.kernel.org, "Randy.Dunlap" <rdunlap@xenotime.net>
Subject: Re: [PATCH] Disable partition scan
Date: Mon, 14 Sep 2009 08:33:52 +0200 [thread overview]
Message-ID: <4AADE3D0.200@suse.de> (raw)
In-Reply-To: <909257926@web.de>
devzero@web.de wrote:
> Hello,
>
> iirc i had a setup a while ago where i also found disabling partition scanning would be nice to have.
>
> actually, we have a bugzilla entry for this - have a look at:
>
> http://bugzilla.kernel.org/show_bug.cgi?id=8588
>
> anyway, wouldn`t it be better to disable that on a per device basis or at least be able to exclude
> the boot/system devices from being skipped?
>
Hmm. Not sure about this.
For once, you'd have to have a tool like kpartx anyway to generate the partition mappings for the
not-excluded devices. Hence it's not a big deal to use this tool _always_, ie for all devices.
But more importantly the commandline will be a killer. You would have to specify the device
to be excluded prior to driver probing. Which means you'd have to know how the driver would
enumerate the device and how the device to be excluded would be named.
But exactly this isn't guaranteed, so it'll be virtually impossible to do so.
Cheers,
Hannes
PS.: One wonders what'll happen to the patch. Maybe it'll linger forever in bugzilla as no-one
feels it important enough to have a look at it, let alone merge ...
So, if there are any users out there, please speak up to have it merged!
--
Dr. Hannes Reinecke zSeries & Storage
hare@suse.de +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Markus Rex, HRB 16746 (AG Nürnberg)
next prev parent reply other threads:[~2009-09-14 6:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-12 11:45 [PATCH] Disable partition scan devzero
2009-09-14 6:33 ` Hannes Reinecke [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-09-14 20:59 devzero
2008-08-27 10:31 Hannes Reinecke
2008-08-27 12:30 ` Hannes Reinecke
2008-08-28 12:00 ` Randy.Dunlap
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=4AADE3D0.200@suse.de \
--to=hare@suse.de \
--cc=devzero@web.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/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