From 3dfaae40e8b8a2453d92622192a3d8c1d561b391 Mon Sep 17 00:00:00 2001 From: George Danchev Date: Mon, 4 Jul 2011 17:43:15 +0000 Subject: [PATCH] burning tests/ideas mailed by Thomas --- libisoburn/trunk/releng/TODO | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/libisoburn/trunk/releng/TODO b/libisoburn/trunk/releng/TODO index 129e7290..8a037684 100644 --- a/libisoburn/trunk/releng/TODO +++ b/libisoburn/trunk/releng/TODO @@ -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.