diff options
| author | Thomas Petazzoni <thomas.petazzoni@free-electrons.com> | 2013-12-28 15:56:32 +0100 |
|---|---|---|
| committer | Thomas Petazzoni <thomas.petazzoni@free-electrons.com> | 2013-12-29 12:17:27 +0100 |
| commit | b49c231cab4db6c34ebcd546cdbd92bcd31db8c6 (patch) | |
| tree | 27e7db15e96e5fae96c4eee9ea5bd5d8e9ddbf77 /package/qt5/qt5script/qt5script.mk | |
| parent | f1fedbb246ae90bf30e4342202b11bc3030d9ca7 (diff) | |
| download | buildroot-b49c231cab4db6c34ebcd546cdbd92bcd31db8c6.tar.gz buildroot-b49c231cab4db6c34ebcd546cdbd92bcd31db8c6.zip | |
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 'package/qt5/qt5script/qt5script.mk')
0 files changed, 0 insertions, 0 deletions
