[prev in list] [next in list] [prev in thread] [next in thread] 

List:       fwts-devel
Subject:    [PATCH] Update README
From:       Colin King <colin.king () canonical ! com>
Date:       2012-05-31 17:22:18
Message-ID: 1338484938-6977-1-git-send-email-colin.king () canonical ! com
[Download RAW message or body]

From: Colin Ian King <colin.king@canonical.com>

Signed-off-by: Colin Ian King <colin.king@canonical.com>
---
 README |   23 +----------------------
 1 file changed, 1 insertion(+), 22 deletions(-)

diff --git a/README b/README
index a9abbcd..c6a6ba0 100644
--- a/README
+++ b/README
@@ -18,9 +18,6 @@ sudo apt-get install iasl acpidump pciutils dmidecode
 make
 sudo make install
 
-I hope to get this into a PPA once I've got the code into a more
-stable form.
-
 To get help:
 
 fwts --help
@@ -203,28 +200,10 @@ look at the results log, e.g.
 
 sudo fwts mtrr --stdout-summary
 
-One can override the text using the following environment variables:
-
-BIOS_TEST_TOOLKIT_PASSED_TEXT
-BIOS_TEST_TOOLKIT_FAILED_TEXT
-
-e.g.
-
-sudo BIOS_TEST_TOOLKIT_PASSED_TEXT="yay" fwts mtrr --stdout-summary
-yay
-
-Finally, the exit code returns 1 for test failure and 0 for test success, so the
+The exit code returns 1 for test failure and 0 for test success, so the
 test suite can be run from a shell script and one can detect if the test worked or not, e.g.
 
 #!/bin/bash
 LOG=stdout
 sudo fwts dmi_decode --results-output=$LOG
 failed=$?
-
-Misc
-====
-
-Debug mode.. shows what the controlling test suite framework is doing. It's for
-the developer only!
-
-fwts --fwts-debug
-- 
1.7.9.5



[prev in list] [next in list] [prev in thread] [next in thread]