From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-fx0-f49.google.com ([209.85.161.49]) by bombadil.infradead.org with esmtp (Exim 4.72 #1 (Red Hat Linux)) id 1Oh0cs-00053J-5A for linux-mtd@lists.infradead.org; Thu, 05 Aug 2010 13:36:54 +0000 Received: by fxm3 with SMTP id 3so3550611fxm.36 for ; Thu, 05 Aug 2010 06:36:48 -0700 (PDT) Subject: Re: error!: "/dev/ubi0" is not a character device ?!? From: Artem Bityutskiy To: Arno Steffen In-Reply-To: References: <1280150054.14917.108.camel@localhost> <1280244340.3021.38.camel@localhost.localdomain> <1280471755.2838.29.camel@localhost.localdomain> Content-Type: text/plain; charset="UTF-8" Date: Thu, 05 Aug 2010 16:36:45 +0300 Message-Id: <1281015405.1175.32.camel@localhost.localdomain> Mime-Version: 1.0 Content-Transfer-Encoding: 8bit Cc: linux-mtd@lists.infradead.org Reply-To: dedekind1@gmail.com List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , 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 (Артём Битюцкий)