public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Rafał Bilski" <rafalbilski@interia.pl>
To: linux-mtd@lists.infradead.org
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Problem with udev and block2mtd
Date: Wed, 01 Aug 2007 21:05:59 +0200	[thread overview]
Message-ID: <46B0D997.8030805@interia.pl> (raw)

Hi!

I have changed static /dev to udev on my machine. It has 
a lot of RAM (94MB) so I was expecting that udev will not make 
things worse. Unfortunately udev isn't noticing that new mtd 
device was born. I was suspecting that this is my fault, but 
udev's /dev is populated and:
UEVENT[1185991604.930847] add@/module/mtdcore
UEVENT[1185991604.969089] add@/module/mtdpart
UEVENT[1185991605.005954] add@/module/block2mtd
UEVENT[1185991647.726551] add@/module/mtdsuper
UEVENT[1185991647.783396] add@/module/jffs2
UEVENT[1185991647.801242] add@/slab/jffs2_i
UDEV  [1185991647.815670] add@/slab/jffs2_i
UEVENT[1185991647.827608] add@/slab/:0000072
UDEV  [1185991647.842338] add@/slab/:0000072
I don't see nothing about new device.

Is this situation known? Or this is 2.6.23-rc1-git3 regression? 
Or is my udev misconfigured?

Regards
Rafał

----------------------------------------------------------------------
Wszystko czego potrzebujesz latem: kremy do opalania, 
stroje kapielowe, maly romans 

>>>http://link.interia.pl/f1b15

             reply	other threads:[~2007-08-01 19:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-01 19:05 Rafał Bilski [this message]
2007-08-03 18:06 ` Problem with udev and block2mtd Andrew Morton

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=46B0D997.8030805@interia.pl \
    --to=rafalbilski@interia.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.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