Simple Rule Now Broken in udev089

Simple Rule Now Broken in udev089

[Robert Kennedy]

For awhile I have been using the following simple rule to create a 
persistent symlink for my removable CDRW burner:

KERNEL="scd0", SYMLINK="cdrwiter"

I placed this rule in 10-local.rules inside the /etc/udev/rules.d/ 
directory.

It used to work in previous version of udev but now it does not work.  udev 
is still creating the /dev/scd0 node but not the /dev/cdwriter node.

Any ideas on what might be happening.    Has anything changed in udev 089?

Rob




-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x110944&bid$1720&dat\x121642
_______________________________________________
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

Re: Simple Rule Now Broken in udev089

[Kay Sievers]

On Tue, Apr 11, 2006 at 09:49:43PM +0000, Robert Kennedy wrote:
> 
> For awhile I have been using the following simple rule to create a 
> persistent symlink for my removable CDRW burner:
> 
> KERNEL="scd0", SYMLINK="cdrwiter"
> 
> I placed this rule in 10-local.rules inside the /etc/udev/rules.d/ 
> directory.
> 
> It used to work in previous version of udev but now it does not work.  udev 
> is still creating the /dev/scd0 node but not the /dev/cdwriter node.
> 
> Any ideas on what might be happening.    Has anything changed in udev 089?

No, something like this works for me. But you should always use += to
add a new symlink to the list, otherwise you reset all earlier added
ones. Maybe there is a later rule that overwrites that one?

Kay


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x110944&bid$1720&dat\x121642
_______________________________________________
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

Re: Simple Rule Now Broken in udev089

[Robert Kennedy]

>From: Kay Sievers <kay.sievers@vrfy.org>
>To: Robert Kennedy <amtor@hotmail.com>
>CC: linux-hotplug-devel@lists.sourceforge.net
>Subject: Re: Simple Rule Now Broken in udev089
>Date: Wed, 12 Apr 2006 10:45:15 +0200
>
>On Tue, Apr 11, 2006 at 09:49:43PM +0000, Robert Kennedy wrote:
> >
> > For awhile I have been using the following simple rule to create a
> > persistent symlink for my removable CDRW burner:
> >
> > KERNEL="scd0", SYMLINK="cdrwiter"
> >
> > I placed this rule in 10-local.rules inside the /etc/udev/rules.d/
> > directory.
> >
> > It used to work in previous version of udev but now it does not work.  
>udev
> > is still creating the /dev/scd0 node but not the /dev/cdwriter node.
> >
> > Any ideas on what might be happening.    Has anything changed in udev 
>089?
>
>No, something like this works for me. But you should always use += to
>add a new symlink to the list, otherwise you reset all earlier added
>ones. Maybe there is a later rule that overwrites that one?
>
>Kay

Thanks for the tip Kay.  I tried changing the rule to:

KERNEL="scd0", SYMLINK+="cdwriter"

and then doing a udevstart but it did not work.  I still get a /dev/scd0 
node but not a /dev/cdwriter node.  Very strange.    I only have this one 
rule in 10-local.rules.  10-local.rules should be the first file processed 
in /etc/udev/rules.d/

Rob




-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x110944&bid$1720&dat\x121642
_______________________________________________
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

Re: Simple Rule Now Broken in udev089

[Kay Sievers]

On Wed, Apr 12, 2006 at 09:11:43PM +0000, Robert Kennedy wrote:
> >From: Kay Sievers <kay.sievers@vrfy.org>
> >To: Robert Kennedy <amtor@hotmail.com>
> >CC: linux-hotplug-devel@lists.sourceforge.net
> >Subject: Re: Simple Rule Now Broken in udev089
> >Date: Wed, 12 Apr 2006 10:45:15 +0200
> >
> >On Tue, Apr 11, 2006 at 09:49:43PM +0000, Robert Kennedy wrote:
> >>
> >> For awhile I have been using the following simple rule to create a
> >> persistent symlink for my removable CDRW burner:
> >>
> >> KERNEL="scd0", SYMLINK="cdrwiter"
> >>
> >> I placed this rule in 10-local.rules inside the /etc/udev/rules.d/
> >> directory.
> >>
> >> It used to work in previous version of udev but now it does not work.  
> >udev
> >> is still creating the /dev/scd0 node but not the /dev/cdwriter node.
> >>
> >> Any ideas on what might be happening.    Has anything changed in udev 
> >089?
> >
> >No, something like this works for me. But you should always use += to
> >add a new symlink to the list, otherwise you reset all earlier added
> >ones. Maybe there is a later rule that overwrites that one?
> >
> >Kay
> 
> Thanks for the tip Kay.  I tried changing the rule to:
> 
> KERNEL="scd0", SYMLINK+="cdwriter"
> 
> and then doing a udevstart but it did not work.  I still get a /dev/scd0 
> node but not a /dev/cdwriter node.  Very strange.    I only have this one 
> rule in 10-local.rules.  10-local.rules should be the first file processed 
> in /etc/udev/rules.d/

