From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: Feature/Bug? udev/hotplug creates device nodes with strange
Date: Mon, 11 Apr 2005 12:21:56 +0000 [thread overview]
Message-ID: <1113222116.6758.18.camel@localhost.localdomain> (raw)
In-Reply-To: <20050410131837.GB21307@gamma.logic.tuwien.ac.at>
On Sun, 2005-04-10 at 15:18 +0200, Norbert Preining wrote:
> Hi all!
>
> Is the following a bug or feature: If I have the option
> all_partitions
> set in my local rules.d file, all the device nodes for all partitions
> are created, but for those which are *NOT* physically available, the
> minor of the last available is used:
>
> Examples: I have an sdcard reader which I NAME /dev/sdcardX, and the
> card has only one partition. But the created devices look like:
> brw-rw---- 1 root root 8, 0 2005-04-10 14:58 /dev/sdcard
> brw-rw---- 1 root root 8, 1 2005-04-10 14:58 /dev/sdcard1
> brw-rw---- 1 root root 8, 1 2005-04-10 14:58 /dev/sdcard2
> brw-rw---- 1 root root 8, 1 2005-04-10 14:58 /dev/sdcard3
This looks broken.
> Here it is not really a problem, but it really hit me when I was using a
> new hard disk which did NOT contain already a partition table (so a bit
> like a floppy). So, I got minor 0 (!!!) for all /dev/sdbN (ie the
> partitions). I (stupid me) didn't check, made mke2fs -j /dev/sdb1 and
> voilà , now I have a floppy instead of a external firewire harddisk with
> a normal partition table. Grmmm.
>
> So my question: Is this a feature or a bug?
Looks like a bug, but I have no idea, how this can happen.
What version of udev do you use?
Thanks,
Kay
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id\x14396&opÌk
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2005-04-11 12:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-10 13:18 Feature/Bug? udev/hotplug creates device nodes with strange major/minor numbers Norbert Preining
2005-04-11 12:21 ` Kay Sievers [this message]
2005-04-11 12:55 ` Norbert Preining
2005-04-11 13:16 ` Feature/Bug? udev/hotplug creates device nodes with strange Kay Sievers
2005-04-11 13:50 ` Feature/Bug? udev/hotplug creates device nodes with strange major/minor numbers Tobias Klauser
2005-04-11 14:30 ` Norbert Preining
2005-04-11 14:56 ` Feature/Bug? udev/hotplug creates device nodes with strange Kay Sievers
2005-04-11 14:58 ` Kay Sievers
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=1113222116.6758.18.camel@localhost.localdomain \
--to=kay.sievers@vrfy.org \
--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).