* Re: Udev and Mylex Dac960
2004-02-05 23:02 Udev and Mylex Dac960 claude
@ 2004-02-06 0:07 ` Greg KH
2004-02-06 14:40 ` claude
` (10 subsequent siblings)
11 siblings, 0 replies; 13+ messages in thread
From: Greg KH @ 2004-02-06 0:07 UTC (permalink / raw)
To: linux-hotplug
On Fri, Feb 06, 2004 at 12:02:21AM +0100, claude wrote:
> Hi all,
>
> Udev reports my DAC960 devices as /dev/rd!c0d0 ? Is this ok ?
Depends, do you like that name? :)
Can you give me the output of 'tree -d /sys/block' on your system? I
think udev just needs to change that '!' character to a '/' to make it
correct.
thanks,
greg k-h
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
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
^ permalink raw reply [flat|nested] 13+ messages in thread* Re: Udev and Mylex Dac960
2004-02-05 23:02 Udev and Mylex Dac960 claude
2004-02-06 0:07 ` Greg KH
@ 2004-02-06 14:40 ` claude
2004-02-07 19:04 ` claude
` (9 subsequent siblings)
11 siblings, 0 replies; 13+ messages in thread
From: claude @ 2004-02-06 14:40 UTC (permalink / raw)
To: linux-hotplug
Greg KH wrote:
> On Fri, Feb 06, 2004 at 12:02:21AM +0100, claude wrote:
>
> Depends, do you like that name? :)
>
I can't say :). I just want to have right naming. Devices list at
lanana.org is pretty old, and things change too quickly. I wanted
to know which name is the right today.
> Can you give me the output of 'tree -d /sys/block' on your system? I
> think udev just needs to change that '!' character to a '/' to make it
> correct.
>
Yes, the output is below, and I think you're right too ;)
> thanks,
>
Thanks to you all for this great work :)
> greg k-h
>
Claude
snslinux@snscrew.net# tree -d /sys/block
/sys/block
|-- fd0
| `-- queue
| `-- iosched
|-- hda
| |-- device -> ../../devices/pci0000:00/0000:00:07.1/ide0/0.0
| `-- queue
| `-- iosched
|-- loop0
|-- loop1
|-- loop2
|-- loop3
|-- loop4
|-- loop5
|-- loop6
|-- loop7
|-- md0
|-- ram0
|-- ram1
|-- ram10
|-- ram11
|-- ram12
|-- ram13
|-- ram14
|-- ram15
|-- ram2
|-- ram3
|-- ram4
|-- ram5
|-- ram6
|-- ram7
|-- ram8
|-- ram9
|-- rd!c0d0
| |-- queue
| | `-- iosched
| |-- rd!c0d01
| |-- rd!c0d02
| |-- rd!c0d03
| |-- rd!c0d04
| |-- rd!c0d05
| `-- rd!c0d06
|-- rd!c0d1
| `-- queue
| `-- iosched
|-- rd!c0d10
| `-- queue
| `-- iosched
|-- rd!c0d11
| `-- queue
| `-- iosched
|-- rd!c0d12
| `-- queue
| `-- iosched
|-- rd!c0d13
| `-- queue
| `-- iosched
|-- rd!c0d14
| `-- queue
| `-- iosched
|-- rd!c0d15
| `-- queue
| `-- iosched
|-- rd!c0d16
| `-- queue
| `-- iosched
|-- rd!c0d17
| `-- queue
| `-- iosched
|-- rd!c0d18
| `-- queue
| `-- iosched
|-- rd!c0d19
| `-- queue
| `-- iosched
|-- rd!c0d2
| `-- queue
| `-- iosched
|-- rd!c0d20
| `-- queue
| `-- iosched
|-- rd!c0d21
| `-- queue
| `-- iosched
|-- rd!c0d22
| `-- queue
| `-- iosched
|-- rd!c0d23
| `-- queue
| `-- iosched
|-- rd!c0d24
| `-- queue
| `-- iosched
|-- rd!c0d25
| `-- queue
| `-- iosched
|-- rd!c0d26
| `-- queue
| `-- iosched
|-- rd!c0d27
| `-- queue
| `-- iosched
|-- rd!c0d28
| `-- queue
| `-- iosched
|-- rd!c0d29
| `-- queue
| `-- iosched
|-- rd!c0d3
| `-- queue
| `-- iosched
|-- rd!c0d30
| `-- queue
| `-- iosched
|-- rd!c0d31
| `-- queue
| `-- iosched
|-- rd!c0d4
| `-- queue
| `-- iosched
|-- rd!c0d5
| `-- queue
| `-- iosched
|-- rd!c0d6
| `-- queue
| `-- iosched
|-- rd!c0d7
| `-- queue
| `-- iosched
|-- rd!c0d8
| `-- queue
| `-- iosched
`-- rd!c0d9
`-- queue
`-- iosched
134 directories
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
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
^ permalink raw reply [flat|nested] 13+ messages in thread* Re: Udev and Mylex Dac960
2004-02-05 23:02 Udev and Mylex Dac960 claude
2004-02-06 0:07 ` Greg KH
2004-02-06 14:40 ` claude
@ 2004-02-07 19:04 ` claude
2004-02-11 23:49 ` Greg KH
` (8 subsequent siblings)
11 siblings, 0 replies; 13+ messages in thread
From: claude @ 2004-02-07 19:04 UTC (permalink / raw)
To: linux-hotplug
Hi,
I have another question about Mylex Dac960.
Is there any way for udev to create device only for existing array ?
(eg : I only have /dev/rd!c0d0 but udev create /dev/rd!c0d[1-31]).
Thanks for your response !
claude
>
> snslinux@snscrew.net# tree -d /sys/block
> /sys/block
> |-- fd0
> | `-- queue
> | `-- iosched
> |-- hda
> | |-- device -> ../../devices/pci0000:00/0000:00:07.1/ide0/0.0
> | `-- queue
> | `-- iosched
> |-- loop0
> |-- loop1
> |-- loop2
> |-- loop3
> |-- loop4
> |-- loop5
> |-- loop6
> |-- loop7
> |-- md0
> |-- ram0
> |-- ram1
> |-- ram10
> |-- ram11
> |-- ram12
> |-- ram13
> |-- ram14
> |-- ram15
> |-- ram2
> |-- ram3
> |-- ram4
> |-- ram5
> |-- ram6
> |-- ram7
> |-- ram8
> |-- ram9
> |-- rd!c0d0
> | |-- queue
> | | `-- iosched
> | |-- rd!c0d01
> | |-- rd!c0d02
> | |-- rd!c0d03
> | |-- rd!c0d04
> | |-- rd!c0d05
> | `-- rd!c0d06
> |-- rd!c0d1
> | `-- queue
> | `-- iosched
> |-- rd!c0d10
> | `-- queue
> | `-- iosched
> |-- rd!c0d11
> | `-- queue
> | `-- iosched
> |-- rd!c0d12
> | `-- queue
> | `-- iosched
> |-- rd!c0d13
> | `-- queue
> | `-- iosched
> |-- rd!c0d14
> | `-- queue
> | `-- iosched
> |-- rd!c0d15
> | `-- queue
> | `-- iosched
> |-- rd!c0d16
> | `-- queue
> | `-- iosched
> |-- rd!c0d17
> | `-- queue
> | `-- iosched
> |-- rd!c0d18
> | `-- queue
> | `-- iosched
> |-- rd!c0d19
> | `-- queue
> | `-- iosched
> |-- rd!c0d2
> | `-- queue
> | `-- iosched
> |-- rd!c0d20
> | `-- queue
> | `-- iosched
> |-- rd!c0d21
> | `-- queue
> | `-- iosched
> |-- rd!c0d22
> | `-- queue
> | `-- iosched
> |-- rd!c0d23
> | `-- queue
> | `-- iosched
> |-- rd!c0d24
> | `-- queue
> | `-- iosched
> |-- rd!c0d25
> | `-- queue
> | `-- iosched
> |-- rd!c0d26
> | `-- queue
> | `-- iosched
> |-- rd!c0d27
> | `-- queue
> | `-- iosched
> |-- rd!c0d28
> | `-- queue
> | `-- iosched
> |-- rd!c0d29
> | `-- queue
> | `-- iosched
> |-- rd!c0d3
> | `-- queue
> | `-- iosched
> |-- rd!c0d30
> | `-- queue
> | `-- iosched
> |-- rd!c0d31
> | `-- queue
> | `-- iosched
> |-- rd!c0d4
> | `-- queue
> | `-- iosched
> |-- rd!c0d5
> | `-- queue
> | `-- iosched
> |-- rd!c0d6
> | `-- queue
> | `-- iosched
> |-- rd!c0d7
> | `-- queue
> | `-- iosched
> |-- rd!c0d8
> | `-- queue
> | `-- iosched
> `-- rd!c0d9
> `-- queue
> `-- iosched
>
> 134 directories
>
>
> -------------------------------------------------------
> The SF.Net email is sponsored by EclipseCon 2004
> Premiere Conference on Open Tools Development and Integration
> See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
> http://www.eclipsecon.org/osdn
> _______________________________________________
> 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
>
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
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
^ permalink raw reply [flat|nested] 13+ messages in thread* Re: Udev and Mylex Dac960
2004-02-05 23:02 Udev and Mylex Dac960 claude
` (2 preceding siblings ...)
2004-02-07 19:04 ` claude
@ 2004-02-11 23:49 ` Greg KH
2004-02-12 1:41 ` Greg KH
` (7 subsequent siblings)
11 siblings, 0 replies; 13+ messages in thread
From: Greg KH @ 2004-02-11 23:49 UTC (permalink / raw)
To: linux-hotplug
On Fri, Feb 06, 2004 at 03:40:28PM +0100, claude wrote:
> Greg KH wrote:
> >On Fri, Feb 06, 2004 at 12:02:21AM +0100, claude wrote:
> >
> >Depends, do you like that name? :)
> >
> I can't say :). I just want to have right naming. Devices list at
> lanana.org is pretty old, and things change too quickly. I wanted
> to know which name is the right today.
>
> >Can you give me the output of 'tree -d /sys/block' on your system? I
> >think udev just needs to change that '!' character to a '/' to make it
> >correct.
> >
> Yes, the output is below, and I think you're right too ;)
Thanks for the output. I've fixed this in the current udev tree, so the
next release should work just fine for this kind of device.
Please let me know if it doesn't.
Thanks again for reporting this.
greg k-h
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id\x1356&alloc_id438&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
^ permalink raw reply [flat|nested] 13+ messages in thread* Re: Udev and Mylex Dac960
2004-02-05 23:02 Udev and Mylex Dac960 claude
` (3 preceding siblings ...)
2004-02-11 23:49 ` Greg KH
@ 2004-02-12 1:41 ` Greg KH
2004-02-12 2:02 ` claude
` (6 subsequent siblings)
11 siblings, 0 replies; 13+ messages in thread
From: Greg KH @ 2004-02-12 1:41 UTC (permalink / raw)
To: linux-hotplug
On Sat, Feb 07, 2004 at 08:04:32PM +0100, claude wrote:
> Hi,
>
> I have another question about Mylex Dac960.
>
> Is there any way for udev to create device only for existing array ?
>
> (eg : I only have /dev/rd!c0d0 but udev create /dev/rd!c0d[1-31]).
Well your kernel is saying that you really do have all of those other
devices. You might want to talk to the kernel driver about this...
But yes, you can ignore devices with the following rule:
KERNEL="*c0d[1-31]", NAME=""
The NAME="" section is optional, but a bit nicer to try to figure out
what is happening.
The ability to ignore devices is broken in udev 016, but is now fixed in
the current tree. Try this with the next release (hopefully in a few
days...)
thanks,
greg k-h
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id\x1356&alloc_id438&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
^ permalink raw reply [flat|nested] 13+ messages in thread* Re: Udev and Mylex Dac960
2004-02-05 23:02 Udev and Mylex Dac960 claude
` (4 preceding siblings ...)
2004-02-12 1:41 ` Greg KH
@ 2004-02-12 2:02 ` claude
2004-02-13 21:05 ` Greg KH
` (5 subsequent siblings)
11 siblings, 0 replies; 13+ messages in thread
From: claude @ 2004-02-12 2:02 UTC (permalink / raw)
To: linux-hotplug
Greg KH wrote:
> On Sat, Feb 07, 2004 at 08:04:32PM +0100, claude wrote:
>
>>Hi,
>>
>>I have another question about Mylex Dac960.
>>
>>Is there any way for udev to create device only for existing array ?
>>
>>(eg : I only have /dev/rd!c0d0 but udev create /dev/rd!c0d[1-31]).
>
>
> Well your kernel is saying that you really do have all of those other
> devices. You might want to talk to the kernel driver about this...
>
Yes i will do, but is there any docs about sysfs and how it works ? I've
only found sysfs.txt in linux-2.6.2/Documentation, and it was too light
explanation for my poor knowledge. Any pointer ?
> But yes, you can ignore devices with the following rule:
> KERNEL="*c0d[1-31]", NAME=""
>
> The NAME="" section is optional, but a bit nicer to try to figure out
> what is happening.
>
> The ability to ignore devices is broken in udev 016, but is now fixed in
> the current tree. Try this with the next release (hopefully in a few
> days...)
ok, I will wait for it.
>
> thanks,
>
thanks too and thanks to all others for this great work :)
> greg k-h
>
claude
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id\x1356&alloc_id438&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
^ permalink raw reply [flat|nested] 13+ messages in thread* Re: Udev and Mylex Dac960
2004-02-05 23:02 Udev and Mylex Dac960 claude
` (5 preceding siblings ...)
2004-02-12 2:02 ` claude
@ 2004-02-13 21:05 ` Greg KH
2004-02-16 5:46 ` claude
` (4 subsequent siblings)
11 siblings, 0 replies; 13+ messages in thread
From: Greg KH @ 2004-02-13 21:05 UTC (permalink / raw)
To: linux-hotplug
On Thu, Feb 12, 2004 at 03:02:56AM +0100, claude wrote:
> Yes i will do, but is there any docs about sysfs and how it works ? I've
> only found sysfs.txt in linux-2.6.2/Documentation, and it was too light
> explanation for my poor knowledge. Any pointer ?
What do you want to know about sysfs?
How to write code to use it? If so, lwn.net has has a few good articles
about it, and there is a OLS and linux.conf.au paper about it.
If you just want to know what in the world these different directories
are, and how they relate to each other, from a user point of view,
that's not so well documentated, yet :(
thanks,
greg k-h
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id\x1356&alloc_id438&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
^ permalink raw reply [flat|nested] 13+ messages in thread* Re: Udev and Mylex Dac960
2004-02-05 23:02 Udev and Mylex Dac960 claude
` (6 preceding siblings ...)
2004-02-13 21:05 ` Greg KH
@ 2004-02-16 5:46 ` claude
2004-02-16 5:52 ` Greg KH
` (3 subsequent siblings)
11 siblings, 0 replies; 13+ messages in thread
From: claude @ 2004-02-16 5:46 UTC (permalink / raw)
To: linux-hotplug
Greg KH wrote:
> On Thu, Feb 12, 2004 at 03:02:56AM +0100, claude wrote:
>
>>Yes i will do, but is there any docs about sysfs and how it works ? I've
>>only found sysfs.txt in linux-2.6.2/Documentation, and it was too light
>>explanation for my poor knowledge. Any pointer ?
>
>
> What do you want to know about sysfs?
>
> How to write code to use it? If so, lwn.net has has a few good articles
> about it, and there is a OLS and linux.conf.au paper about it.
>
Many thanks for links, that's just what I want.
Also a bad news :(. I've downloaded udev-017.tar.gz, compiled and installed it,
but my Mylex logical device are always created as /dev/rd!c0d0. Is there anything
I can do ?
> If you just want to know what in the world these different directories
> are, and how they relate to each other, from a user point of view,
> that's not so well documentated, yet :(
>
> thanks,
>
> greg k-h
>
>
> -------------------------------------------------------
> SF.Net is sponsored by: Speed Start Your Linux Apps Now.
> Build and deploy apps & Web services for Linux with
> a free DVD software kit from IBM. Click Now!
> http://ads.osdn.com/?ad_id\x1356&alloc_id438&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
>
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id\x1356&alloc_id438&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
^ permalink raw reply [flat|nested] 13+ messages in thread* Re: Udev and Mylex Dac960
2004-02-05 23:02 Udev and Mylex Dac960 claude
` (7 preceding siblings ...)
2004-02-16 5:46 ` claude
@ 2004-02-16 5:52 ` Greg KH
2004-02-16 7:35 ` claude
` (2 subsequent siblings)
11 siblings, 0 replies; 13+ messages in thread
From: Greg KH @ 2004-02-16 5:52 UTC (permalink / raw)
To: linux-hotplug
On Mon, Feb 16, 2004 at 06:46:16AM +0100, claude wrote:
> Greg KH wrote:
> >On Thu, Feb 12, 2004 at 03:02:56AM +0100, claude wrote:
> >
> >>Yes i will do, but is there any docs about sysfs and how it works ? I've
> >>only found sysfs.txt in linux-2.6.2/Documentation, and it was too light
> >>explanation for my poor knowledge. Any pointer ?
> >
> >
> >What do you want to know about sysfs?
> >
> >How to write code to use it? If so, lwn.net has has a few good articles
> >about it, and there is a OLS and linux.conf.au paper about it.
> >
>
> Many thanks for links, that's just what I want.
>
> Also a bad news :(. I've downloaded udev-017.tar.gz, compiled and installed
> it,
> but my Mylex logical device are always created as /dev/rd!c0d0. Is there
> anything
> I can do ?
Ick. Can you build udev by doing the following:
make clean
make DEBUG=true USE_LOG=true
And then run the udevtest binary in that directory that gets built for
your block device:
./udevtest block/rd!c0d0
(you might have to do this as:
./udevtest block/rd\!c0d0
depending on your shell)
and then send the output that this program creates to us?
thanks,
greg k-h
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id\x1356&alloc_id438&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
^ permalink raw reply [flat|nested] 13+ messages in thread* Re: Udev and Mylex Dac960
2004-02-05 23:02 Udev and Mylex Dac960 claude
` (8 preceding siblings ...)
2004-02-16 5:52 ` Greg KH
@ 2004-02-16 7:35 ` claude
2004-02-16 18:22 ` Greg KH
2004-02-16 20:10 ` claude
11 siblings, 0 replies; 13+ messages in thread
From: claude @ 2004-02-16 7:35 UTC (permalink / raw)
To: linux-hotplug
Greg KH wrote:
> On Mon, Feb 16, 2004 at 06:46:16AM +0100, claude wrote:
>
>>Also a bad news :(. I've downloaded udev-017.tar.gz, compiled and installed
>>it,
>>but my Mylex logical device are always created as /dev/rd!c0d0. Is there
>>anything
>>I can do ?
>
>
> Ick. Can you build udev by doing the following:
> make clean
> make DEBUG=true USE_LOG=true
>
> And then run the udevtest binary in that directory that gets built for
> your block device:
> ./udevtest block/rd!c0d0
> (you might have to do this as:
> ./udevtest block/rd\!c0d0
> depending on your shell)
Yeah, that's why '!' bother me ! ;)
>
> and then send the output that this program creates to us?
Yes output follow (i have to type :
udevtest /block/rd\!c0d0 )
main: version 017
udev_hotplug: looking at '/block/rd!c0d0'
get_dirs: sysfs_path='/sys'
parse_config_file: reading '/etc/udev/udev.conf' as config file
namedev_init_rules: reading '/etc/udev/udev.rules' as rules file
namedev_init_permissions: reading '/etc/udev/udev.permissions' as permissions file
sleep_for_dev: looking for '/sys/block/rd!c0d0/dev'
get_class_dev: looking at '/sys/block/rd!c0d0'
get_class_dev: class_dev->name='rd!c0d0'
get_major_minor: dev='48:0
'
get_major_minor: found majorH, minor=0
get_blockdev_parent: rd!c0d0 not a partition
sysfs_path_is_link: stat() failed
sysfs_path_is_link: stat() failed
sysfs_path_is_link: stat() failed
sysfs_path_is_link: stat() failed
sysfs_path_is_link: stat() failed
sysfs_path_is_link: stat() failed
sysfs_path_is_link: stat() failed
sysfs_path_is_link: stat() failed
sysfs_path_is_link: stat() failed
sysfs_path_is_link: stat() failed
get_sysfs_device: timed out waiting for device symlink, continuing on anyway...
namedev_name_device: class_dev->name = 'rd!c0d0'
namedev_name_device: udev->kernel_name = 'rd/c0d0'
namedev_name_device: kernel_number='0'
namedev_name_device: name, 'rd!c0d0' is going to have owner='root', group='root', mode = 0600
udev_add_device: name='rd!c0d0'
creating device node '/dev/rd!c0d0'
create_node: mknod(/dev/rd!c0d0, 020600, 48, 0)
create_node: chmod(/dev/rd!c0d0, 020600)
>
> thanks,
>
> greg k-h
thanks,
claude -
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id\x1356&alloc_id438&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
^ permalink raw reply [flat|nested] 13+ messages in thread* Re: Udev and Mylex Dac960
2004-02-05 23:02 Udev and Mylex Dac960 claude
` (9 preceding siblings ...)
2004-02-16 7:35 ` claude
@ 2004-02-16 18:22 ` Greg KH
2004-02-16 20:10 ` claude
11 siblings, 0 replies; 13+ messages in thread
From: Greg KH @ 2004-02-16 18:22 UTC (permalink / raw)
To: linux-hotplug
On Mon, Feb 16, 2004 at 08:35:12AM +0100, claude wrote:
> Yes output follow (i have to type :
> udevtest /block/rd\!c0d0 )
Oops, sorry, forgot the leading '/' I need to document udevtest, I made
it for my testing but it looks like it really is handy to find problems
like this.
>
> main: version 017
> udev_hotplug: looking at '/block/rd!c0d0'
> get_dirs: sysfs_path='/sys'
> parse_config_file: reading '/etc/udev/udev.conf' as config file
> namedev_init_rules: reading '/etc/udev/udev.rules' as rules file
> namedev_init_permissions: reading '/etc/udev/udev.permissions' as
> permissions file
> sleep_for_dev: looking for '/sys/block/rd!c0d0/dev'
> get_class_dev: looking at '/sys/block/rd!c0d0'
> get_class_dev: class_dev->name='rd!c0d0'
> get_major_minor: dev='48:0
> '
> get_major_minor: found majorH, minor=0
> get_blockdev_parent: rd!c0d0 not a partition
> sysfs_path_is_link: stat() failed
> sysfs_path_is_link: stat() failed
> sysfs_path_is_link: stat() failed
> sysfs_path_is_link: stat() failed
> sysfs_path_is_link: stat() failed
> sysfs_path_is_link: stat() failed
> sysfs_path_is_link: stat() failed
> sysfs_path_is_link: stat() failed
> sysfs_path_is_link: stat() failed
> sysfs_path_is_link: stat() failed
> get_sysfs_device: timed out waiting for device symlink, continuing on
> anyway...
> namedev_name_device: class_dev->name = 'rd!c0d0'
> namedev_name_device: udev->kernel_name = 'rd/c0d0'
> namedev_name_device: kernel_number='0'
> namedev_name_device: name, 'rd!c0d0' is going to have owner='root',
> group='root', mode = 0600
> udev_add_device: name='rd!c0d0'
> creating device node '/dev/rd!c0d0'
> create_node: mknod(/dev/rd!c0d0, 020600, 48, 0)
> create_node: chmod(/dev/rd!c0d0, 020600)
Ah, found it. I was testing this with the following rule in my rules
file:
BUS="scsi", NAME="%k"
If you put that at the end of your udev.rules file, you should get the
proper name generated.
Or you can apply the following patch, which will solve the problem if
you do not have a rule in udev.rules for this device.
thanks a lot for helping me find the problem.
greg k-h
# Fix bug where we did not use the "converted" kernel name if we had no rule.
#
# This fixes the bug with names that have a ! in them and no rule to match.
diff -Nru a/namedev.c b/namedev.c
--- a/namedev.c Mon Feb 16 10:19:58 2004
+++ b/namedev.c Mon Feb 16 10:19:58 2004
@@ -745,7 +745,7 @@
}
/* no rule was found so we use the kernel name */
- strfieldcpy(udev->name, class_dev->name);
+ strfieldcpy(udev->name, udev->kernel_name);
goto done;
found:
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id\x1356&alloc_id438&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
^ permalink raw reply [flat|nested] 13+ messages in thread* Re: Udev and Mylex Dac960
2004-02-05 23:02 Udev and Mylex Dac960 claude
` (10 preceding siblings ...)
2004-02-16 18:22 ` Greg KH
@ 2004-02-16 20:10 ` claude
11 siblings, 0 replies; 13+ messages in thread
From: claude @ 2004-02-16 20:10 UTC (permalink / raw)
To: linux-hotplug
I've applied patch and it works great ! many thanks again !
Greg KH wrote:
> On Mon, Feb 16, 2004 at 08:35:12AM +0100, claude wrote:
>
>>Yes output follow (i have to type :
>> udevtest /block/rd\!c0d0 )
>
>
> Oops, sorry, forgot the leading '/' I need to document udevtest, I made
> it for my testing but it looks like it really is handy to find problems
> like this.
>
>
>>main: version 017
>>udev_hotplug: looking at '/block/rd!c0d0'
>>get_dirs: sysfs_path='/sys'
>>parse_config_file: reading '/etc/udev/udev.conf' as config file
>>namedev_init_rules: reading '/etc/udev/udev.rules' as rules file
>>namedev_init_permissions: reading '/etc/udev/udev.permissions' as
>>permissions file
>>sleep_for_dev: looking for '/sys/block/rd!c0d0/dev'
>>get_class_dev: looking at '/sys/block/rd!c0d0'
>>get_class_dev: class_dev->name='rd!c0d0'
>>get_major_minor: dev='48:0
>>'
>>get_major_minor: found majorH, minor=0
>>get_blockdev_parent: rd!c0d0 not a partition
>>sysfs_path_is_link: stat() failed
>>sysfs_path_is_link: stat() failed
>>sysfs_path_is_link: stat() failed
>>sysfs_path_is_link: stat() failed
>>sysfs_path_is_link: stat() failed
>>sysfs_path_is_link: stat() failed
>>sysfs_path_is_link: stat() failed
>>sysfs_path_is_link: stat() failed
>>sysfs_path_is_link: stat() failed
>>sysfs_path_is_link: stat() failed
>>get_sysfs_device: timed out waiting for device symlink, continuing on
>>anyway...
>>namedev_name_device: class_dev->name = 'rd!c0d0'
>>namedev_name_device: udev->kernel_name = 'rd/c0d0'
>>namedev_name_device: kernel_number='0'
>>namedev_name_device: name, 'rd!c0d0' is going to have owner='root',
>>group='root', mode = 0600
>>udev_add_device: name='rd!c0d0'
>>creating device node '/dev/rd!c0d0'
>>create_node: mknod(/dev/rd!c0d0, 020600, 48, 0)
>>create_node: chmod(/dev/rd!c0d0, 020600)
>
>
> Ah, found it. I was testing this with the following rule in my rules
> file:
> BUS="scsi", NAME="%k"
> If you put that at the end of your udev.rules file, you should get the
> proper name generated.
>
> Or you can apply the following patch, which will solve the problem if
> you do not have a rule in udev.rules for this device.
>
> thanks a lot for helping me find the problem.
>
> greg k-h
>
> # Fix bug where we did not use the "converted" kernel name if we had no rule.
> #
> # This fixes the bug with names that have a ! in them and no rule to match.
>
> diff -Nru a/namedev.c b/namedev.c
> --- a/namedev.c Mon Feb 16 10:19:58 2004
> +++ b/namedev.c Mon Feb 16 10:19:58 2004
> @@ -745,7 +745,7 @@
> }
>
> /* no rule was found so we use the kernel name */
> - strfieldcpy(udev->name, class_dev->name);
> + strfieldcpy(udev->name, udev->kernel_name);
> goto done;
>
> found:
>
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id\x1356&alloc_id438&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
^ permalink raw reply [flat|nested] 13+ messages in thread