Are sure you have a scd* kernel device and not a sr*?
What does:
  ls -l /sys/block
show?

Kay


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x110944&bid$1720&dat\x121642
_______________________________________________
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

Re: Simple Rule Now Broken in udev089

[Robert Kennedy]

>On Wed, Apr 12, 2006 at 09:11:43PM +0000, Robert Kennedy wrote:
> > >From: Kay Sievers <kay.sievers@vrfy.org>
> > >To: Robert Kennedy <amtor@hotmail.com>
> > >CC: linux-hotplug-devel@lists.sourceforge.net
> > >Subject: Re: Simple Rule Now Broken in udev089
> > >Date: Wed, 12 Apr 2006 10:45:15 +0200
> > >
> > >On Tue, Apr 11, 2006 at 09:49:43PM +0000, Robert Kennedy wrote:
> > >>
> > >> For awhile I have been using the following simple rule to create a
> > >> persistent symlink for my removable CDRW burner:
> > >>
> > >> KERNEL="scd0", SYMLINK="cdrwiter"
> > >>
> > >> I placed this rule in 10-local.rules inside the /etc/udev/rules.d/
> > >> directory.
> > >>
> > >> It used to work in previous version of udev but now it does not work.
> > >udev
> > >> is still creating the /dev/scd0 node but not the /dev/cdwriter node.
> > >>
> > >> Any ideas on what might be happening.    Has anything changed in udev
> > >089?
> > >
> > >No, something like this works for me. But you should always use += to
> > >add a new symlink to the list, otherwise you reset all earlier added
> > >ones. Maybe there is a later rule that overwrites that one?
> > >
> > >Kay
> >
> > Thanks for the tip Kay.  I tried changing the rule to:
> >
> > KERNEL="scd0", SYMLINK+="cdwriter"
> >
> > and then doing a udevstart but it did not work.  I still get a /dev/scd0
> > node but not a /dev/cdwriter node.  Very strange.    I only have this 
>one
> > rule in 10-local.rules.  10-local.rules should be the first file 
>processed
> > in /etc/udev/rules.d/
>
>Are sure you have a scd* kernel device and not a sr*?
>What does:
>   ls -l /sys/block
>show?
>
>Kay

Thanks Kay.  I think we are getting close.  See the following:

[root@myarch ~]# ls -l /sys/block
total 0
drwxr-xr-x  3 root root 0 2006-04-12 16:57 fd0
drwxr-xr-x  9 root root 0 2006-04-12 16:57 hda
drwxr-xr-x  3 root root 0 2006-04-12 16:57 hdc
drwxr-xr-x  2 root root 0 2006-04-12 16:57 loop0
drwxr-xr-x  2 root root 0 2006-04-12 16:57 loop1
drwxr-xr-x  2 root root 0 2006-04-12 16:57 loop2
drwxr-xr-x  2 root root 0 2006-04-12 16:57 loop3
drwxr-xr-x  2 root root 0 2006-04-12 16:57 loop4
drwxr-xr-x  2 root root 0 2006-04-12 16:57 loop5
drwxr-xr-x  2 root root 0 2006-04-12 16:57 loop6
drwxr-xr-x  2 root root 0 2006-04-12 16:57 loop7
drwxr-xr-x  2 root root 0 2006-04-12 16:57 ram0
drwxr-xr-x  2 root root 0 2006-04-12 16:57 ram1
drwxr-xr-x  2 root root 0 2006-04-12 16:57 ram10
drwxr-xr-x  2 root root 0 2006-04-12 16:57 ram11
drwxr-xr-x  2 root root 0 2006-04-12 16:57 ram12
drwxr-xr-x  2 root root 0 2006-04-12 16:57 ram13
drwxr-xr-x  2 root root 0 2006-04-12 16:57 ram14
drwxr-xr-x  2 root root 0 2006-04-12 16:57 ram15
drwxr-xr-x  2 root root 0 2006-04-12 16:57 ram2
drwxr-xr-x  2 root root 0 2006-04-12 16:57 ram3
drwxr-xr-x  2 root root 0 2006-04-12 16:57 ram4
drwxr-xr-x  2 root root 0 2006-04-12 16:57 ram5
drwxr-xr-x  2 root root 0 2006-04-12 16:57 ram6
drwxr-xr-x  2 root root 0 2006-04-12 16:57 ram7
drwxr-xr-x  2 root root 0 2006-04-12 16:57 ram8
drwxr-xr-x  2 root root 0 2006-04-12 16:57 ram9
drwxr-xr-x  3 root root 0 2006-04-12 16:58 sr0

