From: Scott James Remnant <scott@canonical.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev problem (and fix) for /dev/mtdblock*
Date: Thu, 19 Mar 2009 10:08:30 +0000 [thread overview]
Message-ID: <1237457310.6618.36.camel@quest> (raw)
In-Reply-To: <ac3eb2510903181845r62f3ed39sd5c8e4dd0ac39c7a@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1051 bytes --]
On Thu, 2009-03-19 at 02:45 +0100, Kay Sievers wrote:
> > The boot is easily cleaned up by a patch to a udev rules
> > file: /etc/udev/rules.d/60-persistent-storage.rules is
> > already skipping a bunch of devices, it just needs to add
> > the "mtd*" devices to what should be skipped:
> >
> > KERNEL=="ram*|loop*|fd*|mtd*|nbd*|gnbd*|dm-*|md*", GOTO="persistent_storage_end"
> >
> > It'd be good to see this bug fixed before lenny goes final...
>
> Udev, by default, investigates all block devices which are created by
> the kernel. People use label/uuid and other metadata based stuff, so
> we should look at them. We can not know in advance which device will
> not respond properly. I have requests where people ask for more
> persistent link support for mtd devices, while disabling them would
> really not make them happier. :)
>
Indeed, for the Ubuntu ARM port we *rely* on having UUIDs for the MTD
partitions. I would be unhappy if mtd devices did not have them.
Scott
--
Scott James Remnant
scott@canonical.com
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-03-19 10:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-19 1:45 udev problem (and fix) for /dev/mtdblock* Kay Sievers
2009-03-19 10:08 ` Scott James Remnant [this message]
2009-03-20 18:46 ` David Brownell
2009-03-22 15:39 ` Kay Sievers
2009-03-23 18:49 ` David Brownell
2009-03-23 20:17 ` Kay Sievers
2009-03-24 21:14 ` David Brownell
2009-03-23 20:39 ` David Brownell
2009-03-23 21:21 ` Kay Sievers
2009-03-23 22:23 ` David Brownell
-- strict thread matches above, loose matches on Subject: below --
2009-03-18 19:44 Fwd: " David Brownell
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=1237457310.6618.36.camel@quest \
--to=scott@canonical.com \
--cc=linux-hotplug@vger.kernel.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).