Questions concerning udev and removeable media, dvd and links

Questions concerning udev and removeable media, dvd and links

[Norbert Preining]

Hi dear hotplug developers!

I have several removeable disks (SD card reader, CF card reader, etc),
but udev/hotplug only generates the base device file name (/dev/sda etc)
and *not* the partition device nodes (/dev/sda1) because at boot time
the partition table is not available.

Now, having /dev/sda1 for /mnt/sd in /etc/fstab will not work.

Thus, is it possible to do some changes that the partition devnodes are
*always* also created for these kinds of disks, or all?

------------

Next question: The /dev/dvd link:
I have two CDROMS: The first, hdc, is a DVD, the second, hdd, is a
plextor cd writer.

Now interestingly I get
	/dev/cdrom -> hdd
and *no*
	/dev/dvd
This is strange because what I see in /etc/udev/cdsymlinks.sh looks like
a dvd node *should* be created.

-----------

Last question: What is the suggested place to add links I want to have?

I would like to have a link
	/dev/pilot -> /dev/ttyUSB1
ttyUSB1 is only generated when I press the HotSync button on the palm,
but I want /dev/pilot to point to it. 

Where should I configure this.

----------------------------

Finally, some info:
debian/sid uptodate
kernel-2.6.7-mm3

Thanks a lot and all the best

Norbert

-------------------------------------------------------------------------------
Norbert Preining <preining AT logic DOT at>         Technische Universität Wien
gpg DSA: 0x09C5B094      fp: 14DF 2E6C 0307 BE6D AD76  A9C0 D2BF 4AA3 09C5 B094
-------------------------------------------------------------------------------
DREBLEY (n.)
Name for a shop which is supposed to be witty but is in fact
wearisome, e.g. 'The Frock Exchange', 'Hair Apparent', etc.
			--- Douglas Adams, The Meaning of Liff


-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
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: Questions concerning udev and removeable media, dvd and links

[Greg KH]

On Tue, Jun 29, 2004 at 08:01:22AM +0200, Norbert Preining wrote:
> Hi dear hotplug developers!
> 
> I have several removeable disks (SD card reader, CF card reader, etc),
> but udev/hotplug only generates the base device file name (/dev/sda etc)
> and *not* the partition device nodes (/dev/sda1) because at boot time
> the partition table is not available.
> 
> Now, having /dev/sda1 for /mnt/sd in /etc/fstab will not work.
> 
> Thus, is it possible to do some changes that the partition devnodes are
> *always* also created for these kinds of disks, or all?

Yes, look at the section in the udev manpage that talks about
NAME{all_partitions}.

> ------------
> 
> Next question: The /dev/dvd link:
> I have two CDROMS: The first, hdc, is a DVD, the second, hdd, is a
> plextor cd writer.
> 
> Now interestingly I get
> 	/dev/cdrom -> hdd
> and *no*
> 	/dev/dvd
> This is strange because what I see in /etc/udev/cdsymlinks.sh looks like
> a dvd node *should* be created.

What distro are you using that added such a .sh file?  I don't see it in
the main udev release.

> 
> -----------
> 
> Last question: What is the suggested place to add links I want to have?
> 
> I would like to have a link
> 	/dev/pilot -> /dev/ttyUSB1
> ttyUSB1 is only generated when I press the HotSync button on the palm,
> but I want /dev/pilot to point to it. 
> 
> Where should I configure this.

Add a symlink for ttyUSB1 with a rule like:
	KERNEL="ttyUSB1", SYMLINK="pilot"


> ----------------------------
> 
> Finally, some info:
> debian/sid uptodate

Ah, go bug the debian maintainer of the udev package about that
cdsymlinks.sh script :)

hope this helps,

greg k-h


-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
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: Questions concerning udev and removeable media, dvd and links

[Norbert Preining]

Hi Greg!

Thanks for the hints:

