Dave Miner wrote: > Jean McCormack wrote: >> Great. Here's what I'm working doing. >> >> The user specifies the "boot_area" in the manifest. Let's say it's >> rpool/dc-builds. >> >> We create pkg_image and bootroot as zfs dataset/mountpoints >> underneath it. >> Also we create logs, media, and tmp as just plain old directories >> under it. They >> don't need to be datasets and it could cause loss of info they want >> like an old logfile >> if they rollback. So I'm not doing that. >> > > That would seemingly only be a concern if snapshots were taken of > those datasets, and would still be a concern with this design if you > actually snapshot the top-level dataset (which I'm not clear on), so I > guess I don't see how this is a reason not to make them datasets. By > making them datasets, you would provide for independent rollback of > each of them if desired, as well as all the other goodness that > separate datasets allow, which is not possible in the scheme you're > suggesting. > > Dave True. It's not a major change and easily made. And I'm not snapshotting the top level.
Jean
