loader: zfs boot should check for provided fstype
The loader default behavior is to check for currently used file system and if it is zfs, the loader will set the zfs-bootfs and other needed properties, which is all nice.
However, if there is an setup where it is desired to keep running on boot archive based ramdisk, we would need an mechanism to tell loader not to set up zfs specific properties for us; the logical way for this would be that fstype property will be set to something else - like ufs, and if fstype is set and is not zfs, the loader would skip setting zfs properties.
Updated by Toomas Soome over 6 years ago
- Tracker changed from Bug to Feature
Updated by Electric Monk about 6 years ago
- Status changed from In Progress to Closed
- % Done changed from 90 to 100
git commit 6fec69aa7d808587436432f75023de288451324f
commit 6fec69aa7d808587436432f75023de288451324f Author: Toomas Soome <email@example.com> Date: 2017-03-02T14:09:15.000Z 7788 loader: zfs boot should check for provided fstype Reviewed by: Robert Mustacchi <firstname.lastname@example.org> Reviewed by: Paul Dagnelie <email@example.com> Reviewed by: Yuri Pankov <firstname.lastname@example.org> Approved by: Hans Rosenfeld <email@example.com>