From 9e8d5151979040c331f45b9d2cd443a59ca297e4 Mon Sep 17 00:00:00 2001
From: Peter Jones <pjones@redhat.com>
Date: Fri, 14 Feb 2014 14:44:31 -0500
Subject: [PATCH 2/4] Fix a part of the test plan that was out of order.
Signed-off-by: Peter Jones <pjones@redhat.com>
---
testplan.txt | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/testplan.txt b/testplan.txt
index 118dfcd..96aa364 100644
--- a/testplan.txt
+++ b/testplan.txt
@@ -25,10 +25,10 @@ How to test a new shim build for RHEL/fedora:
9) copy grub.cfg to our test directory:
cp /boot/efi/EFI/redhat/grub.cfg /boot/efi/EFI/test/grub.cfg
10) *move* \EFI\redhat\BOOT.CSV to \EFI\test
- mv /boot/efi/EFI/redhat/BOOT.CSV /boot/efi/EFI/test/BOOT.CSV
-11) sign a copy of fallback.efi and put it in \EFI\BOOT\fallback.efi
rm -rf /boot/efi/EFI/BOOT/
mkdir /boot/efi/EFI/BOOT/
+ mv /boot/efi/EFI/redhat/BOOT.CSV /boot/efi/EFI/test/BOOT.CSV
+11) sign a copy of fallback.efi and put it in \EFI\BOOT\fallback.efi
pesign -i /usr/share/shim/fallback.efi \
-o /boot/efi/EFI/BOOT/fallback.efi \
-s -c "Red Hat Test Certificate"
@@ -55,7 +55,7 @@ How to test a new shim build for RHEL/fedora:
If you get the expected result, shim can run things signed by its internal
key ring. Check a box someplace that says it can do that.
23) from the EFI shell, copy grub to grubx64.efi:
- cp \EFI\test\grubx.efi \EFI\test\grubx64.efi
+ cp \EFI\test\grub.efi \EFI\test\grubx64.efi
24) in the EFI shell, run fs0:\EFI\test\shim.efi
result: this should start grub, which will let you boot a kernel
If grub starts, it means shim can run things signed by a key in the system's
--
1.8.5.3