On Fri, Jul 15, 2005 at 11:55:24AM -0400, Ming Zhang wrote:
> On Fri, 2005-07-15 at 18:51 +0300, Pasi Kärkkäinen wrote:
> > > 1) VSS provide on INI
> > > 2) iet kernel code to do something
> > > 3) ietadm to do something
> > > 4) possible management daemon
> > >
> >
> > Hmm.. what do we need more in kernel?
> >
> list there then we can discuss. :)
>
> for example, iet might need to block the write request (shall we do this
> in IET or provider?)
>
Good point..
>
> > We possibly need more stuff in ietadm, but isn't the management
> > daemon
> yes, ietadm is the actual workhorse.
>
> > (light version allowing only the snapshot control) required to be
> > able
> > to do VSS provider?
> vss provider need part code at INI side in windows.
>
Yes, of course. VSS provider needs to talk to ietadm, and to linux lvm, so
the natural way would be to use xmlrpc interface from the windows plugin to
connect to management daemon?
- Pasi
>
> >
> > - Pasi
> >
>
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id492&op=click
|
