Mention potential issues with using 'rpool' and 'bpool' naming convention in a multi install system.

[DebianDoesDallas]

If you use the default naming convention of 'rpool' and 'bpool' for an installation that will be in a system with another install that uses 'rpool' and 'bpool', such as a system with a previous install created from having followed the root on ZFS docs. It can cause issues during booting. With one install conflicting with the other. Using a different name for the 'rpool' and 'bpool' during the install process avoids this issue.

My solution is to append something to the 'rpool' and 'bpool' name. Something like a number or the date. Might I suggest that the docs mention the potential issues of having two installs (on separate disks), in the same system? And furthermore, might I suggest setting a variable for the 'rpool' and 'bpool' names?

[gmelikov]

You may use guid in this case https://github.com/openzfs/zfs/pull/8052/files

Case with several OSes is rare, and usually you may even use one pool for many OSes (so, you need a separate parent dataset per OS, like rpool/ROOT/ubuntu_UUID in https://openzfs.github.io/openzfs-docs/Getting%20Started/Ubuntu/Ubuntu%2022.04%20Root%20on%20ZFS.html )

We may add a note about this case with basic description about ways to do so, maybe even common page for all distros. This case is by default for experienced users, so it should be ok (step-by-step guide may be excessive and it would be harder to maintain).