On 28/07/2016 13:34, Andriy Gapon wrote:
> Locally I have the following rc script to handle subordinate datasets of
> a boot environment: http://dpaste.com/0Q0JPGN.txt
> It is designed for exactly the scenario described above.
> The script is automatically enabled when zfs_enable is enabled.
>
>
Is this actually required? Instead of the extra steps, how about just
moving/creating each dataset into each BE (or at least the ones desired)
and setting them to mountpoint=inherit. With zfs_enable="YES" this should
mount the dataset appropriately. Only the root BE should need
canmount=noauto
On Thu, Jul 28, 2016 at 01:34:03PM +0300, Andriy Gapon wrote:
> Locally I have the following rc script to handle subordinate datasets of
> a boot environment: http://dpaste.com/0Q0JPGN.txt
> It is designed for exactly the scenario described above.
> The script is automatically enabled when
Andriy Gapon wrote on 07/28/2016 14:44:
I also would like to add, just in case, that I never set a BE's
mountpoint to '/'. I leave it at its default value like
/pond/ROOT/foobar. When the BE is active it would be mounted at /
anyway. And when it is not active and I want to access it for some
I also would like to add, just in case, that I never set a BE's
mountpoint to '/'. I leave it at its default value like
/pond/ROOT/foobar. When the BE is active it would be mounted at /
anyway. And when it is not active and I want to access it for some
modifications, etc, then I can mount it
On 28/07/2016 05:18, Allan Jude wrote:
> On 2016-07-27 22:05, Randy Westlund wrote:
>> I'm trying to follow Michael Dexter's post about using bhyve with boot
>> environments. It involves moving all child datasets under
>> zroot/ROOT/default, so that you can have entirely independent systems.
>>
On 2016-07-27 22:05, Randy Westlund wrote:
> I'm trying to follow Michael Dexter's post about using bhyve with boot
> environments. It involves moving all child datasets under
> zroot/ROOT/default, so that you can have entirely independent systems.
>
>
I'm trying to follow Michael Dexter's post about using bhyve with boot
environments. It involves moving all child datasets under
zroot/ROOT/default, so that you can have entirely independent systems.
http://callfortesting.org/bhyve-boot-environments/
> Let's change the datasets with "canmount