[root@myarch ~]# ls -l /dev/sr*
ls: /dev/sr*: No such file or directory

[root@myarch ~]# ls -l /dev/sc*
brw-rw----  1 root optical 11, 0 2006-04-12 19:08 /dev/scd0

[root@myarch ~]# ls -l /dev/sg*
crw-rw----  1 root optical 21, 0 2006-04-12 19:08 /dev/sg0

Even though the kernel shows it as a sr0 device, the /dev/sr0 is not being 
created but instead /dev/scd0 is being created.  Strange.

I tried changing the rule to
KERNEL="sr0", SYMLINK+="cdwriter"

and did a usevstart but that did not work either.

I think I have a more fundamental problem to address -- i.e why is the 
/dev/sr0 not being created.

Rob




-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x110944&bid$1720&dat\x121642
_______________________________________________
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

Re: Simple Rule Now Broken in udev089

[Kay Sievers]

On Wed, Apr 12, 2006 at 11:17:08PM +0000, Robert Kennedy wrote:
> >On Wed, Apr 12, 2006 at 09:11:43PM +0000, Robert Kennedy wrote:
> >> >On Tue, Apr 11, 2006 at 09:49:43PM +0000, Robert Kennedy wrote:
> >> >>
> >> >> For awhile I have been using the following simple rule to create a
> >> >> persistent symlink for my removable CDRW burner:
> >> >>
> >> >> KERNEL="scd0", SYMLINK="cdrwiter"
> >> >>
> >> >> I placed this rule in 10-local.rules inside the /etc/udev/rules.d/
> >> >> directory.
> >> >>
> >> >> It used to work in previous version of udev but now it does not work.
> >> >udev
> >> >> is still creating the /dev/scd0 node but not the /dev/cdwriter node.
> >> >>
> >> >> Any ideas on what might be happening.    Has anything changed in udev
> >> >089?
> >> >
> >> >No, something like this works for me. But you should always use += to
> >> >add a new symlink to the list, otherwise you reset all earlier added
> >> >ones. Maybe there is a later rule that overwrites that one?
> >> >

> >> Thanks for the tip Kay.  I tried changing the rule to:
> >>
> >> KERNEL="scd0", SYMLINK+="cdwriter"
> >>
> >> and then doing a udevstart but it did not work.  I still get a /dev/scd0
> >> node but not a /dev/cdwriter node.  Very strange.    I only have this 
> >one
> >> rule in 10-local.rules.  10-local.rules should be the first file 
> >processed
> >> in /etc/udev/rules.d/
> >
> >Are sure you have a scd* kernel device and not a sr*?
> >What does:
> >  ls -l /sys/block
> >show?

> Thanks Kay.  I think we are getting close.  See the following:
> 
> [root@myarch ~]# ls -l /sys/block
> total 0

> drwxr-xr-x  3 root root 0 2006-04-12 16:58 sr0
> 
> [root@myarch ~]# ls -l /dev/sr*
> ls: /dev/sr*: No such file or directory
> 
> [root@myarch ~]# ls -l /dev/sc*
> brw-rw----  1 root optical 11, 0 2006-04-12 19:08 /dev/scd0
> 
> [root@myarch ~]# ls -l /dev/sg*
> crw-rw----  1 root optical 21, 0 2006-04-12 19:08 /dev/sg0
> 
> Even though the kernel shows it as a sr0 device, the /dev/sr0 is not being 
> created but instead /dev/scd0 is being created.  Strange.

