Sarah Jelinek wrote: > Hi Dave and All, > > Sorry for responding to my own email, but I was wrong about the > preservation of data and the feature being complete in the current code. >>>> >>> >>> If I didn't have a preservation capability, then what would I be able >>> to do with the VTOC management? >> >> The thinking was we would be let the user create vtoc slices for use >> in the rpool independent of what was currently on the disk. We >> originally thought that we didn't have support for getting slice data >> and maintaining state about preserving slice data in the supporting >> libraries. We do have this functionality though, so being able to >> preserve slice data should be doable and included in the vtoc management. >> > > We would need to make some changes to support an interactive installer. > Most specifically, we need to provide support for passing back of slice > data to the UI, and validating the user choices. So, it isn't free. We > can do basic management of vtoc slices now, that is simply allow the > user to create a vtoc slice without validation. We have to see if it > makes any sense to do this partial feature first, then add the > additional parts of the vtoc slice management. >
I wouldn't expect that to be acceptable - it's even less functional than the partition management we currently have on x86. Dave
