aboutsummaryrefslogtreecommitdiff
path: root/fs
diff options
context:
space:
mode:
authorGravatar Thomas Petazzoni <thomas.petazzoni@free-electrons.com>2013-12-28 15:56:32 +0100
committerGravatar Thomas Petazzoni <thomas.petazzoni@free-electrons.com>2013-12-29 12:17:27 +0100
commitb49c231cab4db6c34ebcd546cdbd92bcd31db8c6 (patch)
tree27e7db15e96e5fae96c4eee9ea5bd5d8e9ddbf77 /fs
parentf1fedbb246ae90bf30e4342202b11bc3030d9ca7 (diff)
downloadbuildroot-b49c231cab4db6c34ebcd546cdbd92bcd31db8c6.tar.gz
buildroot-b49c231cab4db6c34ebcd546cdbd92bcd31db8c6.tar.bz2
fs/iso9660: put the Buildroot boot entry first in Grub menu.lst
The ISO9660-specific Grub menu.lst contains two entries: one entry to chainload the bootloader available in the first hard drive, and another entry to boot the Buildroot system. However, it defaults to booting the first entry, i.e chainloading what's on the first hard drive. For a Buildroot generated system, this is quite odd: we're not even booting the system built by Buildroot. So, switch the two entries, and put the Buildroot boot entry first. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Diffstat (limited to 'fs')
-rw-r--r--fs/iso9660/menu.lst8
1 files changed, 4 insertions, 4 deletions
diff --git a/fs/iso9660/menu.lst b/fs/iso9660/menu.lst
index d78caebe15..ed7836a434 100644
--- a/fs/iso9660/menu.lst
+++ b/fs/iso9660/menu.lst
@@ -2,10 +2,10 @@ default 0
timeout 10
color cyan/blue white/blue
+title Buildroot ISO9660 image
+kernel /kernel
+initrd /initrd
+
title Hard Drive (first partition)
rootnoverify (hd0)
chainloader +1
-
-title BuildRoot ISO9660 image
-kernel /kernel
-initrd /initrd