Moinak Ghosh wrote: > Sundar Yamunachari wrote: >> [...] >> What is the interaction between TI module and transfer module? does the >> transfer module expects a mounted directory? Where does this information >> come from? >> > > For the Transfer Module the requirement is that TI module > should create the pool but leave it unmounted. Also there > is the question of pool/dataset naming. The names should > passed on to the Transfer Module in some way or decide on > standardized names. In addition the Transfer Module will > require to know the device name for the Solaris fdisk partition > because of the need to perform an installgrub at the end. > > The Transfer module will import the pool on an alternate > root and perform the necessary operations. I will post a > specifications document for the Transfer Module shortly. >
Actually, I'd think getting the pool mounted into an appropriate area is something that will ultimately be handled by the BE management function that Ethan posted some initial notes about back on Sept. 7. In the short term (i.e. for the October preview) it might be handled elsewhere, but I'd think the transfer module could then confine itself to moving the bits from the media or repository to a pre-mounted file system hierarchy. Dave
