diff options
| author | Daniel Fullmer <danielrf12@gmail.com> | 2020-04-23 14:47:56 -0400 |
|---|---|---|
| committer | Lennart Poettering <lennart@poettering.net> | 2020-05-26 19:27:59 +0200 |
| commit | e6190e2882e1d6772a9e586fcc65c91d406e52fb (patch) | |
| tree | 61ad6838c5926fbe5324ca310b826cde8d3ac13e /docs/AUTOMATIC_BOOT_ASSESSMENT.md | |
| parent | 2d2d75047ed885d318abc190cc47086627c7f9cc (diff) | |
| download | systemd-e6190e2882e1d6772a9e586fcc65c91d406e52fb.tar.gz | |
sd-boot: fix menu ordering with boot counting
systemd-boot selects the last valid entry by default, not the first.
Fixes: #15256
Diffstat (limited to 'docs/AUTOMATIC_BOOT_ASSESSMENT.md')
| -rw-r--r-- | docs/AUTOMATIC_BOOT_ASSESSMENT.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/AUTOMATIC_BOOT_ASSESSMENT.md b/docs/AUTOMATIC_BOOT_ASSESSMENT.md index aff203b590..83ddf28fdd 100644 --- a/docs/AUTOMATIC_BOOT_ASSESSMENT.md +++ b/docs/AUTOMATIC_BOOT_ASSESSMENT.md @@ -101,9 +101,9 @@ Here's an example walkthrough of how this all fits together. 6. If this boot also fails, on the next boot the boot loader will see the tag `+0-3`, i.e. the counter reached zero. At this point the entry will be - considered "bad", and ordered to the end of the list of entries. The next - newest boot entry is now tried, i.e. the system automatically reverted back - to an earlier version. + considered "bad", and ordered to the beginning of the list of entries. The + next newest boot entry is now tried, i.e. the system automatically reverted + back to an earlier version. The above describes the walkthrough when the selected boot entry continuously fails. Let's have a look at an alternative ending to this walkthrough. In this |