** Also affects: ubuntu-budgie-meta (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ubuntu-budgie-meta (Ubuntu)
Assignee: (unassigned) => fossfreedom (fossfreedom)
** Changed in: ubuntu-budgie-meta (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1843768
Title:
[FFe] Ubiquity with zfs install option
Status in ubiquity package in Ubuntu:
New
Status in ubuntu-budgie-meta package in Ubuntu:
New
Status in ubuntu-mate-meta package in Ubuntu:
Fix Released
Status in ubuntu-meta package in Ubuntu:
Fix Released
Bug description:
Part of the 19.10 feature announcement is zfs experimental support in
the installer (https://ubuntu.com/blog/enhancing-our-zfs-support-on-
ubuntu-19-10-an-introduction). We modified ubiquity to present an
“EXPERIMENTAL” (with warning) ZSYS install option. This option is only
visible is zfsutils-linux is installed on the system. So, it won't be
available for derivatives that use ubiquity but do not seed zfsutils-
linux.
Update as of 20/09/2019: the plan is to not seed zsys (security review
will take a while), but to only seed zfsutils-linux. People can then
opt-in to zsys which should be available by default next cycle.
This option takes an entire disk and have a fix set of dataset
installed. There is no support but we need this to make an official
install option for the next LTS.
The patch has been created to be as minimal as possible. Partman does
a full disk partitioning, and then the script zsys-setup the first
non-ESP partition and replaces with zfs pools.
4 partitions are created:
1. if GPT partitioning: ESP partition. This one is done by partman directly.
2. bpool (for boot), pool with older zfs compatible version to be readable by
grub)
3. rpool (for / and userdataset)
4. /boot/grub (ext4) to contain a single grub (NOTE: this could be later on
moved to the ESP)
Additionaly if a swap file has been created by ubiquity, it is
recreated as a ZFS volume. If the script fails to execute, the final
installation is an ext4 installation on entire disk.
Note that the implementation is slightly different from the
specification due to a difficult cohabitation with partman in the
custom partitioning page.
Please find attached the MP on ubiquity as well as the package build
log.
https://launchpadlibrarian.net/442036321/buildlog_ubuntu-eoan-
amd64.ubiquity_19.10.10~ppa1_BUILDING.txt.gz
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1843768/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
