From: "Prakash K. Cheemplavam" <PrakashKC@gmx.de>
To: Greg KH <greg@kroah.com>
Cc: linux-hotplug-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] udev 021 release
Date: Sat, 13 Mar 2004 09:34:07 +0000 [thread overview]
Message-ID: <4052D58F.40104@gmx.de> (raw)
In-Reply-To: <20040311012127.GC11828@kroah.com>
Greg KH wrote:
> On Thu, Mar 11, 2004 at 12:17:12AM +0100, Prakash K. Cheemplavam wrote:
>
>>Greg KH wrote:
>>
>>>On Wed, Mar 10, 2004 at 01:56:37PM +0100, Prakash K. Cheemplavam wrote:
>>>
>>>>I have a problem with udev and my ZIP drive (using latest mm based
>>>>kernel):
>>>>
>>>>When I insert a zip the /dev for the partition doesn't get created (ie
>>>>hdd4, fdisk shows it though).
>
> See the manpage for udev and look at the NAME{all_partitions} section.
>
Well, I tried several variatons of following rule:
SYSFS{dev}="22:64", KERNEL="hdd", NAME{all_partitions}="hdd%n"
But no partitions popped up. I searched a bit in lkml and some time ago,
there was a thread about a jaz drive with the same problem. It rather
seems udev doesn't see the partitions appearing or I do something wrong.
For the time being I just put this into my local.start:
mknod -m 660 /dev/hdd4 b 22 68
chown root:disk hdd4
If you are sure udev should hanlde it, it would be nice if you kick me a
bit further into the right direction...
Prakash
PS:udevinfo -a -p /sys/block/hdd/
udevinfo starts with the device the node belongs to and then walks up the
device chain to print for every device found all possibly useful attributes
in the udev key format.
Only attributes within one device section may be used in a rule to match the
device for which the node will be created.
device '/sys/block/hdd' has major:minor 22:64
looking at class device '/sys/block/hdd':
SYSFS{dev}="22:64"
SYSFS{range}="64"
SYSFS{size}="196608"
SYSFS{stat}=" 35 0 42 747 0 0
0 0 0 747 747"
follow the class device's "device"
looking at the device chain at
'/sys/devices/pci0000:00/0000:00:09.0/ide1/1.1':
BUS="ide"
ID="1.1"
SYSFS{detach_state}="0"
looking at the device chain at
'/sys/devices/pci0000:00/0000:00:09.0/ide1':
BUS=""
ID="ide1"
SYSFS{detach_state}="0"
looking at the device chain at '/sys/devices/pci0000:00/0000:00:09.0':
BUS="pci"
ID="0000:00:09.0"
SYSFS{detach_state}="0"
SYSFS{vendor}="0x10de"
SYSFS{device}="0x0065"
SYSFS{subsystem_vendor}="0x147b"
SYSFS{subsystem_device}="0x1c00"
SYSFS{class}="0x01018a"
SYSFS{irq}="0"
looking at the device chain at '/sys/devices/pci0000:00':
BUS=""
ID="pci0000:00"
SYSFS{detach_state}="0"
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id\x1470&alloc_id638&op=click
_______________________________________________
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:[~2004-03-13 9:34 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-03 0:09 [ANNOUNCE] udev 021 release Greg KH
2004-03-03 0:25 ` Greg KH
2004-03-03 1:16 ` Marco d'Itri
2004-03-03 3:09 ` Greg KH
2004-03-03 9:56 ` Michael Weiser
2004-03-03 12:22 ` Ed Tomlinson
2004-03-03 15:14 ` Greg KH
2004-03-03 19:28 ` David Brownell
2004-03-03 22:53 ` Michael Weiser
2004-03-04 1:25 ` Greg KH
2004-03-04 3:58 ` Bill Nottingham
2004-03-04 18:26 ` Greg KH
2004-03-04 1:22 ` Marco d'Itri
2004-03-04 1:28 ` Greg KH
2004-03-04 9:27 ` Michael Weiser
2004-03-03 15:15 ` Greg KH
2004-03-03 23:56 ` Michael Weiser
2004-03-04 1:19 ` Greg KH
2004-03-03 10:19 ` Marco d'Itri
2004-03-03 10:52 ` Alexander E. Patrakov
2004-03-03 11:02 ` Marco d'Itri
2004-03-03 15:49 ` Alexander E. Patrakov
2004-03-04 1:18 ` Marco d'Itri
[not found] ` <4046CE91.50701@kubla.de>
2004-03-04 18:44 ` Greg KH
[not found] ` <40482ACC.3070504@kubla.de>
2004-03-10 22:53 ` Greg KH
[not found] ` <1078422507.3614.20.camel@nosferatu.lan>
2004-03-04 18:46 ` Greg KH
2004-03-09 11:51 ` "Andrey Borzenkov"
2004-03-10 2:34 ` Oliver Neukum
2004-03-10 12:29 ` "Andrey Borzenkov"
2004-03-10 12:56 ` Prakash K. Cheemplavam
2004-03-10 22:51 ` Greg KH
2004-03-10 23:17 ` Prakash K. Cheemplavam
2004-03-11 1:21 ` Greg KH
2004-03-13 9:34 ` Prakash K. Cheemplavam [this message]
2004-03-11 3:30 ` Oliver Neukum
2004-03-11 9:22 ` "Andrey Borzenkov"
2004-03-12 23:39 ` Greg KH
[not found] <20040303153403.21649.81059.Mailman@linux.us.dell.com>
[not found] ` <4048D503.10808@mail.ru>
2004-03-09 8:19 ` Greg KH
2004-03-09 10:16 ` rihad
2004-03-09 13:43 ` Alex Goddard
2004-03-10 22:52 ` Greg KH
[not found] <fa.dbn18ei.1k46o3i@ifi.uio.no>
[not found] ` <fa.afjk56q.t0ulic@ifi.uio.no>
2004-03-10 13:02 ` walt
2004-03-10 21:01 ` Prakash K. Cheemplavam
[not found] <fa.fkf6pbs.vk4328@ifi.uio.no>
[not found] ` <fa.aj3o3v7.pgqn9l@ifi.uio.no>
[not found] ` <404F9E5F.2010001@myrealbox.com>
2004-03-11 0:11 ` Prakash K. Cheemplavam
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=4052D58F.40104@gmx.de \
--to=prakashkc@gmx.de \
--cc=greg@kroah.com \
--cc=linux-hotplug-devel@lists.sourceforge.net \
--cc=linux-kernel@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).