Maybe you have a rule like Fedora is using, which may probably
better be converted to be symlink:
  # rename sr* to scd*
  KERNEL="sr[0-9]*", BUS="scsi", NAME="scd%n"

> I tried changing the rule to
> KERNEL="sr0", SYMLINK+="cdwriter"
> 
> and did a usevstart but that did not work either.
> 
> I think I have a more fundamental problem to address -- i.e why is the 
> /dev/sr0 not being created.

Try:
  udevtest /block/sr0

Kay


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x110944&bid$1720&dat\x121642
_______________________________________________
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

Re: Simple Rule Now Broken in udev089

[Robert Kennedy]

>On Wed, Apr 12, 2006 at 11:17:08PM +0000, Robert Kennedy wrote:
> > >On Wed, Apr 12, 2006 at 09:11:43PM +0000, Robert Kennedy wrote:
> > >> >On Tue, Apr 11, 2006 at 09:49:43PM +0000, Robert Kennedy wrote:
> > >> >>
> > >> >> For awhile I have been using the following simple rule to create a
> > >> >> persistent symlink for my removable CDRW burner:
> > >> >>
> > >> >> KERNEL="scd0", SYMLINK="cdrwiter"
> > >> >>
> > >> >> I placed this rule in 10-local.rules inside the /etc/udev/rules.d/
> > >> >> directory.
> > >> >>
> > >> >> It used to work in previous version of udev but now it does not 
>work.
> > >> >udev
> > >> >> is still creating the /dev/scd0 node but not the /dev/cdwriter 
>node.
> > >> >>
> > >> >> Any ideas on what might be happening.    Has anything changed in 
>udev
> > >> >089?
> > >> >
> > >> >No, something like this works for me. But you should always use += 
>to
> > >> >add a new symlink to the list, otherwise you reset all earlier added
> > >> >ones. Maybe there is a later rule that overwrites that one?
> > >> >
>
> > >> Thanks for the tip Kay.  I tried changing the rule to:
> > >>
> > >> KERNEL="scd0", SYMLINK+="cdwriter"
> > >>
> > >> and then doing a udevstart but it did not work.  I still get a 
>/dev/scd0
> > >> node but not a /dev/cdwriter node.  Very strange.    I only have this
> > >one
> > >> rule in 10-local.rules.  10-local.rules should be the first file
> > >processed
> > >> in /etc/udev/rules.d/
> > >
> > >Are sure you have a scd* kernel device and not a sr*?
> > >What does:
> > >  ls -l /sys/block
> > >show?
>
> > Thanks Kay.  I think we are getting close.  See the following:
> >
> > [root@myarch ~]# ls -l /sys/block
> > total 0
>
> > drwxr-xr-x  3 root root 0 2006-04-12 16:58 sr0
> >
> > [root@myarch ~]# ls -l /dev/sr*
> > ls: /dev/sr*: No such file or directory
> >
> > [root@myarch ~]# ls -l /dev/sc*
> > brw-rw----  1 root optical 11, 0 2006-04-12 19:08 /dev/scd0
> >
> > [root@myarch ~]# ls -l /dev/sg*
> > crw-rw----  1 root optical 21, 0 2006-04-12 19:08 /dev/sg0
> >
> > Even though the kernel shows it as a sr0 device, the /dev/sr0 is not 
>being
> > created but instead /dev/scd0 is being created.  Strange.
>
>Maybe you have a rule like Fedora is using, which may probably
>better be converted to be symlink:
>   # rename sr* to scd*
>   KERNEL="sr[0-9]*", BUS="scsi", NAME="scd%n"
>
> > I tried changing the rule to
> > KERNEL="sr0", SYMLINK+="cdwriter"
> >
> > and did a usevstart but that did not work either.
> >
> > I think I have a more fundamental problem to address -- i.e why is the
> > /dev/sr0 not being created.
>
>Try:
>   udevtest /block/sr0
>
>Kay
>
[root@myarch ~]# udevtest /block/sr0
main: looking at device '/block/sr0' from subsystem 'block'
run_program: '/lib/udev/cdrom_id --export /dev/.tmp-11-0'
run_program: '/lib/udev/cdrom_id' (stdout) 'ID_CDROM=1'
run_program: '/lib/udev/cdrom_id' (stdout) 'ID_CDROM_CD_R=1'
run_program: '/lib/udev/cdrom_id' (stdout) 'ID_CDROM_CD_RW=1'
run_program: '/lib/udev/cdrom_id' (stdout) 'ID_CDROM_MRW=1'
run_program: '/lib/udev/cdrom_id' (stdout) 'ID_CDROM_MRW_W=1'
run_program: '/lib/udev/cdrom_id' (stdout) 'ID_CDROM_RAM=1'
run_program: '/lib/udev/cdrom_id' returned with status 0
udev_rules_get_name: add symlink 'cd/cdrom-sr0'
udev_rules_get_name: add symlink 'cd/cdrw-sr0'
udev_rules_get_name: rule applied, 'sr0' becomes 'scd0'
udev_db_get_device: no db file to read 
/dev/.udev/db/devices@pci0000:00@0000:00:07.2@usb1@1-1@1-1:1.0@host3@target3:0:0@3:0:0:0: 
No such file or directory
run_program: '/lib/udev/usb_id -x'
run_program: '/lib/udev/usb_id' (stdout) 'ID_VENDOR=Micro_Solutions'
run_program: '/lib/udev/usb_id' (stdout) 'ID_MODELºCKPACK_USB_Cable'
run_program: '/lib/udev/usb_id' (stdout) 'ID_REVISION\x0306'
run_program: '/lib/udev/usb_id' (stdout) 
'ID_SERIAL=Micro_Solutions_BACKPACK_USB_Cable_21268560'
run_program: '/lib/udev/usb_id' (stdout) 'ID_TYPEÍ'
run_program: '/lib/udev/usb_id' (stdout) 'ID_BUS=usb'
run_program: '/lib/udev/usb_id' returned with status 0
udev_rules_get_name: add symlink 
'disk/by-id/usb-Micro_Solutions_BACKPACK_USB_Cable_21268560'
run_program: '/lib/udev/path_id /block/sr0'
run_program: '/lib/udev/path_id' (stdout) 
'ID_PATH=pci-0000:00:07.2-usb-0:1:1.0-scsi-0:0:0:0'
run_program: '/lib/udev/path_id' returned with status 0
udev_rules_get_name: add symlink 
'disk/by-path/pci-0000:00:07.2-usb-0:1:1.0-scsi-0:0:0:0'
create_node: creating device node '/dev/scd0', major = '11', minor = '0', 
mode = '0660', uid = '0', gid = '93'
create_node: creating symlink '/dev/cd/cdrom-sr0' to '../scd0'
create_node: creating symlink '/dev/cd/cdrw-sr0' to '../scd0'
create_node: creating symlink 
'/dev/disk/by-id/usb-Micro_Solutions_BACKPACK_USB_Cable_21268560' to 
'../../scd0'
create_node: creating symlink 
'/dev/disk/by-path/pci-0000:00:07.2-usb-0:1:1.0-scsi-0:0:0:0' to 
'../../scd0'
main: run: 'socket:/org/freedesktop/hal/udev_event'
main: run: '/lib/udev/cdsymlinks.sh'
main: run: 'socket:/org/kernel/udev/monitor'
[root@myarch ~]#




