On Tue, 2007-06-12 at 11:09 -0700, Matthew Ahrens wrote:
> The 'altroot' field of 'zpool list' will be broken into two distinct
> properties. The first is 'temporary', which indicates that the pool is
> not persistent and should not be re-opened on reboot. In implementation
> terms, the pool is not kept in /etc/zfs/zpool.cache. The second
> property is 'altroot', which is prepended to the mountpoint of all
> datasets. The existing 'zpool create -R' and 'zpool import -R' will
> retain the same behavior, but correspond to setting both 'temporary=on'
> and 'alroot=<path>'. This separation is useful in clustering and other
> custom scenarios where more control is needed over the way pools are
> imported, without conflating the need for an alternate root. These
> properties can be set at create or import time but are otherwise
> readonly.
am I correct in assuming that this would permit full operation of ZFS
(in some "custom scenarios" -- clearly startup scripts would need a
workover) without ever needing /etc/zfs/zpool.cache to exist or be
writeable?
- Bill
