On Wed, Oct 26, 2005 at 07:25:38PM +0200, Marco Amadori wrote:
[...]
> Yes, we need only to scan for plugins if we like.
we do! :) (aw, well at least I do)
> The list of all plugins needed is given by, in shell terms and with my system
> examples:
>
> # evms_query volumes | xargs -i evms_query plugins \{\} | uniq
> Ext2/3
> XFS
> SWAPFS
> # evms_query regions | xargs -i evms_query plugins \{\} | uniq
> LVM2
> MDRaid1RegMgr
> MDRaid5RegMgr
> # evms_query disks| xargs -i evms_query plugins \{\} | uniq
> LocalDskMgr
nice, I'm starting to get it right. So having a look at [1] do you think
it would be possible to flat down this structure ending with a list of
volumes each of which having an array of disks and an array of plugins?
Could you provide the full output of 'evms_query {volumes,regions,disks}'
and for each volume also 'evms_query info <volume>'?
(my current setup is so trivial that I'd like to gather some info)
[1]: http://evms.sourceforge.net/architecture/evms-data-example.png
> So we need to do the equivalent of calling evms_query plugins for each
> volume,
> region and disk, the we need a link to lib name; I think that for the time
> being a simple 2 colum structure with (name of the plugin | name of the
> library) would be enough to have evms working, but also it could be not
> future proof.
I think a simple lookup table will suffice at the moment.
--
mattia
:wq!
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
