#1972: udevtest semi-broken
---------------------------+------------------------------------------------
 Reporter:  Bryan Kadzban  |        Owner:  [email protected]
     Type:  task           |       Status:  new                          
 Priority:  normal         |    Milestone:  6.3                          
Component:  Book           |      Version:  SVN                          
 Severity:  normal         |   Resolution:                               
 Keywords:                 |  
---------------------------+------------------------------------------------
Comment (by Bryan Kadzban):

 Firewire:  Never used it myself, but according to
 http://www.linux1394.org/faq.php#sbp2, it shows up as SCSI, since "All of
 these devices comply with a standard called SBP-2 (Serial Bus Protocol-2).
 They are accessed like SCSI devices in Linux since the sbp2 driver is a
 low-level SCSI provider."  However, that page is talking a lot about
 kernel 2.4, too, so I have a feeling it may be out of date.  I'd still
 assume SCSI though, at least for the moment.

 cdrom_id: No, it's not immediately useful when looking for which values
 will be used to ID the device.  But it does tell the user which symlink
 "base" names will be used for the symlinks.  Here's the mapping, from
 udev-105's write_cd_rules script:

 {{{
 ID_CDROM:                 /dev/cdromX
 ID_CDROM_{R,RW}:          /dev/cdrwX
 ID_CDROM_DVD:             /dev/dvdX
 ID_CDROM_DVD_{R,RW,RAM}:  /dev/dvdrwX
 }}}

 (Where "X" means "empty string for the first CD-type device, and
 1/2/3/4/etc. for subsequent CD-type devices".)  I'm not sure how to mark
 this up into a table in the book (or whether it's even useful information
 to give the user), though.

-- 
Ticket URL: <http://wiki.linuxfromscratch.org/lfs/ticket/1972#comment:3>
LFS Trac <http://wiki.linuxfromscratch.org/lfs/>
Linux From Scratch: Your Distro, Your Rules.
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-book
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Reply via email to