2011-06-28 17:33:08 +00:00
|
|
|
|
2011-07-09 07:33:33 +00:00
|
|
|
* Expose xorriso --version of tested binary just once.
|
2011-07-07 09:42:01 +00:00
|
|
|
|
2011-07-02 18:00:33 +00:00
|
|
|
* Merge 'merge_into_isocontent' into 'releng_isocontent' (former hardlinks)
|
2011-07-02 15:28:37 +00:00
|
|
|
Extend it to use some more demanding directory tree.
|
|
|
|
|
MD5s should be checked. ACLs and xattr (if we are on Linux).
|
|
|
|
|
All file types as of stat(2) should be tested.
|
2011-07-07 07:56:44 +00:00
|
|
|
|
2011-07-09 07:33:33 +00:00
|
|
|
* Also check as many as possible trivial operations like:
|
|
|
|
|
xorriso --devices
|
|
|
|
|
xorriso -indev file.iso -pvd_info
|
2011-07-02 15:28:37 +00:00
|
|
|
|
2011-07-07 07:56:44 +00:00
|
|
|
* We could mark all own stderr messages by a prefix like "===".
|
2011-07-04 17:43:15 +00:00
|
|
|
|
|
|
|
|
* 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.
|
