User:Gordon/Optical Drive Testing Script/scratchpad

• http://club.myce.com/f34/dvd-rw-multisession-questions-306321/
• http://club.myce.com/f33/best-media-optical-drive-testing-306320/
• http://club.myce.com/f52/uniquely-iding-optical-discs-306323/
• http://fy.chalmers.se/~appro/linux/DVD+RW/
• http://club.myce.com/f52/determine-dvd-r-write-capability-ubuntu-306981/ not much luck yet
• http://ubuntuforums.org/showthread.php?t=1240043 -- maybe use 'hal' to determine dvd+r info?
• http://dannipenguin.livejournal.com/206645.html -- python hal+dbus example
• http://ubuntuforums.org/showthread.php?p=8928791 -- genisoimage "Short read on old image" error

Dependencies

Ubuntu

• python-setuptools (?)
• python-virtualenv
• python-pip
• python-dbus (this won't install to a virtualenv based on 10 min of trying, so no-site-packages shouldn't be used when creating the virtualenv for lazers)
• python-openssl (probably, for fast pseudorandom number generator, faster than urandom)
• mercurial (won't be needed for a dpkg dependency, most likely)
• hal (probably -- it probably has to be there to talk to via python-dbus)
• cdrkit (probably) or cdrtools
  • cdrtools is not included in Debian and Ubuntu due to licensing disputes
  • however, it has bugfixes which the Debian fork, cdrkit, does not
  • see here for cdrtools installation details
• dvd+rw-tools (probably)

Python

(Hopefully) see pip-requirements.txt once the project is closer to completion, and automatically install all these with pip.

• cmdln
• nose (for testing)
  • examples

Development installation

1. Install all Ubuntu dependencies
2. cd to the dir where you want the virtualenv containing the code to live.
3. virtualenv lazers (I would prefer to use --no-site-packages but python-dbus/dbus-python doesn't play nice)
4. cd lazers
5. . bin/activate
6. pip install -E . yolk (optional, but useful)
7. pip install -E . cmdln
8. pip install -E . nose (if you want to run the tests)
9. mkdir src
10. cd src
11. hg clone http://bitbucket.org/gmfreegeek/lazers/

Optical drive examination procedure

1. Given a block device (defaults to /dev/sr0), query HAL via DBus to see if we can get a HAL UDI for a device with capability storage.cdrom and a property block.device that corresponds.
2. Query HAL about the drive's capabilities and store them.
3. Query wodim -- probably by scraping stdout of wodim dev=/dev/sr0 -prcap about the drive's capabilities and store those as well. Does NOT detect DVD+R capability.
4. Find any mismatches and decide whether to alert the user (???)

Scratchpad for command line hal...

1. hal-find-by-capability --capability storage.cdrom to get a udi
2. lshal -u [udi] reveals the drive's capabilities one by one, including plusr, dvdram, etc. Dunno about lightscribe.