From: Artem Bityutskiy <dedekind1@gmail.com>
To: Arno Steffen <arno.steffen@googlemail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: error!: "/dev/ubi0" is not a character device ?!?
Date: Thu, 05 Aug 2010 16:36:45 +0300 [thread overview]
Message-ID: <1281015405.1175.32.camel@localhost.localdomain> (raw)
In-Reply-To: <AANLkTikZb=R=8BObvTN6uGaZGAmvvUZd4oYKvkCJih7H@mail.gmail.com>
On Thu, 2010-08-05 at 13:55 +0200, Arno Steffen wrote:
> cat /proc/devices give me back, that (252 ubi8) is a character device.
Ok.
> But looking above, in /dev it is listed as block device !?!
udev!?!
> For me creating entries are not transparent, this happend with
> ubiattach. No idea how to force ubiattach to write ubi8 in the
> devicelist as character device.
I thought I explained how udev works briefly. I also suggested you
udevmonitor, you can also google. Neither UBI nor ubiattach nor any
other ubi utility should create any /dev device.
Sorry, I cannot provide more help. Try to dig this yourself - there are:
many ways. You can add printks to the kernel. You can even do echo 1
> /proc/sys/vm/block_dump and find out which process creates /dev
entries. Hey, be creative, do not wait that others will solve your
issues! :-)
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
next prev parent reply other threads:[~2010-08-05 13:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-26 12:00 error!: "/dev/ubi0" is not a character device ?!? Arno Steffen
2010-07-26 13:14 ` Artem Bityutskiy
2010-07-26 13:49 ` Arno Steffen
2010-07-27 15:25 ` Artem Bityutskiy
2010-07-28 11:04 ` Arno Steffen
2010-07-30 6:35 ` Artem Bityutskiy
2010-08-05 11:55 ` Arno Steffen
2010-08-05 13:23 ` twebb
2010-08-05 13:36 ` Artem Bityutskiy [this message]
[not found] ` <AANLkTikkRNqnEX0PkHigv=zT+Z36J52DEtoVeMGbBExf@mail.gmail.com>
2010-08-16 11:27 ` Arno Steffen
2010-08-23 12:34 ` Artem Bityutskiy
2010-08-23 14:13 ` Arno Steffen
2010-08-23 14:41 ` Artem Bityutskiy
2010-08-24 8:32 ` Arno Steffen
2010-08-24 8:53 ` Artem Bityutskiy
2010-08-24 9:19 ` Arno Steffen
2010-08-24 9:33 ` Artem Bityutskiy
2010-07-30 6:23 ` Artem Bityutskiy
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=1281015405.1175.32.camel@localhost.localdomain \
--to=dedekind1@gmail.com \
--cc=arno.steffen@googlemail.com \
--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;
as well as URLs for NNTP newsgroup(s).