#1 The documentation needs improvements
{ I am professional developer and unix/linux
administrator. A few months ago I started using LVM,
recently I noticed EVMS and took a look at it. }
In my experience, EVMS really lacks good 'entry-level'
documentation. I can compare my feelings after reading
LVM and EVMS HOWTO's
After reading LVM HOWTO I clearly
understood what the software does, why should I use it
and what should I do to start (and what do terms like
volume group, physical volume, logical volume mean).
Finally I installed LVM fairly quickly and so far I
use it without particular problems.
After reading EVMS HOWTO I feel completely lost. Huge
amount of unclear terminology (there is chapter for
terminology but it only adds more confusion), no clear
description what is the software''s purpose, no usage
scenarios, no ''how tostart'' descirption (I mean
starting the real usage, not compilation which is
described).
The most important things absent in EVMS docs are
chapters similar to chapters 5 (Anatomy of LVM) and
10-20 (descriptions of different common tasks) of the
LVM FAQ (http://www.sistina.com/lvm_howtos/lvm_howto/).
And the most important problem with EVMS doc is that it
concentrates on describing simple tasks like how to
create segment without describing the whole picture
(when and why should I create the segment).
Logged In: NO
On a related note, the documentation spends so much time
talking about backwards compatibility that it is hard to
figure out what the best recommended practice is when you
don't care about compatibility with OS/2, AIX, Linux LVM and
md, etc.
md support seems essential for software RAID, regardless of
compatibility concerns so it should be described as the evms
software RAID implementation, not merely for backwards
compatibility. Beyond that, what are the best approaches to
volume managment features? DriveLinking vs. LVM logical
volumes. More discussion along these lines would be helpful.
Logged In: NO
On a related note, the documentation spends so much time
talking about backwards compatibility that it is hard to
figure out what the best recommended practice is when you
don't care about compatibility with OS/2, AIX, Linux LVM and
md, etc.
md support seems essential for software RAID, regardless of
compatibility concerns so it should be described as the evms
software RAID implementation, not merely for backwards
compatibility. Beyond that, what are the best approaches to
volume managment features? DriveLinking vs. LVM logical
volumes. More discussion along these lines would be helpful.
Logged In: YES
user_id=73079
New docs are in the works.