On Mon, 28 Jun 2004, Greg KH wrote:
> > Thus, is it possible to do some changes that the partition devnodes are
> > *always* also created for these kinds of disks, or all?
> 
> Yes, look at the section in the udev manpage that talks about
> NAME{all_partitions}.

I have added the following to /etc/udev/rules.d/local.rules:
BUS="scsi", SYSFS{model}="HS-CF", NAME{all_partitions}="sda"
BUS="scsi", SYSFS{model}="HS-MS", NAME{all_partitions}="sdb"
BUS="scsi", SYSFS{model}="HS-SM", NAME{all_partitions}="sdc"
BUS="scsi", SYSFS{model}="HS-SD/MMC", NAME{all_partitions}="sdd"

But restarting udev didn't create the partitions:
udev[7998]: creating device node '/dev/sdd'
udev[8000]: creating device node '/dev/sdc'
udev[8002]: creating device node '/dev/sdb'
udev[8004]: creating device node '/dev/sda'
udev[8006]: configured rule in '/etc/udev/rules.d/udev.rules' at line 19 applied, 'hdd' becomes '%k'
...

> > This is strange because what I see in /etc/udev/cdsymlinks.sh looks like
> > a dvd node *should* be created.
> 
> Ah, go bug the debian maintainer of the udev package about that
> cdsymlinks.sh script :)

Will do.

> > Where should I configure this.
> 
> Add a symlink for ttyUSB1 with a rule like:
> 	KERNEL="ttyUSB1", SYMLINK="pilot"

ok, thanks.
BUT: Is it will create it *in advance* so that pilot-xfer etc do not
bomb out because device is not existent!

Best wishes

Norbert

-------------------------------------------------------------------------------
Norbert Preining <preining AT logic DOT at>         Technische Universität Wien
gpg DSA: 0x09C5B094      fp: 14DF 2E6C 0307 BE6D AD76  A9C0 D2BF 4AA3 09C5 B094
-------------------------------------------------------------------------------
ARDSCULL (n.)
Excuse made by rural Welsh hairdresser for deep wounds inflicted on
your scalp in an attempt to rectify whatever it was that induced the
ardscalpsie (q.v.).
			--- Douglas Adams, The Meaning of Liff


-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
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: Questions concerning udev and removeable media, dvd and links

[Greg KH]

On Tue, Jun 29, 2004 at 08:50:52AM +0200, Norbert Preining wrote:
> Hi Greg!
> 
> Thanks for the hints:
> 
> On Mon, 28 Jun 2004, Greg KH wrote:
> > > Thus, is it possible to do some changes that the partition devnodes are
> > > *always* also created for these kinds of disks, or all?
> > 
> > Yes, look at the section in the udev manpage that talks about
> > NAME{all_partitions}.
> 
> I have added the following to /etc/udev/rules.d/local.rules:

Why "local.rules"?  Try "00-local.rules" instead to make sure that file
is read first.

Anyway, it looks like your rules are not matching the device properly,
because of:

> BUS="scsi", SYSFS{model}="HS-CF", NAME{all_partitions}="sda"
> BUS="scsi", SYSFS{model}="HS-MS", NAME{all_partitions}="sdb"
> BUS="scsi", SYSFS{model}="HS-SM", NAME{all_partitions}="sdc"
> BUS="scsi", SYSFS{model}="HS-SD/MMC", NAME{all_partitions}="sdd"
> 
> But restarting udev didn't create the partitions:
> udev[7998]: creating device node '/dev/sdd'
> udev[8000]: creating device node '/dev/sdc'
> udev[8002]: creating device node '/dev/sdb'
> udev[8004]: creating device node '/dev/sda'
> udev[8006]: configured rule in '/etc/udev/rules.d/udev.rules' at line 19 applied, 'hdd' becomes '%k'

