Actions
Feature #8129
closed
bootadm: add support for non-zfs boot entries in menu.lst
Start date:
2017-04-30
Due date:
% Done:
100%
Estimated time:
Difficulty:
Medium
Tags:
Gerrit CR:
External Bug:
Description
The loader support in bootadm was built keeping in mind the zfs based boot environments, each BE has two lines, title and bootfs line. To support other types of "boot environments", small update is needed. We would be specifically interested in supporting different type of entry for chainload support and different type of device:
tsoome@test:~$ bootadm list-menu the location for the active menu is: /rpool/boot/menu.lst Index Default Type Device Menu 0 - chain disk1: Disk1 1 - chain disk2: Disk2 2 - chain disk3: Disk3 3 - bootfs disk3s1a: Disk3_ufs 4 - bootfs rpool/ROOT/oi-431 oi-431 5 * bootfs rpool/ROOT/oi-432 oi-432
So, we should have the entry type column for menu listing; and we need to take account that the menu.lst entry may not have the corresponding entry in zfs dataset list. Note that with this change, we only address the menu listing, not creation/change.
Updated by Electric Monk almost 6 years ago
- Status changed from In Progress to Closed
- % Done changed from 90 to 100
git commit 760a3dc429d80e72277b67bec8135d2d185efe9a
commit 760a3dc429d80e72277b67bec8135d2d185efe9a
Author: Toomas Soome <tsoome@me.com>
Date: 2017-06-10T16:16:47.000Z
8129 bootadm: add support for non-zfs boot entries in menu.lst
8226 missing boot environments cause bootadm list-menu to segfault
Reviewed by: Yuri Pankov <yuripv@gmx.com>
Reviewed by: Hans Rosenfeld <rosenfeld@grumpf.hope-2000.org>
Reviewed by: John Howard <Echosoft.LLC@gmail.com>
Reviewed by: Andrew Stormont <andyjstormont@gmail.com>
Approved by: Richard Lowe <richlowe@richlowe.net>
Actions