Skip to contentSkip to conversation

Documentation/efi-stub.txt: Fix a typo

PATCH In review Joonas Lahtinen 2 participants 3 messages Oct 21, 2015 – Oct 23, 2015 2 messages not in the archive

Subsystems (2)
lore
Share & tools
lore
#0 lore raw

PATCH 1/1 Documentation/efi-stub.txt: Fix a typo

In the command invocation "initrd=\Kernels\..." should really read "initrd=\Ramdisks\..." instead.

---
 Documentation/efi-stub.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
Documentation/efi-stub.txt +1 -1
index 7747024..e1ee764 100644
@@ -68,7 +68,7 @@ fs0:>
 to boot with the initrd-large.img file if the current working
 directory is fs0:\Kernels, the following command must be used,
 
-	fs0:\Kernels> bzImage.efi initrd=\Kernels\initrd-large.img
+	fs0:\Kernels> bzImage.efi initrd=\Ramdisks\initrd-large.img
 
 Notice how bzImage.efi can be specified with a relative path. That's
 because the image we're executing is interpreted by the EFI shell,
Signature · 1 line
2.4.3

A message that is not in the archive (sent off-list or not yet received): 1445430404-1908-1-git-send-email-joonas.lahtinen-VuQAYsv1563Yd54FQh9/[email protected]

#2 lore raw
Quoted 13 lines · Joonas Lahtinen

In the command invocation "initrd=\Kernels\..." should really read "initrd=\Ramdisks\..." instead.

---
 Documentation/efi-stub.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
Documentation/efi-stub.txt +0 -0
index 7747024..e1ee764 100644

Documentation/efi-stub.txt fs0:> · line 72

Quoted 6 lines
Documentation/efi-stub.txt +1 -1
@@ -68,7 +68,7 @@ fs0:>
 to boot with the initrd-large.img file if the current working
 directory is fs0:\Kernels, the following command must be used,
 
-       fs0:\Kernels> bzImage.efi initrd=\Kernels\initrd-large.img
+       fs0:\Kernels> bzImage.efi initrd=\Ramdisks\initrd-large.img
 

I don't think this change is correct. From just above in efi-stub.txt:

For example, given the following directory layout,

fs0:>

        Kernels\
                        bzImage.efi
                        initrd-large.img

        Ramdisks\
                        initrd-small.img
                        initrd-medium.img

The file initrd-large.img is in the Kernels directory, and the point of this section
is to highlight that the path given to "initrd=" must be absolute.

Roy

Quoted 9 lines
Documentation/efi-stub.txt +0 -1
 Notice how bzImage.efi can be specified with a relative path. That's
 because the image we're executing is interpreted by the EFI shell,
--

2.4.3

--
To unsubscribe from this list: send the line "unsubscribe linux-efi" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html

A message that is not in the archive (sent off-list or not yet received): CAFECyb__gq0mYpTGH8sapQxLr89hKFTL8zvrixdfaYjGshVAVw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org

#4 lore raw
Quoted 38 lines · Roy Franz
Quoted 14 lines · Joonas Lahtinen

In the command invocation "initrd=\Kernels\..." should really read "initrd=\Ramdisks\..." instead.

---
 Documentation/efi-stub.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
Documentation/efi renamed from Documentation/efi-stub.txt +0 -1
-stub.txt

index 7747024..e1ee764 100644

Documentation/efi-stub.txt fs0:> · line 72

Quoted 6 lines
Documentation/efi-stub.txt +1 -1
@@ -68,7 +68,7 @@ fs0:>
 to boot with the initrd-large.img file if the current working
 directory is fs0:\Kernels, the following command must be used,
 
-       fs0:\Kernels> bzImage.efi initrd=\Kernels\initrd-large.img
+       fs0:\Kernels> bzImage.efi initrd=\Ramdisks\initrd-large.img
 

I don't think this change is correct. From just above in efi -stub.txt:

For example, given the following directory layout,

fs0:>

        Kernels\
                        bzImage.efi
                        initrd-large.img

        Ramdisks\
                        initrd-small.img
                        initrd-medium.img
Quoted 4 lines

The file initrd-large.img is in the Kernels directory, and the point of this section
is to highlight that the path given to "initrd=" must be absolute.

True so, I was skip reading it seems. Based on that, I'd consider the example somewhat misleading (Ramdisks directory only add some confusion).

Regards, Joonas

Quoted 15 lines

Roy

Quoted 11 lines
Documentation/efi-stub.txt +0 -0
 Notice how bzImage.efi can be specified with a relative path.

That's
because the image we're executing is interpreted by the EFI shell,
--
2.4.3

--
To unsubscribe from this list: send the line "unsubscribe linux -efi" in
the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html

Signature · 3 lines
Joonas Lahtinen
Open Source Technology Center
Intel Corporation