burning tests/ideas mailed by Thomas

This commit is contained in:
George Danchev 2011-07-04 17:43:15 +00:00
parent 95ab0b811e
commit 321d9ae044
1 changed files with 10 additions and 0 deletions

View File

@ -15,3 +15,13 @@
* We need to give a hint about how much storage space will be consumed.
* We could mark all own stderr messages by a prefix like "===".
* Burning tests ideas/thoughts by Thomas:
> There will have to be a warning and user input before we load
> the drive tray. -dev, -indev, -oudev do this loading which can
> cause finger injury, psychical trauma, and chuting computers.
>
> Further if we want to have a burn test (with MD5 and checkreading)
> then we will need configuration means to enable this. By default
> it should not risk to burn one-time media which sit in the drive
> by mere accident.