From 8bd2a2866ccc3f606566ce5503b32053948513ab Mon Sep 17 00:00:00 2001 From: Gregor Kopka Date: Wed, 9 Jan 2019 01:15:30 +0100 Subject: Removed suggestion to use root dataset as bootfs The dracut howto proposed to boot from the root dataset of a pool. Apart from this giving problems when booting (as the code seems to expect a child dataset and creates an illegal dataset name when using the root dataset) the technical limitations of the root dataset (among others the inability to rename or destroy through the `zfs` command) resulted in the general consensus to only use it as a container for the datasets in the pool - not as a filesystem itself. Removed the idea to boot from the root dataset. Reviewed-by: George Melikov Reviewed-by: Brian Behlendorf Reviewed-by: bunder2015 Signed-off-by: Gregor Kopka Closes #8247 --- contrib/dracut/README.dracut.markdown | 6 ------ 1 file changed, 6 deletions(-) diff --git a/contrib/dracut/README.dracut.markdown b/contrib/dracut/README.dracut.markdown index 46d032f70..b5fb288a1 100644 --- a/contrib/dracut/README.dracut.markdown +++ b/contrib/dracut/README.dracut.markdown @@ -11,12 +11,6 @@ the dataset mountpoint property to '/'. $ zpool set bootfs=pool/dataset pool $ zfs set mountpoint=/ pool/dataset -It is also possible to set the bootfs property for an entire pool, just in -case you are not using a dedicated dataset for '/'. - - $ zpool set bootfs=pool pool - $ zfs set mountpoint=/ pool - Alternately, legacy mountpoints can be used by setting the 'root=' option on the kernel line of your grub.conf/menu.lst configuration file. Then set the dataset mountpoint property to 'legacy'. -- cgit v1.2.3