You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now, an sdbootutil managed system has an initial boot menu entry of os-release "PRETTY_NAME" and for each snapshot gets new boot menu entries mentioning os-release versions, snapshots, and kernel versions
I think the verbosity of the boot entries for each snapshot is AWESOME and love it
But, it does mean that initial entry can be confusing for first time users
They see the menu and think "I don't want openSUSE Aeon $DATE $SNAPSHOT $KERNEL... I want openSUSE Aeon" and then they incorrectly pick the simpliest boot menu entry and boot into an ancient snapshot
(This includes me...I made this mistake...)
I think it would be AWESOME if the first boot menu entry had a name like "$PRETTY_NAME (Initial Installation)" or "$PRETTY_NAME (Factory Reset)" or something similar to make it clear that it's the first snapshot, not the simplest snapshot to select
The text was updated successfully, but these errors were encountered:
Right now, an sdbootutil managed system has an initial boot menu entry of os-release "PRETTY_NAME" and for each snapshot gets new boot menu entries mentioning os-release versions, snapshots, and kernel versions
I think the verbosity of the boot entries for each snapshot is AWESOME and love it
But, it does mean that initial entry can be confusing for first time users
They see the menu and think "I don't want openSUSE Aeon $DATE $SNAPSHOT $KERNEL... I want openSUSE Aeon" and then they incorrectly pick the simpliest boot menu entry and boot into an ancient snapshot
(This includes me...I made this mistake...)
I think it would be AWESOME if the first boot menu entry had a name like "$PRETTY_NAME (Initial Installation)" or "$PRETTY_NAME (Factory Reset)" or something similar to make it clear that it's the first snapshot, not the simplest snapshot to select
The text was updated successfully, but these errors were encountered: