Ubuntu 22.04 / Debian: Deprecate zsys

Ubuntu almost removed support for ZFS from the installer, and zsys is
on life support:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1966773
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1968150

I plan to rework the Ubuntu 22.04 instructions to be closer to those for
Debian Buster.  This will be straightforward, but I need to actually test
the resulting instructions before pushing that change.

Signed-off-by: Richard Laager <rlaager@wiktel.com>
This commit is contained in:
Richard Laager
2022-04-29 16:44:23 -05:00
parent d8e15645f6
commit 8105d010fe
3 changed files with 14 additions and 44 deletions

View File

@@ -425,8 +425,10 @@ Step 3: System Installation
On Solaris systems, the root filesystem is cloned and the suffix is
incremented for major system changes through ``pkg image-update`` or
``beadm``. Similar functionality has been implemented in Ubuntu 20.04 with
the ``zsys`` tool, though its dataset layout is more complicated. Even
``beadm``. Similar functionality was implemented in Ubuntu with the
``zsys`` tool, though its dataset layout is more complicated, and ``zsys``
`is on life support
<https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1968150>`__. Even
without such a tool, the `rpool/ROOT` and `bpool/BOOT` containers can still
be used for manually created clones. That said, this HOWTO assumes a single
filesystem for ``/boot`` for simplicity.

View File

@@ -435,8 +435,10 @@ Step 3: System Installation
On Solaris systems, the root filesystem is cloned and the suffix is
incremented for major system changes through ``pkg image-update`` or
``beadm``. Similar functionality has been implemented in Ubuntu 20.04 with
the ``zsys`` tool, though its dataset layout is more complicated. Even
``beadm``. Similar functionality was implemented in Ubuntu with the
``zsys`` tool, though its dataset layout is more complicated, and ``zsys``
`is on life support
<https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1968150>`__. Even
without such a tool, the `rpool/ROOT` and `bpool/BOOT` containers can still
be used for manually created clones. That said, this HOWTO assumes a single
filesystem for ``/boot`` for simplicity.