-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x110944&bid$1720&dat\x121642
_______________________________________________
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

Re: Simple Rule Now Broken in udev089

[Kay Sievers]

On Fri, Apr 14, 2006 at 12:34:42AM +0000, Robert Kennedy wrote:
> >On Wed, Apr 12, 2006 at 11:17:08PM +0000, Robert Kennedy wrote:
> >> >On Wed, Apr 12, 2006 at 09:11:43PM +0000, Robert Kennedy wrote:
> >> >> >On Tue, Apr 11, 2006 at 09:49:43PM +0000, Robert Kennedy wrote:
> >> >> >>
> >> >> >> For awhile I have been using the following simple rule to create a
> >> >> >> persistent symlink for my removable CDRW burner:
> >> >> >>
> >> >> >> KERNEL="scd0", SYMLINK="cdrwiter"
> >> >> >>
> >> >> >> I placed this rule in 10-local.rules inside the /etc/udev/rules.d/
> >> >> >> directory.
> >> >> >>
> >> >> >> It used to work in previous version of udev but now it does not 
> >work.
> >> >> >udev
> >> >> >> is still creating the /dev/scd0 node but not the /dev/cdwriter 
> >node.
> >> >> >>
> >> >> >> Any ideas on what might be happening.    Has anything changed in 
> >udev
> >> >> >089?
> >> >> >
> >> >> >No, something like this works for me. But you should always use += 
> >to
> >> >> >add a new symlink to the list, otherwise you reset all earlier added
> >> >> >ones. Maybe there is a later rule that overwrites that one?
> >> >> >
> >
> >> >> Thanks for the tip Kay.  I tried changing the rule to:
> >> >>
> >> >> KERNEL="scd0", SYMLINK+="cdwriter"
> >> >>
> >> >> and then doing a udevstart but it did not work.  I still get a 
> >/dev/scd0
> >> >> node but not a /dev/cdwriter node.  Very strange.    I only have this
> >> >one
> >> >> rule in 10-local.rules.  10-local.rules should be the first file
> >> >processed
> >> >> in /etc/udev/rules.d/
> >> >
> >> >Are sure you have a scd* kernel device and not a sr*?
> >> >What does:
> >> >  ls -l /sys/block
> >> >show?
> >
> >> Thanks Kay.  I think we are getting close.  See the following:
> >>
> >> [root@myarch ~]# ls -l /sys/block
> >> total 0
> >
> >> drwxr-xr-x  3 root root 0 2006-04-12 16:58 sr0
> >>
> >> [root@myarch ~]# ls -l /dev/sr*
> >> ls: /dev/sr*: No such file or directory
> >>
> >> [root@myarch ~]# ls -l /dev/sc*
> >> brw-rw----  1 root optical 11, 0 2006-04-12 19:08 /dev/scd0
> >>
> >> [root@myarch ~]# ls -l /dev/sg*
> >> crw-rw----  1 root optical 21, 0 2006-04-12 19:08 /dev/sg0
> >>
> >> Even though the kernel shows it as a sr0 device, the /dev/sr0 is not 
> >being
> >> created but instead /dev/scd0 is being created.  Strange.
> >
> >Maybe you have a rule like Fedora is using, which may probably
> >better be converted to be symlink:
> >  # rename sr* to scd*
> >  KERNEL="sr[0-9]*", BUS="scsi", NAME="scd%n"
> >
> >> I tried changing the rule to
> >> KERNEL="sr0", SYMLINK+="cdwriter"
> >>
> >> and did a usevstart but that did not work either.
> >>
> >> I think I have a more fundamental problem to address -- i.e why is the
> >> /dev/sr0 not being created.
> >
> >Try:
> >  udevtest /block/sr0
> >
> >Kay
> >
> [root@myarch ~]# udevtest /block/sr0