No mention of using the local.rules file :(

Are you sure the sda device has a SYSFS{model}="HS-CF" field?
What does:
	 udevinfo -p /sys/block/sda -a
show?	

> > > Where should I configure this.
> > 
> > Add a symlink for ttyUSB1 with a rule like:
> > 	KERNEL="ttyUSB1", SYMLINK="pilot"
> 
> ok, thanks.
> BUT: Is it will create it *in advance* so that pilot-xfer etc do not
> bomb out because device is not existent!

pilot-xfer knows better than to die these days.  Anyway, creating a link
that points to a device node that isn't there isn't going to help
pilot-xfer out any.  This is just the way the hardware works for pilot
devices, sorry.

greg k-h


-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
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: Questions concerning udev and removeable media, dvd and links

[Norbert Preining]

Hi Greg!

On Die, 29 Jun 2004, Greg KH wrote:
> > I have added the following to /etc/udev/rules.d/local.rules:
> 
> Why "local.rules"?  Try "00-local.rules" instead to make sure that file
> is read first.

Ok, done.

> > BUS="scsi", SYSFS{model}="HS-CF", NAME{all_partitions}="sda"
> 
> Are you sure the sda device has a SYSFS{model}="HS-CF" field?
> What does:
> 	 udevinfo -p /sys/block/sda -a
> show?	

Yup, its not:
    SYSFS{model}="      HS-CF"

What is the best way to specify such devices: (For the full output see
attached file)
    BUS="scsi"
    ID="0:0:0:0"
    SYSFS{detach_state}="0"
    SYSFS{device_blocked}="0"
    SYSFS{max_sectors}="240"
    SYSFS{model}="      HS-CF"
    SYSFS{queue_depth}="1"
    SYSFS{rev}="1.64"
    SYSFS{scsi_level}="3"
    SYSFS{state}="running"
    SYSFS{timeout}="30"
    SYSFS{type}="0"
    SYSFS{vendor}="USB2.0  "

> pilot-xfer knows better than to die these days.  Anyway, creating a link

Ok, thanks.

Best wishes

Norbert

-------------------------------------------------------------------------------
Norbert Preining <preining AT logic DOT at>         Technische Universität Wien
gpg DSA: 0x09C5B094      fp: 14DF 2E6C 0307 BE6D AD76  A9C0 D2BF 4AA3 09C5 B094
-------------------------------------------------------------------------------
LOSSIEMOUTH (n.)
One of those middle-aged ladies with just a hint of a luxuriant
handlebar moustache.
			--- Douglas Adams, The Meaning of Liff


-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
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: Questions concerning udev and removeable media, dvd and links

[Norbert Preining]

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

On Die, 29 Jun 2004, preining wrote:
> What is the best way to specify such devices: (For the full output see
> attached file)

Here it is.

Best wishes

Norbert

-------------------------------------------------------------------------------
Norbert Preining <preining AT logic DOT at>         Technische Universität Wien
gpg DSA: 0x09C5B094      fp: 14DF 2E6C 0307 BE6D AD76  A9C0 D2BF 4AA3 09C5 B094
-------------------------------------------------------------------------------
GLEMENUILT (n.)
The kind of guilt which you'd completely forgotten about which comes
roaring back on discovering an old letter in a cupboard.
			--- Douglas Adams, The Meaning of Liff

[-- Attachment #2: sda.txt --]
[-- Type: text/plain, Size: 3352 bytes --]


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 together in one rule,
to match the device for which the node will be created.

  looking at class device '/sys/block/sda':
    SYSFS{dev}="8:0"
    SYSFS{range}="16"
    SYSFS{size}="0"
    SYSFS{stat}="       0        0        0        0        0        0        0        0        0        0        0"

follow the class device's "device"
  looking at the device chain at '/sys/devices/pci0000:00/0000:00:07.3/usb2/2-1/2-1:1.0/host0/0:0:0:0':
    BUS="scsi"
    ID="0:0:0:0"
    SYSFS{detach_state}="0"
    SYSFS{device_blocked}="0"
    SYSFS{max_sectors}="240"
    SYSFS{model}="      HS-CF"
    SYSFS{queue_depth}="1"
    SYSFS{rev}="1.64"
    SYSFS{scsi_level}="3"
    SYSFS{state}="running"
    SYSFS{timeout}="30"
    SYSFS{type}="0"
    SYSFS{vendor}="USB2.0  "

  looking at the device chain at '/sys/devices/pci0000:00/0000:00:07.3/usb2/2-1/2-1:1.0/host0':
    BUS=""
    ID="host0"
    SYSFS{detach_state}="0"

  looking at the device chain at '/sys/devices/pci0000:00/0000:00:07.3/usb2/2-1/2-1:1.0':
    BUS="usb"
    ID="2-1:1.0"
    SYSFS{bAlternateSetting}=" 0"
    SYSFS{bInterfaceClass}="08"
    SYSFS{bInterfaceNumber}="00"
    SYSFS{bInterfaceProtocol}="50"
    SYSFS{bInterfaceSubClass}="06"
    SYSFS{bNumEndpoints}="02"
    SYSFS{detach_state}="0"
    SYSFS{iInterface}="00"

  looking at the device chain at '/sys/devices/pci0000:00/0000:00:07.3/usb2/2-1':
    BUS="usb"
    ID="2-1"
    SYSFS{bConfigurationValue}="1"
    SYSFS{bDeviceClass}="00"
    SYSFS{bDeviceProtocol}="00"
    SYSFS{bDeviceSubClass}="00"
    SYSFS{bMaxPower}=" 96mA"
    SYSFS{bNumConfigurations}="1"
    SYSFS{bNumInterfaces}=" 1"
    SYSFS{bcdDevice}="0164"
    SYSFS{bmAttributes}="80"
    SYSFS{detach_state}="0"
    SYSFS{devnum}="2"
    SYSFS{idProduct}="0500"
    SYSFS{idVendor}="10df"
    SYSFS{manufacturer}="USB2.0"
    SYSFS{maxchild}="0"
    SYSFS{product}="     "
    SYSFS{serial}="0440000020FB"
    SYSFS{speed}="12"
    SYSFS{version}=" 2.00"

  looking at the device chain at '/sys/devices/pci0000:00/0000:00:07.3/usb2':
    BUS="usb"
    ID="usb2"
    SYSFS{bConfigurationValue}="1"
    SYSFS{bDeviceClass}="09"
    SYSFS{bDeviceProtocol}="00"
    SYSFS{bDeviceSubClass}="00"
    SYSFS{bMaxPower}="  0mA"
    SYSFS{bNumConfigurations}="1"
    SYSFS{bNumInterfaces}=" 1"
    SYSFS{bcdDevice}="0206"
    SYSFS{bmAttributes}="c0"
    SYSFS{detach_state}="0"
    SYSFS{devnum}="1"
    SYSFS{idProduct}="0000"
    SYSFS{idVendor}="0000"
    SYSFS{manufacturer}="Linux 2.6.7-mm3 uhci_hcd"
    SYSFS{maxchild}="2"
    SYSFS{product}="VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (#2)"
    SYSFS{serial}="0000:00:07.3"
    SYSFS{speed}="12"
    SYSFS{version}=" 1.10"

  looking at the device chain at '/sys/devices/pci0000:00/0000:00:07.3':
    BUS="pci"
    ID="0000:00:07.3"
    SYSFS{class}="0x0c0300"
    SYSFS{detach_state}="0"
    SYSFS{device}="0x3038"
    SYSFS{irq}="12"
    SYSFS{subsystem_device}="0x1234"
    SYSFS{subsystem_vendor}="0x0925"
    SYSFS{vendor}="0x1106"

  looking at the device chain at '/sys/devices/pci0000:00':
    BUS=""
    ID="pci0000:00"
    SYSFS{detach_state}="0"

Re: Questions concerning udev and removeable media, dvd and links

[Greg KH]

On Tue, Jun 29, 2004 at 09:22:02AM +0200, Norbert Preining wrote:
> Hi Greg!
> 
> On Die, 29 Jun 2004, Greg KH wrote:
> > > I have added the following to /etc/udev/rules.d/local.rules:
> > 
> > Why "local.rules"?  Try "00-local.rules" instead to make sure that file
> > is read first.
> 
> Ok, done.
> 
> > > BUS="scsi", SYSFS{model}="HS-CF", NAME{all_partitions}="sda"
> > 
> > Are you sure the sda device has a SYSFS{model}="HS-CF" field?
> > What does:
> > 	 udevinfo -p /sys/block/sda -a
> > show?	
> 
> Yup, its not:
>     SYSFS{model}="      HS-CF"
> 
> What is the best way to specify such devices: (For the full output see
> attached file)

Try just adding those spaces in.  That should work, right?

I've never seen spaces at the front of the string, only at the end.
{sigh}  when will firmware engineers get sane...

thanks,

greg k-h


-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
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: Questions concerning udev and removeable media, dvd and links

[Norbert Preining]

Hi Greg!

On Die, 29 Jun 2004, Greg KH wrote:
> > Yup, its not:
> >     SYSFS{model}="      HS-CF"
> > 
> > What is the best way to specify such devices: (For the full output see
> > attached file)
> 
> Try just adding those spaces in.  That should work, right?

Yes, that did work. I already tried it.

> I've never seen spaces at the front of the string, only at the end.
> {sigh}  when will firmware engineers get sane...

;-)

Many thanks and all the best

Norbert

-------------------------------------------------------------------------------
Norbert Preining <preining AT logic DOT at>         Technische Universität Wien
gpg DSA: 0x09C5B094      fp: 14DF 2E6C 0307 BE6D AD76  A9C0 D2BF 4AA3 09C5 B094
-------------------------------------------------------------------------------
DUDOO (n.)
The most deformed potato in any given collection of potatoes.
			--- Douglas Adams, The Meaning of Liff


-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
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: Questions concerning udev and removeable media, dvd and links

[Harald Hoyer]

Greg KH wrote:
> On Tue, Jun 29, 2004 at 08:01:22AM +0200, Norbert Preining wrote:
>>
>>Last question: What is the suggested place to add links I want to have?
>>
>>I would like to have a link
>>	/dev/pilot -> /dev/ttyUSB1
>>ttyUSB1 is only generated when I press the HotSync button on the palm,
>>but I want /dev/pilot to point to it. 
>>
>>Where should I configure this.
> 
> 
> Add a symlink for ttyUSB1 with a rule like:
> 	KERNEL="ttyUSB1", SYMLINK="pilot"
> 

It's not ttyUSB1 all the time, isn't it?? Any better matching rule for this?


-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
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: Questions concerning udev and removeable media, dvd and links

[Greg KH]

On Wed, Sep 29, 2004 at 12:17:15PM +0200, Harald Hoyer wrote:
> Greg KH wrote:
> >On Tue, Jun 29, 2004 at 08:01:22AM +0200, Norbert Preining wrote:
> >>
> >>Last question: What is the suggested place to add links I want to have?
> >>
> >>I would like to have a link
> >>	/dev/pilot -> /dev/ttyUSB1
> >>ttyUSB1 is only generated when I press the HotSync button on the palm,
> >>but I want /dev/pilot to point to it. 
> >>
> >>Where should I configure this.
> >
> >
> >Add a symlink for ttyUSB1 with a rule like:
> >	KERNEL="ttyUSB1", SYMLINK="pilot"
> >
> 
> It's not ttyUSB1 all the time, isn't it?? Any better matching rule for this?

It all depends on the type of device, and if you have any other usb to
serial devices in the system at the same time.

So, for visor devices, you can go by their usb id, or usb product
string, but you need the second instance, but for some sony devices you
need to use the first port.

So writing a set of rules for all devices would be possible, but pretty
complex :(  I say stick with the default name for now, and any user can
add a symlink rule once they determine the type of device they have.

thanks,

greg k-h


-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
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