> udev_rules_get_name: rule applied, 'sr0' becomes 'scd0'

You have a rule somewhere to rename the default kernel name
to scd*, that's why sr* never gets created.

Kay


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x110944&bid$1720&dat\x121642
_______________________________________________
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

Re: Simple Rule Now Broken in udev089

[Robert Kennedy]

>On Fri, Apr 14, 2006 at 12:34:42AM +0000, Robert Kennedy wrote:
> > >On Wed, Apr 12, 2006 at 11:17:08PM +0000, Robert Kennedy wrote:
> > >> >On Wed, Apr 12, 2006 at 09:11:43PM +0000, Robert Kennedy wrote:
> > >> >> >On Tue, Apr 11, 2006 at 09:49:43PM +0000, Robert Kennedy wrote:
> > >> >> >>
> > >> >> >> For awhile I have been using the following simple rule to 
>create a
> > >> >> >> persistent symlink for my removable CDRW burner:
> > >> >> >>
> > >> >> >> KERNEL="scd0", SYMLINK="cdrwiter"
> > >> >> >>
> > >> >> >> I placed this rule in 10-local.rules inside the 
>/etc/udev/rules.d/
> > >> >> >> directory.
> > >> >> >>
> > >> >> >> It used to work in previous version of udev but now it does not
> > >work.
> > >> >> >udev
> > >> >> >> is still creating the /dev/scd0 node but not the /dev/cdwriter
> > >node.
> > >> >> >>
> > >> >> >> Any ideas on what might be happening.    Has anything changed 
>in
> > >udev
> > >> >> >089?
> > >> >> >
> > >> >> >No, something like this works for me. But you should always use 
>+> > >to
> > >> >> >add a new symlink to the list, otherwise you reset all earlier 
>added
> > >> >> >ones. Maybe there is a later rule that overwrites that one?
> > >> >> >
> > >
> > >> >> Thanks for the tip Kay.  I tried changing the rule to:
> > >> >>
> > >> >> KERNEL="scd0", SYMLINK+="cdwriter"
> > >> >>
> > >> >> and then doing a udevstart but it did not work.  I still get a
> > >/dev/scd0
> > >> >> node but not a /dev/cdwriter node.  Very strange.    I only have 
>this
> > >> >one
> > >> >> rule in 10-local.rules.  10-local.rules should be the first file
> > >> >processed
> > >> >> in /etc/udev/rules.d/
> > >> >
> > >> >Are sure you have a scd* kernel device and not a sr*?
> > >> >What does:
> > >> >  ls -l /sys/block
> > >> >show?
> > >
> > >> Thanks Kay.  I think we are getting close.  See the following:
> > >>
> > >> [root@myarch ~]# ls -l /sys/block
> > >> total 0
> > >
> > >> drwxr-xr-x  3 root root 0 2006-04-12 16:58 sr0
> > >>
> > >> [root@myarch ~]# ls -l /dev/sr*
> > >> ls: /dev/sr*: No such file or directory
> > >>
> > >> [root@myarch ~]# ls -l /dev/sc*
> > >> brw-rw----  1 root optical 11, 0 2006-04-12 19:08 /dev/scd0
> > >>
> > >> [root@myarch ~]# ls -l /dev/sg*
> > >> crw-rw----  1 root optical 21, 0 2006-04-12 19:08 /dev/sg0
> > >>
> > >> Even though the kernel shows it as a sr0 device, the /dev/sr0 is not
> > >being
> > >> created but instead /dev/scd0 is being created.  Strange.
> > >
> > >Maybe you have a rule like Fedora is using, which may probably
> > >better be converted to be symlink:
> > >  # rename sr* to scd*
> > >  KERNEL="sr[0-9]*", BUS="scsi", NAME="scd%n"
> > >
> > >> I tried changing the rule to
> > >> KERNEL="sr0", SYMLINK+="cdwriter"
> > >>
> > >> and did a usevstart but that did not work either.
> > >>
> > >> I think I have a more fundamental problem to address -- i.e why is 
>the
> > >> /dev/sr0 not being created.
> > >
> > >Try:
> > >  udevtest /block/sr0
> > >
> > >Kay
> > >
> > [root@myarch ~]# udevtest /block/sr0
>
> > udev_rules_get_name: rule applied, 'sr0' becomes 'scd0'
>
>You have a rule somewhere to rename the default kernel name
>to scd*, that's why sr* never gets created.
>
>Kay
>
Thanks Kay.  I changed the rule that changed the kernel name from sr0 to 
scd0.  Instead, I just created a symlink /dev/scd0 to /dev/sr0.  In other 
words, I changed the following rule:

BUS="scsi", KERNEL="sr[0-9]*", SYSFS{type}="5", NAME="scd%n", 
GROUP="optical"
to:
BUS="scsi", KERNEL="sr[0-9]*", SYSFS{type}="5", SYMLINK+="scd%n", 
GROUP="optical"

Since the rule no longer changes the kernel name, I had to change my simple 
rule in 10-local.rules as follows:

KERNEL="sr0", SYMLINK+="cdwriter"

Now, I get a /dev/cdwriter symlink!

I find it very strange that with the old original rule that changed the 
kernel name to scd0,  I could not use KERNEL="scd0" in my simple rule. You 
would think that when you changed the KERNEL name from sr0 to scd0, you 
could use the new kernel name in my simple rule.

Rob




-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x110944&bid$1720&dat\x121642
_______________________________________________
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

Re: Simple Rule Now Broken in udev089

[Scott James Remnant]

[-- Attachment #1: Type: text/plain, Size: 617 bytes --]

On Sat, 2006-04-15 at 19:15 +0000, Robert Kennedy wrote:

> I find it very strange that with the old original rule that changed the 
> kernel name to scd0,  I could not use KERNEL=="scd0" in my simple rule. You 
> would think that when you changed the KERNEL name from sr0 to scd0, you 
> could use the new kernel name in my simple rule.
> 
You're not changing the KERNEL name, you're changing the name of the
device node.

It'd also mean every time you use a NAME rule, you had to go and fix
every other rule for that device, which would be annoying.

Scott
-- 
Scott James Remnant
scott@ubuntu.com

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 191 bytes --]